AudioCodes Mediant 3000 User Manual page 351

User's Manual
Parameter
Web: Remote Can Play Ringback
[IpProfile_SBCRemoteCanPlayRi
ngback]
Web: RFC 2833 DTMF Payload
Type
[IpProfile_SBC2833DTMFPayloa
dType]
Web: User Registration Time
[IpProfile_SBCUserRegistrationTi
me]
Web: Reliable Held Tone Source
[IPProfile_ReliableHoldToneSour
ce]
Web: Play Held Tone
[IpProfile_SBCPlayHeldTone]
Web: Remote Hold Format
[IPProfile_SBCRemoteHoldForm
Version 6.8

[1] Supported = UA is capable of receiving 18x messages with
delayed RTP.
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 508.
Defines the payload type of DTMF digits for this SIP entity. 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
forwards the received payload type as is).
Defines the duration (in seconds) of the periodic registrations that
occur between the users of this SIP entity and the device (the
device responds with this value to the user).
The valid range is 0 to 2,000,000 seconds. The default is 0.
When set to 0, the device does not change the Expires header's
value received in the user's REGISTER request. If no Expires
header is received in the REGISTER message and this
parameter is set to 0, the Expires header's value is set to 180
seconds, by default.
Note: The corresponding global parameter is
SBCUserRegistrationTime.
Enables the device to consider the received call-hold request (re-
INVITE/UPDATE) with SDP containing 'a=sendonly', as genuine.

[0] No (default) = Even if the received SDP contains
'a=sendonly', the device plays a held tone to the held party.
This is useful in cases where the initiator of the call hold does
not support the generation of held tones.

[1] Yes = If the received SDP contains 'a=sendonly', the
device does not play a held tone to the held party (and
assumes that the initiator of the call hold plays the held tone).
Note: The device plays a held tone only if the 'SBC Play Held
Tone' parameter is set to Yes.
Enables the device to play a held tone to the held party. This is
useful if the held party does not support playing a local held tone,
or for IP entities initiating call hold that do not support the
generation of held tones.

[0] No (default)

[1] Yes
Note: If this parameter is set to Yes, the device plays the tone
only if the 'SBC Remote Hold Format' parameter is set to send-
only, send only 0.0.0.0, or not supported.
Defines the format of the SDP in the re-INVITE for call hold that
the device sends to the held party.
351
20. Coders and Profiles
Description
Mediant 3000