MW Light not working

[itguy399]

I cannot get MESSAGE WAITING LIGHT to work

This is Release 7 software and assumed by default if the user got a VM he/she would see a light on the phone. Phones are 4412D.
I've added the extension in the source numbers V710, HSales, HCustomerService.

Any help would be appreciated

 

[Westi]

I have plenty of 4400 series phones and no issues so this might be a specific issue to your hardware or configuration.

Try a different user on the same phone by logging into that set. Maybe the phone is broken too you never know.
Does the MWI work on any user or phone in the system?

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Interrupt the silence only if you improve it by saying something, otherwise be quiet and everybody will be grateful.

 

[itguy399]

Thanks for the quick response I do see in the device type for the extension it says device unknown. I have a total of 8 extensions and only 2 display the device type, all other extensions say Device Unknown. So Message Waiting Light is working on only 2 of the 8 phones. I dont believe its the phone because I plugged the same phone in different ports and it only works in the user port that displays the Device Type correctly.

 

[NYSTECH]

Are you plugging these 4400 set into the base module or do you have an digital expansion module?

I believe that the 4400 series phones will on work on the expansion module not the base/ ip500 for version 7.0.

I could be wrong on the version though

 

[itguy399]

They all plugged into 16 port expansion module, system has legacy card carrier

 

[Westi]

should still show the MWI, try a different phone if you have.

NYSTECH the 4400 series works in no release on the processor ports, only on expansion ports. fun with a customer that has those and other Avaya phones and moves them around, then they call and say the phone displays "barred". I have a customer that calls at least once a month and I tell them every time that it is the port. Oh well customer service can be painful sometimes I guess.

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Interrupt the silence only if you improve it by saying something, otherwise be quiet and everybody will be grateful.

 

[itguy399]

Thanks, I unplugged them, rebooted the system twice and now the MW Light works.

Now how can I set a button to light when the Hunt Group has a VM Message and can they check it by pressing the button, right now I have users who belong to two or three hunt groups and they cant tell whether they have VM for thier extension or the hunt group.

 

[smokinjoe2938]

under their source numbers add a capital H followed by the hunt group name, also give them a visual voicemail button so they can tell which group has the new voicemail message.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[stivtaber]

I recently had the same issue, date on the IPO was wrong. Messages could be seen in visual voice but would not do MWI on 1400's, or allow visual voice management.

Changed the system date, deleted the offending messages using Embedded File Management and everything started working as it should.

Stiv Taber
Certified in Convergent Network Technologies
APSS - SME Communications
PA - Implement IPO Professional Edition