[cisco-voip] CCM Cluster Failover TImes

[Ryan Ratliff]

If you have call survivability enabled on both CUCM and the H.323 gateway then the call will stay up until either the RTP stream dies or the parties hang up.  

No phone will ever reset, failover, etc while it's got an active call.

If you are 7940s and 60s then forget geometric TCP. You are looking at an idle phone taking probably 90 seconds (depending on where it is in the keepalive cycle) to failover.

-Ryan

On Dec 17, 2010, at 11:11 AM, David Zhars wrote:

I am posing a scenario, that the Pub has just crashed.  Maybe the janitor accidentally pulled the power cord, or a breaker has tripped and my battery backup was dead and I didn't know it (these have happened to me before!)

It sounds like 8.5.1 (is Cisco up to 8.5.22 yet, heh heh, sorry my OT rant about rapid version increases) has a real fast failover.  I understand it depends a bit on the phones too, these are mostly 7940s and 7960s.  

My understanding is that with an H.323 gateway, the call will stay up, and the phone will reset once the call terminates (assume the call comes in on an FXO port on the 2801).

Dave

On Fri, Dec 17, 2010 at 9:55 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
What is doing the failover?

For phones there will be differences in model, phone load, and perhaps even protocol.  Gateways will also have different behavior for SIP, SCCP, MGCP, and H.323.

-Ryan

On Dec 17, 2010, at 10:45 AM, David Zhars wrote:

Upgrading to CM 8.0 in a week.  We will install a Pub/Sub setup.

Wondering what the failover times are typically (assume an unexpected failure of Pub).  
I have been told variously that it's instant, and that it's a minute or so.
Does failover time vary based on gateway type (H.323 versus MGCP)?

Thanks.
_______________________________________________
cisco-voip mailing list

cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101217/d2c71fa4/attachment.html>