Maintenance

Basic Reset

Performing a basic reset of a Cisco IP Phone provides a way to recover if the phone experiences an error and provides a way to reset or restore various configuration and security settings.

The following table describes the ways to perform a basic reset. You can reset a phone with any of these operations after the phone has started up. Choose the operation that is appropriate for your situation.

Table 1 Basic Reset Methods

Operation

Action

Explanation

Restart phone

Press Applications and choose Admin Settings > Reset settings > Cold Reboot.

Resets any user and network setup changes that you have made, but that the phone has not written to its Flash memory, to previously saved settings, then restarts the phone.

Reset settings

To reset settings, press Applications and choose Admin Settings > Reset settings > Factory Reset.

Restores phone configuration or settings to factory default.

Perform a Factory Reset with the Phone Keypad

Use these steps to reset the phone to factory default settings using the phone keypad.

Procedure
    Step 1   Unplug the phone:
    • If using PoE, unplug the LAN cable.
    • If using the power cube, unplug the power cube.
    Step 2   Wait 5 seconds.
    Step 3   Press and hold # and plug the phone back in.
    Step 4   When the phone boots up, the headset button, the speaker button, and the mute button light up. When the light on the Mute button turns off, press 123456789*0# in sequence.

    When you press 1, the lights on the headset button turns off. The light on the Select button flashes when a button is pressed.

    After you press these buttons, the phone goes through the factory reset process.

    If you press the buttons out of sequence, the phone powers on normally.

    Caution   

    Do not power down the phone until it completes the factory reset process, and the main screen appears.

    Perform Factory Reset from Phone Menu

    Procedure
      Step 1   Press Applications .
      Step 2   Scroll to Admin Settings > Reset settings and select Factory Reset.
      Step 3   To restore phone configuration or settings to factory default, press Ok.

      Factory Reset the Phone from Phone Web Page

      You can restore your phone to its original manufacturer settings from the phone web page. After you reset the phone, you can reconfigure it.

      Procedure
      Reset your phone from the phone web page from one of the methods:
      • Enter the URL in a supported web browser and click Confirm Factory Reset.

        You can enter URL in the format:

        http://<Phone IP>/admin/factory-reset

        where:

        Phone IP = actual IP address of your phone.

        /admin = path to access admin page of your phone.

        factory-reset = command that you need to enter in the phone web page to factory-reset your phone.

      • On the phone web page, select Admin Login > Advanced > Info > Debug Info.Click Factory Reset in the Factory Reset section and confirm the factory reset message in the next screen. Click Submit All Changes.

      Identify Phone Issues with a URL in the Phone Web Page

      When the phone doesn't work or doesn't register, a network error or any misconfiguration might be the cause. To identify the cause, add a specific IP address or a domain name to the phone admin page. Then, try to access so that the phone can ping the destination and display the cause.

      Procedure
      In a supported web browser, enter a URL that consists of your phone IP address and the destination IP that you want to ping.

      Enter a URL in the format:

      http:/<Phone IP>/admin/ping?<ping destination>

      where:

      Phone IP = actual IP address of your phone.

      /admin = path to access admin page of your phone.

      ping destination = any IP address or domain name that you want to ping. Only alphanumeric characters, ‘-’, and “_” are allowed as the ping destination. Otherwise the phone shows an error on the web page. If the <ping destination> includes spaces, only the first part of the address is used as the pinging destination. For example, “http://<Phone IP>/admin/ping?192.168.1.1 cisco.com” will actually ping 192.168.1.1.


      Cisco IP Phone Cleaning

      To clean your Cisco IP Phone, use only a dry soft cloth to gently wipe the phone and the phone screen. Do not apply liquids or powders directly to the phone. As with all non-weatherproof electronics, liquids and powders can damage the components and cause failures.

      When the phone is in sleep mode, the screen is blank and the Select button is not lit. When the phone is in this condition, you can clean the screen, as long as you know that the phone will remain asleep until after you finish cleaning.

      View Phone Information

      Procedure
      To check the current status of the Cisco IP Phone, click the Info tab.

      The Info tab shows information about all phone extensions, including phone statistics and the registration status.


      Reboot Reasons

      The phone stores the most recent five reasons that the phone was refreshed or rebooted. When the phone is reset to factory defaults, this information is deleted.

      The following table describes the reboot and refresh reasons for the Cisco IP Phone.

      Reason

      Description

      Upgrade

      The reboot was a result of an upgrade operation (regardless whether the upgrade completed or failed).

      Provisioning

      The reboot was the result of changes made to parameter values by using the IP phone screen or phone web user interface, or as a result of synchronization.

      SIP Triggered

      The reboot was triggered by a SIP request.

      RC

      The reboot was triggered as a result of remote customization.

      User Triggered

      The user manually triggered a cold reboot.

      IP Changed

      The reboot was triggered after the phone IP address changed.

      You can view the reboot history as follows:

      • From the phone web user interface

      • From the IP phone screen

      • From the phone Status Dump file (http://phoneIP/status.xml or http://phoneIP/admin/status.xml)

      Reboot History on the Phone Web User Interface

      On the Info > System Status page, the Reboot History section displays the device reboot history, the five most recent reboot dates and times, and a reason for the reboot. Each field displays the reason for the reboot and a time stamp that indicates when the reboot took place.

      For example:

      
Reboot Reason 1: [08/13/14 06:12:38] User Triggered
Reboot Reason 2: [08/10/14 10:30:10] Provisioning
Reboot Reason 3: [08/10/14 10:28:20] Upgrade

      The reboot history displays in reverse chronological order; the reason for the most recent reboot displays in Reboot Reason 1.

      Reboot History on the Cisco IP Phone Screen

      Reboot History is located under Apps > Admin Settings > Status menu. In the Reboot History window, the reboot entries displays in reverse chronological order, similar to the sequence that displays on the phone web user interface.

      Reboot History in the Status Dump File

      The reboot history is stored in the Status Dump file 
(http://<phone_IP_address>/admin/status.xml).

      In this file, tags Reboot_Reason_1 to Reboot_Reason_3 store the reboot history, as shown in this example:

      
<Reboot_History>
<Reboot_Reason_1>[08/10/14 14:03:43]Provisioning</Reboot_Reason_1>
<Reboot_Reason_2>[08/10/14 13:58:15]Provisioning</Reboot_Reason_2>
<Reboot_Reason_3>[08/10/14 12:08:58]Provisioning</Reboot_Reason_3>
<Reboot_Reason_4>
<Reboot_Reason_5>
<Reboot_History/>

      Phone Behavior During Times of Network Congestion

      Anything that degrades network performance can affect Cisco IP Phone voice and video quality, and in some cases, can cause a call to drop. Sources of network degradation can include, but are not limited to, the following activities:

      • Administrative tasks, such as an internal port scan or security scan

      • Attacks that occur on your network, such as a Denial of Service attack

      To reduce or eliminate any adverse effects to the phones, schedule administrative network tasks during a time when the phones are not being used or exclude the phones from testing.