I have read the other thread regarding adding an 8831 to a 8.5.1 cluster. I wanted to make sure I understand everything very clearly.
Am I understanding this completely and correctly?
Yes, cluster reboot is mandatory for new device support
No, which phones will get a new FW is outlined in the RNs/README. You might even get a downgrade. But yes, the DevPack will update the device defaults as necessary and phones will get the new FW if they're reset or reboot.
I just want to double check something here because I am facing the same scenario. We are running on call manager 8.5.1. and we need to be able to add the 8831 conference phone. I have the device pack and I would prefer to add only the new device to the call managers (one pub, two subscribers) and not have all 12 of our remote offices downloading new firmware at the same time.
Won't the phones reboot when the cluster is reset? Is there anyway to not have all of the phones reboot when I bounce each server?
To avoid the new download happening accross the board at all at once I was thinking of trying what Chris suggested in this thread, upload the new device pack and prior to the cluster reboot change the default load back to the current load.
Will this method get me the new 8831 conference phone option AND not having all of the phones in all 12 remote offices bounce at once?
Please let me know.
The method Chris used will allow you to get the new 8831 phone model added in CUCM without your other model phones needing to update firmware.
Is there any reason to not just upload toe cop file for the 8831 ip conference phone? I didn't think it was available as just a single download but my co-worker found it. Is there any reason I can't just upload the file? My call manager is on 8.5.1 release.
|8831 IP Phone SIP Firmware - Compatible with CCM Versions: 7.1(5) and above|
|Size:||15.63 MB (16391140 bytes)|
Brian, correct me if I am wrong but the COP file probably just updates existing firmware and doesn't load support for said new device.
You are correct. COP file only updates. It doesn't add the new device. My co-workers had me thinking I was over complicating this but...not so much.
I am going to you use your method so I can get the 8831 added but not have all phones in 12 offices bouncing and downloading at the same time.
Thank you all.
The other thing to think about as well is that if you are using CMGs, then the phones won't go down for long as they re-register with their secondary server.
Because that's only the FW, that won't add the device to CUCM's DB.
Adding FW to CUCM has never meant you're adding support for a new device.
So, you need a new device??? DevPack, or device enabler (if it exists)
Need to upgrade FW?? Install FW .cop file
The COP file just contains the firmware files and sets the device defaults. It can only be used for upgrading firmware of an existing device. In order to get the 8831 added as an option in the database, you have to do the device pack installation first. Cisco has released COP files to allow adding a single device a few times in the past, but they chose not to go that route when they added the 8831 or any of the most recently released phone models.
As Brian alluded to, this went off without a hitch. As long as you change your device defaults back there will be no mass firmware update.
One thing you can do is take note of all the device defaults now and set them back to original after the device pack update. That way you don't have to worry about phones updating or downgrading firmware when they reset.
So, it should go ahead and change the device defaults before a reboot, at which point we can change them back before the clusterwide reboot and they can do them at a later date?