When you remove a phone from the Cisco Unified Communications Manager database, the
configuration file is deleted from the Cisco Unified Communications Manager TFTP server. The
phone directory number or numbers remain in the Cisco Unified Communications Manager database.
They are called unassigned DNs and can be used for other devices. If unassigned DNs are not used
by other devices, delete these DNs from the Cisco Unified Communications Manager database. You
can use the Route Plan Report to view and delete unassigned reference numbers.
Note
Step 3
Add the phone back to the Cisco Unified Communications Manager database.
Step 4
Power cycle the phone.
Related Topics
Phone Addition Methods, on page 47
Determine DNS or Connectivity Issues
Procedure
Step 1
Use the Reset Settings menu to reset phone settings to their default values.
Step 2
Modify DHCP and IP settings:
a) Disable DHCP.
b) Assign static IP values to the phone. Use the same default router setting that other functioning phones use.
c) Assign a TFTP server. Use the same TFTP server that other functioning phones use.
Step 3
On the Cisco Unified Communications Manager server, verify that the local host files have the correct Cisco
Unified Communications Manager server name mapped to the correct IP address.
Step 4
From Cisco Unified Communications Manager, choose
System
>
Server
and verify that reference to the
server is made by the IP address and not by the DNS name.
Step 5
From Cisco Unified Communications Manager, choose
Device
>
Phone
. Click
Find
to search for this phone.
Verify that you have assigned the correct MAC address to this Cisco IP Phone.
Step 6
Power cycle the phone.
Related Topics
Basic Reset, on page 187
Determine the Phone MAC Address, on page 43
Identify 802.1X Authentication Problems
Procedure
Step 1
Verify that you have properly configured the required components.
Step 2
Confirm that the shared secret is configured on the phone.
Cisco Unified IP Phone 8941 and 8945 Administration Guide for Cisco Unified Communications Manager 10.0 (SCCP
and SIP)
183
Troubleshooting Procedures