<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
MWI refresh and broadcast messages are the primary triggers I know of.<br>
<br>
Reducing the number of ports will not matter if you increase delay and
concurrent calls. though with that combination fewer ports will be
used for MWI so you might as well re-allocate them to answering calls.<br>
<br>
/wes<br>
<br>
On Thursday, September 03, 2009 2:45:46 PM , Lelio Fulgenzi
<a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a> wrote:<br>
<blockquote
cite="mid:85707135.1163691252003546844.JavaMail.root@simcoe.cs.uoguelph.ca"
type="cite">
<style type="text/css">p { margin: 0; }</style>
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">Thanks
Wes. Think I need to make these changes even with fewer MWI ports? I'm
wondering if MWI refresh is also affected by this?<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
"Bad grammar makes me [sic]" - Tshirt<br>
<br>
<br>
----- Original Message -----<br>
From: "Wes Sisk" <a class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a><br>
To: "Lelio Fulgenzi" <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a><br>
Cc: "cisco-voip voyp list" <a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><br>
Sent: Thursday, September 3, 2009 2:39:40 PM GMT -05:00 US/Canada
Eastern<br>
Subject: Re: [cisco-voip] too many MWI ports?<br>
<br>
<link href="/zimbra/css/msgview.css?v=081117021119" rel="stylesheet">
Numerous cases about this. first attempt to fix was<br>
CSCsf99708 MWI message optimization <br>
<br>
net result CM cannot process messages as fast as unity can send them
(due to thread context switching inside the ccm process).<br>
<br>
workaround is:<br>
"In Connection Administration on the Port Group page, there is a group
<br>
of MWI settings. You might try the "Delay Between Requests" or<br>
"Maximum Concurrent Requests" settings."<br>
<br>
decrease number of concurrent requests and increase delay between
requests.<br>
<br>
/Wes<br>
<br>
<br>
<br>
On Thursday, September 03, 2009 2:09:09 PM , Lelio Fulgenzi
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:lelio@uoguelph.ca" target="_blank"><lelio@uoguelph.ca></a>
wrote:<br>
<blockquote
cite="mid:81927208.1151401252001349248.JavaMail.root@simcoe.cs.uoguelph.ca">
<style>p { margin: 0; }</style>
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">so
i just sent out a VM to a distribution list and phones registered to
the same subscriber as the voice mail ports got a fast buy instead of
dial tone with "high traffic" message.<br>
<br>
the only thing I can think of is that because all my voice mail ports
are set to MWI enable, the process of trying to send out 4000 MWIs (via
140 ports) caused the subscriber to hiccup.<br>
<br>
is this expected behaviour? is too many MWI ports a bad thing?<br>
<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
"Bad grammar makes me [sic]" - Tshirt<br>
<br>
</div>
<pre><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
<br>
</body>
</html>