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

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

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

H323 in Route Lists

I'm just a trying to figure out if I have 2 Route Groups in a Route List and the gateways are H323, how does the Route lists know that the PRI is down? I know that in MGCP it will failover to the other Route Group, but does it do the same for H323 PRI and POTS?

1 REPLY
Green

Re: H323 in Route Lists

Tdefault 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,

(CCMAdmin|Service|Service Parameter| Stop hunting... flags) 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.

232
Views
12
Helpful
1
Replies