[cisco-voip] Unity Connection Cluster Port usage for MWI

[Ted Nugent]

Confirmed, I pulled the usage report and I can see many many MWI hits on
the Pub during the timeframe that the PDL was called and zero MWI on the
subscriber. It appears to just be queuing MWI on the Pub ports as opposed
to them overflowing to the sub. If that's a WAD, I'm fine with it, it just
seems strange why its not overflowing.


On Fri, May 30, 2014 at 2:15 PM, Ted Nugent <tednugent73 at gmail.com> wrote:

> I need to confirm this to be 100% certain but from what I'm being told
> they are looking at the the port activity report from the serviceability
> page, assuming the report is correct none of the subscriber dialout ports
> are being used. They are sending to a large distribution list, with many
> more members than there are dialout ports and the activity report shows the
> calls hitting the Pub ports about 48+ times and the subscriber ports are
> not being touched.
>
>
> On Fri, May 30, 2014 at 12:44 PM, Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
>> 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.
>>
>>
>> On Fri, May 30, 2014 at 9:48 AM, Ted Nugent <tednugent73 at gmail.com>
>> wrote:
>>
>>> Thanks Anthony,
>>> 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 "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?
>>>
>>> Unity Connection 8.5
>>>
>>>
>>> On Fri, May 30, 2014 at 9:14 AM, Anthony Holloway <avholloway at gmail.com>
>>> wrote:
>>>
>>>> Dial-out ports
>>>> (for MWIs and notifications)
>>>>
>>>> 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.
>>>>
>>>>
>>>> Under normal conditions, the Cisco Unity Connection cluster will handle
>>>> calls in the following manner:
>>>>
>>>> •The subscriber server will answer most incoming calls. If no
>>>> answering ports on the subscriber server are available, the publisher
>>>> server will answer calls.
>>>>
>>>>  •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.
>>>>
>>>>
>>>> Source:
>>>> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/7x/integration/cucm_sccp/guide/cucintcucmskinny/cucintcucmskinny205.html#wpxref92198
>>>>
>>>>
>>>> On Thursday, May 29, 2014, Ted Nugent <tednugent73 at gmail.com> wrote:
>>>>
>>>>> 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?
>>>>> TIA
>>>>>
>>>>>
>>>>
>>>> --
>>>> Anthony Holloway
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140530/64333b72/attachment.html>