Version 6.4 745 March 2012
SIP User's Manual A. Configuration Parameters Reference
Parameter Description
FORMAT AltRouteCauseTel2IP_Index =
AltRouteCauseTel2IP_ReleaseCause;
[\AltRouteCauseTel2IP]
For example:
AltRouteCauseTel2IP 0 = 486; (Busy Here)
AltRouteCauseTel2IP 1 = 480; (Temporarily Unavailable)
AltRouteCauseTel2IP 2 = 408; (No Response)
Notes:
This parameter can include up to 5 indices.
The reasons for alternative routing for Tel-to-IP calls apply
only when a Proxy is not used.
When there is no response to an INVITE message (after
INVITE retransmissions), the device issues an internal 408
'No Response' implicit release reason.
The device sends the call to an alternative IP route only after
the call has failed and the device has subsequently
attempted twice to establish the call unsuccessfully.
The device also plays a tone to the endpoint whenever an
alternative route is used. This tone is played for a user-
defined time (configured by the parameter
AltRoutingToneDuration).
For configuring ini file table parameters, see ''Configuring ini
File Table Parameters'' on page 84
Reasons for Alternative IP-to-Tel Routing Table
Web: Reasons for Alternative IP-to-
Tel Routing
EMS: Alt Route Cause IP to Tel
[AltRouteCauseIP2Tel]
This parameter table configures call failure reason values
received from the PSTN side (in Q.931 presentation). If a call is
released as a result of one of these reasons, the device
attempts to locate an alternative Hunt Group for the call in the
Inbound IP Routing Table.
The format of this parameter is as follows:
[AltRouteCauseIP2Tel]
FORMAT AltRouteCauseIP2Tel_Index =
AltRouteCauseIP2Tel_ReleaseCause;
[\AltRouteCauseIP2Tel]
For example:
AltRouteCauseIP2Tel 0 = 3 (No Route to Destination)
AltRouteCauseIP2Tel 1 = 1 (Unallocated Number)
AltRouteCauseIP2Tel 2 = 17 (Busy Here)
Notes:
This parameter can include up to 5 indices.
If the device fails to establish a call to the PSTN because it
has no available channels in a specific Hunt Group (e.g., all
the channels are occupied, or the spans are disconnected or
out-of-sync), it uses the Internal Release Cause '3' (No
Route to Destination). This cause can be used in the
AltRouteCauseIP2Tel table to define routing to an
alternative Hunt Group.
This table can be used for example, in scenarios where the
destination is busy and the Release Reason #17 is issued or
for other call releases that issue the default Release Reason
(#3).
The device also plays a tone to the endpoint whenever an