[cisco-voip] MWI Collisions

[Joel Perez]

Hey Jorge,

Actually I do have 25% of my ports assigned to only MWI and they arent part
of the VMHuntGroup.
That is why i opened up the TAC case. Calls should not be going to these
ports at all.
Im kinda going to guess that since the ports between Unity/CUCM
de-registered at around the same time then that would cause Unity to use any
available registered ports for inbound calls also. But that is only a guess,
still waiting on TAC to get back to me.

Joel P


On 3/12/08, Jorge L. Rodriguez Aguila <jorge.rodriguez at netxar.com> wrote:
>
>  Do you have Dedicated MWI ports? It looks like you don't. As a rule of
> thumb, you should dedicate 25% of your ports to MWI, Meaning you do not send
> calls to these ports on the auto attendant Hunt Group. On the Unity, you
> should also set them to MWI only. This Should fix your problem. Keep in mind
> that by doing this you are effectively reducing the amount of port that will
> answer and depending on you port usage, you could be in need of adding
> ports. Set up 4 ports for mwi and 12 for Voice calls, If 12 is not enough,
> your next step should be to add ports, no to reduce the amount of MWI
> dedicated ports.
>
>
>
> Hope this Helps;
>
>
>
>
>
> Jorge Rodríguez Aguila
>
> CCNA,CCVP
>
> Senior Network Consultant
>
> Netxar Technologies
>
> jorge.rodriguez at netxar.com
>
> Office 787-765-0058
>
> PCS 787-688-8530
>
> [image: netxar]
>
>
>
>
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Todd Franklin
> *Sent:* Wednesday, March 12, 2008 9:39 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] MWI Collisions
>
>
>
> 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/74a95a98/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 6292 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20080312/74a95a98/attachment.png