Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

200ICP message key quits working

Status
Not open for further replies.

pandabear1

Technical User
Oct 14, 2004
887
CA
I have a 200ICP release 5.0.2.7 that up until yesterday the message key on the SS4025 sets was working and now nothing when they press the flashing message key. I have had this report on 5 sets so far, probably affecting all sets. They can dial the embedded voicemail manually and get their messages. I have gone through the program and all looks good, I have not rebooted the system.
 
Tenanting along with form 19 controls the VM key.

Verify that the tenanting of the stations have not changed and that the VM destination is programmed in form 19

**********************************************
What's most important is that you realise ... There is no spoon.
 
what I did was delete everything in the tenant form of the sets and the message key still works, since they can dial the voicemail manually it shouldn't be a tenant issue but I did check form 5 anyway. What i think the set is dialing when you press the message key is "dialing sender of oldest message" as I sent a set a message from the console by pressing the "send message" key and pressing the message key on the set called the console. Having said all this I still don't know why it has stopped, I do have an access code in form 2 for "call sender of oldest message" but that is for analogue sets.
 
I missed the flashing key bit. Tenanting controls how it works when it is not flashing.

When pressing a flashing key, you must lift the handset for it to call the sender. Common testing mistake is to leave the handset in the cradle.

If the issue is that the key is flashing but shouldn't be, you can enable transparent multiconsole operation on the console and thus allow it to cancel MWI set from other stations.

Verify that the last and first port are available in the VM hunt group and not used for other purposes.

**********************************************
What's most important is that you realise ... There is no spoon.
 
I should be more clear, the red message lamp is flashing on the 4025 and when you press the hard "message" key nothing happens. There is a message in the mailbox and the key is lamp is flashing like it should be.
I have confirmed the number of allowable ports and that all ports are in one hunt group.
 
It may be that the oldest message is defunct and needs to be scrapped.

if you press the key with the handset in the cradle, do you get the options to read and/or delete the message? If so delete it and retest.

If no, then try enabling the transparent multiconsole option and delete the message from the console and test again.

**********************************************
What's most important is that you realise ... There is no spoon.
 
this is happening on at least 5 sets and they do have voicemail messages in their mailboxes. I smell reboot.
 
Is the light on when they don't have a message?

Reboot is unlikely to resolve MWI issues. MWI is written to disk.

**********************************************
What's most important is that you realise ... There is no spoon.
 
no light on when no message, all functions act ok except the pressing of the message key.
 
bizarre, reboot seems like a good course then.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top