CHAPTER19 Coders and Profiles
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
[IpProfile_
SBCHistoryInfoMode]
■ [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.
'Session Expires Mode'
sbc-session-expires-
mode
[IpProfile_
SBCSessionExpiresMode]
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.
'Remote Update Support'
sbc-rmt-update-supp
[IpProfile_
SBCRemoteUpdateSupport]
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.
■ [3] According Remote Allow = For refreshing the
timer of currently active SIP sessions, the device
sends session refreshes using SIP UPDATE
messages only if the SIP Allow header in the last SIP
message received from the user contains the value
"UPDATE". If the Allow header does not contain the
"UPDATE" value (or if the parameter is not configured
to this option), the device uses INVITE messages for
session refreshes.
'Remote re-INVITE'
sbc-rmt-re-invite-supp
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.
- 416 -
To Next Page
Loading...
