cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
78203
Views
100
Helpful
48
Replies

Cisco 7970 Phone not booting after Factory Reset

Giovanni Ceci
Level 1
Level 1

Hey Community,

I got a Cisco 7970G IP phone that won't boot up after I did a factory reset. It was booting up prior to doing so. Here is what is happening when I plug it in:

- Screen shows "Cisco Systems - Copyright 2002-2005, Cisco Systems, Inc", and has a checkmark on the bottom left corner

- The line buttons are lighting up in sequence from top to bottom

- The Headset key is lit and stays that way

- After about 15 seconds, the screen dims and the check mark changes to a bullseye sign.

- There is no response from any of the keys when pressing them (including the Settings Key)

This process repeats and repeats. I checked the Bug Toolkit, and I found one that may match, but it doesn't have the same symptoms: CSCsc48289

Has anyone ever experienced this and knows how to fix it?

Thanks,

Neocec

48 Replies 48

You can use an UC520 that does everything and not even expensive on the refurbished market.

Not expensive, but not even cheap. By the way, seams to be a great product and, of course, should be easier to set up than the pbx. Thank you Paolo

You're welcome, please remember to rate useful posts clicking on stars below..

cgm
Level 1
Level 1

I know this topic is (now) 4 years old, but I have not been able to locate any place that shows what is IMHO one reason for this problem.

When you do a factory reset on these phones (79xx), only the firmware is left there.

It tries to get its load from a tftp server, and it seems that the tftp client does something wierd, and is not able to download the files from *many* tftp servers included the embedded tftp server of IOS (routers), and the CUCM tftp service. Even my standard 3cd tftp server rejects the second file request with "malformed option".

Just using a more lenient tftp server does the trick. I was not able to spot what the problem is with the requests but it could just be that the transfer ID is the same for all file requests?

Whatever, just try a different tftp server and you may be fine. I used linux's tftp-hpa-0.40.

If someone wants to dig into the reason, attached there's a capture of "rejected" requests of a "bricked" 7911G.