AudioCodes Media Pack MP-124, User Manual

Page: 238 / 584

User's Manual 238 Document #: LTRT-65422
MP-11x & MP-124

To configure alternative Hunt Group routing based on Q.931 cause codes:
1. In the Proxy & Registration page, set the 'Redundant Routing Mode' parameter to
Routing Table so that the device uses the Inbound IP Routing table for alternative
routing.
2. In the Inbound IP Routing table, configure alternative routing rules with the same call
matching characteristics, but with different Hunt Group destinations.
3. Configure up to five Q.931 cause codes that invoke alternative IP-to-Tel routing:
a. Open the Reasons for Alternative Routing page ( Configuration tab > VoIP menu
> GW and IP to IP > Routing > Alternative Routing Reasons ).
Figure 22-5: IP to Tel Reasons - Reasons for Alternative Routing Page
b. Under the 'IP to Tel Reasons' group, select the desired Q.931 cause codes.
c. Click Submit to apply your changes.
Notes:
•
You can configure up to two alternative routing rules in the Inbound IP
Routing table.
•
The default release cause is described in the Q.931 notation and is
translated to corresponding SIP 40x or 50x values (e.g., Cause Code No.
3 to SIP 404, and Cause Code No. 34 to SIP 503).
•
For information on mapping PSTN release causes to SIP responses, see
PSTN Release Cause to SIP Response Mapping.
•
For configuring IP-to-Tel routing rules in the Inbound IP Routing table,
see 'Configuring IP to Hunt Group Routing Table' on page
230 .
•
The Reasons for Alternative Routing IP to Tel table can also be
configured using the table ini file parameter, AltRouteCauseIP2Tel.
22.6.2 Alternative Routing to an IP Destination upon a Busy Trunk
You can configure the device to forward (i.e., call redirection) IP-to-Tel calls to an
alternative IP destination using SIP 3xx responses. This can be done upon the following
scenario:

Unavailable FXS / FXO Hunt Group. This feature can be used, for example, to
forward the call to another FXS / FXO device.
This feature is configured per Hunt Group and is configured in the Forward on Busy Trunk
Destination table, as described in this section.
The alternative destination can be defined as a host name or as a SIP Request-URI user
name and host part (i.e., user@host). For example, the below configuration forwards IP-to-
Tel calls to destination user “112” at host IP address 10.13.4.12, port 5060, using transport
protocol TCP, if Trunk Group ID 2 is unavailable:
ForwardOnBusyTrunkDest 1 = 2, 112@10.13.4.12:5060;transport=tcp;
When configured with user@host, the original destination number is replaced by the user
part.