<div>Hey Jorge,</div>
<div> </div>
<div>Actually I do have 25% of my ports assigned to only MWI and they arent part of the VMHuntGroup.</div>
<div>That is why i opened up the TAC case. Calls should not be going to these ports at all.</div>
<div>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.</div>
<div> </div>
<div>Joel P<br><br> </div>
<div><span class="gmail_quote">On 3/12/08, <b class="gmail_sendername">Jorge L. Rodriguez Aguila</b> <<a href="mailto:jorge.rodriguez@netxar.com">jorge.rodriguez@netxar.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang="ES" vlink="purple" link="blue">
<div>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d">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.</span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d">Hope this Helps;</span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d">Jorge Rodríguez Aguila</span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d">CCNA,CCVP</span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d">Senior Network Consultant</span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d">Netxar Technologies</span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d"><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:jorge.rodriguez@netxar.com" target="_blank">jorge.rodriguez@netxar.com</a></span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d">Office 787-765-0058</span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d">PCS 787-688-8530</span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d"><img height="34" alt="netxar" src="cid:image001.png@01C88434.9CDB9060" width="101"></span><span style="FONT-SIZE: 11pt; COLOR: #1f497d"></span></p>
<p><span style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<p><span lang="EN-US" style="FONT-SIZE: 11pt; COLOR: #1f497d"> </span></p>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p><b><span lang="EN-US" style="FONT-SIZE: 10pt">From:</span></b><span lang="EN-US" style="FONT-SIZE: 10pt"> <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Todd Franklin<br>
<b>Sent:</b> Wednesday, March 12, 2008 9:39 AM<br><b>To:</b> <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> [cisco-voip] MWI Collisions</span></p>
</div>
<div><span class="e" id="q_118a3cf14490ffab_1">
<p> </p>
<p style="MARGIN-BOTTOM: 12pt">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.<br>The entire event lasted maybe 15 minutes.<br>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):<br>
<br>"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. <br> <br>
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." <br>
<br>---<br><br>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!!<br><br>Thanks!</p></span></div>
</div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br></blockquote></div><br>