AudioCodes E-SBC

CHAPTER19 Coders and Profiles
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
■ [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.
■ [1] Supported = UA is capable of receiving 18x
messages with delayed RTP.
'Remote Can Play Ringback'
sbc-rmt-can-play-
ringback
[IpProfile_
SBCRemoteCanPlayRingback]
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.
'Generate RTP'
sbc-generate-rtp
[IPProfile_SBCGenerateRTP]
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 incoming packets
before sending RTP (e.g., early media used for ringback
tone or IVR) during media negotiation.
■ [0] None = (Default) Silence packets are not
generated.
■ [1] Until RTP Detected = The device generates
silence RTP packets to the SIP entity upon receipt of a
SIP response (183 with SDP) from the SIP entity. In
other words, these packets serve as the first incoming
packets for the SIP entity. The device stops sending
silence packets when it receives RTP packets from the
peer side (which it then forwards to the SIP entity).
Note: To generate silence packets, DSP resources are
required (except for calls using the G.711 coder).
SBC Media
'Mediation Mode'
transcoding-mode
[IpProfile_TranscodingMode]
Defines the transcoding mode (media negotiation) for the
SIP entity associated with the IP Profile.
■ [0] RTP Mediation = (Default) Transcoding is done
only ifrequired. If not required, many of the media
settings (such as gain control) are not applied to the
voice stream. The device forwards the RTP packets
transparently (i.e., RTP-to-RTP) without processing the
data; only the RTP headers are re-constructed.
- 403 -