Differences

This shows you the differences between two versions of the page.

--- voip:cisco:7905_unbrick [2020/05/02 21:07] – rplecko
+++ voip:cisco:7905_unbrick [2020/05/06 06:52] (current) – rplecko
@@ Line 1: / Line 1: @@
 === Unbricking Cisco IP phone ===
-[[https://supportforums.cisco.com/document/19846/cisco-790279057912-ip-phones-are-unusable-or-unresponsive-after-their-firmware|https://supportforums.cisco.com/document/19846/cisco-790279057912-ip-phones-are-unusable-or-unresponsive-after-their-firmware]]
+[[https://supportforums.cisco.com/document/19846/cisco-790279057912-ip-phones-are-unusable-or-unresponsive-after-their-firmware|Original text]]
 === Core Issue ===
 After the default Skinny Call Control Protocol (SCCP) firmware of the 7912G IP phone is changed to Session Initiation Protocol (SIP) firmware and the IP phone is powered on, these issues occur:
-  * The hold button is red.
-  * The menu button is green.
-  * The display window is blank.
-This indicates that the phone firmware is corrupted.
+  * The hold button is <fc #ff0000>**red**</fc>.
+  * The menu button is <fc #008000>**green**</fc>.
+  * The display window is **blank**.
+This indicates that the phone firmware is corrupted.
 === Resolution ===
@@ Line 18: / Line 19: @@
 Complete these steps in order to attempt to recover the phone:
-. Connect a PC to the same network as the phone.\\
+. Connect a PC to the same network as the phone. \\ 2. Use a network sniffer in order to verify if the phone is operational.
-. Use a network sniffer in order to verify if the phone is operational.\\
 //Does the phone transmit any IP packets or request any files from a Trivial FTP (TFTP) server?//
-**Yes** The phone is operational. Proceed to step 3. \\
+**Yes**  The phone is operational. Proceed to step 3. \\ **No**  The phone is no longer usable and can not be recovered.
-**No** The phone is no longer usable and can not be recovered.
 . Look at the network sniffer log and note this information used by the phone:
   * Unordered List ItemSoftware image file name
   * TFTP server IP address
 . Put requested software image file on the TFTP server from which the phone requests it. The phone requests the last software image file that it downloaded or attempted to download, if the information is available. Or it requests its default recovery software image file.
+<code>
+     Phone  Recovery Software Image Filename
+     ----------  --------------------------------
+     Cisco 7902  cp7902r.zup
+     Cisco 7905  ldragonr.zup
+     Cisco 7912  cp7912r.zup
+     ----------  --------------------------------
+</code>
+It is recommended that all the recovery files be copied to the primary and secondary TFTP servers specified in the Dynamic Host Configuration Protocol (DHCP) options in order to facilitate automatic recovery of the phones.
+. Reboot the phone. If the phone is not in a reboot cycle, disconnect and reconnect the power adaptor, or if inline power is used, disconnect and reconnectthe Ethernet cable.
+. Verify the phone is functional. The menu and hold buttons must no longer be lit.
+. Re-configure the phone, as needed. If TFTP was originally used to configure the phone, it is possible that the phone does not require manualre-configuration. In this case, the phone downloads the necessary configuration files from the TFTP server and automatically configures itself.
+**Note:**  If encryption was previously used on the Cisco 7905 or Cisco 7912, it is necessary to re-enter the encryption key into the phone.
+Download the recovery software image file for {{:voip:cisco:ldragonr.zip|7905}}. \\
+Download all  {{:voip:cisco:cisco7905pack.zip|7905 tools}} \\
+Download the Cisco {{:voip:cisco:ciscotftp11.zip|TFTP server}}.