Version 7.2 443 Mediant 800B Gateway & E-SBC
User's Manual 20. Coders and Profiles
Parameter Description
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).
Remote Multiple Answers
Mode
sbc-multi-answers
[IpProfile_SBCRemoteMultip
leAnswersMode]
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.
Remote Early Media RTP
Detection Mode
sbc-rmt-early-media-rtp
[IpProfile_SBCRemoteEarly
MediaRTP]
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 685.
Remote RFC 3960 Support
sbc-rmt-rfc3960-supp
[IpProfile_SBCRemoteSupp
ortsRFC3960]
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
685.
[1] Supported = UA is capable of receiving 18x messages with
delayed RTP.
Remote Can Play Ringback
sbc-rmt-can-play-ringback
[IpProfile_SBCRemoteCanPl
ayRingback]
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 685.
Generate RTP
sbc-generate-rtp
Enables the device to generate "silence" RTP packets to the SIP entity
until it detects audio RTP packets from the SIP entity. The parameter
provides support for interworking with SIP entities that wait for the first
To Next Page
Loading...
