Parameter Description
Note: This parameter can be configured in an IP Profile.
CLI: sbc-xfer-prefix
[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.
CLI: sbc-3xx-bhvt
[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] Transparent = (Default) The device forwards the received SIP
3xx response as is, without changing the Contact header
(i.e.,transparent handling).
[1] DB URL = The device changes the Contact header so that the
re-route request is sent through the the device. 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, which the device then sends to the
correct destination.
[2] Handle Locally = The device handles SIP 3xx responses on
behalf of the dialog-initiating UA and retries the request (e.g.,
INVITE) using one or more alternative URIs included in the 3xx
response. The device sends the new request to the alternative
destination according to the IP-to-IP Routing table (the 'Call
Trigger' field must be set to 3xx).
Notes:
When this parameter is changed from 1 to 0, new 3xx Contact
headers remain unchanged. However, requests with the special
prefix continue using the device's database to locate the new
destination.
To Next Page
Loading...
