All features on a M7310 suddenly "Not Allowed" 4

[mbelanger]

Greetings all,

A few days ago one of our conference room phones stopped allowing people to use the Handsfree button. I noticed that every button on the set now returns "Feature 987" then "Not Allowed." About the only thing you can do is make and receive calls.

Absolutely nothing has changed on this system for months and the system has run for years without restart, so I'm more than a little baffled as to what caused this.

We have a Norstar MICS running 4.1 (System Version returns "SP: 30NcG04").

Any and all help appreciated.


Thanks,
MB

 

[NTL555]

Make sure you dont have a stuck button. I had the honor to troubleshoot a stuck button. Was not fun by the way. My customer's employee spilled coffee on the phone and did not tell anyone, hence the stuck button.

Also, if this does not work, try putting another M7310 on the station port and see if the station port works fine. If this does, most likely the phone is bad.

NamLy555

 

[aragon]

Does sound like a stuck key.
If you do not intend on replacing the set then empty the key by first unsticking it.
Then press feature *1
press the key and press hold.

David Brillert

http://www.williamsglobal.com

 

[BagsNYC]

Did you have a soft key programmed for F987? If so, agree with NAMLy555 and aragon.

If not, check with a working phone at that location and see if teh trouble goes away..

 

[mbelanger]

Unfortunately, I don't believe it's the set. I swapped in a different phone and had the same problem.

 

[bkrike]

If you switched the phone without fixing the stuck button, it will look the same.

You have to do what Aragon said...Remove all line appearances, then program every button on the phone to be a blank speed dial with f*1.

 

[ringjenny]

If it is not a stuck f987 button, reset the template on the port by 1. turn off set relocate. 2. install different model of set. Allow new set to ini and then test it. If ok replace with org set.

 

[mbelanger]

It did turn out to be a stuck button, but am utterly baffled as to why that was still a problem when I switched sets. Thanks for the advice, folks.

 

[hawks]

The only thing I can think of is you didn't give the new phone enough time to reset the port.

 

[skippy440]

You can go into Maintance and disable the port to that extention for 5-10 minutes to reset it and re enable it.

If that doesn't resolve it, try moving that extension to a
different port on the ksu and reprogramming the extension back
on that set.