[cisco-voip] Trouble Getting 8831 to register

[Ryan Huff]

Hello Thomas,


I have prepared a few thoughts for you below.


  *   If auto-registration is disabled within the cluster, the device configuration has to be manually added into the cluster first. Without auto-registration or having been manually added first, registration attempts will result is a "rejected" status in Communications Manager's Device->Phone page and the device itself will seem to be in an endless boot<->reboot sequence. You can reference this on page 49 of <http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8831/10_3_1/english/AdminGuide/CS38_BK_AD57597A_00_adminguide-8831.pdf> the Cisco Unified IP Conference Phone 8831 Administration Guide for Cisco Unified Communications Manager 10.0<http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8831/10_3_1/english/AdminGuide/CS38_BK_AD57597A_00_adminguide-8831.pdf>

  *   You mentioned it showed "rejected" before you connected it to the network. Was this phone's registration attempted once already? You may find that deleting the phone configuration and then adding it back in will do the trick. Again, assuming auto-registration is disabled.

  *   Is this a new, out-of-the box device or was this device previously registered to a different system/cluster? If the device is not new, but new to this cluster, you may need to remove the device's Initial Trust List (ITL) file (Admin Settings -> Reset Settings -> Security) before it will successfully register to this cluster.

  *   If auto-registration is enabled in the cluster, is there still "DN room" available? By that I mean that when a phone auto-registers, a DN is automatically assigned to the device from a range specified in the cluster nodes at System->Cisco Unified CM. Typically after a device is registered, the auto-registered DN is exchanged for a different DN. Often times the original auto-registered DN (now orphaned) is not removed from the cluster. Over time, this can end up exhausting the range of DNs used for auto-registration. If this happens, it will result in subsequent auto-registration attempts showing a "rejected" status in the cluster's Device->Phone page.

     *   In this case, you would manually create the device configuration with a valid DN or remove some of the orphaned (unassigned) auto-registration DNs (Call Routing->Route Plan Report Find Unassigned DN).

Thanks,


Ryan

________________________________
From: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of Thomas Theisen <tgtheisen at uri.edu>
Sent: Monday, June 27, 2016 10:31 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Trouble Getting 8831 to register


I have been working with TAC trying to get our first 8831 phone to register with our 10.0.1.11900-2 CUCM but we have had no success.  The strange thing is that I found that the registration is "Rejected" before I even patch the phone into the network.  TAC updated the load information for the 8831 to sip8831.9-3-3-TO-10-3-1 so I think I have the most up-to-date load for the phone.  I am using a switch port that had a 7965 attached to it so I know the pathway to CUCM is clear.  This is the first sip phone we have tried to introduce to the system but we have sip trunks so I know the correct ports are enabled for sip.

--
Thomas Theisen
Network Tech IV
University of Rhode Island
401-874-7870
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160628/01700e0f/attachment.html>