![background image](http://html1.mh-extra.com/html/3com/v6100/v6100_user-manual-manual_3139483267.webp)
V6100 and V7122 User Guide
267
RTP NO-OP
This feature complies with the IETF’s draft-wing-avt-rtp-noop-03.txt titled ‘A No-Op Payload
Format for RTP’.
The IETF document defines a no-op payload format for RTP. This can be used to verify RTP
connectivity and to keep NAT bindings and Firewall pinholes open. The draft defines the
RTP payload as dynamic. 3Com’ default payload type is 120.
Users can control activation of the RTP No-Op Packets by setting the parameter
RTPNoOpEnable.
Receipt of No-Op is always supported.
If RTP No-Op packet transmission is activated, users can control the time interval in
which the No_Op packets are sent in the case of silence (no RTP traffic). This is
performed using parameter RTPNoOpInterval.
Users can control the payload type with which the No_Op packets are sent. This is
performed using parameter RTPNoOpPayloadType
.
Point-to-Point Protocol over Ethernet (PPPoE)
PPPoE is a method of sending the Point-to-Point Protocol over Ethernet network.
Point-to-Point Protocol (PPP) Overview
Point-to-Point Protocol (PPP) provides a method of transmitting data over serial point-to-
point links. The protocol defines establishing, configuring and testing the data link connection
and the network protocol.
The PPP standard describes a state machine used to establish a valid connection between
two hosts over a serial connection. There are three major stages described, helping to
establish a network layer (such as an IP) connection over the point-to-point link: LCP (Link
Configuration Protocol) Authentication and NCP (Network Control Protocol). Once the
network protocol is configured, the two hosts can communicate, sending network layer
protocol (such as IP) over the PPP connection (a small PPP header is added at the
beginning of each packet).
At the initial phase, the hosts use LCP (link configuration protocol) to negotiate for link
characteristic and parameters. Packets sent in this phase have two octets of ‘PPP header’
followed by LCP message with variable length. Various parameters and options are
negotiable at this phase, including MRU (maximum receive unit), Authentication Protocol,
and others.
Summary of Contents for V6100
Page 28: ...28 V6100 and V7122 User Guide Reader s Notes...
Page 48: ...48 V6100 and V7122 User Guide Reader s Notes...
Page 72: ...72 V6100 and V7122 User Guide Reader s Notes...
Page 80: ...80 V6100 and V7122 User Guide Reader s Notes...
Page 152: ...152 V6100 and V7122 User Guide Reader s Notes...
Page 262: ...262 V6100 and V7122 User Guide Reader s Notes...
Page 284: ...284 V6100 and V7122 User Guide Reader s Notes...
Page 291: ...V6100 and V7122 User Guide 291 Figure 95 V7122 Startup Process...
Page 324: ...324 V6100 and V7122 User Guide Reader s Notes...
Page 354: ...354 V6100 and V7122 User Guide Reader s Notes...
Page 374: ...374 V6100 and V7122 User Guide Reader s Notes...
Page 382: ...382 V6100 and V7122 User Guide Figure 130 Example of a User Information File Reader s Notes...
Page 392: ...392 V6100 and V7122 User Guide Reader s Notes...
Page 409: ...V6100 and V7122 User Guide 409 Reader s Notes...
Page 413: ...V6100 and V7122 User Guide 413 Reader s Notes...
Page 425: ...V6100 and V7122 User Guide 425 Figure 145 UDP2File Utility Reader s Notes...
Page 431: ...V6100 and V7122 User Guide 431 Reader s Notes...
Page 447: ...V6100 and V7122 User Guide 447 Reader s Notes...
Page 483: ...V6100 and V7122 User Guide 483 Reader s Notes...