Version 7.2 1141 Mediant 1000B Gateway & E-SBC
User's Manual 62. Configuration Parameters Reference
Parameter Description
Alt Routing Tel to IP Connectivity
Method
configure voip > gateway routing
settings > alt-rte-tel2ip-method
[AltRoutingTel2IPConnMethod]
Determines the method used by the device for periodically
querying the connectivity status of a destination IP address.
ï‚§ [0] ICMP Ping = (Default) Internet Control Message Protocol
(ICMP) ping messages.
ï‚§ [1] SIP OPTIONS = The remote destination is considered
offline if the latest OPTIONS transaction timed out. Any
response to an OPTIONS request, even if indicating an error,
brings the connectivity status to online.
Note: ICMP Ping is currently not supported for the IP Connectivity
feature.
Alt Routing Tel to IP Keep Alive
Time
configure voip > gateway routing
settings > alt-rte-tel2ip-keep-alive
[AltRoutingTel2IPKeepAliveTime]
Defines the time interval (in seconds) between SIP OPTIONS
Keep-Alive messages used for the IP Connectivity application.
The valid range is 5 to 2,000,000. The default is 60.
Max Allowed Packet Loss for Alt
Routing [%]
configure voip > gateway routing
settings > mx-pkt-loss-4-alt-rte
[IPConnQoSMaxAllowedPL]
Defines the packet loss (in percentage) at which the IP connection
is considered a failure and Alternative Routing mechanism is
activated.
The default is 20%.
Max Allowed Delay for Alt
Routing
configure voip > gateway routing
settings > mx-all-dly-4-alt-rte
[IPConnQoSMaxAllowedDelay]
Defines the transmission delay (in msec) at which the IP
connection is considered a failure and the Alternative Routing
mechanism is activated.
The range is 100 to 10,000. The default is 250.
62.10.14 Alternative Routing Parameters
The alternative routing parameters are described in the table below.
Table 62-69: Alternative Routing Parameters
Parameter Description
3xx Use Alt Route Reasons
configure voip > sip-definition
settings > 3xx-use-alt-route
[UseAltRouteReasonsFor3xx]
Defines the handling of received SIP 3xx responses regarding call
redirection to listed contacts in the Contact header.
ï‚§ [0] No = (Default) Upon receipt of a 3xx response, the device tries
each contact, one by one, listed in the Contact headers, until a
successful destination is found. However, if a contact responds
with a 486 or 600, the device does not try to redirect the call to
next contact, and drops the call.
ï‚§ [1] No if 6xx = Upon receipt of a 3xx response, the device tries
each contact, one by one, listed in the Contact headers. However,
if a 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.
ï‚§ [2] Yes = Upon receipt of a 3xx response, the device redirects the
call to the first contact listed in the Contact header. If the contact
responds with a SIP response that is defined in the Reasons for