AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 422 / 1248

User's Manual 422 Document #: LTRT-10375
Mediant 500 MSBR
Parameter Description
to the SIP entity.

[1] Add Routing Headers = Device adds a Record-Route
header for itself to outgoing messages (requests\responses)
sent to the SIP entity in dialog-setup transactions. The
Contact header remains unchanged.

[2] Transparent = Device doesn't change the Contact header
and doesn't add a Record-Route header for itself. Instead, it
relies on its' own inherent mechanism to remain in the route
of future requests in the dialog (for example, relying on the
way the endpoints are set up or on TLS as the transport
type).
Keep Incoming Via Headers
sbc-keep-via-headers
[IpProfile_SBCKeepVIAHeaders]
Enables interworking SIP Via headers between SIP entities. The
parameter defines the device's handling of Via headers for
messages sent to the SIP entity associated with the IP Profile.

[-1] According to Operation Mode = Depends on the setting of
the 'Operation Mode' parameter in the IP Groups table 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 all Via headers received in the
incoming SIP request from the other leg and adds a Via
header identifying only itself, in the outgoing message sent to
the SIP entity.

[1] Enable = Device retains the Via headers received in the
incoming SIP request and adds itself as the top-most listed
Via header in the outgoing message sent to the SIP entity.
Keep Incoming Routing Headers
sbc-keep-routing-headers
[IpProfile_SBCKeepRoutingHead
ers]
Enables interworking SIP Record-Route headers between SIP
entities. The parameter defines the device's handling of Record-
Route 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.