Status Messages

Status Messages on the Cisco Unified IP Phone

 

Message

Description

Possible Explanation and Action

 
BootP server used


The phone obtained its IP address from a BootP server rather than a DHCP server.


None. This message is informational only.


CFG file not found


The name-based and default configuration file was not found on the TFTP Server.


The Cisco Unified Communications Manager creates a configuration file for the phone with the phone is added to the database. If the phone has not been added to the Cisco Unified Communications Manager database, the TFTP server generates a CFG File Not Found response. 

  • Phone is not registered with Cisco Unified Communications Manager. You must manually add the phone to Cisco Unified Communications Manager if you are not allowing phones to auto-register. See Cisco Unified Communications Manager Administration Phone Addition, for details. 
  • If you are using DHCP, verify that the DHCP server is pointing to the correct TFTP server. 
  • If you are using static IP addresses, check configuration of the TFTP server. See Network Configuration Menu for details on assigning a TFTP server.

 


CFG TFTP Size Error


The configuration file is too large for file system on the phone.


Power cycle the phone.


Checksum Error


Downloaded software file is corrupted.


Obtain a new copy of the phone firmware and place it in the TFTPPath directory. You should only copy files into this directory when the TFTP server software is shut down, otherwise the files may be corrupted.


CTL and ITL installed


The CTL and ITL files are installed on the phone.


None. This message is informational only. Neither the CTL file nor the ITL file was installed previously. For more information about the CTL file, see Cisco Unified Communications Manager Security Guide


CTL installed


The CTL file is installed in the phone.


None. This message is informational only. The CTL file was not installed previously. For more information about the CTL file, see Cisco Unified Communications   Manager Security Guide.


DHCP timeout


DHCP server did not respond.

 

  • Network is busy: The errors should resolve themselves when the network load reduces. 
  • No network connectivity between the DHCP server and the phone. Verify the network connections. 
  • DHCP server is down: Check configuration of DHCP server. 
  • Errors persist: Consider assigning a static IP address. See Network Configuration Menu for details on assigning a static IP address.

 


Dialplan Parsing Error (SIP Phones only)


The phone could not properly parse the dialplan XML file.


Problem with the TFTP downloaded dialplan XML file.


Disabled


802.1X Authentication is disabled on the phone.


You can enable 802.1X using the Settings Security Configuration 802.1X Authentication option on the phone. For more information, see 
802.1X Authentication and Status. 


DNS timeout


DNS server did not respond.

 

  • Network is busy: The errors should resolve themselves when the network load reduces. 
  • No network connectivity between the DNS server and the phone. Verify the network connections. 
  • DNS server is down: Check configuration of DNS server.

 


DNS unknown host


DNS could not resolve the name of the TFTP server or Cisco Unified Communications Manager.        

 

  • Verify that the host names of the TFTP server or Cisco Unified Communications Manager are configured properly in DNS. 
  • Consider using IP addresses rather than host names.

 


Duplicate IP

 
Another device is using the IP address assigned to the phone.

 

  • If the phone has a static IP address, verify that you have not assigned a duplicate IP address. See Network Configuration Menusection for details. 
  • If you are using DHCP, check the DHCP server configuration.

 


Erasing CTL and ITL files


Erasing CTL or ITL files.


None. This message is informational only. For more information about the CTL or ITL files, see Cisco Unified Communications Manager Security Guide.
                       

 
Error update locale


One or more localization files could not be found in the TFTPPath directory or were not valid. The locale was not changed.


From Cisco Unified Operating System Administration, check that the following files are located within subdirectories in the TFTP File Management: 

  • Located in subdirectory with same name as network locale: 
    • tones.xml 

  • Located in subdirectory with same name as user locale: 
    • glyphs.xml 
    • dictionary.xml
    • kate.xml

 


Failed


The phone attempted an 802.1X transaction but authentication failed.
 


Authentication typically fails for one of the following reasons: 

  • No shared secret is configured in the phone or authentication server. 
  • The shared secret configured in the phone and the authentication server do not match. 
  • Phone has not been configured in the authentication server.

 


File auth error


An error occurred when the phone tried to validate the signature of a signed file. This message includes the name of the file that failed.

 

  • The file is corrupted. If the file is a phone configuration file, delete the phone from the Cisco Unified Communications Manager database using Cisco Unified Communications Manager Administration. Then add the phone back to the Cisco Unified Communications Manager database using Cisco Unified Communications Manager Administration. 

  • There is a problem with the CTL file and the key for the server from which files are obtained is bad. In this case, run the CTL client and update the CTL file, making sure that the proper TFTP servers are included in this file.


File not found


The phone cannot locate, on the TFTP server, the phone load file that is specified in the phone configuration file.


From Cisco Unified Operating System Administration, make sure that the phone load file is on the TFTP server, and that the entry in the configuration file is correct.


IP address released


The phone has been configured to release its IP address.


The phone remains idle until it is power cycled or you reset the DHCP address. See 
Network Configuration Menu for details.

 ITL installed


The ITL file is installed in the phone.


None. This message is informational only. The ITL file was not installed previously. For more information about the ITL file, see Cisco Unified Communications Manager Security Guide.


Load Auth Failed


The phone could not load a configuration file.


Check that: 

  • A good version of the configuration file exists on the applicable server. 
  • The phone load file being downloaded has not been altered or renamed. 
  • The phone load type is compatible; for example, you cannot place a DEV load configuration file on a REL-signed phone.

 


Load ID incorrect


Load ID of the software file is of the wrong type.


Check the load ID assigned to the phone (from Cisco Unified Communications Manager, choose Device Phone). Verify that the load ID is entered correctly.


Load rejected HC


The application that was downloaded is not compatible with the phone’s hardware.


Occurs if you were attempting to install a version of software on this phone that did not support hardware changes on this newer phone. 

 

Check the load ID assigned to the phone (from Cisco Unified Communications Manager, choose Device Phone). Enter the load displayed on the phone. See Firmware Version Screen to verify the phone setting.


Load Server is invalid


Indicates an invalid TFTP server IP address or name in the Load Server option.


The Load Server setting is not valid. The Load Server specifies a TFTP server IP address or name from which the phone firmware can be retrieved for upgrades on the phones. 

 

Check the Load Server entry (from Cisco Unified Communications Manager Administration, choose Device Phone).


No default router


DHCP or static configuration did not specify a default router.


If the phone has a static IP address, verify that the default router has been configured. See 
Network Configuration Menu for details. If you are using DHCP, the DHCP server has not provided a default router. Check the DHCP server configuration.


No DNS server IP


A name was specified but DHCP or static IP configuration did not specify a DNS server address.
 


If the phone has a static IP address, verify that the DNS server has been configured. See 
Network Configuration Menu for details. 

 

If you are using DHCP, the DHCP server has not provided a DNS server. Check the DHCP server configuration.


No Trust List installed


Certificate Trust List (CTL) file or Identity Trust List (ITL) file is not installed in the phone.


Occurs if the CTL file is not configured on the Cisco Unified Communications Manager and the Cisco Unified Communications Manager does not support security by default. 

For more information about the CTL file or ITL file, see Cisco Unified Communications Manager Security Guide.


Programming Error


The phone failed during programming.


Attempt to resolve this error by power cycling the phone. If the problem persists, contact Cisco technical support for additional assistance.  


Successful: MD5


The phone attempted an 802.1X transaction and authentication achieved.


The phone achieved 802.1X authentication.

 
TFTP access error


TFTP server is pointing to a directory that does not exist.


If you are using DHCP, verify that the DHCP server is pointing to the correct TFTP server. 

If you are using static IP addresses, check configuration of TFTP server. See 
Network Configuration Menu for details on assigning a TFTP server.


TFTP error


The phone does not recognize an error code provided by the TFTP server.


Contact the Cisco TAC. 


TFTP file not found


The requested load file (.bin) was not found in the TFTPPath directory.         


Check the load ID assigned to the phone (from Cisco Unified Communications Manager, choose Device Phone). Verify that the TFTPPath directory contains a .bin file with this load ID as the name.


TFTP timeout


TFTP server did not respond.


Network is busy: The errors should resolve themselves when the network load reduces. 


No network connectivity between the TFTP server and the phone. Verify the network connections. 

 

TFTP server is down: Check configuration of TFTP server. 


Timed Out


Supplicant attempted 802.1X transaction but timed out to due the absence of an authenticator.


Authentication typically times out if 802.1X is not configured on the switch. 


Trust List update failed


Updating CTL and ITL files failed.


Phone has CTL and ITL files installed and it failed to update the new CTL and ITL files. 

 

Possible reasons for failure: 

  • Network failure. 
  • TFTP server was down. 
  • The new security token used to sign CTL file and the TFTP certificate used to sign ITL file are introduced, but are not available in the current CTL and ITL files in the phone. Internal phone failure. 

 

Possible solutions: 

  • Check the network connectivity. 
  • Check if the TFTP server is active and functioning normally. 
  • If the TVS server is supported on Cisco Unified Communications Manager, check if the TVS server is active and functioning normally. 
  • Verify if the security token and the TFTP server are valid. 
  • Manually delete the CTL and ITL files if all the above solutions fail, and reset the phone.

 


Trust List updated


The CTL file, the ITL file, or both files are updated.


None. This message is informational only. 

 

For more information about the Trust List, see Cisco Unified Communications Manager Security Guide


No Trust List installed


The CTL file or the ITL file is not installed in the phone.


The Trust List is not configured on the Cisco Unified Communications Manager, which does not support security by default. 

 

For more information about the Trust List, see Cisco Unified Communications Manager Security Guide.


Version error


The name of the phone load file is incorrect.


Make sure that the phone load file has the correct name. 

 


XmlDefault corresponding to the phone device name


Name of the configuration file.


None. This is an informational message indicating the name of the configuration file for the phone.