Avaya Polycom 1692 - Stuck in DISCOVERY MODE

[rich35]

Hello,

I am running Avaya CM 5.2

I have an Avaya Polycom 1692 that has currently been stuck in DISCOVERY MODE.

I have power cycled it multiple times with no luck.
I have gone in through RESET mode and no IP seems to register.

Call Server, Router, HTTP, VLAN, VLAN Test, etc all populates the correct information.

I have tried entering in a specific IP, but nothing works.
I have also tried clearing all fields to zero. When it reboots, it collects the proper information but is still stuck in DISCOVERY MODE.

I have also tried plugging the device into a known working port, and the issue still remains.

Please advise.
Any help would be greatly appreciated.

Thanks!

[rich35]

??
Anybody
??

[zakabog]

If you do a wireshark trace can you confirm that the data actually gets to and from the CM? Are there any other IP phones having this issue? Was the phone ever working?

[rich35]

Thank for writing @zackabog

Yes, the phone was working and no, there is no other device having this issue.

I dont know about doing a wireshark trace, but I'm pretty sure the CM is communicating with it. At one point, i was able to enter in the extension and password to log the phone in, but then it went into discovery mode.
It does pull the correct vlans, and HTTP server, etc.

[fazil3]

DISCOVERY MODE error generally means , the phone is unable to contact the CM procr/Server IP.

Can you put a laptop to the phones port. Make the Laptop get an IP in the same Vlan of the Phone, and try to ping the CM procr or clan IP. If you plugin any other 96xx phone (if you have one) on the same Ethernet port does it work fine.?

If you cannot do a sniffer/wireshark.

You can assign a static ip or for the dhcp assigned ip, check if any traffic comes to CM from that IP with a list trace.

-> "list trace ras ip-address aa.bb.cc.dd"

[rich35]

Thanks @fazil3

I am able to place any phone type at this Ethernet port, and am able to have it work properly.

I assigned the Polycom device a static IP, was able to ping it successfully, but now it gets stuck at "Running: app = 1692_01400.bin" and then reboots after while.

I tried clearing the IP address, but then it gets stuck in DISCOVERY mode again.

[fazil3]

Is it on the latest firmware already ? I see some KB articles mentioning similar issues (if not exactly same) with some firmware versions.

[rich35]

The device is currently running: 1692_01400.bin
From a lot of posts, i see that was what everyone says is the latest.

But on Avaya's website, i found 1692_H323_1_4_4 as being the latest since 10/22/15
I can try uploading that and see what happens.

Is uploading phone firmware service affecting, or requiring a server reboot?