I have a customer that is having an issue with MWI lights after they reboot their Unity server. They noticed this issue around the time the migrated from Exchange 2002 to Exchange 2003 (Migration was to new server platform not an upgrade).
When they perform a reboot of the Unity 4.0(3) server and lets say during POST of the server a subscriber listens to their Voicemail via Outlook (The state should be at this point MWI OFF). When Unity comes back online it displays the subscriber state as MWI ON (Even though they have NO new voice messages).
To fix this the customer has to go and run configuration setup again and within 5 minutes MWI is back to the state it should be.
This happens every time they need to perform a reboot of Unity
During startup Unity has to login to every mailbox and get the status of the mailbox. This can take a log time if you have a lot of users. Recently I was working on a customer that was VM only with dedicated Exchange servers and it took 45 minutes for 2500 subscribers.
Do you still have them problem after the notifier logs to the event log that it has finished syncing mailboxes?
What happens if you restart the notifier service?
What happens if you refresh the MWI status from the SA?
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...