05-24-2018 03:35 PM - edited 03-17-2019 12:52 PM
I have a new Cisco 8832 conference phone which is not registering with the CUCM 18.104.22.16800-21. Could someone please help in setting up the device registered?
Solved! Go to Solution.
08-16-2018 06:27 AM
I had the same issue of 8832 not registering and just spinning "Connecting". Confirmed fix for my issue was to hold * during initial boot. It registered under the old 12-0-1-12 firmware but then upgraded/installed firmware sip8832.12-1-1-23 after registration.
Now even after unplugging, it will register without holding * However it does say, "Detecting Network" for about 2 minutes, then "Verify Your Network Connection" for another minute then finally pops up the main display screen. Still not sure this Cisco's desired bootup sequence, but it works.
08-30-2018 06:26 PM
Hi Stefan / all,
I have the very same issue. it won't registers without holding the *. after it register and it I unplug it and re plug it, it will default to the old firmware 8832.12-0-1-12 and hangs on connecting...
Any assistance would be much appreciated.
08-31-2018 08:04 AM
08-31-2018 01:19 PM
I've been trying this all day with no luck. 12-1-1-23 as the primary but no matter what, once the device is power-cycled, it insists on switching 12-0-1-12 to the active and then the device won't boot without holding the * key.
8832 = one big useless brick.
09-13-2018 01:41 PM
How about if you leave the phone load specified on the device "Phone Load Name".
That usually forces it to stay.
09-13-2018 01:53 PM
My user had to do the * reboot one more time before it loaded the "active" firmware sip8832.12-1-1-23 again. It was showing her the inactive
12-0-1-12 firmware. I put the sip8832.12-1-1-23 in phone load and let's see if that sticks after next reboot!
09-13-2018 05:28 PM
I have sip8832.12-1-1-23 manually specified, and I have it set as the default load for the 8832. The phone will load 12-1-1-23 the first time after a factory reset, register, and functions normally. The inactive load is 12-0-1-12.
If the phone loses power for any reason, on the next boot it'll hang on the "Connecting" screen in perpetuity. When it does that, the phone's settings indicates that it has loaded 12-0-1-12 despite having 12-1-1-23 manually specified, and that it has not received an IP from DHCP. I haven't tried a packet capture, but there's no MAC address associated with the switchport, so I'm guessing the phone never bothers sending a MAC into the network when it's running 12-0-1-12.
At this point the phone will not load 12-1-1-23 unless the * key is held down during boot. If the * key is not held down, it'll boot to the 12-0-1-12 and not work. If the * key is held down, it boots to 12-1-1-23 and works normally until the next time it loses power.
Bottom line is that after a loss of power this phone inexplicably decides to use the inactive and totally useless useless 12-0-1-12 load for no reason.
09-13-2018 05:48 PM
You need to install firmware of 12-0-1SR3-1.
then ensure you only have firmware of 12-0-1SR3-1 and firmware 12-1-1-23 under 'Device Defaults'.
Go to CM Administration > Device> Device Setting > Device Defaults, then make the primary firmware of 12-1-1-23, secondary firmware of 12-0-1SR3-1 for the 8832 phones.
12-12-2018 08:31 AM
haithambarka hit the nail on the head. The trick is to push 12-0-1-12 out of the inactive load. I couldn't get the phone to factory reset by following the documentation.
Once you have 12-0-1SR3-1 uploaded and youve restarted TFTP services, change the active and inactive loads under Device Defaults Configuration.
You can put that in the device profiles phone load name and push it to the phone.
From the documentation Cisco IP Conference Phone 8832 Release Notes for Firmware Release 12.1(1) bottom of page 4.
12-13-2018 07:17 AM
Daisychain POE connection issue, I have both of my Cisco 8832 phones plugged into the Daisychain POE injector and only one will register the other just spins(connecting). Both phones are programmed in the Call Manger with a share phone number. Each phone will register as a standalone device but not together on the Daisychain unit.
Has anyone had this issue, need help.