[cisco-voip] Cisco 7975 or 7965 stuck at speaker button Red LED, sorry if this is a repost

Mon Feb 12 13:05:04 EST 2018

Ryan is quite likely correct.

What I have done in years past to tell if a phone is really unrecoverable
or is instead just stuck in a post-factory-reset loop where it's looking
for firmware is to packet capture the phone's port. I plug it into a switch
and setup a port monitor/span to a machine running Wireshark. If the phone
is asking for an IP address, or better yet has been given an IP address
with a value for DHCP option 150, you may sometimes see what file(s) the
phone is looking for and at what IP. If you have a phone in this state and
obtain the file(s) the phone is looking for, you may find you are able to
resurrect a phone that otherwise appears visually dead - even where the
screen doesn't seem to come up. I have done this successfully several times
over the years. But it does take some time (it may not be worth it to you
versus just replacing a phone), and you may just find in the end the phone
isn't even transmitting any packets and really is kaput.

On Mon, Feb 12, 2018 at 12:48 PM, Ryan Ratliff (rratliff) <
rratliff at cisco.com> wrote:

> For what it’s worth the symptom you describe matches the Field Notice that
> was provided earlier. This means one of the memory modules has died and the
> phone cannot be recovered (that I know of).
>
> -Ryan
>
> On Feb 12, 2018, at 12:44 PM, Terry Oakley <Terry.Oakley at rdc.ab.ca> wrote:
>
> Vinnie do you have the # button pressed before or after you plug in the
> POE cable?   You need to have the # button pressed before.
>
> Terry
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net
> <cisco-voip-bounces at puck.nether.net>] *On Behalf Of *Vinnie Dao
> *Sent:* Monday, February 12, 2018 10:25 AM
> *To:* 'Ryan Ratliff (rratliff)' <rratliff at cisco.com>; 'Anthony Holloway' <
> avholloway+cisco-voip at gmail.com>
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Cisco 7975 or 7965 stuck at speaker button
> Red LED, sorry if this is a repost
>
> That was awesome guys, however, I tried many times what you said but the
> phone can’t pass Green LED light on Speaker phone.
> Here is what I have done,
> Plug in POE cable to power up the phone,
> Press # button,  and get to the green light on speaker phone and stay
> there like forever.  I can’t even across that point and can’t even get to
> the flashing line 1 to 8 of CP-7975 LED of the phone.
> Any other suggestion before I give up on these?
>
> Thank you very much in advance to all.
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net
> <cisco-voip-bounces at puck.nether.net>] *On Behalf Of *Ryan Ratliff
> (rratliff)
> *Sent:* Monday, February 12, 2018 8:11 AM
> *To:* Anthony Holloway
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Cisco 7975 or 7965 stuck at speaker button
> Red LED, sorry if this is a repost
>
> There are 3 I can find documented internally.
> 1. Soft Reset (documented publicly)
> 2. Hard Reset (see below)
> 3. Hard Reset but keep network settings (Terry’s)
>
> The hard reset is:
> 3491672850*# - the “nuke it from orbit” option which is a total format the
> flash, hard reset but does not preserve the network.
>
> Prior to version 8.3.3 only the first 2 existed, but number 2
> unintentionally kept the network preferences, acting like number 3 does
> today (see CSCsi60439).
>
> -Ryan
>
> On Feb 12, 2018, at 10:39 AM, Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
> *"The code for the network preservation hard reset is: *7412369#085"*
>
> And then there were three.
>
> Wes, Ryan, Brian, how many are there really?
>
> On Mon, Feb 12, 2018 at 9:31 AM Terry Oakley <Terry.Oakley at rdc.ab.ca>
> wrote:
>
> I have used the below to reset 79xx series phones and load a new firmware
> on them.  Setup a laptop with a TFTP server on it and on most I have been
> able to recover what looked like a bricked unit.
>
> Thanks
>
> Terry
>
>
> *Terry Oakley*
> Telecommunications Coordinator *| *Information Technology Services
> *Red Deer College **|*100 College Blvd
> <https://maps.google.com/?q=100%0D+College+Blvd&entry=gmail&source=g>. *|*
>  Box 5005 *| *Red Deer *|* Alberta *| *T4N 5H5
> work (403) 342-*3521   **| * FAX (403) 343-4034 <(403)%20343-4034>
>
>
>
> #Total Hard Reset
> The code for the total hard reset is: 3491672850*#
> A total hard reset formats /flash0 blowing away everything except CNU.
> All settings and personalization of the phone is removed.
> #Hard Reset with Network Setting Preservation
> The code for the network preservation hard reset is: *7412369#085
> And it also does a complete format of /flash0 - yet it preserves the
> network settings so that after the format, any static IP and other network
> settings are preserved. The settings are stored in volatile RAM, so it is
> important to not remove power to the phone during this process
> #Prerequisites
> There are a number of prerequsites that are necessary for a successful
> factory reset.
> 1.            You must have a network environment in which DHCP is used to
> provide the phone with an IP address and a TFTP server (i.e. DHCP option
> 150).
> 2.            There must be an appropriate default load for your phone
> model on that TFTP server:
> o             The default load name is: termxx.default.loads (where xx is
> part of the model number, 41 for 7941, 62 for 7962, 70 for 7970, etc.)
> o             The version of the default load must be the same signing
> type (dev or release) as the phone on which you wish to do a factory reset.
> o             This file (termxx.default.loads) is packaged with every
> phoneload that is installed on the callmanager, but since the name is not
> unique per phoneload version, the copy of termxx.default.loads is always
> the one from the most recent load that was installed on the callmanager. It
> may not be the type (dev or release) that you want.
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Vinnie Dao
> *Sent:* Sunday, February 11, 2018 11:07 AM
> *To:* 'Anthony Holloway' <avholloway+cisco-voip at gmail.com>
>
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Cisco 7975 or 7965 stuck at speaker button
> Red LED, sorry if this is a repost
>
> HI Anthony,
> Appreciated your reply,
> The link you sent requires login,
>
> I am not sure what version on them, since they are stand by units for a
> while,  from the last time they were working at one point.  I tried to
> reset, 1234567890*# but still the same issue.
>
> *From:* Anthony Holloway [mailto:avholloway+cisco-voip at gmail.com
> <avholloway+cisco-voip at gmail.com>]
> *Sent:* Sunday, February 11, 2018 9:53 AM
> *To:* Vinnie Dao
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Cisco 7975 or 7965 stuck at speaker button
> Red LED, sorry if this is a repost
>
> Did you already look through the bug search tool?
>
> https://bst.cloudapps.cisco.com/bugsearch/search?kw=stuck%
> 20boot&pf=prdNm&pfVal=269065653&sb=anfr
>
> What version of firmware is it, and what can you do to clear the problem?
> I.e., Power cycle the phone?
>
> On Sun, Feb 11, 2018 at 11:49 AM Vinnie Dao <vinnie at tdnetwork.com> wrote:
>
> Greeting to all,
>
> Lately, I have some CP-7965 and CP-7975 stuck at speaker button during
> boot up as red LED and stay there for long time.  Has anyone got this issue
> and know how to fix it?
>
> Please advise where to go from here to resolve this issue, and thank you
> very much for your time.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180212/869c002d/attachment.html>