AudioCodes Mediant 800B - Page 442

User's Manual 442 Document #: LTRT-10632
Mediant 800B Gateway & E-SBC
Parameter Description
Remote Early Media
sbc-rmt-early-media-supp
[IpProfile_SBCRemoteEarly
MediaSupport]
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.
Remote Multiple 18x
sbc-rmt-mltple-18x-supp
[IpProfile_SBCRemoteMultip
le18xSupport]
Defines whether multiple 18x responses including 180 Ringing, 181
Call is Being Forwarded, 182 Call Queued, and 183 Session Progress
are forwarded to the caller, for the SIP entity associated with the IP
Profile.
 [0] Not Supported = Only the first 18x response is forwarded to the
caller.
 [1] Supported = (Default) Multiple 18x responses are forwarded to
the caller.
Remote Early Media
Response Type
sbc-rmt-early-media-resp
[IpProfile_SBCRemoteEarly
MediaResponseType]
Defines the SIP provisional response type - 180 or 183 -
for forwarding
early media to the caller, for the SIP entity associated with the IP
Profile.
 [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.
Remote Multiple Early
Dialogs
sbc-multi-early-diag
[IpProfile_SBCRemoteMultip
leEarlyDialogs]
Defines the device's handling of To-header tags in call forking
responses (i.e., multiple SDP answers) sent to the SIP entity
associated with the IP Profile. When the SIP entity initiates an INVITE
that is subsequently forked (for example, by a proxy server) to multiple
endpoints, the endpoints respond with a SIP 183 containing an SDP
answer. Typically, each endpoint's response has a different To-header
tag. For example, a call initiated by the SIP entity (100@A) is forked
and two endpoints respond with ringing, each with a different tag:
 Endpoint "tag 2":
SIP/2.0 180 Ringing
From: <sip:100@A>;tag=tag1
To: sip:200@B;tag=tag2
Call-ID: c2
 Endpoint "tag 3":
SIP/2.0 180 Ringing
From: <sip:100@A>;tag=tag1
To: sip:200@B;tag=tag3
Call-ID: c2
In non-standard behavior (when the parameter is configured to
Disable), the device forwards all the SDP answers with the same tag.
In the example, endpoint "tag 3" is sent with the same tag as endpoint
"tag 2" (i.e., To: sip:200@B;tag=tag2).
 [-1] According to Operation Mode = (Default) Depends on the
setting of the 'Operation Mode' parameter in the IP Group or SRDs
table:

B2BUA: Device operates as if the parameter is set to Disable
[0].

Call State-full Proxy: Device operates as if the parameter is set
to Enable [1]. In addition, the device preserves the From tags
and Call-IDs of the endpoints in the SDP answer sent to the
SIP entity.
 [0] Disable = Device sends the multiple SDP answers with the