sundance-communications.com/forum Forums TDM Business Telephone Systems Comdial Telephones & Systems DX-80 Voice Mail Light

This is a two part question.

1. How do you manually update the MW light on the dx-80 phones. I know there is a command I just can't remember what it is.

2. The message waiting lights are not updating on any phones. And one phone has the message waiting light on even though there are no vms on that phone. Any suggestions on how to fix this?

I have both keylink and DX80 PCDBA with a computer hooked up so I can access both at will remotely.
KSU Revision is K16UM0.A40

All the boxes have:
MW lamp on #96xww
MW lamp off #*96x

I made sure that box 10 was created and had the vm on and off codes in it.

Backstory: We recently had an issue where the auto attendant would pick up the phone and immediately say invalid extension then continue on. I couldn't figure it out so We had comdial specialized techs from 2 different companies come out to try and fix it. The first one failed miserably, the second one eventually fixed the problem after about three weeks. (and a lot of money)
However after they fixed the invalid extension, none of our message waiting lights work.
Meaning someone leaves a voice mail and the mw lamp does not turn green or light up at all for that matter. I have been working with the company that fixed the issue but they are saying that its not related and have been working on it for over a week now.

Simply thing but a reset of system usually fixes that.

I'm guessing a reset has already been tried. Unless backplane integration is being used for message waiting, the code would be shown in each mailbox in the voicemail, when looking at it using the KeylinkDX software.

I'm guessing they messed with the MWL on and off strings, and caused the problem, or attempted to move from inband to out of band signaling and broke it.

Question: why do you have a mailbox 10? Aren't your extensions 3-digit, starting with 101? If not, that's part of your problem. The DX80/DX120 did not work well with modified extension numbers, especially when integrating with voicemail. I've seen weird problems when deviating from the default extensions.

Justin

Thank you for the responce, however we already tried resetting the system. (multiple times with many differant configurations)

I double checked and the mw code is indeeed shown in each and every mb.

I am unsure of how to check inband to out of band signaling, how could I check? I did notice in his attempt yesterday he changed 4 of the boxes to use serial in the mw code section, however that did not fix the problem.

I added box 10 because I found on these forums that adding box 10 is a known fix for systems having this problem with software below a42 (we have a40) Deltron\'s post to fix a similar issue


Every phone in the building uses a 3 digit ext. We do have a hand full of 2 digit transfers but they are instant blind transfers to 3 digit boxes. We have been using them without trouble for over 6 years.

Thanks.

New Info:
He is now saying that he fixed the invalid extention error by deleting box "400 or so, maybe 410" that it had "all kinds of weird data in it I have never seen before"

I went in and checked 410 did not have mw codes in it so I added them, but it Did not seem to help.

Is this a hard drive VM or flash? The original problem is a classic problem of the older hard drive systems, I would just change the file extension of that invalid ext. prompt and that would take care of it so it wouldn't play, instead the client would get 2 seconds of silence. If it is the old hard drive board it has already outlived it's life expectancy and you might consider an upgrade to the flash drive system. Any Comdial dealer worth having on site would have a new (crash kit) VM board to test with your system.

If it is a flashed based system with these problems, you have other options. Send me a PM and I will explain.

Mark


Mark

We have a flash system. It currently has 128mb storage. I just purchased a flash to usb converter so I can back up the vm system.

Also Mark, your pm box is full.

Thanks
Jef

Resolved.

We just had the first company come back again as a last ditch effort. It took them about 10 minutes to fix the issue. port 4 aka 160 was frozen. He changed the vm port to a different one and everything works.

Thanks for your help.