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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Turn off Merlin Mail?

Status
Not open for further replies.

bunkman

Vendor
Jul 16, 2002
46
US
We've just connected a Merlin to centralized VM, so we don't need MM anymore, but it may be awhile before the module can be removed from the system. Is there a way to deactivate the Merlin Mail system? The main reason being I don't want it to control any MW lamps.

-Bunkman
 
The best way is to delete all mbxs from the system. Then there are no mbxs to turn off and on mwl. Otherwise, you might consider busying out the slot. I usually don't like to leave a slot busied for long because the merlin tends to be a little particular sometimes and anything out of the norm seems to cause quirky errors. Realistically, by removing the ports from the calling group and extensions from the cover group, this should not be a problem. But for the sake of best practices, you should either delete mbxs or busy the slot until you are able to remove the board and reprogram.
 
I would change the coverage to the new vm UDP and then clear all mw lights thru maint. then remove the ports from the hunt goup of the old vm then make changes to the hunt goup to remove refrences to integrated vm and any overflow for delay aa. then shut down, pull out the card, power up and do a board renumber, this should take it out of memory, be sure to save to the flash card before doing any of this in case yoo have problems you can revert back.

 
I'm a little confused, when you went to the centralized Vm, you had to create another calling group with one non-local Ext. Then you had to assign that calling group a coverage group. When you assigned the coverage group, you should've just moved your existing one to the new vm calling group. Even if you didn't, you still had to assign the ext's to the new coverage group. Either way, there can be no duplication. The system will not allow you to assign a coverage group to multiple calling groups. As well, the system will not allow you to assign an Ext. to multiple coverage groups. So, with that said, it doesn't really matter if the Messaging is there or not, the calls shouldn't be going there anyway. It isn't a bad idea to do what gokings had mentioned, delete the mailboxes and remove the members from the old calling group. If you have the messaging, I know you said mail but you never know, you can log into the sysadmin and press 989CLEAR, and this will delete the whole VM, I don't think this works on the 007MLM. Good luck.
 
Yeah, but jinxs, think if the old mbxs had msgs in them that were unchecked. The switch takes a power hit. When it returnns to service...guess what it does? It refreshes MWL from the old and new voice mail. There's your potential MWL conflict. That's why you should always remove the board or delete the mbxs when you change systems.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top