AudioCodes Mediant 500 E-SBC, Руководство пользователя

Страница: 324 / 920

User's Manual 324 Document #: LTRT-10437
Mediant 500 E-SBC
Parameter Description
Web: Remote Early Media RTP
Behavior
CLI: sbc-rmt-early-media-rtp
[IpProfile_SBCRemoteEarlyMediaRTP
] Defines whether the destination UA sends RTP immediately
after it sends 18x response.

[0] Immediate = (Default) Remote client sends RTP
immediately after it sends 18x response with early media.
Device forwards 18x and RTP as is.

[1] Delayed = After sending 18x response, the remote
client waits before sending RTP (e.g., Microsoft Lync
environment). For the device's handling of this remote UA
support, see Interworking SIP Early Media on page
461 .
Web: Remote RFC 3960 Gateway
Model Support
CLI: sbc-rmt-rfc3960-supp
[IpProfile_SBCRemoteSupportsRFC3
960] Defines whether the destination UA is capable of receiving
18x messages with delayed RTP.

[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 on page
461 .

[1] Supported = UA is capable of receiving 18x messages
with delayed RTP.
Web: Remote Can Play Ringback
CLI: sbc-rmt-can-play-ringback
[IpProfile_SBCRemoteCanPlayRingba
ck] 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
461 .
Web: RFC 2833 DTMF Payload Type
CLI: sbc-2833dtmf-payload
[IpProfile_SBC2833DTMFPayloadTyp
e] 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).
Web: User Registration Time
CLI: sbc-usr-reg-time
[IpProfile_SBCUserRegistrationTime] 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.