Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Maintenance Command to Turn Off Message Waiting
- Thread starter bgibsonin
- Start date
MitelInMyBlood
Technical User
There is no "command".
However, on the SX2000 and 3300 ICP systems you can turn ALL of them off by performing a data save/restore and rebooting across a partition (2K) or reloading and restoring the database on the 3300. A total service outage will result, approx 20 minutes for an SX2K, approx 1 hour for a 3300 (longer if VM messages are saved/restored).
The message waiting lamp status is not saved across a datasave/restore operation. Therefore all lamps will be off following this admittedly drastic procedure.
Once completed be sure to refresh your message waiting lamps via your voice mail server.
Prevent "the problem" from reoccurring by turning off the ability to send msg wtg in all station classes of service (except your voice mail ports, obviously).
This too means that you need to define and use separate classes of service. In a properly designed database you should be using separate classes of service for each type of device, i.e., a separate one just for trunks, another one for your VM ports and still another for your station sets. Some advocate taking that to the next level and have separate classes of service for TDM sets vs IP sets. In our SX2K systems we will typically use a dozen or more classes of service to accommodate specific classes of user (admins, execs, regular users, some wanting a 3-ring rollover, others want a 4-ring, etc). We also put modems and faxes in their own separate class of service to lock them down and prevent forwarding to or from, making sure modems inside the firewall are non-DID (even blocked from DISA) etc.
However, on the SX2000 and 3300 ICP systems you can turn ALL of them off by performing a data save/restore and rebooting across a partition (2K) or reloading and restoring the database on the 3300. A total service outage will result, approx 20 minutes for an SX2K, approx 1 hour for a 3300 (longer if VM messages are saved/restored).
The message waiting lamp status is not saved across a datasave/restore operation. Therefore all lamps will be off following this admittedly drastic procedure.
Once completed be sure to refresh your message waiting lamps via your voice mail server.
Prevent "the problem" from reoccurring by turning off the ability to send msg wtg in all station classes of service (except your voice mail ports, obviously).
This too means that you need to define and use separate classes of service. In a properly designed database you should be using separate classes of service for each type of device, i.e., a separate one just for trunks, another one for your VM ports and still another for your station sets. Some advocate taking that to the next level and have separate classes of service for TDM sets vs IP sets. In our SX2K systems we will typically use a dozen or more classes of service to accommodate specific classes of user (admins, execs, regular users, some wanting a 3-ring rollover, others want a 4-ring, etc). We also put modems and faxes in their own separate class of service to lock them down and prevent forwarding to or from, making sure modems inside the firewall are non-DID (even blocked from DISA) etc.
As mentioned, there is no command to do it. Do a locate feature on the set (loc feat ext XXXX) and see what type of M/W it is. If it's a dialed message waiting, look up the Message Waiting-Deactivate code and dial it plus the extension number, that'll kill the lamp. If it's a Callback Message, check the sets COS, enable Multiline Set Voicemail Callback Erasure Allowed to Yes, then press the Message key and follow the prompts to erase.
- Thread starter
- #4
I usually come to this issue sometimes on the 3300s i dont know if its alot lately because of the upgrade. One of my coworkers called tech support and its a bug in the new patch.
but i just go in the 3300 feature codes section and go to message waiting deactivate set it to whatever and i push *-- then the ext number and takes it off.
but i just go in the 3300 feature codes section and go to message waiting deactivate set it to whatever and i push *-- then the ext number and takes it off.
Mitelpassion
IS-IT--Management
where can I get this appliation MitaiBrowser...
brendonwright
Technical User
On my Mitel SX-2000, to turn on the message waiting lamp, it's #15XXXX (XXXX being the extension number.) #16 to turn off. It is the function of the phone switch to turn off/on the MW indicator, under the direction of the Voicemail server. The VM server should learn the switch's language.
Most modern voicemail integrations do not use the feature access codes for MW requests. They can either use set emulation to press virtual keys or on the most advanced systems they transmit CTI events to activate MW.
They not only know the language, they live it.
*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.
They not only know the language, they live it.
*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.
TheMitelGuy
IS-IT--Management
Say bye-bye to Embedded Voice Mail!
TheMitelGuy
IS-IT--Management
It's going to be phased out and replaced with a new embedded-type VM - w/Unified Messaging. Way more powerful all in the ICP.
My understanding is that the new Embedded VM will be based on the Nupoint.
As the Nupoint is now running on servers using the 6000MAS software (Linux) my expectation is that it will run on a separate harddrive within the system.
This is all speculation. (I don't work for Mitel)
*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.
As the Nupoint is now running on servers using the 6000MAS software (Linux) my expectation is that it will run on a separate harddrive within the system.
This is all speculation. (I don't work for Mitel)
*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.
TheMitelGuy
IS-IT--Management
It will be a "dumbed down" version of NuPoint.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
