We have a problem lighting MWIs. After we leave a message, the following error appears in the event log.
FAILED TO SET MESSAGE WAITING LAMP FOR Brad Welch, EXT 1055, SWITCH 0, CLUSTER 0, REASON NO SUITABLE PORT.
In SAWeb, the ports are enabled for lighting MWIs. On the Brad Welch subscriber page, the MWI status shows OFF even though a voicemail was just left. Dialing the MWI DN from the phones lights the lamp. TSP settings match. Any ideas what is misconfigured?
Exchange 5.5 on box
2 port demo mode right now, -waiting for dongle to arrive.
This will happen when the system has been or is in a dual-switch configuration and the switch ID that is assigned to a subscriber (hidden if the system is now single-switch) is on a switch that is different than all ports configured for MWI.
Here's a couple of things to check:
1. On the subscriber page is there a listing for a switch choice?
2. On the SA ports page, is there is a choice for a switch for a range of ports? If so, what's there?
3. If there's not a choice for a switch on the SA ports page, check the registry for the ports....
Somewhere around in that area, there will the switches listed and the ports listed. What's listed for the switch(s) and for each port, what ID shows up for each switch?
The reason why the SA was showing the MWI is off is because that status is what Unity thinks what the light is not what the light should be. Since Unity knows that the MWI didn't work, that's why it thinks it is off.
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...