AudioCodes Mediant 500L User Manual page 454

Parameter
History-Info Header Mode
sbc-history-info-mode
[IpProfile_SBCHistoryInfoMo
de]
Session Expires Mode
sbc-session-expires-mode
[IpProfile_SBCSessionExpir
esMode]
Remote Update Support
sbc-rmt-update-supp
[IpProfile_SBCRemoteUpdat
eSupport]
Remote re-INVITE
sbc-rmt-re-invite-supp
[IpProfile_SBCRemoteReinvi
teSupport]
Remote Delayed Offer
User's Manual
Note: If the Diversion header is used, you can specify the URI type
(e.g., "tel:") to use in the header, using the SBCDiversionUriType
parameter.
Defines the device's handling of the SIP History-Info header for the
SIP entity associated with the IP Profile.

[0] As Is = (Default) History-Info header is not handled.

[1] Add = Diversion header is converted to a History-Info header.

[2] Remove = History-Info header is removed from the SIP dialog
and the conversion to the Diversion header depends on the
SBCDiversionMode parameter.
For more information on interworking of the History-Info and Diversion
headers, see Interworking SIP Diversion and History-Info Headers on
page 658.
Defines the required session expires mode for the SIP entity
associated with the IP Profile.

[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.
Defines whether the SIP UPDATE message is supported by the SIP
entity associated with the IP Profile.

[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.
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 without
SDP.
Defines whether the remote endpoint supports delayed offer (i.e.,
454
Mediant 500L Gateway & E-SBC
Description
Document #: LTRT-10532