This issue occurs after an enterprise telephony system is migrated to a completely new build of Cisco CallManager, such as from a 3.x cluster to a 4.x cluster with different IP addresses for the publisher, subscribers, and Trivial FTP (TFTP).
Specifically, when the IP phones are migrated through a change in the TFTP IP address in Dynamic Host Configuration Protocol (DHCP) option 150, and the phones are reset so that they rehome to the new Cisco CallManager cluster and TFTP, the IP phones work with all the expected functionality, but the CCMAdmin displays their status as Not found.
This issue can occur when the link between the Call Managed Database and the Real-Time Information Server (RIS) database is broken.
In order to resolve this issue, restart the RIS Data Collector Service on all the nodes of the Cisco CallManager server. Refer to Understanding Cisco Real-Time Information Server Data Collector for more information about the RIS Data Collector Service.
Make sure that the replication between the publisher and subscriber servers works. It can checked with the DBLHelper Tool. Refer to Reestablish the Relationship Between Publisher and Subscriber Using DBLHelper for more information about the procedures.
Call control software (CallManager, CallManager Express, ICS7750, SRST, SS7 call agents)
Installation, upgrade, password recovery, backup, virus, subsystem, licensing, compatibility, support or other CCM issue
Common Software and Product Issues
Switched server hardware
Problems after an upgrade
End Where Problem is Heard or Device Type Involved
CallManager Configuration, Administration, Accounts and Passwords