AudioCodes Mediant 500 MSBR, User Manual

Page: 413 / 1248

Version 7.2 413 Mediant 500 MSBR
User's Manual 23. Coders and Profiles
Parameter Description
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 on page
638.
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 DTMF Payload Type
sbc-2833dtmf-payload
[IpProfile_SBC2833DTMFPayloa
dType]
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).
Send Multiple DTMF Methods
sbc-send-multiple-dtmf-
methods
[IPProfile_SBCSupportMultipleD
TMFMethods]
Enables the <device> to send DTMF digits out-of-band (not with
audio stream) using both the SIP INFO and RFC 2833 methods
for the same call on the leg to which this IP Profile is associated.
The RFC 2833 method sends out-of-band DTMF digits using the
RTP protocol while the SIP INFO method sends the digits using
the SIP protocol.

[0] Disable = (Default) The device sends DTMF digits using
only one method (either SIP INFO, RFC 2833, or in-band).

[1] Enable = The device sends DTMF digits using both
methods - SIP INFO and RFC 2833.
If you have enabled the parameter, you can also configure the
<device> to stop sending DTMF digits using the SIP INFO
method if the <device> receives a SIP re-INVITE (or UPDATE)
from the SIP entity to where the SIP INFO is being sent (and
keep sending the DTMF digits using the RFC 2833 method).
This is done using AudioCodes proprietary SIP header X-AC-
Action and a Message Manipulation rule (inbound) to instruct the
<device> to switch to a different IP Profile that is configured to
disable the sending of DTMF digits using both methods (i.e.,
'Send Multiple DTMF Methods' is configured to
Disable ):
X-AC-Action: 'switch-profile;profile-name=<IP Profile Name>'
If the IP Profile name contains one or more spaces, you must
enclose the name in double quotation marks, for example:
X-AC-Action: 'switch-profile;profile-name="My IP Profile"'
The Message Manipulation rule adds the proprietary header with
the value of the new IP Profile to the incoming re-INVITE or
UPDATE message and as a result, the device uses the new IP
Profile for the SIP entity and stops sending it SIP INFO
messages. You can also configure an additional Message