That is working as designed...<br><br>You should make sure your users cannot dial VM ports directly by using separate partition / search spaces.<br><br>I had this on a large install, and it was happening twice daily in some cases. As Ryan says below, this should only happen when the hunt group cant reach the primary unity ports.<br>
<br>Cheers,<br><br>Tim.<br><br><div class="gmail_quote">On Thu, Jun 4, 2009 at 12:18 AM, Robert Kulagowski <span dir="ltr"><<a href="mailto:rkulagow@gmail.com">rkulagow@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Ryan Ratliff wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'll defer to Pat or somebody with more (recent) Unity experience but Unity still sees all the ports as individual. It's only the CUCM side where you lose the tracking of individual ports.<br>
</blockquote>
<br></div>
We've had instances where Unity has failed over because for whatever reason, a call was answered on the secondary Unity. And that triggers the entire "Primary Unity must be dead" failover sequence.<br>
<br>
Does switching to a trunk versus individual ports mitigate that?<div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br>