Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: ctmedina on March 03, 2010, 01:45:36 PM
-
Hey Everyone,
Has anyone had this? I am getting reports from users that the MWI ligts are staying on even when the users do not have any messages. I am not really sure where to begin. I am using a 3300 4.0 or should I say MCD 4.0 with the embedded voicemail. It is a CX controller.
All the phones are 5330s. Just a simple setup. No alarms, no warnings, nothing out of the ordinary. Can anyone point me in the right direction?
Carlos
-
Do this first:
With the handset down, press the msg button. then press the read messages button. It should show you what left the message. If someone other than the VM light the light, beat them.
If the message came from VM, you may have a port that is not in your vm hunt group. Be sure all VM ports are in your VM hunt group. If yes, call each of the ports to be sure they all answer.
Ralph
-
probalby a callback set by accident. do 'loc feat ext xxxx' in maint commands
-
When the user pushes the envelope key it says "call me back"???????????????????
Carlos
-
I forgot a step.
Press the Call Me Back Key.
Just be sure the phone is on hook when you do it.
Ralph
-
the easiest way to clear is for them to complete the callback. So as Ralph says press the msg key and then it displays 'callback' press the yes softkey and it will display the number that set the callback press call and it will clear once the other party answers
-
Forgot to mention: to erase the call back message, the COS of the phone must allow it.
Ralph
-
Which class of service setting? does it actaully say call back cancel or something like that?
Carlos
I was going to post my exported COS that is assigned to those phones, but it just looked like crap when I pasted in the post.
-
I can't remember the exact name but its something the effect of 'Call back Erasure Allow'
-
I did not find the COS setting relating to that. I am running 4.0 on that system. One thing I did not mention, was that the ext were moved to this system from another 3300 system running a 9.x release. We used EntMan/OpsMan to move them after setting up the controller.
Carlos
-
The actual COS option is "Multiline Set Voicemail Callback message erasure allowed" Turn it to yes and then you will be able to delete the message light from the phone.
Ralph
-
Awesome, that was it. Thanks a gazillion Ralph. You do not know how crazy I was going trying to find that darm COS setting. After staring at them for a while things just start to get blurry!
It would be awesome if you could tag a discussion with something to indicate that the question was actually answered. I know it would save me digging thru the forums looking thru just questions without answers. I always try to dig thru the forums to find stuff before I post a question. I know how annoying it can be to answer the same question over and over again...
Carlos
-
Good question - I'll look into it....
-Chak
-
Here's a fun one.
Just today I had a customer that had a MWI key on her phone for the mailbox of the main number.
Somehow she managed to light the light from her phone. Now the light is on, when she presses it, it trys to ring her own phone but since she is on the phone (because she pressed the MWI button) she gets a busy tone. She can't clear the light.
Had to send a tech to site to resolve. The extn for the MWI turned out to be an analog line that existed only so that we could have a MWI key. Had the tech put his butt set on it and call the other phone. Light goes out because they talked.
Such fun but another example of some of the weird things you can see with MWI's.
Ralph
-
And since I'm thinking about it.
Had a phone with a light on that wouldn't go out. Tech replaced the phone, deleted and recreated the phone but couldn't turn it out.
If you see something like this, try the simple thing first: dial the msg wtg on code + the extension number of the phone. Then dial the msg wtg off code + the extn of the phone. Light goes out. Like magic.
Ralph
-
Hello,
As mentioned, if the user has a display phone -
on hook.
press message waiting light.
message says call me back.
select yes option.
display says call speed dial to voicemail (if it was a callback error)
select erase.
If not using a display phone, from call xpress deactivate the MWI in the users voicemail account (callxpress - administration). Apply changes. And then reactivate MWI.
I had both our PBX and CallXpress voicemail vendor look at this situation for us. It had to do w/ the way the call xpress syncs the MWI lights every night. We use dialogic cards for voicemail ports. I was told IP integration on our voicemail platform would take care of the issue.
Regards,
Mike G.
Seattle, WA
-
I had the same thing happening to me yesterday. Not a call back situation. 2 of my phones (1 5212, 1 generic sip) has the MWI on all the time even if there is no message in the mailbox. Drove me crazy trying to check my provisioning.
What happened was I tried couple of days ago to use my last VM port for RAD and it failed terribly. Later I changed RAD to 1st port and it worked. So I returned the last port to embedded VM. And that somehow messed MWI up (even after rebooting the box).
I tried *91+extn (FAC: Message Waiting - Deactivate) from any extn and it worked. MWIs are not blinking anymore.
On the flip side, it is very interesting that any extn can dial *90 (FAC: Message Waiting - Activate)+target extn and turn target station's MWI on and drive the other guy crazy...
-
The ability to turn the light on for someone else is a real pain.
It's a legacy item left over from the old 2000 days when not everyone (can you believe this now?!!) had voice mail systems.
Can be turned off in COS.
I believe that putting the RADs on the 1st ports is recommended.
I do like the idea of creating a hot desk phone that has a VM COS with permanent DND and putting it in the VM hunt group. Then you can kill a light remotely if needed.
Problem for me is I can't understand why this happens. Doesn't matter the VM or even the integration apparently. It's like the MWI pointers get lost.
Ralph