SpAnKiNeM

I would tend to lean on the voicemail itself. I dont know the callxpress and how it intergrates with the PABX. Either it uses OAI, MCI or numbering plan to light message lamps. 1 thing to try is if you can in the callexpress set a MW manually to see it lights immediately. Also if your useful in programming on the NEC try and create a doe in cmd 200 to manually set lamps. One thing is this problem happening system wide or to jut one user?

R4+Z

Voicemails sometimes have problems like this because, when a message is left it tries to turn on the lamp. But if the phone is in use it can't so it tries three times at intervals before giving up and assuming the lamp is on. Later it may run a refresh routine to check all the lamps and suddenly up pops the missing or late lamp.

At least that's my explanation and I'm sticking with it. Got many a customer off my back that has!

dmad

I've done a fair bit of Callxpress in my time and a lot of NEC but never a CX talking to an NEC... Some pointers though

Under Callxpress System Configurator (found in the Windows Control Panel), under Switch Section Options, MWI callouts: set this to something like a 3rd of the number of ports you have. This is so the voicemail system can use a dialogic port to dial out and activate the message waiting on a phone. If it can't find an available port because they're in use a lot of the time, it'll be slow to turn on or off the lamp.

Integration Options/Advanced Message Waiting Settings, Preference for refreshing MWIs on new messages I generally set to “on all new messages”. This is actually down to personal/company preference but I find this is generally the accepted way.

Within the mailbox itself, in the callxpress administrator, under the Features tab, Set Primary Extn MWI and clear on all.

Having said all that, we do quite a few different voicemail systems and the MWI can be a bit of a tough area to crack because you're looking at both the PBX and the voicemail and then you can have other features which activate the lamp or extinguish which are unrelated to voicemail.

fullur

Thanks for the responses. I will let you know how it goes.

TomTomTom

I've got a 2000 IPS with an Active Voice AD-8. I've got my phone set up that if my prime line is busy, it FWD-busy to a virtual. I can press the caller-id and see who is calling, then decide to take the call or let it go to voice mail. When it goes to voice mail, the message waiting lamp lights up while I'm still on the phone after someone leaves a message. But at least once or twice a month, someone is on my back that they missed an important voice mail because the lamp wasn't on. I've looked at the logs on voice mail and the log says it sent the code within seconds after the message was recorded. Why doesn't the phone system turn on the light? I do find that doing maintenance (defragmenting the hard drive) on voice mail helps reduce the missed lamps. Any suggestions?

fullur

Well, I said I'd post back so I am.

I wasn't able to get it figured out, but the user said that the problem has gone away. So that's all. Thanks for your help.