cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
390
Views
0
Helpful
2
Replies

External Calls wont Route to MGCP Gateway RouteListExhausted E911-T1

Phil-C123
Level 1
Level 1

I have a SIP trunk on a C8300 CUBE/VGW. External calls route through CUBE on the SIP Trunk dial peers. There are no issues with inbound calls to phones, or anything else I have configured with it (other T1's, SIP Trunks, etc.) The particular MGCP gateway I am having trouble with is a 911 center's link to my voice gateway (I have 2 different T1's connected to 2 different Voice gateways). Only 1 of the T1's is currently working as the other one has a "State = AWAITING_ESTABLISHMENT" Layer 2 issue which is another problem that I'm tracking down.

Calls going from internal (local phones) have no issue routing over the route pattern to the MGCP gateway to the 911 center. However, calls coming in from the SIP trunk and then going to the MGCP gateway do not work. In RTMT they show a 41 RouteListExhausted error, I dug deeper down and this results from it matching the Route Pattern, then trying the Route List, finding the Route Group, and when it tries the T1 connections, both report as DOWN.  See attached file: 41-error.txt (The SIP messages report rejected and a 480 SIP error).

I have another MGCP Gateway to a T1 which is for a totally different system and that one works fine.

The 911 T1 worked fine until I messed with the device pools and CCM-managers for the gateways, and routelists, as I was trying to consolidate them in order to take down some of my servers for maintenance. This ended up completely stopping all calls to the 911 MGCP T1, but when I changed the Routelist to Running on all nodes it fixed it.


I am stumped and have been working on this one for a while now, I've checked CSS permissions, the MGCP says registered, and the configs look no different than the MGCP T1 for the other system that works fine (that one is on a VG450 not a C8300).

It should also be noted that calls work from MGCP 911 to outbound. Calls work when received from external to inbound extensions and then are transferred to MGCP 911 T1, but calls don't work when external calls are redirected with a Forward All to the MGCP 911 T1.

1 Accepted Solution

Accepted Solutions

RESOLVED: https://community.cisco.com/t5/collaboration-knowledge-base/quot-route-list-exhausted-quot-cause-list/ta-p/3140817

Thanks to @Juan Gerardo Hernandez for the comment to restart the CM Service. Also I ran into a Codec mismatch issue right after that (not sure how it was working before) but I just changed the codec to G729 and it fixed it.

View solution in original post

2 Replies 2

Phil-C123
Level 1
Level 1

Here is another log file excerpt but for a working call from internal 5559824 to MGCP gateway 5553108.

The other log file numbers were: 5025553108 (5553108) (MGCP gateway) called by 9122703401 (external caller).

Obviously, the numbers are not original, but they are consistent throughout logs.

RESOLVED: https://community.cisco.com/t5/collaboration-knowledge-base/quot-route-list-exhausted-quot-cause-list/ta-p/3140817

Thanks to @Juan Gerardo Hernandez for the comment to restart the CM Service. Also I ran into a Codec mismatch issue right after that (not sure how it was working before) but I just changed the codec to G729 and it fixed it.