Sticky Message Waiting Light

[cg11]

I have a Message waiting light that behaves erratically on a Small Office Edition with embedded VM.

I have a receptionist phone x206 and a HG mailbox x296 setup to light the MWI on x206. When you leave messages on both x206 and x296, then check them, the light still stays on. Also, sometimes there is no light on whilst there is a message in x206 or x296 vm boxes.

Catalyst has told us to remove the user, merge the config, then add the user back in, and merge again. This does not work!

Any insight to this would be helpful. It's driving me and my customers batty........!@##@@#$.

More info: X206 simply has an H296 & V206 setup under "Source Numbers" on x206 users tab. A VMcollect button was setup to collect the VM for hunt group 296.

 

[hohumIPO]

what version?

 

[cg11]

Sorry, forgot to mention versions. IPO was at 3.0.44. It has been upgraded to 3.0.59. MWI problem still exits.

 

[allenkitchen]

FWIW - I have an IPO 412 now running 3.0.59, VM PRO 3.0.17.

Have found this to be highly reproducible: when a user's MWI is controlled by both the presence of new item(s) in their own VM and ALSO in a HG's mailbox, the algorithm that turns ON the MWI on new mail in the HG mailbox works - but the algorithm that turns OFF the MWI based on the HG mailbox's status doesn't work.

Probably related: the icon-based MWI indicators in the SoftConsole BLF-like display panes work similarly. In other words, for HG mailboxes only, MW indicators come ON when there is a new message but do not go OFF when the message is no longer new. Reloading SoftConsole causes the correct current status to be displayed - and my attendant reloads about 6x per day, just before and after checking for msgs in several group mbx's.

 

[Belrick]

Known bug, reportedly fixed in 3.0(68)

 

[SuperJenks]

That was a known bug in 3.0.xx I went around in circles on this problem at two different sites. This issue was escalated to tier 3 engineers at avaya and they were able to reproduce the problem but never came up with a fix for me. When the problem was finally admitted by avaya, it was too close to the release of 3.1 to implement the bug fix. As far as I know, there is no fix for this. One thing I did notice is it happened alot on group mailbox and personal mailboxs. For those users who have notification for more than one box was really affected. The voicemail system doesnt check the message status of multiple memeber boxes before lighting or un-lighting the lamp. Meaning: If you have a message in your personal box and a message in a group box that lights they light on your phone, the vmail will turn off the light after you check you personal box, but does not check to see if there is still a message in the group box. There is no fix for this. Sad to say. Unless they never told me about it.

 

[cg11]

We upgraded the SME to 3.0.67 and tested in our labs. Sticky light seemed to have been fixed. We then installed at customer location and they said the MWI problem was back in 2 days. Sad to say, but customer is difficult to work with and has asked us to pull the system out.

I hope this is truely fixed in 3.1. This has caused us much time and grief.

 

[kristiandg]

I'm sorry to say, I'm running 3.1.2901 and it still happens. I'll be testing 3.1.44 later in the week to see if that helps.

Kris G.