AudioCodes Mediant 500 E-SBC, User Manual

Page: 403 / 920

User's Manual 24. Routing
Version 6.8 403 Mediant 500 E-SBC
The steps for configuring alternative Tel-to-IP routing based on SIP response codes are
summarized below.

To configure alternative Tel-to-IP routing based on SIP response codes:
1. Configure SIP response codes (call failure reasons) that invoke alternative Tel-to-IP
routing:
a. Open the Reasons for Tel-to-IP Alternative Routing page ( Configuration tab >
VoIP menu > GW and IP to IP > Routing > Alternative Reasons > Reasons
for Tel-to-IP ).
b. Click Add ; the following dialog box appears:
Figure 24-6: Reasons for Tel-to-IP Alternative Routing Table - Add Record
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 Description
Index
[AltRouteCauseTel2Ip_Index]
Defines an index number for the new table record.
Release Cause
CLI: rel-cause
[AltRouteCauseTel2Ip_ReleaseCause]
Defines a SIP response code that if received, the device
attempts to route the call to an alternative destination (if
configured).
2. Enable alternative routing based on SIP responses, by setting the 'Redundant Routing
Mode' parameter in the Proxy & Registration page
to one of the following:
•
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.