Message Waiting Lamps

[killbox]

Hey everyone. I'm not the most advanced on the Definity, so here's where I'm at...

I have an account where their message waiting lamps are not lighting?? Can't seem to get them to light again. We've even went to the extreme of rebooting the Audix and the Definity. It's a release 6 I believe.

Thanks,

KILLBOX

 

[dmoore7648]

Are they regular users or call center agents with agent login ID's?

 

[killbox]

Well, I have about 12 people in an ACD, but everyones lamps aren't lighting.

KILLBOX

 

[AvayaArmy]

Try Busyout & release the station Or Remove and re-add the station. That should work.

 

[orypecos]

The voice mail will only try to light the lamps once. If there was some kind of trouble before, rebooting won't help even if it clears up all the problems 'cept the message waiting lights. It depends on what type of audix u have, but it is in the Audix where u need to work. I believe an audix of the mailboxes will update the message waiting lights.

 

[killbox]

Well, I've had problems like this before and I've cleared the lamps in the system. But that's not working now. I'll try and remove and add the station.

Is there a system wide message lamp reset on the system??

KILLBOX

 

[marcell55]

Did this just happen suddenly, or has some programming been done in the meantime? For example, has the node of the switch changed recently? Do the voicemail boxes have the correct "Switch Number" in them? In the station form, what do you have in the field for "LWC Reception"?

 

[colby007]

The name fields on the definity and the Audix have to be excatly the same the MWI can be very difficult sometimes.

 

[killbox]

Everything has been working fine. All the names are the same and it's all been working.

Yes there has been programming. Just some vectors and vdn's added for some particular 800 call routing to one ACD. This is everyone all of a sudden.

I know you can clear the message waiting lights per extension in the PBX, which I've done and still no luck. I'm going to try and busy and release them next.

KILLBOX

 

[killbox]

LWC is set to msa-spe

KILLBOX

 

[eriador]

We kind of have a similar problem on our Definity G3 (Release 8) system but it is only affecting every user on one particular circuit pack. I have yet to busy the whole board out, but have busied many of the individual stations affected. When I run a test station xxxx long on any of those stations I get no failures. I am guessing there is some sort of an issue/problem with the circuit pack, especially since there are also intermittent dialing problems with those same users.

How many users are there that are affected, and are they all on the same circuit pack? I doubt that that is your issue but I figured I would ask anyway in the hopes it might help.

-Frank

 

[chiefred]

I am not sure what you looking for but in answer to yourquestion:

"Is there a system wide message lamp reset on the system??"

The only thing close is "cle amw all xxxx(ext)"

have you tried other phone sets to see if its just the lamp on that or those sets?

also if voicemail is going to an extension and agents are logging in and staying logged in--I dont think the message lamp will light until they log off. I could be wrong though.

 

[AvayaHelp]

Use your FAC Code <disp feat> for "Leave word Calling Send a Message" to force the lamp on. If it comes on then "Leave Word Calling Cancel A Message" to cancel the lamp. Then you know the issue is with the voice mail system.

Avaya, Octel, AUDIX, CMS and other fun stuff.

&quot;There is always a way, it may not be pretty but there is always a way.&quot;

&quot;I don't have a technical solution to your management problem.&quot; <PeaveyPhones>

P:-D

 

[TMiyake]

We had a weird problem a few years ago when we were on release 6 with Definity Audix. The problem had something to do with the stations that Definity Audix uses. I can’t remember the exact fix, but you should try checking into a few things.
Run “list conf all” to find out what board assignment the Definity Audix uses for it’s stations (ours is 01a11).
Then run “list sta port 01a11” to find out what extensions they are.
Then run a list history to find out if anything changed on those stations. If so, try to change it back if you can figure out what was changed.
I hope this helps.


Thanks,

Tom

 

[orypecos]

Is it in fact a Definity Audix? And have u tried the LWC to see if it is with a problem on the PBX side? If it is a Definity Audix, what kind of integration is it using?

 

[WillKoo]

If the agents are not logged in, does it work? If the agents are logged in and the light does not work, that is because the system thinks an agent is a station. There is a field in the "CH AGENT xxxx" that can make it lite on the sations rather than the agent.

Will

 

[antonyn]

Killbox
Are the agents logging onto dumb terminals if so check on the station forms what the message lamp extension is . If the agent has the voicemail put the agent number in that field.

 

[killbox]

It's everyone. Agent or not. It is a release 6 with an Audix. I've tried busy and release, I've tried reseting the board, and clearing the lamps. Nothing worked. I've tried to reboot both the Definity and the Audix. I've tried to swap out phones too.

No changes were made to the stations or the hunt group to the audix.

KILLBOX

 

[n00benduser]

do a "disp activity log" in Audix for one of the subscribers. Do you see mwi-on/off logs when calls are received?

should look like this:
03/22/04 16:36 received CA message from unknown extension
message counts: new=1, unopened=0, old=7
03/22/04 16:36 mwi-on

 

[donbott]

I had message lights not working and found on page 2 of the station form Audix name had not been set to AUDIX

Might help