[cisco-voip] MWI Collisions

[Joel Perez]

Hey Todd,

Same issue happened to me yesterday at one of my customers site. Pretty much
took all inbound calls down as well as VM access.
I opened a Tac case and I am waiting final resolution. But in the meantime
this system did not have the UnityDST patch installed nor the W2k3sp1 dst
patch installed either. I am waiting for TAC to see if this was caused by
the DST change or not. Other than that no other errors were logged in the
Event logs. System is fine now.

Joel P.


On 3/12/08, Todd Franklin <toddnh65 at gmail.com> wrote:
>
> Yesterday we had a failure with the system whereby calls coming in on the
> PRI were not happening, but we could call out on the PRI.
> The entire event lasted maybe 15 minutes.
> When I looked at the Unity event viewer, I see many THOUSANDS of these
> during that timeframe (on average it looks like 60 every second were
> logged):
>
> "Cisco Unity-CM TSP device 20 (Cisco Unity port 16): An attempt to turn ON
> the message waiting indicator (MWI) for extension 1212 failed because a
> collision occurred with an incoming call on the same port.
>
> The MWI request will be retried. But to prevent collisions, we recommend
> that ports setting MWIs be isolated from ports handling incoming calls. If
> the MWI status remains unchanged for an extended period of time or if there
> are many of these warnings from Cisco Unity in a short period of time, there
> may be an MWI misconfiguration or another problem."
>
> ---
>
> Any ideas anyone?  Unity looks quiet today, but this was a bizarre failure
> right out of the blue.  If I need to do something to avoid a repeat of this,
> I'm more than willing!!
>
> 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/20080312/a9af6280/attachment.html