Cisco Unified IP Phones 7960G/7940G Administration Guide for Cisco Unified Communications Manager 7.0 (SIP)
Viewing Status, Statistics, and Firmware Information on the Cisco Unified IP Phone
Downloads: This chapterpdf (PDF - 379.0KB) The complete bookPDF (PDF - 3.73MB) | Feedback

Viewing Status, Statistics, and Firmware Information on the Cisco Unified IP Phone

Table Of Contents

Viewing Status, Statistics, and Firmware Information on the Cisco Unified IP Phone

Status Messages Screen

Network Statistics Screen

Firmware Versions Screen


Viewing Status, Statistics, and Firmware Information on the Cisco Unified IP Phone


This chapter describes how to access and use the following screens on the Cisco Unified IP Phone:

Status Messages Screen—Displays important system messages

Network Statistics Screen—Displays information about the phone and network performance

Firmware Versions Screen—displays information about the firmware that is running on the phone

You access these screens from the Status menu on the phone.

You can use the information on these screens to monitor the operation of a phone and to assist with troubleshooting

For more information about troubleshooting, see Chapter 7, "Troubleshooting and Maintenance."

Status Messages Screen

You can access the Status Messages screen at any time, even if the phone has not finished starting up. Table 6-1 describes the status messages that might appear. This table also includes actions you can take to address errors that are indicated.

To display the Status Messages screen, follow these steps:

Procedure


Step 1 Press the Settings button.

Step 2 Select Status.

Step 3 Select Status Messages.


To exit the Status Messages screen, press the Exit softkey.

Table 6-1 Status Messages on the Cisco Unified IP Phones 7960G and 7940G 

Message
Description
Possible Explanation and Action

BootP server used

The phone obtained its IP address from a BootP server rather than a DHCP server.

None. This message is informational only.

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 using Cisco Unified Communications Manager Administration. Then add the phone back to the Cisco Unified Communications Manager database 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.

CFG file not found

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

The configuration file for a phone is created when the phone is added to the Cisco Unified Communications Manager 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.

Phone is not registered with Cisco Unified Communications Manager.

You must manually add the phone to Cisco Unified Communications Manager if you are not allowing phones to auto-register. See the "Adding Phones to the Cisco Unified Communications Manager Database" section on page 2-7 for details.

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. See the "Network Configuration Menu" section on page 4-4 for details on assigning a TFTP server.

CFG TFTP Size Error

The configuration file is too large for 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 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 phone—Verify the network connections.

DHCP server is down—Check configuration of DHCP server.

Errors persist—Consider assigning a static IP address. See the "Network Configuration Menu" section on page 4-4 for details on 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 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 the "Network Configuration Menu" section on page 4-4 section for details

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.

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:

tones.xml

Located in subdirectory with same name as user locale:

glyphs.xml

dictionary.xml

kate.xml

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 the "Network Configuration Menu" section on page 4-4 section for details.

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 Device > Phone). Verify that the load ID is entered correctly.

Load rejected HC

The application that was downloaded is not compatible with the phone's 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 Device > Phone). Re-enter the load displayed on the phone. See the "Firmware Versions Screen" section to verify the phone setting.

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 the "Network Configuration Menu" section on page 4-4 section 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 the "Network Configuration Menu" section on page 4-4 section for details.

If you are using DHCP, the DHCP server has not provided a DNS server. Check the DHCP server configuration.

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.

XmlDefault.cnf.xml, or .cnf.xml 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.

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. See the "Network Configuration Menu" section on page 4-4 for details on assigning a TFTP server.

TFTP file not found

The requested load file (.bin) was not found in the TFTPPath directory.

From Cisco Unified Operating System Administration, make sure that the phone load file is listed in TFTP File Management.

TFTP server not authorized

The specified TFTP server could not be found in the phone's CTL.

The DHCP server is not configured properly and is not serving the correct TFTP server address. In this case, update the TFTP server configuration to specify the correct TFTP server.

If the phone is using a static IP address, the phone may 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 may 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 the phone—Verify the network connections.

TFTP server is down—Check configuration of TFTP server.


Network Statistics Screen

The Network Statistics screen displays information about the phone and network performance. Table 6-2 explains components of text messages that might appear in this screen.

To display the Network Statistics screen, follow these steps:

Procedure


Step 1 Press the Settings button.

Step 2 Select Status.

Step 3 Select Network Statistics.


To exit the Network Statistics screen, press the Exit softkey.

Table 6-2 Network Statistics Message Components 

Message Component
Description

Rcv

Number of packets received by the phone

Xmt Frames

Number of packets transmitted by the phone

REr

Number of broadcast packets received by the phone

BCast

Number of broadcast packets transmitted by the phone

Phone Initialized

Amount of time that has elapsed since the phone last initialized.

Elapsed Time

Amount of time that has elapsed since the phone last rebooted.

Port 1

Link state and connection of the PC port (for example, Auto 100 Mb Full-Duplex means that the PC port is in a link up state and has auto-negotiated a full-duplex, 100-Mbps connection)

Port 2

Link state and connection of the Network port


Firmware Versions Screen

The Firmware Versions screen displays information about the firmware that is running on the phone. Table 6-3 explains the information that is displayed on this screen.

To display the Firmware Version screen, follow these steps:

Procedure


Step 1 Press the Settings button.

Step 2 Select Status.

Step 3 Select Firmware Versions.


To exit the Firmware Version screen, press the Exit softkey.

Table 6-3 Firmware Version Information 

Message Component
Description

Application Load ID

Identifies the phone application running on the phone

Boot Load ID

Identifies the factory-installed load running on the phone

DSP Load ID

Identifies the DSP version on the phone.