AudioCodes E-SBC

CHAPTER19 Coders and Profiles
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
'Direct Media Tag'
sbc-dm-tag
[IPProfile_SBCDirectMediaTag]
Defines an identification tag for enabling direct media (no
Media Anchoring) for the SIP entity associated with the IP
Profile. Direct media occurs between all endpoints whose
IP Profiles have the same tag value (non-empty value). For
example, if you set the parameter to "direct-rtp" for two IP
Profiles "IP-PBX-1" and "IP-PBX-2", the device employs
direct media for calls amongst endpoints associated with
IP Profile "IP-PBX-1", for calls amongst endpoints
associated with IP Profile "IP-PBX-2", and for calls
between endpoints associated with IP Profile "IP-PBX-1"
and IP Profile "IP-PBX-2".
The valid value is a string of up to 16 characters. By
default, no value is defined.
For more information on direct media, see Direct Media.
Note: If you enable direct media for the IP Profile, make
sure that your Media Realm provides sufficient ports, as
media may traverse the device for mid-call services (e.g.,
call transfer).
'RFC 2833 Mode'
sbc-rfc2833-behavior
[IpProfile_
SBCRFC2833Behavior]
Defines the handling of RFC 2833 SDP offer-answer
negotiation for the SIP entity associated with the IP Profile.
■ [0] As is = (Default) The device does not intervene in
the RFC 2833 negotiation.
■ [1] Extend = Each outgoing offer-answer includes RFC
2833 in the offered SDP. The device adds RFC 2833
only if the incoming offer does not include RFC 2833.
■ [2] Disallow = The device removes RFC 2833 from the
incoming offer.
Note: If the device interworks between different DTMF
methods and one of the methods is in-band DTMF packets
(in RTP), detection and generation of DTMF methods
requires DSP resources. However, RFC 2833 to SIP INFO
does not require DSP resources.
'RFC 2833 DTMF Payload
Type'
sbc-2833dtmf-payload
[IpProfile_
SBC2833DTMFPayloadType]
Defines the payload type of DTMF digits for the SIP entity
associated with the IP Profile. This enables the
interworking of the DTMF payload type for RFC 2833
between different SBC call legs. For example, if two
entities require different DTMF payload types, the SDP
offer received by the device from one entity is forwarded to
the destination entity with its payload type replaced with
the configured payload type, and vice versa.
The value range is 0 to 200. The default is 0 (i.e., the device
forwards the received payload type as is).
- 406 -