04-05-2018 08:49 AM - edited 03-17-2019 12:33 PM
I have an 8845 which was successfully programmed one time. The configuration for it in CUCM was modified, and a factory reset was started (123456789*0#). However, it was unplugged before the reset was able to complete. Now when power is applied, there is only a blank screen the voicemail light is lit. There are no lights of any other kind, and no response to any key presses. This happens regardless of whether # is held or not. The configuration has since been removed from CUCM in an effort to force an Autoreg, but this did not resolve the issue.
Is it now a brick? And if so, what would the procedure be to unbrick it?
04-05-2018 12:19 PM
Are you holding # as power is applied to the phone? Have you tried a power brick instead of PoE for power?
Brandon
04-06-2018 05:31 AM
04-07-2018 05:49 AM
Hello Eileen,
Do you know if the phone is getting IP from the DHCP server?.
If you want to troubleshoot this issue yourself, you might need make a phone console cable. This will allow you to gather the phone console logs and determine what is happening during the boot process.
Here are two guides on how to make such a cable:
If you happen to go through this process, i will be more than glad to check the phone console logs for you.
Best Regards, Jaime.
04-09-2018 06:25 AM
Hello Jaime,
No, the phone is not able to be found on the network. I've also not been able to locate a Power Cube 4 (I'll try to get one ordered).
Thank you for the links and for the offer to go over the logs! I will search around for a console cable and give this a try.
04-09-2018 11:57 AM
04-09-2018 12:10 PM
Apologies for the log directly to the thread. I had attached it as a .txt file and written a short note. Obviously, that did not work the way I intended.
04-13-2018 10:28 AM
Anybody know how to unbrick an 8845 IP video phone? Log is inline above...
Thanks!
06-27-2019 02:54 PM
We also have a 8851 that has bricked (4th session button light stuck during boot). I have Cisco TAC case and sent AUX debug log, but no bugs (even internal) match our issue. In our situation, we were doing network replacement project (moved from 3750 switches to 9300 switches) and found the phone stuck after doing this work. I suspect that the phone was possibly unplugged from the patch panel while randomly booting, or, possibly it was hard to unplug at the patch and caused the issue.
I found this thread by searching UNIDENTIFIED PMU as this was in my log on the 8851.
I have also seen odd stuff at three different Corporations with 88xx model including needing to use CAT6 instead of CAT5e (symptom is phone will spin in 'Connecting' and indicate 'No Ethernet Connected' in status messages).
Not trying to threadjack, just commenting that maybe there are some issues with 88xx model as Cisco would not share the internal details of the BUG with me.
Here is one of the bugs that describes this: “ https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuq79974 “, however in the cases where I see this they just replaced the phone.
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