[cisco-voip] H323 Gateway redundancy

[Kevin Thorngren]

Hi Jimmy,

Konstantin is correct that rerouting is based on the disconnect cause  
code.  With a PRI down, I believe, the GW uses the 8081 disconnect  
cause code which is "Unallocated or unassigned number".  You can look  
at this web page for disconnect cause codes:
http://www.cisco.com/en/US/tech/tk801/tk379/ 
technologies_tech_note09186a008012e95f.shtml

In the case of 8081 then the CallManager service parameter of "Stop  
Routing On Unallocated Number" needs to be set to false for CCM to  
reroute the call.

If all the B Channels are in use I am not sure what the cause code is  
but it might be something like 8083 which is "No route to destination".  
  In this case the CCM should try the next device in the route list.

You can use "debug h225 q931" to see the disconnect cause codes sent  
back to CCM.

If the GW is inaccessible via IP then the CCM won't be able to create a  
TCP connection to it.  CCM will then try the next device in the RL.

Also, if you have done so already, make sure to verify that CCM can  
send a call out each of the GWs by having a RL that contains only one  
GW.

Kevin
On Aug 10, 2006, at 5:49 AM, Fedorov, Konstantin wrote:

> Hello,
>
> Look this
> http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/ 
> sys_a
> d/4_1_3/ccmsys/a03rp.htm#wp1045311
>
> good describtion.
>
> But, rerouting depends of cause value of disconnect(release)
> I guess that if GW down - there is no h225 tcp session  and rerouting
> not work.
>
>
> -----------------------
> Sincerely Yours,
> Konstantin Fedorov
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jimmy Pale
> Sent: Thursday, August 10, 2006 6:09 AM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] H323 Gateway redundancy
>
> Thought I would repost this.
>
>
>
> Three different routers with PRIs are set up as h323 gateways. In
> CallManager those gateways are added to three different route groups  
> and
> those route groups are added to a route list. If the PRI in the first
> gateway, in the first route group of the route list is down or all
> channels
> in use the call will not then be sent to the next route group/gateway.
> The
> call fails with reorder. There are no gatekeepers. Am I correct in
> saying
> that this will not work with H323 gateways in Callmanager? Or is there
> some
> setting or configuration in CallManager and/or on the H323 voice  
> gateway
> that needs to be set to allow this to happen?
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>