Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

H323 Redundancy between two ISR gateways

I have 2 ISR gateways with one E1 circuit on both. In callmanager i have 1 Route list and one route group with both gateways identified. If i make outside call the call is routed to gateway 1 this is all ok. if all trunks busy on gateway 1 the call is created via gateway 2 and proceeds ok. Now the problem. If i fail the E1 on the firsat gateway i can see the initial call going to this gateway, the call is rejected due to the failure of the E1, but the call does not then try gateway 2 !! Any ideas would be helpfull. The callmanager is 5.1. I cannot use MGCP for htese gateways because i also need FAX support T38 which is not supported on MGCP with callmanager version 5.1

New Member

Re: H323 Redundancy between two ISR gateways


I have a same problem.

Can you resolve?

Please send to

Thanks a lot.

Cisco Employee

Re: H323 Redundancy between two ISR gateways

courtesy of gogasca:

H323 Failover

The default behavior in IOS, when there are no valid POTS dial-peers for a call to go out of, is to return “unallocated number” as a cause code to CCM. This can happen even if a t1 goes down. When the T1 goes down, the POTS peer is marked as down, and when CCM sends a call to the gateway, it'll return a UAN cause code to the ccm, causing CCM (by default) to stop hunting for other available gateways. There are ways to change the behavior using service parameters in CCM, but this behavior didn't make sense to me, so we looked for other ways to do it.

It turns out that you can issue the global command "no dial-peer outbound status-check pots" on the IOS GW, if you're opposed to changing the CCM behavior. What this command will do is cause the dial-peer to stay up. IOS will try and route the call, and when the T1 is down, it returns "No circuit available" to CCM. When CCM receives this cause code, it knows there's been a non-user error, and continues hunting, achieving the desired behavior.

In your case since it is H323 it will be retruning only H225 release comp message with proper code to continue re-routing.

The IOS code will translate any code we get from pots side to IP side

you may also use the search feature within netpro, probably someone already asked the same thing



if this helps, please rate



if this helps, please rate
New Member

Re: H323 Redundancy between two ISR gateways

it's works fine, +5 points for you.

Thank you

New Member

Re: H323 Redundancy between two ISR gateways

worked like a charm, thanks!!!!