Version 6.4 637 March 2012
SIP User's Manual A. Configuration Parameters Reference
Parameter Description
This parameter can also be configured per IP Profile, using the
IPProfile parameter.
For more information on RTP multiplexing, see RTP
Multiplexing (ThroughPacket) on page 157.
Web: RTP Multiplexing Local
UDP Port
[L1L1ComplexTxUDPPort]
Defines the local (source) UDP port for outgoing multiplexed RTP
packets, for RTP multiplexing.
The valid value is the range of possible UDP ports: 6,000 to
64,000. The default value is 0 (i.e., RTP multiplexing is disabled).
Note: For this parameter to take effect, a device reset is required.
Web: RTP Multiplexing Remote
UDP Port
[L1L1ComplexRxUDPPort]
Defines the remote UDP port to where the multiplexed RTP
packets are sent and the local UDP port for incoming multiplexed
RTP packets, for RTP multiplexing.
The valid value is the range of possible UDP ports: 6,000 to
64,000. The default value is 0 (i.e., RTP multiplexing is disabled).
Notes:
For this parameter to take effect, a device reset is required.
All devices that participate in the same RTP multiplexing
session must use this same port.
EMS: No Op Enable
[NoOpEnable]
Enables the transmission of RTP or T.38 No-Op packets.
[0] = Disable (default)
[1] = Enable
This mechanism ensures that the NAT binding remains open
during RTP or T.38 silence periods.
EMS: No Op Interval
[NoOpInterval]
Defines the time interval in which RTP or T.38 No-Op packets are
sent in the case of silence (no RTP/T.38 traffic) when No-Op
packet transmission is enabled.
The valid range is 20 to 65,000 msec. The default is 10,000.
Note: To enable No-Op packet transmission, use the
NoOpEnable parameter.
EMS: No Op Payload Type
[RTPNoOpPayloadType]
Defines the payload type of No-Op packets.
The valid range is 96 to 127 (for the range of Dynamic RTP
Payload Type for all types of non hard-coded RTP Payload types,
refer to RFC 3551). The default value is 120.
Note: When defining this parameter, ensure that it doesn't cause
collision with other payload types.
[RTCPActivationMode]
Disables RTCP traffic when there is no RTP traffic. This feature is
useful, for example, to stop RTCP traffic that is typically sent
when calls are put on hold (by an INVITE with 'a=inactive' in the
SDP).
[0] Active Always = RTCP is active even during inactive RTP
periods, i.e., when the media is in 'recvonly' or 'inactive' mode.
(default)
[1] Inactive Only If RTP Inactive = No RTCP is sent when RTP
is inactive.
RTP Control Protocol Extended Reports (RTCP XR) Parameters
(Note: For a detailed description of RTCP XR reports, refer to the Product Reference Manual.)
Web: Enable RTCP XR
Enables voice quality monitoring and RTCP Extended Reports
(RTCP XR), according to Internet-Draft draft-ietf-sipping-rtcp-
To Next Page
Loading...
