Filter
Top Products
Chapter 6 Troubleshooting the Cisco IP Phone
Resolving Startup Problems
6-16
Cisco IP Phone Administration Guide for Cisco CallManager 3.3, Cisco IP Phones 7902G/7905G/7912G
OL-6313-01
If you are using DHCP, check the IP addresses distributed by your DHCP server.
Refer to Understanding and Troubleshooting DHCP in Catalyst Switch or
Enterprise Networks on Cisco.com:
http://www.cisco.com/warp/customer/473/100.html#41
Verifying DNS Settings
If you are using DNS to refer to the TFTP server or Cisco CallManager, you must
ensure you have specified a DNS server (Settings > Network Configuration >
DNS Server 1). You should also verify that you have a CNAME entry in the DNS
server for the TFTP server and Cisco CallManager system.
You must also ensure that DNS is configured to do reverse look-ups. The default
setting on Windows 2000 is to perform forward-only look-ups.
Verifying Cisco CallManager Settings
On the Cisco IP Phone, press Settings > Network Configuration >
CallManager 1, 2, 3, 4. The Cisco IP Phone attempts to open a TCP connection
to all the Cisco CallManager servers that are part of the assigned
Cisco CallManager group. If none of these fields have IP addresses or state
“Active” or “Standby”, the phone is not properly registered with
Cisco CallManager. See the “Registering the Phone with Cisco CallManager”
section on page 6-14 for tips on resolving this problem.
Cisco CallManager and TFTP Services Are Not Running
If the Cisco CallManager or TFTP services are not running, phones might not be
able to start up properly. However, in this case, it is likely that you are
experiencing a system-wide failure. Rather than being isolated to one phone that
is experiencing problems, in this situation many or all phones and other devices
are not able to start up properly.
If the Cisco CallManager service is not running, all devices on the network that
rely on it to make phone calls will be affected. If the TFTP service is not running,
many devices will not be able to start up successfully.