Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
535
Views
0
Helpful
1
Replies

Route Pattern vs RL and RG

webstd.design
Level 1
Level 1

‎02-22-2008 04:39 AM - edited ‎03-15-2019 09:00 AM

is it normal to use many RL and RG?

I used Route pattern PRI with RL not gateway, but in the RTMT I see message

"Most Recent Alert Raised: At 14:33:20 on 02/22/2008 on cluster StandAloneCluster. Number of RouteListExhausted events exceed 0 within 60 minutes.

There are 12 RouteListExhausted events (up to 30) received during the monitoring interval from 14:32:51 02/22/2008 to 15:32:51 02/22/2008:

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

RouteListExhausted Originated from CallManager

Route list name: Ks_RL

"

What does it mean?

Labels:
0 Helpful
1 Reply 1

MARTIN STREULE
Spotlight
Spotlight

‎02-22-2008 06:32 AM

TAC case collection:

Solution # K20653428

Title

The Route list Exhausted event appears in the Cisco CallManager Event Viewer

Core Issue

This issue can occur if an available route is not found in the indicated route list.

If the call fails on the current gateway, Cisco CallManager attempts to extend the call to the next route in the route list. This occurs until it reaches the last route. If the call cannot be completed with the last gateway, the Route List Exhausted event is logged.

These are possible reasons for a failure on the current gateway:

Unallocated number, such as a non-existing destination

Busy user

Out of bandwidth

Gateway fails to respond to the call setup request

-> It does not necessarily mean that you lack gateways/channels...

You should look into the CDRs and debug the gateway and try to find the issue.

Hope that helps.

/Martin

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents