10-13-2016 12:31 AM - edited 03-17-2019 08:21 AM
I'm currently having an issue with a 7965 that I haven't run across yet. I reinstall firmware for Voips on a regular basis, but have yet to come across this issue. I'm using TFTPd32 as I normally do.
After hooking the phone up and doing a factory reset the phone pulls an IP fine and is reachable, however it never gets to the Cisco loading screen, in fact it stays black the whole time except in the beginning where it briefly flashes then goes back to black.
The logs on the TFTP server show that it is pulling the term65.default.loads file over and over again, but not pulling any of the files specified in the folder. I've re-downloaded these files to rule out any corruption issues.
So, it's communicating with the TFTP fine, pulling the right loads file, but that's it. All the firmware files are in the same folder as the loads file.
Also, I have tried to SSH to the phone but the connection is refused. I'm not sure if that is relevant at all as I rarely ever SSH into phones.
Any ideas of what could be happening? I've run out of things to try.
10-13-2016 12:34 AM
Also, I should say that I have tried both clearing the setting with the "1-#" sequence as well as factory resetting with the "349167...." sequence.
10-13-2016 04:42 AM
So, I ended up resolving this issue myself, but I'd thought I'd document what was happening in case anybody has this issue in the future.
On our CUCM we are currently using sccp9.3.1-SR4 for 7965s. Whenever a a factory reset was performed on these phones they would pull term65.default.loads twice, not pull the firmware, then reboot. Upon reboot they would come to the bullseye screen and get stuck.
When trying to roll back to any other firmware version using TFTPd32 on a laptop the screen would stay black, it would pull the term65.default.loads file twice repeatedly, never downloading the firmware files.
The fix was to flash the phone via TFTPd32 to the version we are currently using on CUCM, sccp9.3.1.SR4. It would not pull the files from CUCM, and trying to flash to any other version would not work. After reflashing the phone it would update successfully and register with CUCM.
Still though, performing a configuration reset with the "1-#" sequence or a factory reset with the " 349167..." sequence will brick the phone and require a reflash with TFTPd32. I have tested this repeatedly.
I looked at the field notes for the firmware and found no mention of this occurring.
The CUCM version we are using is 8.6.2.25900-8.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide