AudioCodes Mediant 3000 User Manual page 354

Gateway & enterprise sbc, family of media gateways & session border controllers
Hide thumbs Also See for Mediant 3000:
Table of Contents

Advertisement

Parameter
Web: Use Silence Suppression
CLI: sbc-use-silence-supp
[IpProfile_SBCUseSilenceSupp]
Web: Play RBT To Transferee
[IpProfile_SBCPlayRBTToTransf
eree]
Web: RTCP Mode
[IPProfile_SBCRTCPMode]
User's Manual
is used as the ptime in the SDP offer.
The valid range is 0 to 200. The default is 0 (i.e., a preferred
ptime is not used).
Defines silence suppression support for this SIP entity.
[0] Transparent (default) = Forward as is.
[1] Add = Enable silence suppression for each relevant coder
listed in the SDP.
[2] Remove = Disable silence suppression for each relevant
coder listed in the SDP.
Note: The parameter requires DSP resources.
Enables the device to play a ringback tone to the transferred
party (transferee) during a blind call transfer, for this SIP entity
(which does not support such a tone generation during call
transfer). The ringback tone indicates to the transferee of the
ringing of the transfer target (to where the transferee is being
transferred).
[0] No (Default)
[1] Yes
Typically, the transferee hears a ringback tone only if the transfer
target sends it early media. However, if the transferee is put on-
hold before being transferred, no ringback tone is heard.
When this feature is enabled, the device generates a ringback
tone to the transferee during call transfer in the following
scenarios:
Transfer target sends a SIP 180 (Ringing) to the device.
For non-blind transfer, if the call is transferred while the
transfer target is ringing and no early media occurs.
The 'Remote Early Media RTP Behavior parameter is set to
Delayed (used in the Lync environment), and transfer target
sends a 183 Session progress with SDP offer. If early media
from the transfer target has already been detected, the
transferee receives RTP stream from the transfer target. If it
has not been detected, the device generates a ringback tone
to the transferee and stops the tone generation once RTP has
been detected from the transfer target.
For any of these scenarios, if the transferee is put on-hold by the
transferor, the device retrieves the transferee from hold, sends a
re-INVITE if necessary, and then plays the ringback tone.
Note: For the device to play the ringback tone, it must be loaded
with a Prerecorded Tones (PRT) file. For more information, see
Prerecorded Tones File on page 592.
Defines how the device handles RTCP packets during call
sessions for this SIP entity. This is useful for interworking RTCP
between SIP entities. For example, this may be necessary when
incoming RTCP is not compatible with the destination SIP entity's
(this IP Profile) RTCP support. In such a scenario, the device can
generate the RTCP and send it to the SIP entity.
[0] Transparent (default) = RTCP is forwarded as is (unless
transcoding is done, in which case, the device generates
RTCP on both legs).
[1] Generate Always = Generates RTCP packets during active
and inactive (e.g., during call hold) RTP periods (i.e., media is
354
Description
Document #: LTRT-89738
Mediant 3000

Advertisement

Table of Contents
loading

Table of Contents