Alternative Routing Upon Sip 3Xx With Multiple Contacts - AudioCodes Mediant 800B User Manual

User's Manual
c. Configure a SIP response code for alternative routing according to the
parameters described in the table below.
d. Click Submit, and then save ("burn") your settings to flash memory.
Table 24-6: Reasons for Tel-to-IP Alternative Routing Table Parameter Descriptions
Parameter
Index
[AltRouteCauseTel2Ip_Index]
Release Cause
CLI: rel-cause
[AltRouteCauseTel2Ip_ReleaseCause]
2. Enable alternative routing based on SIP responses, by setting the 'Redundant Routing
Mode' parameter in the Proxy & Registration page
•
Routing Table: Outbound IP Routing table is used for alternative routing.
•
Proxy: Proxy Set redundancy feature is used for alternative routing.
3. If you are using the Outbound IP Routing table, configure alternative routing rules with
identical call matching characteristics, but with different IP destinations.
4. If you are using the Proxy Set, configure redundant proxies.

24.5.3 Alternative Routing upon SIP 3xx with Multiple Contacts

You can configure how the device handles received SIP 3xx responses that contain
multiple alternative contacts. The 3xx response indicates that the original destination is
unavailable (e.g., 301 Moved Permanently – user cannot be found) and that the call can be
redirected to alternative destinations specified in the SIP Contact headers.
Configured by the '3xx Use Alt Route Reasons' parameter, the device can handle the
receipt of 3xx responses using one of the following methods:

The device tries each contact sequentially, listed in the Contact headers, until a
successful destination is found. If a contact responds with a SIP 486 or 600, the
device does not try to redirect the call to the next contact and drops the call.

The device tries each contact sequentially, listed in the Contact headers. If a SIP 6xx
Global Failure response is received during this process (e.g., 600 Busy Everywhere),
the device does not try to redirect the call to the next contact and drops the call.

The device redirects the call to the first contact listed in the Contact header. If the
contact responds with a SIP response that is configured in the Reasons for Tel-to-IP
Alternative Routing table (see ''Alternative Routing Based on SIP Responses'' on page
385), the device tries to redirect the call to the next contact, and so on. If a contact
responds with a response that is not configured in the table, the device does not try to
redirect the call to the next contact and drops the call.
Note:
to redirect the call to the next contact. Instead, the device continues with the regular
authentication process, as indicated by these response types.
Version 6.8
Defines an index number for the new table record.
Defines a SIP response code that if received, the device
attempts to route the call to an alternative destination (if
configured).
If a SIP 401 or 407 response is received from a contact, the device does not try
Description
to one of the following:
387 Mediant 800B Gateway and E-SBC
24. Routing