<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#404040;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#404040">Thanks Jason. I’m actually referring to UnityCx ports assigned to a SIP port group. The environment is indeed using SIP NOTIFY for MWI. However, Conversation Manager traces and RISDC logs show that only a specific
number of ports are used during a system-wide MWI resync, meanwhile over 100 ports are available and also configured for MWI dialout. These ports are released by the MIU once UnityCx receives the 200 final response, but the MIU never exceeds a specific number
of ports for MWI usage during the resync task. I’m wondering if MWI throttling is responsible for limiting the number of simultaneous ports allocated for MWI functionality and, if so, how that throttling mechanism is designed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#404040"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#404040">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#404040"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#404040">- Daniel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#404040"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#404040"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Jason Aarons (AM) [mailto:jason.aarons@dimensiondata.com]
<br>
<b>Sent:</b> Monday, June 16, 2014 12:01 PM<br>
<b>To:</b> Daniel Pagan; cisco-voip@puck.nether.net<br>
<b>Subject:</b> RE: UnityCx | MWI Throttle<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">We’ve moved on to SIP unsolicited notify
</span><span style="font-family:Wingdings;color:#1F497D">J</span><span style="color:#1F497D">.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Was it 8x and higher you get 250 SCCP ports per server for free…the licensing model moved on to per-user versus port based. Don’t quote me I don’t get to do anything with licensing other than install it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Daniel Pagan<br>
<b>Sent:</b> Monday, June 16, 2014 11:49 AM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> [cisco-voip] UnityCx | MWI Throttle<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
<p class="MsoNormal">Folks:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hoping someone can give me a bit of information on UnityCx’s MWI throttle mechanism. Does the MWI throttle mechanism limit the number of ports that can be reserved simultaneously for MWI events? Unfortunately an online search only brings
a known defect that references the MWI throttle mechanism – it doesn’t provide much detail on its behavior or design.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks ahead of time.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Daniel<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
<br>
<span style="color:white">itevomcid</span> <o:p></o:p></span></p>
</div>
</body>
</html>