AudioCodes Mediant 3000 User Manual page 269

Enterprise session border controller / voip digital media gateway
Hide thumbs Also See for Mediant 3000:
Table of Contents

Advertisement

User's Manual
Parameter
Web: Diversion Mode
[IpProfile_SBCDiversionMode]
Web: History Info Mode
[IpProfile_SBCHistoryInfoMode]
Web: Media Security Behavior
[IpProfile_SBCMediaSecurityBe
haviour]
Version 6.6
in the Allowed Coders Group table.
Note: If the SBCExtensionCodersGroupID parameter of the IP
Profile table is set to None, this parameter is not applicable.
Determines the device's handling of the SIP Diversion header.
For more information on interworking of the History-Info and
Diversion headers, see Interworking SIP Diversion and History-
Info Headers.
[0] Don't Care = (Default) Diversion header is not handled.
[1] Add = History-Info header converted to a Diversion
header.
[2] Remove = Removes the Diversion header and the
conversion to the History-Info header depends on the
settings of the SBCHistoryInfoMode parameter.
Determines the device's handling of the History-Info header.
For more information on interworking of the History-Info and
Diversion headers, see Interworking SIP Diversion and History-
Info Headers.
[0] Don't Care = (Default) History-Info header is not handled.
[1] Add = Diversion header converted to a History-Info
header.
[2] Remove = History-Info header removed from the SIP
dialog and the conversion to the Diversion header depends
on the settings of the SBCDiversionMode parameter.
Determines the transcoding method between SRTP and RTP
and enforce an SBC leg to use SRTP or RTP.
[0] As is = (Default) No special handling for RTP\SRTP is
done.
[1] SRTP = SBC legs negotiate only SRTP media lines, and
RTP media lines are removed from the incoming SDP
offer\answer.
[2] RTP = SBC legs negotiate only RTP media lines, and
SRTP media lines are removed from the incoming
offer\answer.
[3] Both = Each offer\answer is extended (if not already) to
two media lines - one RTP and the other SRTP.
If two SBC legs (after offer\answer negotiation) use different
security types (i.e., one RTP and the other SRTP), the device
performs RTP-SRTP transcoding. To transcode between RTP
and SRTP, the following prerequisites must be met:
At least one supported SDP "crypto" attribute and
parameters
EnableMediaSecurity must be set to 1
If one of the above transcoding prerequisites is not met, then:
any value other than "As is" is discarded.
if the incoming offer is SRTP, force transcoding, coder
transcoding, and DTMF extensions are not applied.
269
18. Coders and Profiles
Description
Mediant 3000

Advertisement

Table of Contents
loading

Table of Contents