AudioCodes Mediant 2600 - Page 310

User's Manual 310 Document #: LTRT-42060
Mediant 2600 E-SBC
Parameter Description
Web: Remote Early Media
Response Type
CLI: sbc-rmt-early-media-resp
[IpProfile_SBCRemoteEarlyMed
iaResponseType]
Defines the SIP provisional response type - 180 or 183 - for
forwarding early media to the caller, for this SIP entity.
 [0] Transparent = (Default) All early media response types are
supported; the device forwards all responses as is (unchanged).
 [1] 180 = Early media is sent as 180 response only.
 [2] 183 = Early media is sent as 183 response only.
Web: Remote Early Media
CLI: sbc-rmt-early-media-supp
[IpProfile_SBCRemoteEarlyMed
iaSupport]
Defines whether the remote side can accept early media or not.
 [0] Not Supported = Early media is not supported.
 [1] Supported = (Default) Early media is supported.
Web: Enforce MKI Size
CLI: sbc-enforce-mki-size
[IpProfile_SBCEnforceMKISize]
Enables MKI length negotiation for SRTP-to-SRTP flows between
SIP networks (i.e., IP Groups). This includes the capability of
modifying the MKI length on the inbound or outbound SBC call leg
for this SIP entity.
 [0] Don't enforce = (Default) Device forwards the MKI size as is.
 [1] Enforce = Device changes the MKI length according to the
settings of the IP Profile parameter, MKISize.
Web: Remote Early Media RTP
Behavior
CLI: sbc-rmt-early-media-rtp
[IpProfile_SBCRemoteEarlyMed
iaRTP]
Defines whether the destination UA sends RTP immediately after it
sends 18x response.
 [0] Immediate = (Default) Remote client sends RTP immediately
after it sends 18x response with early media. Device forwards
18x and RTP as is.
 [1] Delayed = After sending 18x response, the remote client
waits before sending RTP (e.g., Microsoft Lync environment).
For the device's handling of this remote UA support, see
Interworking SIP Early Media on page 341.
Web: Remote RFC 3960
Gateway Model Support
CLI: sbc-rmt-rfc3960-supp
[IpProfile_SBCRemoteSupports
RFC3960]
Defines whether the destination UA is capable of receiving 18x
messages with delayed RTP.
 [0] Not Supported = (Default) UA does not support receipt of
18x messages with delayed RTP. For the device's handling of
this remote UA support, see Interworking SIP Early Media on
page 341.
 [1] Supported = UA is capable of receiving 18x messages with
delayed RTP.
Web: Remote Can Play
Ringback
CLI: sbc-rmt-can-play-ringback
[IpProfile_SBCRemoteCanPlay
Ringback]
Defines whether the destination UA can play a local ringback tone.
 [0] No = UA does not support local ringback tone. The device
sends 18x with delayed SDP to the UA.
 [1] Yes = (Default) UA supports local ringback tone. For the
device's handling of this remote UA support, see Interworking
SIP Early Media on page 341.
Web: RFC 2833 DTMF Payload
Type
CLI: sbc-2833dtmf-payload
[IpProfile_SBC2833DTMFPaylo
adType]
Defines the payload type of DTMF digits for this SIP entity. 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).