had recently tested out a H.323-based voice gateway with 2 CCM (Publisher & Subscriber). As norm, we had the subscriber as the Active & Publisher as Standby for failover.
We then made a call out to the PTSN from an IP Phone, had the Subscriber CM services stopped, and expected the Publisher to failer over immeditaely w/o dropping the ongoing call. However, the call dropped & there was a message displayed on the IP phone indicating the CM has fallenback, and features were disabled. It then took about 20 to 30s for the IP phone to be reverted to the Publisher,but only after some push of the phone's button.
This wasnt the case when MGCP was used for the gateway.
Below is a brief description of my configurations. Would appreciate any feedbacks/comments. Btw, using CCM 3.1.4a, IP Phone firmware 4.8 & IOS
I'm pretty sure that's expected behavior. In an h.323 call, the CM is actively involved in the call and acts as a 'middle man'. If the CM process fails, is stopped or otherwise becomes unavailable, the call drops as you've described. MGCP doesn't have that limitation because the gateway and phone can communicate directly without the intervention of CM once the call is up.
er hunh, then whats the point of failing over when the ongoing call will be disrupted despite claims being made that existing calls will not be dropped, unless MGCP is used..? Is there any way 2 smooth out this H.323 failover transition ?
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...