8841 stuck on detecting network

[Sloaner72]

I have a 8841 that is stuck on detecting network.  IPv4 settings have been manually configured and I can ping the IP phone but the phone does not move past the detecting network message.  I already tried factory reset with the same results.

Recreated xml config file and it started working.

[Baiju Mehta]

Did you setup the option 150 on your DHCP server so it registers with Call Manager?

[Gail Yochum]

I have this problem also.  How do you recreate the xml config file?

Thanks

[Marlon SC]

Was there a resolution to this other than recreating the XML file? I have the same issue. 8845 and 7900 series has been getting stuck on detecting network. I can see that it gets an ip.I can ping it from our voice gateway. Option 150 pointed to CM. This just started happening. Any ideas?

[Slavik Bialik]

Could be some defect with the phone or with its firmware. I've tried to look for some cisco bugs that may be related but found none. Try to go and see the status messages, go to: Admin Settings -> Status -> Status Message, and see if there are any errors there that may help us to investigate the issue. You may also go to phone's web page and gather the logs and see if there are errors in the logs or something like that.

I would also try to register this device to other CUCM (if you have any, like lab or something like that) and by that upgrade it's firmware of the phone (that of course if the registration to another cluster will work), and if it'll let you I would try again on your current cluster.

Also, you can try to delete the device from the CUCM and re-create it again, it should re-create the configuration xml file from scratch, unless you experience it with all the phones which may be more problematic. 

[Marlon SC]

Hi Slavik

I put a static ip address on the phone,a different one from what the DHCP handed out and it registers fine. Do you think the TFTP service needs a restart?

[gwgibbons]

I had the same problem but with an 8851.  Our voice gateway issues IP's to the phones so I had to

1.      Unplug the phone

2.      Go to the VG and run show ip dhcp binding and find the MAC address of the phone and look for the IP it was getting. 

3.      Then clear ip dhcp binding x.x.x.x (the IP your phone keeps getting).

4.      Plugged the phone back in and waited forever while it sat on the Verify your network connection screen.

5.      Got fed up with waiting and went into Settings/Admin Settings/Reset Settings/All Settings and let it clear everything.

6.      Phone rebooted and after about 5 min it finally registered properly.

Next time I will reset all settings first and then see if it registers properly before clearing the DHCP binding.

[mleboeuf]

I did reset all settings without clearing the DHCP bindings and it worked for me.  Thanks.

[robinfen]

Tried to reset all settings and also clearing ip dhcp binding - did not helped.
Still 'detecting network' message or (after reset) 'Verify your network connection'

For me helped removing and then recreating phone in CUCM.

[MyFriendKen]

I've performed a Factory Reset.  The phone eventually resets but gets stuck on the "Detecting Network" screen.  However, the phone actually does register in CUCM.  It obtains an IP address.  I can browser into the phone to see the logs, etc.  I can also dial the extension, the phone rings and I can answer it.  Good two-way audio.  However, I can't dial out from the phone.  I can't get to the Settings screen at all to get to Admin settings - Reset settings - All settings.  I've deleted the device from CUCM and added it back in... still doesn't resolve the issue.

We are on CUCM 11.5.  We recently installed the latest Device Pack for 11.5 a few weeks ago.  We did not restart all phones in our CUCM.  Phones will only get any new firmware if the phone is removed from POE or reset.  Which, when the phone comes back up, now has a new default "Wallpaper" image.  (That's another story...)  Not sure if others in this thread also went through a recent change, but if so, that could be the reason these phones are acting up.  I'll open a TAC and see how far I get.  I'm guessing the phone might need to have new firmware pushed to it manually because it's not getting it on it's own after a reset.

[mrdfoutz1]

8841 and 8861 - Cisco Phone Stuck at Registering or Discovering Network

User reports "My phone is not working. It sits there saying Discovering Network" (previous firmware displayed "Registering").

We found that by doing a Supercopy of the device to a new identical model device with its new MAC address causes the original device to register. Of course, the new device was then deleted and returned to its box.

We later found that by simply changing a DN's associated device in Call Manager, the affected device would register.

Example: Removed the user's CSF object (Jabber). The device then registered momentarily and we then reassociated the CSF object to the DN.

Today, I had a high-priority issue. That device did not have any other associations, so could not use method above. I did a Supercopy and used ABABABABABAB as the MAC address. Then I deleted the new object. A few moments later, the original device registered.

I don't know the depths of Call Manager (I'm just a POTS guy assisting with this fancy IP stuff!), but it seems apparent that the issue lies somewhere in the device associations.

[mightyking]

Reset the DHCP service.

Thanks,

MK