I have several 7902 phones that for some reason have stop working. I noticed in Call Manager that those phones's status was "Not found". So I figured that they were unplugged, but they were plugged in. So I reset them by unplugging them and back on. The phones never come back up. They get power, but it seems that they never do register with Call Manager. The physical phone seems to be in a loop, continously attempting to boot. It is difficult to see exactly where it gets stuck because of it not having a display.
Has anyone run into this issue before. The major difference that has occurred recently is that the CallManager was upgraded to latest versions to include the OS.
My guess is that the 7902's are fighting it out for a duplicate IP address (we had this happen during an upgrade with 7905's and 7912's) and because they have no display you can't actually see that message. You probably will see errors in the Event viewer that reference the macs of these 7902's. The easiest thing to do would be to delete them and start over.
Make sure that they are running a recent phone load as well.
Another thing that I have found is in the cabling itself. In this setup were the phones working before? I have run into issues where the cables weren't punched and patched down correctly so not all the pins were properly seated causing a half power connection.
If the phones are running their default configuration, they will wait for a DHCP address. There are basically three things to do - first, take a working 7902 phone and plug it into one of the cables used by the non-working ones - if it does not work check the tftp and dhcp connectivity. If it works, delethe the phones from ccm and create them again. if it still does not work open an RMA - might be faulty hardware.
I have solved this issue. I found that the load file for the type of phone was corrupted. I had to delete and download the file itself from Cisco website. Then place it in the tftppath directory. That fixed it.
Funny that the .exe program does not actually install the file into the directory. From what i could see apparently it only confiures the device defaults.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...