Unity version is 4.04 SR1 with ES 35,40 & 95. TSP is 8.1(2)2. 72 ports configured. 1-40 for CallManager and 41-72 for 4 seperate PIMGs. 38 and 39 are set for MWI only as well as 47, 55, 63, 72.
Problem: MWI was not working today for CallManager extensions or PBX extensions. Event log on Unity showed no errors. Resynch MWI did nothing. The subscriber page in unity under messages section showed MWI Request failed during time of problem. This was on several Subscribers that we checked.
Port status tool was not showing and MWI dialout attempts.
We Disabled the Dialout MWI on the PIMG ports then Unity was able to send MWI to IP phones on Call manager. We then enabled the PIMG ports again and test messages left for both CallManager and PBX users resulted in proper MWI indication.
Any ideas what the root cause may have been? When attempting to set MWI for a CallManager extension does Unity still start at the highest port and timeout until it reaches a port that connects to CallManager?
I have no guesses on the root cause. For your second question though, each subscriber is associated with an integration and MWIs will follow this association. Thus if a subscriber is associated with the CCM integration, Unity will send all MWI requests for that subscriber to CCM ports.
Great, the info on the MWI requests is an important piece of the puzzle. Now we just have to figure out why the apparent lockup of one of the PIMG ports prevented MWI changes for the CallManager extensions.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.