AudioCodes Mediant 3000

Version 7.0 417 Mediant 3000
User's Manual 20. Coders and Profiles
Parameter Description
SDP Remove Crypto LifeTime
[IpProfile_SBCRemoveCryptoLif
etimeInSDP]
Defines the handling of the lifetime field in the 'a=crypto' attribute of
the SDP for the SIP entity associated with the IP Profile. The SDP
field defines the lifetime of the master key as measured in
maximum number of SRTP or SRTCP packets using the master
key.
 [0] No = (Default) The device retains the lifetime field (if present)
in the SDP.
 [1] Yes = The device removes the lifetime field from the
'a=crypto' attribute.
Note: If you configure the parameter to Yes, the following IP Profile
parameters must be configured as follows:
 IpProfile_EnableSymmetricMKI configured to Enable [1].
 IpProfile_MKISize configured to 0.
 IpProfile_SBCEnforceMKISize configured to Enforce [1].
RFC 2833 Mode
[IpProfile_SBCRFC2833Behavi
or]
Defines the handling of RFC 2833 SDP offer-
answer negotiation for
the SIP entity associated with the IP Profile.
 [0] As is = (Default) The device does not intervene in the RFC
2833 negotiation.
 [1] Extend = Each outgoing offer-answer includes RFC 2833 in
the offered SDP. The device adds RFC 2833 only if the
incoming offer does not include RFC 2833.
 [2] Disallow = The device removes RFC 2833 from the incoming
offer.
Note: If the device interworks between different DTMF methods
and one of the methods is in-band DTMF packets (RFC 2833),
detection and generation of DTMF methods requires DSP
resources.
Alternative DTMF Method
[IpProfile_SBCAlternativeDTMF
Method]
The device's first priority for DTMF method at each leg is RFC
2833. Thus, if the device successfully negotiates RFC 2833 for the
SIP entity associated with the IP Profile, the chosen DTMF method
for this leg is RFC 2833. When RFC 2833 negotiation fails, the
device uses the parameter to define the DTMF method for the leg.
 [0] As Is = (Default) The device does not attempt to interwork
any special DTMF method.
 [1] In Band
 [2] INFO - Cisco
 [3] INFO - Nortel
 [4] INFO - Lucent = INFO, Korea
Note: If the device interworks between different DTMF methods
and one of the methods is in-band DTMF packets (RFC 2833),
detection and generation of DTMF methods requires DSP
resources.
RFC 2833 DTMF Payload Type
[IpProfile_SBC2833DTMFPaylo
adType]
Defines the payload type of DTMF digits for the SIP entity
associated with the IP Profile. This enables the interworking of the
DTMF payload type for RFC 2833 between different SBC call legs.
For example, if two entities require different DTMF payload types,
the SDP offer received by the device from one entity is forwarded
to the destination entity with its payload type replaced with the
configured payload type, and vice versa.
The value range is 0 to 200. The default is 0 (i.e., the device