AudioCodes Mediant 3000 User Manual page 748

Parameter
Web: Keep original user in
Register
[SBCKeepContactUserinRegi
ster]
[SBCReferBehavior]
[SBCXferPrefix]
[SBC3xxBehavior]
SIP User's Manual
Determines whether the device replaces the Contact user with a
unique Contact user in the outgoing message in response to a
REGISTER request.

[0] Disable = (default) The device replaces the original Contact
user with a unique Contact user, for example:

Received Contact: <sip:123@domain.com>

Outgoing (unique) Contact: <sip:FEU1_7_1@SBC>

[1] Enable = The original Contact user is retained and used in
the outgoing REGISTER request.
Note: This parameter is applicable only to REGISTER messages
received from USER IP Groups and that are sent to SERVER IP
Groups.
Determines the device's handling of REFER requests.

[0] = Refer-To header is unchanged (default).

[1] = Uses the database for Refer-To as described below.
When enabled, the device handles REFERs as follows:
Before passing on the REFER request, the device changes the
1
host part to the device's IP address and adds a special prefix
("T~&R_") to the Contact user part.
The incoming INVITE is identified as a REFER-resultant INVITE
2
according to the special prefix.
The device replaces the host part (in the Request-URI) with the
3
host from the REFER contact. The prefix ("T~&R_") remains in
the user part for regular classification, manipulation, and routing.
The special prefix can be used for specific routing rules for
REFER-resultant INVITES.
The prefix is removed before the resultant INVITE is sent to the
4
destination.
When the SBCReferBehavior is set to 1, the device, while
interworking the SIP REFER message, adds the prefix "T~&R-" to
the user part of the URI in the Refer-To header. After this, the
device can receive an INVITE with such a prefix (the INVITE is sent
by the UA that receives the REFER message or 302 response). If
the device receives an INVITE with such a prefix, it replaces the
prefix with the value defined for the SBCXferPrefix parameter.
The default value is empty ("").
Note: This feature is also applicable to 3xx redirect responses. The
device adds the prefix "T~&R-" to the URI user part in the Contact
header if the SBC3xxBehavior parameter is set to 1.
Determines the device's handling of SIP 3xx responses. When
enabled, the device handles SIP redirections between different
subnets (e.g., between LAN and WAN sides). This is required
where the new address provided by the redirector (Redirect sever)
may not be reachable by the far-end user (FEU) located in another
subnet. For example, a far-end user (FEU) in the WAN sends a SIP
request via the device to a Redirect server in the LAN, and the
Redirect server replies with a SIP 3xx response to a PBX in the
LAN in the Contact header. If the device sends this response as is
(i.e., with the original Contact header), the FEU is unable to reach
the new destination.

[0] (default) = The device sends the received SIP 3xx response
without changing the Contact header (transparent handling).
748
Description
Document #: LTRT-89712
Mediant 3000