Version 6.8 309 Mediant 2600 E-SBC
User's Manual 19. Coders and Profiles
Parameter Description
Web: Remote 3xx Behavior
CLI: sbc-rmt-3xx-behavior
[IpProfile_SBCRemote3xxBeha
vior]
Defines the device's handling of SIP 3xx redirect responses for this
SIP entity. By default, the device's handling of SIP 3xx responses is
to send the Contact header unchanged. However, some SIP
entities may support different versions of the SIP 3xx standard
while others may not even support SIP 3xx.
When enabled, the device handles SIP redirections between
different subnets (e.g., between LAN and WAN sides). This is
required when 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] Database URL = The device changes the Contact header so
that the re-route request is sent through 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.
Only one database entry is supported for the same host, port,
and transport combination. For example, the following URLs
cannot be distinguished by the device:
sip:10.10.10.10:5060;transport=tcp;param=a
sip:10.10.10.10:5060;transport=tcp;param=b
The database entry expires two hours after the last use.
The maximum number of destinations (i.e., database entries) is
50.
The corresponding global parameter is SBC3xxBehavior.
Web: Remote Multiple 18x
CLI: sbc-rmt-mltple-18x-supp
[IpProfile_SBCRemoteMultiple1
8xSupport]
Defines whether multiple 18x responses including 180 Ringing, 181
Call is Being Forwarded, 182 Call Queued, and 183 Session
Progress are forwarded to the caller, for this SIP entity.
[0] Not Supported = Only the first 18x response is forwarded to
the caller.
[1] Supported = (Default) Multiple 18x responses are forwarded
to the caller.
To Next Page
Loading...
