Version 7.0 519 Mediant 3000
User's Manual 25. Routing
3. Configure Q.931 cause codes that invoke alternative IP-to-Tel routing:
a. Open the Reasons for IP-to-Tel Alternative Routing table (Configuration tab >
VoIP menu > Gateway > Routing > Alternative Routing Reasons > Reasons
for IP-to-Tel).
b. Click Add; the following dialog box appears:
Figure 25-9: Reasons for IP-to-Tel Alternative Routing Table - Add Row Dialog Box
c. Configure a Q.931 release cause code for alternative routing according to the
parameters described in the table below.
d. Click Add.
Table 25-9: Reasons for IP-to-Tel Alternative Routing Table Parameter Descriptions
Parameter Description
Index
[AltRouteCauseIP2Tel_Inde
x]
Defines an index number for the new table row.
Note: Each row must be configured with a unique index.
Release Cause
[AltRouteCauseIP2Tel_Rel
easeCause]
Defines a Q.931 release code that if received, the device attempts to
route the call to an alternative destination (if configured).
25.7.2 Alternative Routing to an IP Destination upon a Busy Trunk
The Forward on Busy Trunk Destination table lets you configure alternative routing rules for
forwarding (i.e., call redirection) IP-to-Tel calls to an alternative IP destination using SIP
3xx responses. These rules are used upon the following:
Trunk Group has no free channels (i.e., “busy”).
This feature is configured per Trunk Group. 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.
The device forwards calls using this table only if no alternative IP-to-Tel routing rule has
been configured in the Inbound IP Routing table or alternative routing fails and the
following reason(s) in the SIP Diversion header of 3xx messages exists:
“out-of-service” - all trunks are unavailable/disconnected