AudioCodes Mediant 500L User Manual page 444

Enterprise session border controller (e-sbc) & media gateway
Hide thumbs Also See for Mediant 500L:
Table of Contents

Advertisement

Parameter
Remote Multiple Answers
Mode
sbc-multi-answers
[IpProfile_SBCRemoteMultip
leAnswersMode]
Remote Early Media RTP
Detection Mode
sbc-rmt-early-media-rtp
[IpProfile_SBCRemoteEarly
MediaRTP]
Remote RFC 3960 Support
sbc-rmt-rfc3960-supp
[IpProfile_SBCRemoteSupp
ortsRFC3960]
User's Manual
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
same To-header tag, to the SIP entity. In other words, this option
is relevant if the SIP entity does not support multiple dialogs (and
multiple tags). However, non-standard, multiple answer support
may still be configured by the SBCRemoteMultipleAnswersMode
parameter.
[1] Enable = Device sends the multiple SDP answers with different
To-header tags, to the SIP entity. In other words, the SIP entity
supports standard multiple SDP answers (with different To-header
tags). In this case, the SBCRemoteMultipleAnswersMode
parameter is ignored.
Note: If the parameter and the SBCRemoteMultipleAnswersMode
parameter are disabled, multiple SDP answers are not reflected to the
SIP entity (i.e., the device sends the same SDP answer in multiple
18x and 200 responses).
Enables interworking multiple SDP answers within the same SIP
dialog (non-standard). The parameter enables the device to forward
multiple answers to the SIP entity associated with the IP Profile. The
parameter is applicable only when the
IpProfile_SBCRemoteMultipleEarlyDialogs parameter is disabled.
[0] Disable = (Default) Device always sends the same SDP
answer, which is based on the first received answer that it sent to
the SIP entity, for all forked responses (even if 'Forking Handling
Mode' is Sequential), and thus, may result in transcoding.
[1] Enable = If the 'Forking Handling Mode' parameter is
configured to Sequential, the device sends multiple SDP answers.
Defines whether the destination UA sends RTP immediately after it
sends a 18x response.
[0] By Signaling = (Default) Remote client sends RTP immediately
after it sends 18x response with early media. The device forwards
18x and RTP as is.
[1] By Media = After sending 18x response, the remote client waits
before sending RTP (e.g., Microsoft Skype for Business
environment). For the device's handling of this remote UA support,
see Interworking SIP Early Media on page 660.
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
444
Mediant 500L Gateway & E-SBC
Description
Document #: LTRT-10532

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents