[cisco-voip] CUCM split brain question

[Jason Aarons (AM)]

The phones don't really know about the CallManager's ICCS traffic being down unless they were registered across the WAN link and will re-register if the CallManager Group has the server in its list. Features that rely on the Publisher would be down but these are fewer and fewer. For example older versions of CallManager the CallFwdAll button required Publisher access.

Dialing out from Branch would give fast busy, inbound would just go to voicemail if configured.

I would do a lot of controlled testing so you know what works/doesn't., expected results during failure.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ovidiu Popa
Sent: Wednesday, April 06, 2011 11:52 AM
To: cisco-voip
Subject: [cisco-voip] CUCM split brain question

Hello everyone

Here's an unusual scenario that kind of puzzles me.

Here are the details:
- 2 CUCM with Clustering over WAN (HQ and Branch)
- Centralized PSTN Access at HQ (DID numbers routed to HQ)
- 1 phone with the Branch CUCM as primary and the HW CUCM as secondary

Disaster strikes, the WAN link goes down and we have a split brain condition.

What is the state to the phone on HQ CUCM? Will the phone be Unregistered or state Unknown?

And the most important question is will the HQ CUCM follow the CFUR if the state is Unknown?

Thanks for your input.

Regards,
Ovidiu





-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110406/251a8879/attachment.html>