[\AltRouteCauseTel2IP]
This parameter can include up to 5 indices.
Notes:
The reasons for alternative routing for Tel-to-IP calls only
apply 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.
For an explanation on using
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).
ini file table parameters, refer
to ''Format of ini File Table Parameters'' 191 on page .
Reasons for Alternative Routing
Table
Reasons for Alternative IP-to-Tel Routing Table
This
[AltRouteCauseIP2Tel]
ini file table parameter configures call failure reason
values received from the Tel side . 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 'IP to Hunt
[AltRouteCauseIP2Tel]
FORMAT AltRouteCauseIP2Tel_
Group
Routing' table.
The format of this parameter is as follows:
Index =
AltRouteCauseIP2Tel_ReleaseCause
For example:
AltRouteCauseIP2Tel 0 = 3 (No Route to Destination)
AltRouteCauseIP2Tel 1 = 1 (Unallocated Number)
AltRouteCauseIP2Tel 2 = 17 (Busy Here)
;
[\AltRouteCauseIP2Tel]
This parameter can include up to 5 indices.
Notes:
This table can be used for example, in scenarios when the
destination is busy and the release reason #17 is issued, or
for other call releases that issue the default release reason
(#3).
For an explanation on using
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).
ini file table parameters, refer
to ''Format of ini File Table Parameters'' 191 on page .