[cisco-voip] FW: CUCM Route List

[Mark Marquez]

Thanks Ryan, that was the fix.  I overlooked that setting.  I was focusing under H.323 Clusterwide Parameters.

Mark Marquez
Unified Communications Specialist
Gold Systems, Inc.
4840 Pearl East Circle, Suite #106
Boulder, Colorado 80301
303.447.2774 say "Mark Marquez"
mmarquez at goldsys.com<mailto:loui at goldsys.com>

From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Wednesday, November 18, 2009 8:22 PM
To: Mark Marquez
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] FW: CUCM Route List

>From the aforementioned service parameters...
[cid:image001.png at 01CA68F5.3162DF80]
-Ryan

On Nov 18, 2009, at 4:29 PM, Mark Marquez wrote:


Here is some supplemental information regarding my previous email.  Here is a summary of the problem.

RouteList-1
   H323-HW-RG
  MGCP-GW-RG

I make a call that uses Route List (RL-1).  The first call is successful call via the H323-HW-RG.  I then disconnect the T1 cable to the H323 GW (creating a failover scenario) and my second call fails over successfully to the MGCP-GW-RG.  I make a third call, which again uses MGCP-GW-RG and the call fails.  All other subsequent calls also fail.

I ran a CCM trace and I see that on the second call attempt (first screenshot below) the H323 GW (10.10.32.2) sends back a H.225 RELEASE_COMP message with Cause i = 0x08E089 - Temporary Failure.  CUCM responds to this cause code by sending an MGCP CRCX message to the failover GW (10.10.32.1) thereby resulting in a successful call.


In the second screenshot where I made the third failed call attempt you'll notice that the H.323 GW also sends a RELEASE_COMP message but it has a different cause code Cause I = 0x080081 - Unallocated/Unassigned Number.  As a result of this cause code CUCM does not send the MGCP CRCX message to the failover MGCP GW and the call ultimately fails.    Any ideas on how to modify this behavior?



<image001.png>


<image002.png>





From: Mark Marquez
Sent: Monday, November 16, 2009 4:42 PM
To: 'cisco-voip at puck.nether.net<mailto:'cisco-voip at puck.nether.net>'
Subject: CUCM Route List

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.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091119/d4937c99/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 36033 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091119/d4937c99/attachment.png>