Possible explanation and action
Description
Message
•
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 server did not respond.
DNS timeout
•
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.
DNS could not resolve the name
of the TFTP server or Cisco
Unified Communications
Manager.
DNS unknown host
•
If the phone has a static IP address, verify
that you have not assigned a duplicate IP
address. See
on page 32
section for details.
•
If you are using DHCP, check the DHCP
server configuration.
Another device is using the IP
address assigned to the phone.
Duplicate IP
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
One or more localization files
could not be found in the
TFTPPath directory or were not
valid. The locale was not
changed.
Error update locale
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.
The phone cannot locate, on the
TFTP server, the phone load file
that is specified in the phone
configuration file.
File not found
Cisco Unified IP Phone 8941 and 8945 Administration Guide for Cisco Unified Communications Manager 10.0 (SCCP
and SIP)
143
Cisco Unified IP Phone Status
