Version 6.2 861 February 2011
SIP User's Manual 12. Configuration Parameters Reference
Parameter Description
[SBCReferBehavior]
Defines how the device handles 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:
1 Before passing on the REFER request, the device
changes the host part to the device's IP address and adds
a special prefix ("T~&R_") to the Contact user part.
2 The incoming INVITE is identified as a REFER-resultant
INVITE according to the special prefix.
3 The device replaces the host part (in the Request-URI)
with the 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.
4 The prefix is removed before the resultant INVITE is sent
to the destination.
[SBCXferPrefix]
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.
[SBC3xxBehavior]
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).
[1] = The device changes the URI in the Contact header
of the received SIP 3xx response to its own URI and adds
a special user prefix ("T~&R_”), which is then sent to the
FEU. The FEU then sends a new INVITE to the device,
To Next Page
Loading...
