[cisco-voip] Route List Exhausted

[dschulz]

Nenad - 

The route list exhausted message in RTMT can occur due to a number of issues
(as below).  It will only tell you that it can't find a route....even a
wrong number, for example.  No other information is given.  Cisco does
mention that this option can be turned off in most cases (see below).  My
suggestion would be to use the DNA tool if you suspect there being a problem
with your route plan.  HTH,

Dave



The web site for this is at:
 
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186
a0080111ac2.shtml#topic1
 
 
Error Message: %CCM_CALLMANAGER-CALLMANAGER-4-RouteListExhausted: 

An available route could not be found in the indicated route list. Route
List Name [String] 

Explanation-An available route could not be found in the indicated route
list. This error can appear if an available route is not found in the
indicated route list. Cisco CallManager attempts to extend the call to the
next route in the route list until it reaches the last route if the call
fails on the current gateway. If the call cannot be completed using the last
gateway, the Route List Exhausted event is logged. Reasons for a failure on
the current gateway can include: 

Unallocated number 

User busy 

Out of bandwidth 

Gateway fails to respond to the call setup request 

 

You can change this behavior using Cisco CallManager Service Parameters.
This event can usually be ignored. For example, the Unallocated Number error
can be caused if the user calls a non-existing destination. Or, if a
destination is busy, it will be busy when trying the next available
gateways. If you think this event is not caused by similar failures, you can
enable the detailed Cisco CallManager traces according to the procedures in
Setting up Cisco CallManager Traces for the TAC. You can also use the
Q931Translator.exe, located in C:\Program Files\Cisco\bin, to analyze the
call setup and disconnection sequences.

If you have a route list with an H.323 gateway as the first route group, and
a second route group that takes any overflow, the first H.323 gateway can
send a user busy back to the Cisco CallManager if all of its channels or
ports are busy. If this occurs, the call is not forwarded to the second
route group in the route list.

If your route list is configured as explained, set both the Stop Routing on
User Busy Flag and Stop Routing on Unallocated Number Flag service
parameters to False. In order to do this, go to Cisco CallManager Admin >
Service > Service Parameters > Select a Server > Cisco CallManager and set
the parameters to False.

This enables Cisco CallManager to try other gateways to re-route the call on
a user busy before it reaches the RouteListExhausted state. 

Recommended Action-You might need to add additional routes in the indicated
route list

Dave
 

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of nenad lazarevic
Sent: Monday, November 19, 2007 3:42 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Route List Exhausted

 I received a message from RTMT tool (Callmanager 4.1.3)

At 19:38:18 on 11/19/2007 on cluster StandAloneCluster.
Number of RouteListExhausted events exceed 1 within 60 minutes.

Where I can find which Route List is Exhausted at Standalone Cluster?

Thx
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip