BootP server used
|
Cisco IP Communicator obtained its IP address from a BootP server rather than from 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 configuration file is created when Cisco IP Communicator is added to the Cisco Unified Communications Manager database. If it has not been added to the database, the TFTP server generates a CFG File Not Found response.
|
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 might be corrupted.
|
CTL Installed
|
A CTL file is installed on Cisco IP Communicator.
|
None. This message is informational only.
See the Cisco Unified Communications Manager Security Guide at this URL:
http://www.cisco.com/en/us/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
|
CTL update failed
|
Cisco IP Communicator could not update its CTL file.
|
A problem occurred with the CTL file on the TFTP server.
See the Cisco Unified Communications Manager Security Guide at this URL:
http://www.cisco.com/en/us/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
|
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 Cisco IP Communicator —Verify the network connections.
- DHCP server is down—Check the DHCP server configuration.
- Errors persist—Consider assigning a static IP address.
|
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 Cisco IP Communicator—Verify the network connections.
- DNS server is down—Check the DNS server configuration.
|
DNS unknown host
|
DNS could not resolve the TFTP server name or Cisco Unified Communications Manager. |
- Verify that the TFTP server host names of Cisco Unified Communications Manager are properly configured in DNS.
- Consider using IP addresses rather than host names.
|
Duplicate IP
|
Another device is using the IP address assigned to Cisco IP Communicator. |
If Cisco IP Communicator has a static IP address, verify that you have not assigned a duplicate IP address. If you are using DHCP, check the DHCP server configuration.
|
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.
|
Check that these files are located within subdirectories in the TFTPPath directory:
- Located in subdirectory with same name as network locale:
- Located in subdirectory with same name as user locale:
|
File auth error
|
An error occurred when Cisco IP Communicator 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 Cisco IP Communicator from the database. Then add it to the database by 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
|
Cisco IP Communicator cannot locate the phone load file that is specified in the phone configuration file on the TFTP server.
|
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
|
Cisco IP Communicator has been configured to release its IP address.
|
Cisco IP Communicator remains idle until you reset the DHCP address.
|
Load Auth Failed
|
Cisco IP Communicator could not load a configuration file.
|
The configuration file that Cisco IP Communicator received from the server identified in this message is corrupt. Make sure that a good version of the configuration file exists on that server.
|
Load Auth Failed
|
A signed phone load file has been modified or renamed.
|
Make sure that the phone load file that Cisco IP Communicator is downloading has not been altered or renamed.
|
Load ID incorrect
|
Load ID of the software file is of the wrong type.
|
Check the load ID assigned to Cisco IP Communicator in Cisco Unified Communications Manager Administration (). Verify that the load ID is entered correctly.
|
Load rejected HC
|
The application that was downloaded is not compatible with the phone hardware.
|
Occurs if you were attempting to install a version of software on this Cisco IP Communicator that did not support hardware changes on this newer phone.
Check the load ID assigned to the phone in Cisco Unified Communications Manager Administration (). Re-enter the load displayed on the phone.
|
No CTL installed
|
A CTL file is not installed in Cisco IP Communicator.
|
Occurs if security is not configured or, if security is configured, because the CTL file does not exist on the TFTP server.
See the Cisco Unified Communications Manager Security Guide at this URL:
http://www.cisco.com/en/us/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
|
No default router
|
DHCP or static configuration did not specify a default router. |
- If Cisco IP Communicator has a static IP address, verify that the default router has been configured.
- 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 Cisco IP Communicator has a static IP address, verify that the DNS server has been configured. If you are using a DHCP server, it did not provide a DNS server address. Check the DHCP server configuration.
|
Programming Error
|
Cisco IP Communicator failed during programming.
|
Attempt to resolve this error by exiting (or closing) the application and then relaunching it. If the problem persists, contact Cisco technical support for assistance.
|
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 the TFTP server configuration.
|
TFTP Error
|
Cisco IP Communicator 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 Cisco IP Communicator in Cisco Unified Communications Manager Administration (). Verify that the TFTPPath directory contains a .bin file with this load ID as the name.
|
TFTP server not authorized
|
The specified TFTP server could not be found in CTL for Cisco IP Communicator. |
- The DHCP server is not configured properly, and the TFTP server address is not correct. In this case, update the TFTP server configuration to specify the correct TFTP server.
- If Cisco IP Communicator is using a static IP address, the phone might be configured with the wrong TFTP server address. In this case, enter the correct TFTP server address in the Network Configuration menu on the phone.
- If the TFTP server address is correct, there might be a problem with the CTL file. In this case, run the CTL client and update the CTL file, making sure that the proper TFTP servers are included in this file.
|
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 Cisco IP Communicator—Verify the network connections.
- TFTP server is down—Check TFTP server configuration.
|
Version error
|
The name of the phone load file is incorrect.
|
Make sure that the phone load file has the correct name.
|
XmlDefault.cnf.xml, or .cnf.xml corresponding to Cisco IP Communicator device name
|
Name of the configuration file.
|
None. This is an informational message indicating the name of the configuration file for the phone.
|