AudioCodes E-SBC - Page 457

CHAPTER19 Coders and Profiles
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
✔ 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_
SBCKeepUserAgentHeader]
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_SBCHandleXDetect]
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.
'ISUP Body Handling'
sbc-isup-body-handling
[IpProfile_
SBCISUPBodyHandling]
Defines the handling of ISUP data for interworking 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.
■ [2] Create = ISUP body is added to outgoing INVITE
messages.
■ [3] Create If Not Exists = ISUP body is added to
outgoing INVITE messages if it does not exist in the
incoming leg. If it exists, unknown fields and messages
by the device are passed transparently, while known
fields can be manipulated using Message Manipulation
rules. For known fields, some values that are "reserved
for national use" may be changed to default.
- 419 -