The problem is that the phone will remain registered to the Branch CUCM and what i would like is to use CFUR to route the call to a backup BRI at the Branch site.<div><br></div><div>What I'm not sure is what the state of the phone in the HQ CUCM. If I configure CFUR will the HQ CUCM follow it ?</div>
<div><br></div><div>Thanks.<br><br><div class="gmail_quote">On Wed, Apr 6, 2011 at 5:58 PM, Jason Aarons (AM) <span dir="ltr"><<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">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.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Dialing out from Branch would give fast busy, inbound would just go to voicemail if configured.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I would do a lot of controlled testing so you know what works/doesn’t., expected results during failure.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Ovidiu Popa<br>
<b>Sent:</b> Wednesday, April 06, 2011 11:52 AM<br><b>To:</b> cisco-voip<br><b>Subject:</b> [cisco-voip] CUCM split brain question</span></p><div><div></div><div class="h5"><p class="MsoNormal"> </p><p class="MsoNormal">
Hello everyone</p>
<div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Here's an unusual scenario that kind of puzzles me.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Here are the details:</p></div>
<div><p class="MsoNormal">- 2 CUCM with Clustering over WAN (HQ and Branch)</p></div><div><p class="MsoNormal">- Centralized PSTN Access at HQ (DID numbers routed to HQ)</p></div><div><p class="MsoNormal">- 1 phone with the Branch CUCM as primary and the HW CUCM as secondary</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Disaster strikes, the WAN link goes down and we have a split brain condition.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">What is the state to the phone on HQ CUCM? Will the phone be Unregistered or state Unknown?</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">And the most important question is will the HQ CUCM follow the CFUR if the state is Unknown?</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">
Thanks for your input.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Regards,</p></div><div><p class="MsoNormal">Ovidiu</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> </p>
</div><div><p class="MsoNormal"> </p></div></div></div></div></div>
<div><p></p><hr size="1"><p></p>
<a href="http://dimensiondata.stream57.com/04141pm/" target="_blank"><span style="color:blue;text-decoration:none"><img border="0" alt="DDIPT"></span></a>
<p><strong>
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.
</strong></p></div></blockquote></div><br></div>