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.
|
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.
|
CFG TFTP Size Error
|
The configuration file is too large for the 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 TFTP 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
|
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 on the phone previously.
For more information about the Trust List, see
the Cisco Unified Communications Manager Security
Guide.
|
CTL installed
|
The CTL file is installed on the phone.
|
None. This message is informational only. The CTL
file was not installed previously.
For more information about the CTL file, see the
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.
|
Disabled
|
802.1X Authentication is disabled on the phone.
|
You can enable 802.1X authentication by using the
option on the phone. For more
information, see
802.1X Authentication and Status Menus.
|
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 Menu for
details.
If you are using
DHCP, check the DHCP server configuration.
|
Erasing CTL and ITL files
|
Erasing CTL or ITL file.
|
None. This message is informational only.
For more information about the CTL and ITL files, see
the Cisco Unified Communications Manager Security
Guide.
|
Error update locale
|
One or more localization files could not be found in
the TFTP directory or were not valid. The locale was not changed.
|
From Cisco Unified Operating System Administration,
check that the following files are located within the subdirectories in TFTP
File Management:
- Located in
subdirectory with same name as network locale:
- 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 by using
Cisco Unified Communications Manager Administration. Then add the phone back to
the Cisco Unified Communications Manager database by using Cisco Unified Communications Manager Administration.
The CTL file has a problem 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 in the phone configuration file specifies.
|
From Cisco Unified Operating System Administration,
ensure that the TFTP File Management lists the phone load file.
|
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. The ITL file
was not installed.
|
None. This message is informational only. Phone does
not have prior installation of the ITL file.
For more information about the ITL file, see
the Cisco Unified Communications Manager Security
Guide.
|
ITL update failed
|
Updating ITL file failed.
|
Phone has CTL or ITL file installed and it failed to
update new ITL file.
Possible reasons for failure:
- Network failure
- TFTP server was
down
- Trust Verification
Service (TVS) server was down
Possible
solutions:
- Check the network
connectivity.
- Check whether the TFTP
server is active and functioning normally.
- Check whether the Trust
Verification Service (TVS) server is active and functioning normally.
- Manually delete
CTL and ITL files if all the above solutions fail.
|
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
being downloaded has not been altered or renamed.
- 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
).
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 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
).
Re-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
).
|
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
|
The Trust List is not configured on Cisco
Unified Communications Manager, which does not support security by default.
|
Occurs if the Trust List is not configured on
Cisco Unified Communications Manager and Cisco Unified Communications
Manager does not support security by default.
For more information about CTL and ITL files, see the
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 points 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
TFTP directory.
|
Check the load ID assigned to the phone (from Cisco
Unified Communications Manager, choose
).
Verify that the TFTP 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 due the absence of an authenticator.
|
Authentication typically times out if 802.1X
authentication is not configured on the switch.
|
Trust List update failed
|
The CTL and ITL files are installed on the phone,
and it failed to update the new files.
|
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 Trust
Verification Service (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 the 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.
|