User's Manual 456 Document #: LTRT-10632
Mediant 800B Gateway & E-SBC
Parameter Description
[IpProfile_SBCKeepRouting
Headers]
for request/response messages sent to the the SIP entity associated
with the IP Profile.
[-1] According to Operation Mode = (Default) Depends on the
setting of the 'Operation Mode' in the IP Group or SRDs table:
B2BUA: Device operates as if the parameter is set to Disable
[0].
Call State-full Proxy: Device operates as if the parameter is set
to Enable [1].
[0] Disable = Device removes the Record-Route headers received
in requests and responses from the other side, in the outgoing SIP
message sent to the SIP entity. The device creates a route set for
that side of the dialog based on these headers, but doesn't send
them to the SIP entity.
[1] Enable = Device retains the incoming Record-Route headers
received in requests and non-failure responses from the other side,
in the following scenarios:
The message is part of a SIP dialog-setup transaction.
The messages in the setup and previous transaction didn't
include the Record-Route header, and therefore hadn't set the
route set.
Note: Record-Routes are kept only for SIP INVITE, UPDATE,
SUBSCRIBE and REFER messages.
Keep User-Agent Header
sbc-keep-user-agent
[IpProfile_SBCKeepUserAge
ntHeader]
Enables interworking SIP User-Agent headers between SIP entities.
The parameter defines the device's handling of User-Agent headers
for response/request messages sent to the SIP entity associated with
the IP Profile.
[-1] According to Operation Mode = (Default) Depends on the
setting of the 'Operation Mode' parameter in the IP Group or SRDs
table:
B2BUA: Device operates as if this parameter is set to Disable
[0].
Call State-
full Proxy: Device operates as if this parameter is set
to Enable [1].
[0] Disable = Device removes the User-Agent/Server headers
received in the incoming message from the other side, and adds
its' own User-Agent header in the outgoing message sent to the
SIP entity.
[1] Enable = Device retains the User-Agent/Server headers
received in the incoming message and sends the headers as is in
the outgoing message to the SIP entity.
Handle X-Detect
sbc-handle-xdetect
[IpProfile_SBCHandleXDete
ct]
Enables the detection and notification of events (AMD, CPT, and fax),
using the X-Detect SIP header.
[0] No (default)
[1] Yes
For more information, see Event Detection and Notification using X-
Detect Header on page 211.
ISUP Body Handling
sbc-isup-body-handling
[IpProfile_SBCISUPBodyHa
ndling]
Defines the handling of ISUP data for interworking between SIP and
SIP-I endpoints.
[0] Transparent = (Default) ISUP data is passed transparently (as
is) between endpoints (SIP-I to SIP-I calls).
[1] Remove = ISUP body is removed from INVITE messages.