An Overview of Operational Information

Table 7-1 is an overview that shows you how to access different types of operational information. You can access this information locally (on the Cisco IP Communicator interface) and/or remotely (from a web site). The last column in the table points to sections in this guide where you can find more detailed instructions.

Cisco CallManager servers that are available for processing calls from this application, in prioritized order. For an available server, an option will show the Cisco CallManager server IP address and one of the following states:

•Active—Cisco CallManager server from which the application is currently receiving call-processing services.

•Standby—Cisco CallManager server to which the application switches if the current server becomes unavailable.

•Blank—No current connection to this Cisco CallManager server.

An option may also include the Survivable Remote Site Telephony (SRST) designation, which indicates an SRST router capable of providing Cisco CallManager functionality with a limited feature set. This router assumes control of call processing if all other Cisco CallManager servers become unreachable. The SRST Cisco CallManager always appears last in the list of servers, even if it is active. You configure the SRST router address in the Device Pool section in Cisco CallManager.

Directories URL

URL of the server from which the application obtains directory information.

Services URL

URL of the server from which the application obtains Cisco IP Phone services.

Messages URL

URL of the server from which the application obtains message services.

Information URL

URL of the help text that appears on the application.

Authentication URL

URL that the application uses to validate requests made to the application web server.

Proxy Server URL

URL used to proxy HTTP requests for access to non-local host addresses from the application HTTP client.

Idle URL

URL that the application displays when the application has not been used for the time specified in the Idle URL Time option. For example, you could use the Idle URL option and the Idle URL Timer option to display a log on the LCD screen when the application has not been used for five minutes.

Idle URL Time

Amount of time in seconds that elapses before the URL specified in the Idle URL option appears.

User Locale

User locale associated with the application user. The user locale identifies a set of detailed information to support users, including language, font, date and time formatting, and alphanumeric keyboard text information.

Network Locale

Network locale associated with the application user. The network locale identifies a set of detailed information to support the application in a specific location, including definitions of the tones and cadences used by the application.

User Locale Version

Version of the user locale loaded on the application.

Network Locale Version

Version of the network locale loaded on the application.

User Locale Char Set

Character set that the application uses for the user locale.

Auto Line Select Enabled

When enabled, indicates that the phone will shift the call focus to incoming calls on all lines. When disabled, the phone will only shift the focus to incoming calls on the currently used line.

Viewing the Status Menu Locally

The Status menu displays the Status Messages screen, which shows a log of important system messages. Table 7-3 describes the status messages that might appear. This table also includes actions you can take to address errors that are indicated.

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

The configuration file for a application is created when the application is added to the Cisco CallManager database. If the application has not been added to the Cisco CallManager database, the TFTP server generates a CFG File Not Found response.

•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.

CFG TFTP Size Error

The PC's hard disk is full.

Delete some files

Checksum Error

Downloaded software file is corrupted.

Obtain a new copy of the application software 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.

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 application—Verify the network connections.

•DHCP server is down—Check configuration of DHCP server.

•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 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:

Cisco CallManager servers that are available for processing calls from the device, in prioritized order. For an available server, an option will show the Cisco CallManager server IP address and one of the following states:

•Active—Cisco CallManager server from which the device is currently receiving call-processing services.

•Standby—Cisco CallManager server to which the device switches if the current server becomes unavailable.

•Blank—No current connection to this Cisco CallManager server.

An option may also include the Survivable Remote Site Telephony (SRST) designation, which indicates an SRST router capable of providing Cisco CallManager functionality with a limited feature set. This router assumes control of call processing if all other Cisco CallManager servers become unreachable. The SRST Cisco CallManager always appears last in the list of servers, even if it is active. You configure the SRST router address in the Device Pool section in Cisco CallManager.

Information URL

URL of the help text that appears on the device.

Directories URL

URL of the server from which the device obtains directory information.

Messages URL

URL of the server from which the device obtains message services.

Services URL

URL of the server from which the device obtains Cisco IP Phone services.

Alternate TFTP

Indicates whether the device is using an alternative TFTP server.

Idle URL

URL that the phone displays when the device has not been used for the time specified by Idle URL Time.

Idle URL Time

Amount of time in seconds that elapses before the URL shown in Idle URL appears.

Proxy Server URL

URL of proxy server, which makes HTTP requests to non-local host addresses on behalf of the device HTTP client and provides responses from the non-local host to the device HTTP client.

Authentication URL

URL that the device uses to validate requests made to the web server.

TFTP Server 2

Backup TFTP server that the device uses if the primary TFTP server is unavailable.

User Locale

User locale associated with the Cisco IP Communicator user. Identifies a set of detailed information to support users, including language, font, date and time formatting, and alphanumeric keyboard text information.

Network Locale

Network locale associated with the Cisco IP Communicator user. Identifies a set of detailed information to support the device in a specific location, including definitions of tones and cadences.

User Locale Version

Version of the user locale loaded on the device.

Network Locale Version

Version of the network locale loaded on the phone.

Viewing Device Logs Remotely

The device logs area on a application's web page provides information you can use to help monitor and troubleshoot the application:

•Status Messages area—Displays up to the 10 most recent status messages that Cisco IP Communicator generated since it was last powered up. These are the same status messages that you can see on the interface by choosing Settings > Status > Status Message. Table 7-3 describes the status messages that can appear.

•Debug Display area—Displays a log of up to the 50 most recent alarms for the phone. Alarms indicate a variety of errors or conditions. Table 7-7 lists alarm message numbers and their meanings.

Configuration file the that device tried to obtain from the TFTP server was too large (greater than 2 MB)

3

Firmware image that the device tried to obtain has and incorrect name

4

A PC on which Cisco IP Communicator is installed has run out of disc space

6

Configuration file that the device requested does not exist on the TFTP server

7

A request to the TFTP server timed out

8

The device could not log on to the TFTP server

9

General TFTP error

14

Cisco CallManager closed socket

15

The device lost its connection to the remote host

16

Cisco CallManager indicates that the device could not unregister for some reason

17

Cisco CallManager stopped responding to KeepAlive requests

18

The device failed back to a higher priority Cisco CallManager

20

User clicked **#** on the phone

21

The device obtained a new IP address

22

Cisco CallManager sent a reset instruction to the device

23

Cisco CallManager sent a restart instruction to the device

24

Cisco CallManager rejected a registration attempt from the device

25

No prior reset cause (default condition)

32

General alarm

33

Could not write to the hard drive

Viewing Streaming Statistics Remotely

A Cisco IP Communicator device can stream information to and from up to three devices simultaneously. Cisco IP Communicator streams information when it is on a a call or running a service that sends or receives audio or data.

The streaming statistics areas on the device web page provide information about the streams. Most calls use only one stream (Stream 1), but some calls use two or three stream. For example, a barged call uses Stream 1 and Stream 2.