rratliff at cisco
Nov 16, 2009, 6:49 PM
Post #2 of 2
(318 views)
Permalink
|
With MGCP the failover (hunt) happens because when the cable is unplugged the endpoint unregisters, and CUCM knows it can't send a call out using it. With the H.323 gateway we will only continue to the next device in the RL under certain circumstances, and it depends on the release cause we get back from the gateway.
Check the CUCM service parameters to see the conditions we still stop hunting on. Then compare this with the disconnect cause you are getting from the H.323 gateway when you want it to go on to the MGCP one and adjust accordingly.
-Ryan
On Nov 16, 2009, at 6:41 PM, Mark Marquez wrote:
Are there any special rules regarding H.323 and MGCP gateways configured within the same CUCM Route List. I have a route list with two route groups. RG1 has the H.323 GW. RG2 has the MGCP GW.
RL-1
RG1 (H.323)
RG2 (MGCP)
In the above configuration, failover to the MGCP GW doesn’t work.
RL-1
RG2 (MGCP)
RG1 (H.323)
I modify the Route List to include RG2 and then RG1 (as illustrated above) and failover works as expected. FYI, I cause a failover by unplugging the T1 cable from the controller.
I also tested just using RG1 or RG2 within RL-1 and calls complete successfully. Any help is appreciated.
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip
|
