I have 2 H323 gateways in a Route Group. Each gateway has an ISDN connection to a remote office.
When the ISDN connection goes down in the primary gateway the callmanager(4.1.3) won't send the call to the secondary gateway (because the gateway is still alive).
I know that if the primary gateway goes down, the CCM will send the calls to the secondary gateway in the route group.
But is there a way to let know the callmanager know when the controller goes down?
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 as explained above, but this behavior don't make sense to me, so we looked for other ways to do it in 1 case.
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.