cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
446
Views
0
Helpful
5
Replies

Message Waiting Indicator - Unity 2.4

javentre
Level 1
Level 1

The WMI's don't seem to be functioning properly for my system.

When I go into the Messages Section for each user the Web Interface tells me that their Indicator Light is ON ... and the Telephone has the light on .... but in actuality there are no new messages. If I resync it (for that user or for everyone) .... the light goes off and the Web Interface also reflects an off status. It impacts more than one user and appears to be random. The event viewer is not showing anything irregular. Any Idea's?

5 Replies 5

javentre
Level 1
Level 1

I forgot to add a few things.

a Message can take 30 minutes (from the time it was ended - hang up) to the time it will set off the MWI.

We are not on a high volume office - it's for about 25 mailboxes.

My best guess is that Unity is trying to light the lamp X times before it's actually going on... we might be getting failures or the lamp code is being ignored by the switch for whatever reason (seen this before). Which switch and integration are you using here?

Can you run a message activity report for a user where you've seen these delays (i.e. where you leave a message and it takes 30 minutes to turn the light on)?

I'll look into running the report for today - and try to duplicate the problem.

Manufacturer: NEC

Model: NEAX 2000 IVS

Switch PBX Software version: ALL

Integration: ANALOG

Hi there,

I have the same problem. MWI light is on and the Display tells you that you have voicemail even though there is no new or unread message. Here is Message Activity report from one user that has this problem.

8/30/2002 9:32:39 AM OTHERS NEW MESSAGE 1 8/30/2002 9:32:39 AM NA

8/30/2002 9:32:39 AM OTHERS MWI ON REQUESTED 1 8/30/2002 9:32:39 AM NA

8/30/2002 9:32:39 AM TELEPHONE NEW MESSAGE N/A Unknown Caller 8/30/2002 9:32:39 AM N/A Unknown

8/30/2002 9:32:40 AM OTHERS MWI ON COMPLETED 1 8/30/2002 9:32:39 AM NA

8/30/2002 10:00:06 AM TELEPHONE LOGIN N/A N/A 8/30/2002 10:00:06 AM N/A Unknown

8/30/2002 10:00:21 AM OTHERS MESSAGE READ 0 8/30/2002 9:32:39 AM NA

8/30/2002 10:00:21 AM OTHERS MWI OFF REQUESTED 0 8/30/2002 10:00:21 AM NA

8/30/2002 10:00:47 AM TELEPHONE DELETE MESSAGE N/A Unknown Caller 8/30/2002 9:32:39 AM N/A Unknown

8/30/2002 10:00:49 AM TELEPHONE LOGOUT N/A N/A 8/30/2002 10:00:49 AM N/A Unknown

8/30/2002 10:03:21 AM OTHERS MWI OFF COMPLETED 0 8/30/2002 10:00:21 AM NA

This log indicates that the notifier is properly logged into the user's box and getting event updates and requesting the MWI off... which narrows the list of suspects down quite a bit... I think your next step here is to get some traces on the CM side (assuming you're using CM) to see where the MWI request is falling down up stream...

If you're using a PBX we can turn on some MIU traces to see the MWI requests actually going out on a port or across the serial link.