<div dir="ltr">When you say that it does not appear to be happening, how are you checking that all of the publisher dial out ports are in use or unavailable? The MWI activity takes only a very short amount of time, so is it possible that your publisher is not 100% utilized. They only real way to test this, with 100% certainty, is to drop the publisher's ability to use the ports for MWI down to only a single port. If what you are describing is a large amount of MWI status updates at once, then this would surely force you into using subscriber ports.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 30, 2014 at 9:48 AM, Ted Nugent <span dir="ltr"><<a href="mailto:tednugent73@gmail.com" target="_blank">tednugent73@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks Anthony, <div>That is basically what we're seeing. We are sending a message to a large PDL and the cluster is only using the Publisher port group when sending MWI. Based on what is documented "<span style="font-family:arial,sans-serif;font-size:12.727272033691406px">If no dial-out ports on the publisher server are available, the subscriber server will dial out for MWIs and notifications" I would expect that once all the publisher dial out ports are consumed it would start rolling over to the subscribers dialout ports but this does not appear to be happening. I'm curious if this is a defect or WAD?</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">Unity Connection 8.5</span></div></div><div class="HOEnZb">
<div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, May 30, 2014 at 9:14 AM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway@gmail.com" target="_blank">avholloway@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-weight:bold;margin:0em 0em 7px;text-indent:0em"><font><span style="background-color:rgba(255,255,255,0)">Dial-out ports <br>(for MWIs and notifications)</span></font></div><font><span style="background-color:rgba(255,255,255,0)"><a name="1464d9a777e5d928_1464d44801011c9c_wp1073463"></a></span></font><p style="margin:1px 0em 6px;text-indent:0em">
<font><span style="background-color:rgba(255,255,255,0)">Beginning with the dial-out port that has the lowest number in its display name, assign half the dial-out ports to the primary server so that the primary server will handle MWIs and notification calls. Assign the remaining dial-out ports to the subscriber server.</span></font></p>
<p style="margin:1px 0em 6px;text-indent:0em"><font><span style="background-color:rgba(255,255,255,0)"><br></span></font></p><p style="margin:1px 0em 6px"><font><span style="background-color:rgba(255,255,255,0)">Under normal conditions, the Cisco Unity Connection cluster will handle calls in the following manner:</span></font></p>
<p style="text-indent:0px;margin:0px 0em 7px 0.25in"><font><span style="background-color:rgba(255,255,255,0)">•<img src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" alt="" width="19" height="2" border="0" style="border-width:0px">The subscriber server will answer most incoming calls. If no answering ports on the subscriber server are available, the publisher server will answer calls.</span></font></p>
<p style="margin:1px 0em 6px;text-indent:0em"><font><span style="background-color:rgba(255,255,255,0)"><a name="1464d9a777e5d928_1464d44801011c9c_wp1073526"></a><a name="1464d9a777e5d928_1464d44801011c9c_wp1073527"></a></span></font></p>
<p style="text-indent:0px;margin:0px 0em 7px 0.25in">
<font><span style="background-color:rgba(255,255,255,0)">•<img src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" alt="" width="19" height="2" border="0" style="border-width:0px">The publisher server will dial out for MWIs and notifications If no dial-out ports on the publisher server are available, the subscriber server will dial out for MWIs and notifications.</span></font></p>
<p style="margin:1px 0em 6px;text-indent:0em"><font><span style="background-color:rgba(255,255,255,0)"><br></span></font></p>Source: <a href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/7x/integration/cucm_sccp/guide/cucintcucmskinny/cucintcucmskinny205.html#wpxref92198" target="_blank">http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/7x/integration/cucm_sccp/guide/cucintcucmskinny/cucintcucmskinny205.html#wpxref92198</a><div>
<div><div>
<br></div><div><br>On Thursday, May 29, 2014, Ted Nugent <<a href="mailto:tednugent73@gmail.com" target="_blank">tednugent73@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I can't believe I've not run across this previously and I can't seem to find an answer in the docs. When you have a Unity Connection Cluster what determines which port group is used for MWI assuming you have a separate port group for each server within the same integration? <div>
TIA</div><div><br></div></div>
</blockquote></div><br><br></div></div><span><font color="#888888">-- <br>Anthony Holloway<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>