7-7
Cisco IP Communicator Administration Guide for Cisco CallManager
OL-4698-01
Chapter 7 Viewing Operational Information
Viewing Operational Information Locally on the Cisco IP Communicator Interface
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 application—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 CallManager.
• Verify that the host names of the TFTP server or
Cisco CallManager are configured properly in DNS.
• Consider using IP addresses rather than host names.
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 the following files are located within
subdirectories in the TFTPPath directory:
• 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
–
dictionary.xml
Load ID incorrect Load ID of the software
file is of the wrong type.
Check the load ID assigned to the application (from
Cisco CallManager, choose Device > Phone). Verify that
the load ID is entered correctly.
SEPDefault.cnf.x
ml
Name of the
configuration file.
None. This is an informational message indicating the
name of the configuration file for the application.
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.
Table 7-3 Status messages displayed on Cisco IP Communicator (continued)
Message Description Possible Explanation and Action
To Next Page
Loading...
Need help?
General