07-28-2008 09:36 AM - edited 03-17-2019 09:27 PM
Today, I observe this situation which prove Cisco MGCP Callmanager route list won't failover to 2nd route group when the 1st route group's T1 circuit is down.
Ie, RoutePattern 9.@ -> RouteList: RL_siteA -> Two RouteGroup: VGW1_T1 and VGW2_T2 which in turn point to the different T1 circuit in different vgw.
When VGW1_T1 circuit status get error 'TEI_Assigned' other than 'Multi_Frame_estabished', Callmanager still show this T1 circuit regsitered and never use 2nd circuit which is VGW2_T2.
So users cannot place outbound calls due to this failed vgw1-T1 circuit even though vgw2-T2 is up.
Is it callmanager limitation?
Anyone know the workaround without manual task to remove and/or re-order route group inside the route list.
My ccm is: 4.1.3
mgcp ver: 0.1
07-28-2008 10:23 AM
Addon here:
If vgw1 router is completed down, then 2nd route group will be used.
Hope anyone have such observation and find out any workaround and/or contact Cisco TAC for assistance.
08-13-2008 05:53 PM
What worked for me was the service parameter "Stop Routing on Unassigned Number Flag".
08-27-2008 07:23 AM
Appreciate for the share.
Acutally, the issue was due to hang up local T1 port (no PSTN vendor issue) - after reset it came backup. So I didn't have chance to test out this parameter.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide