[cisco-voip] 3905 SIP showing AUTO-REG for DN despite Factory Reset

[Jason Aarons (AM)]

Auto Registration is disabled on the cluster (has been).  Database replication was good.

I experienced this with both 8.6 last year at another customer.

Currently this is 9.1.1.21018-1 and 3905 is running 3905.9-2-2ES7

From: Adam Frankel (afrankel) [mailto:afrankel at cisco.com]
Sent: Monday, September 30, 2013 9:13 PM
To: Jason Aarons (AM); cisco-voip (cisco-voip at puck.nether.net)
Subject: RE: 3905 SIP showing AUTO-REG for DN despite Factory Reset

Assuming autoreg enabled properly, and the cluster is not in mixed mode, check the database replication status using "utils dbreplication runtimestate" and "utils dbreplication status".  If that looks good, please post the exact CUCM version and firmware version on the 3905.

--
Adam

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Monday, September 30, 2013 6:40 PM
To: cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: [cisco-voip] 3905 SIP showing AUTO-REG for DN despite Factory Reset

This phone is in CallManager 9.1  It's a new 3905 deployment.

In CallManager the phone shows Rejected.  The phone web page says Phone DN is AUTO-REG.  I've factory reset the phone and reset it in CallManager but the phone stays Rejected in CCM.  Any ideas?  Perhaps a bug in the phone firmware?

If I http to the phone I see;
http://10.XX.XX.XX/Device_Information.html
MAC Address 08:CC:68:E8:3A:36
Host Name SEP08CC68E83A36
Phone DN  AUTO-REG
App Load ID        3905.9-2-2ES7
Boot Load ID      3905.0-0-0-01-01
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20131001/0b3d698c/attachment.html>