MWI doesn't turn off

[slapin]

MWI doesn't turn off even there is no messages in the VM box. Feature code for MWI ON/OFF is not working. MiTAI brouser indicates that for this patricular DN MWI is ON. Trying to cancel, it says OK and nothig changes. What else could light up MWI.

 

[Lundah]

Any telephone with access to "Send Message" feature can light MWI on a phone, not just VM. What platform is this on?

 

[slapin]

ICP3300MX, In the VM log I see that VM process sends feature code to turn MWI off but there is something else. I'm just wandeting is there any way to trace it down to the source?

 

[Lundah]

loc feat ext <extension number>" will tell you if there's an active callback on a set, but the only way (that I know of) to find out where it came from is to actually go to the set and press the "Message" key.

 

[slapin]

Looks like that's it

Active Features :
Message Waiting Lamp On
Callback Messages : 1

"***" For the answer.

 

[Lundah]

What type of phone is it? "***" is a strange one, unless you happen to have something with that as it's DN or name (don't know why you would, though).

 

[kwbMitel]

If this phone is a display set and the Message Status Inquire Option is turned on in COS the message can be erased at the desktop thru the message key and softkeys.

You can also determine thru this method who initiated the request.

*******************************************************
The secret to success is knowing who to blame for your failures.

 

[slapin]

***" - It's triple thank you. I knew about this feature and it never was the issue and I just didn't check it. The user is located at "far far away" site and I cannot see what's on the screen. Besides that it's a perfect confirmation of follwing rules.
1. Users can't remember
2. Users can't read
3. Users can't control the Mouse
4. Users do the unexpected

I was told that MWI is blinking but there is no messages in VM box. It's 5212 phone and it has indicatin about callback, but see item 2. All users get training session, but see item 1. Nobody is using callback feature as far as I know, but see item 4.

 

[Lundah]

The only way to clear the existing callback is to do it from the set.

To keep it from happening in the future, change COS option "Disable Send Message" to "Yes" for all COS's (except for the COS used by the Voicemail's MWI ports), and clear any assignment for "Callback - Setup" in Feature Access Code Assignment.

 

[slapin]

Thank you guys.
I don't want to apply any extra limitations for users. We are trying to be user fiendly as much as posible. I just put this solution to our knowlege database and next time when user cannot read what's on the screen I'll be able to help him, just more job for us. What's the point to have whole bunch of advanced features and disable all of those.(except some special cases) I was talking that callback is not very popular feature and I didn't think that it could be the source.
In my case when I cannot solve the problem it's usualy very complicated and it's all because of lack of brainpower or very simple and I'm just overlooking it.