AudioCodes Mediant 2000 User Manual page 501

Voip media gateway sip protocol
Hide thumbs Also See for Mediant 2000:
Table of Contents

Advertisement

SIP User's Manual
Parameter
Web: Remote RTP Base UDP Port
EMS: Remote Base UDP Port
[RemoteBaseUDPPort]
EMS: No Op Enable
[NoOpEnable]
EMS: No Op Interval
[NoOpInterval]
EMS: No Op Payload Type
[RTPNoOpPayloadType]
Version 6.4
A. Configuration Parameters Reference
The UDP ports are allocated randomly to channels.
You can define a UDP port range per Media Realm (see
Configuring Media Realms on page 159).
If RTP Base UDP Port is not a factor of 10, the following
message is generated: 'invalid local RTP port'.
For more information on the default RTP/RTCP/T.38 port
allocation, refer to the Product Reference Manual.
Defines the lower boundary of UDP ports used for RTP,
RTCP and T.38 by a remote device. If this parameter is set
to a non-zero value, ThroughPacket™ (RTP multiplexing) is
enabled. The device uses this parameter (and
BaseUDPPort) to identify and distribute the payloads from
the received multiplexed IP packet to the relevant channels.
The valid range is the range of possible UDP ports: 6,000 to
64,000.
The default value is 0 (i.e., RTP multiplexing is disabled).
Notes:
The value of this parameter on the local device must
equal the value of BaseUDPPort on the remote device.
When VLANs are implemented, RTP multiplexing is not
supported.
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 148.
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.
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.
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.
501
Description
November 2011

Advertisement

Table of Contents
loading

Table of Contents