There's a couple of things that will determine if MWI's will be attempted multiple times and using different ports. The first determination would be if there are MWI retries set on the SA switch page. If the retry setting is set at 1, there will be at least 2 attempts to light an MWI for a single new message. I say "at least" because there would be at least 1 normal request and 1 retry request sent. These attempts would have to be deemed "successful" in Unity's eyes. "Success" is determined in different manners depending upon the integration.
If the MWI request was not successful, it doesn't count against the normal and retry setting amount. So if for whatever reason MWI's are failing intermittently or consistently on a certain port, the actual MWI's sent out could rise. Make sense?
Another reason why MWI's being initiated multiple times or on multiple ports could be due to Multiple CCM cluster support. In this case, there would be an MWI request (plus any subsequent configured retries) happening on each connected CCM cluster. Unity doesn't know which cluster a subscriber belongs to, so it sends out MWI requests to all clusters.
What is the integration type that is being used? Are retries configured? Are there any warnings or errors in the event log? Are there any complaints from subscribers saying that MWI is not working properly?
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...