AudioCodes Mediant 500L MSBR - Page 347

User's Manual 22. Coders and Profiles
Version 6.8 347 Mediant 500L MSBR
Parameter Description
For more information on interworking of the History-Info and
Diversion headers, see Interworking SIP Diversion and
History-Info Headers on page 528.
Web: PRACK Mode
CLI: sbc-prack-mode
[IpProfile_SbcPrackMode]
Defines the device's handling of SIP PRACK messages for
this SIP entity.
 [1] Optional = PRACK is optional. If required, the device
performs the PRACK process on behalf of the SIP entity.
 [2] Mandatory = PRACK is required for this SIP entity.
Calls from endpoints that do not support PRACK are
rejected. Calls destined to these endpoints are also
required to support PRACK.
 [3] Transparent (default) = The device does not intervene
with the PRACK process and forwards the request as is.
Web: Session Expires Mode
CLI: sbc-session-expires-mode
[IpProfile_SBCSessionExpiresMode]
Defines the required session expires mode for this SIP
entity.
 [0] Transparent = (Default) The device does not interfere
with the session expires negotiation.
 [1] Observer = If the SIP Session-Expires header is
present, the device does not interfere, but maintains an
independent timer for each leg to monitor the session. If
the session is not refreshed on time, the device
disconnects the call.
 [2] Not Supported = The device does not allow a session
timer with this SIP entity.
 [3] Supported = The device enables the session timer
with this SIP entity. If the incoming SIP message does not
include any session timers, the device adds the session
timer information to the sent message. You can configure
the value of the Session-Expires and Min-SE headers,
using the SBCSessionExpires and SBCMinSE
parameters, respectively.
Web: Remote Update Support
CLI: sbc-rmt-update-supp
[IpProfile_SBCRemoteUpdateSupport]
Defines whether this SIP entity supports the SIP UPDATE
message.
 [0] Not Supported = UPDATE message is not supported.
 [1] Supported Only After Connect = UPDATE message is
supported only after the call is connected.
 [2] Supported = (Default) UPDATE message is supported
during call setup and after call establishment.
Web: Remote re-INVITE
CLI: sbc-rmt-re-invite-supp
[IpProfile_SBCRemoteReinviteSuppor
t]
Defines whether the destination UA of the re-INVITE request
supports re-INVITE messages and if so, whether it supports
re-INVITE with or without SDP.
 [0] Not Supported = re-INVITE is not supported and the
device does not forward re-INVITE requests. The device
sends a SIP response to the re-INVITE request, which
can either be a success or a failure, depending on
whether the device can bridge the media between the
endpoints.
 [1] Supported only with SDP = re-INVITE is supported,
but only with SDP. If the incoming re-INVITE arrives
without SDP, the device creates an SDP and adds it to
the outgoing re-INVITE.
 [2] Supported = (Default) re-INVITE is supported with or