Back when it was VCS and TMS, you could use TMS to push updates to many TC-based endpoints and it would manage that process. I'm wondering how this is done when CUCM is managing these endpoints, or if that's even supported. It'd be a pretty big functionality gap to have CUCM be able to provision and manage these endpoints, but have them require manual firmware updates.
Yeah, I was hoping that wasn't the case, or at least, not the only option.
These image files are enormous, and as such, they bloat the already-bloated DRS backups by 250MB - 300MB, per endpoint type. We have SX20's, MX G1's, and an SX80. That's over 1GB of bloat added to every backup. I'd suggested to Cisco that they allow us to configure a dedicated load server for stuff like this, so we can keep these images off the core TFTP service and out of the DRS backup flow. They allow you to define the image itself in the Product Specific Configuration, but not the Load Server.
The other issue, at least, from my practical experience, is that if the upload of the image to the endpoint takes too long (>20 minutes or so), it just fails. Having CUCM centralized, and having these endpoints registered over WAN, it's been...challenging to update them efficiently.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...