M2616 Deskset Blinking????

[BLOWE]

Have a M2616 Deskset that all the arrows are blinking. If you hold in on a button for a few seconds, it brings up a message stating that the phone is in Local Diagnostic Mode. Then when you press each button, the arrows disapear. But the phone still does not funciton correctly. Not dial tone, no message on the screen (date and time) and you can not dial to that phone (internally or externally).
The user unplugged the phone this morning to plug in a longer cord to move the deskset to the opposite side of his office. This is when it all started.

Any help is greatly appricieated.

 

[SStieferman]

If you can't IDU it then its probably plugged into a 1fb or analog port. Put an analog phone on there and see what happens.

 

[BLOWE]

I did a couple of quick things: I disabled the port, then re-enabled it. Not change to the deskset, still arrows blinking. There was an M2008 deskset plugged into that port a couple of days ago. I outed that from the switch and added the m2616 to the switch. It worked just fine at first, then when the user switched the phone plug, it started doing the blinking.

So its not on an Analog port. Not sure what you mean by IDU or 1fb. Not a regular Option 11 (Meridian System) programmer.

 

[johnpoole]

blinking digital set is usually plugged into an analog port, very seldom a bad port

john poole
bellsouth business
columbia,sc

 

[saw164]

If you are sure its not a analog port, the problem could be because the polarity is wrong. i would suggest to put the old cord back in the phone. if the phone works properly, its most likely the phone cord the user is using. the cord may have the middle 2 pins reversed.

hope this helps

 

[telecomproPA]

i've seen this happen, just can't remember what i did to fix it. all the advice above is good, i also would have checked the set to make sure it's not disabled. you can check certain settings on the phone when you press the program key on the top right, but like the rest, i'm leaning towards possibly a polarity problem. if you swap out the line cord and move to a different TN, that might just do the trick. even the house pair could be an issue.

 

[hawks]

I forget what and how but there is a way to put the phone into a self test mode. Maybe it was actavated by accident.

 

[ribbon12]

sure sounds like set type defined in tnb does not match the hardware...

 

[SStieferman]

In LD 20 you can IDU SPACE TN to see if the swtich "see's" the attached device. On the 11 you just have a xx xx TN though.

REQ: idu 4 0 1 1
ARIES TN: 004 0 01 01
TN ID CODE: M2616

So I'm guessing this was a legit move? We usually tell people not to touch the devices, we'll move them.

Here's another option. LD 80 TRAK the TN. IF the device is on the wire you'll see MCR/SCR and cfw state.

 

[BLOWE]

Yes, was a legit move. I will try the LD 20 and IDU TN XX XX and see what the results are.

 

[NastyNed2]

The phone itself could be bad.

I've also had a similar problem with reversed polarity. had to punch the phone down backwards on purpose then hang a tag there explaining the "poor workmanship."

This is an obvious thing, but caught me off guard once. A 2008 was plugged into a TN programmed as a 2006 (or vice versa). Make sure your phone and your TNB match.