9508 Please wait 2

[dajohnso2]

I have an Avaya that's about 5 years old. Its been working fine for quite some time. Now occasionally, one of the 9508 phones gets a white screen with "please wait" message and the phone is otherwise locked. doesn't respond to anything. I have tried plugging a new 9508 directly into the port and it gets the same message. The only way to clear it was to reboot the system and it would come up fine without doing anything else.

I know this is vague and I should have an update with versions shortly.

 

[Okkie26]

This is a firmware issue.

Outthe top of my head, the IP Office server folder is missing the 14xx.bin file (or something like that).

Check sys monitor with TFTP filter enabled in order to see what file the phone is asking for.

Copy that file from the manager folder to the IPO sd card primary folder.

 

[dajohnso2]

Just clarifying. Its only happening on one phone. I have Digital, analog, and IP phones installed. Only 1 extension appears to be having the problem. Its happened several times now. When it happened I tried connecting another phone to that port and it still did it. Are you saying the issue is the firmware on the card or phone? I saw previous posts about this from nearly 10 years ago so I am assuming my PBX that was installed new in 2019 has to be newer. What version was this type of issue fixed in?

Does it make sense that it still happens even if I plug a different phone directly into the port and it still happens? I had a tech insist that it was a cabling issue which is why I plugged directly into the PBX but I wasnt sure if a cabling issue could "lockup a port"?

 

[budbyrd]

If you have a combo card only the first 6 are digital.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[dajohnso2]

yes, its port 2-1, was working fine for several years without any issues. The problem happened 3 times in the last few weeks. Nothing was changed on the system programming or cabling. A tech company for the avaya is telling me its a cabling problem, except that the 9508 only uses 1 pair, but if it was a cabling problem the phone wouldn't boot up at all since it only using the 1 pair, it wouldn't get power or data! Its 1 pair so its either working or its not but this was further proven by plugging a new phone directly into the port with a new patch cord.

 

[qtelcom]

Probably the port or card then, move the extn assigned on port 2-1 to a spare port on a different card and plug it in there and see if all your problems go away.

 

[CMUK]

I have had a similar problem...same user does it every few months, tried installing replacement cards, handsets and cabling...also upgraded system

If i disconnect a few other phones it starts working then plug the others back in, very odd.

Calum M
ACSS

 

[dajohnso2]

I resolved the issue. I found the cable for the extension having an issue that went under a chair mat, it was crushed and exposed. I hadnt realized that the phone was plugged into a jack that was extended under the chair mat back to a wall jack (not my install). When I was toning out the line I discovered the poor installation. I have since replaced all the damaged cabling (running it along the base board instead of under the carpet) and its back on line. I suspect the cord was sporadically shorting out as the chair rolled over it making it a random outage. The Avaya support tech says there was nothing in the logs? Wouldn't a shorting cord show up some place?

 

[critchey]

Glad you got it resolved and thank you posting the resolution.

The truth is just an excuse for lack of imagination.

 

[dajohnso2]

Doesn't the Avaya have any reporting that would show a port was shorted? When I worked for New York Telephone back in the 80's one of our customers had a fire (on wall street) and our PBX health center (now a days called a NOC) knew it before the fire department did as the phone system "called home" to report dozens (at first, then hundreds) of extensions shorting out at the same time. I'm sure at first they thought it was a bad card but as the numbers quickly grew they knew it was more than a hardware fault.