[cisco-voip] UnityCx | MWI Throttle

[Daniel Pagan]

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.

Thanks

- Daniel


From: Jason Aarons (AM) [mailto:jason.aarons at dimensiondata.com]
Sent: Monday, June 16, 2014 12:01 PM
To: Daniel Pagan; cisco-voip at puck.nether.net
Subject: RE: UnityCx | MWI Throttle

We’ve moved on to SIP unsolicited notify ☺.

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.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Daniel Pagan
Sent: Monday, June 16, 2014 11:49 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] UnityCx | MWI Throttle


Folks:

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.

Thanks ahead of time.

Daniel


itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140616/acc8afbc/attachment.html>