Re: [cisco-voip] 8832s

"...I bet the partner takes the full brunt of that pain." Ryan R., You have just made my day! Thank you. And Brian, I'm right there with you on the TFTP/MOH/Announcement sync topic. Ping me via Spark if you'd like to brain storm a bulk upload to TFTP solution together. Or if you already know

Re: [cisco-voip] 8832s

With the new Cisco Headsets that adds another level of software management too ;) Stephen On 1 May 2018, at 20:34, Brian Meade > wrote: I can't believe there's still no syncing of TFTP/MOH Files or at least making it the default option. Uploading

Re: [cisco-voip] 8832s

I can't believe there's still no syncing of TFTP/MOH Files or at least making it the default option. Uploading things to every node over-complicates things. And TFTP File Management has no bulk upload which is super annoying when I rebuild subscribers on an upgrade. I keep meaning to make a

Re: [cisco-voip] IOS crypto pki certificate pool

No and no: they’re H.323 ISDN gateways for CUCM (also SRST), no CAPF is configured anywhere, or encrypted voice in general. -- James Andrewartha Network & Projects Engineer Christ Church Grammar School Claremont, Western Australia Ph. (08) 9442 1757 Mob. 0424 160 877 From:

Re: [cisco-voip] 8832s

In my head PCD is this server. What it doesn’t have (yet?) is the hook back to Cisco where it can notify you that an upgrade is available (for every collab product you have) and let you install/stage/deploy to your alpha users/schedule/ignore. The PM for the product gets it, but like any

Re: [cisco-voip] 8832s

"With upgrades, some phones begin upgrading before I can switch this back though." I've had this happen more times than I'm comfortable admitting, and especially, I've already set the expectation that phones will not upgrade. Installing the COP and then changing the Device Defaults is six of one

Re: [cisco-voip] 8832s

I think we've got to remember a lot of different types of customers use CUCM. I've got some customers that need the ease of use with the COP file updating the device defaults automatically. I actually use this method most of the time as well and just revert the device default change before

Re: [cisco-voip] 8832s

Phone firmware should be decoupled from the whole process and be it’s own, simpler entity. Long gone are the Celsius days where one load essentially applied to everything Take one of those Red Hat Kernel licenses laying around and make a “Cisco UC Update Server”, version specific and

Re: [cisco-voip] 8832s

M, popcorn. I feel like it's less about the word "support" for me, and more about the delivery of phone firmware. Ryan R. just happened to address that one piece, of the larger thing I was saying. I feel passionate about the OP's story, since I too have been impacted by the phone firmware

Re: [cisco-voip] 8832s

[image1.jpeg] On May 1, 2018, at 13:17, Anthony Holloway > wrote: Thanks, now I want to watch that movie again. It's been a looong time. I can agree that support is not black and white. Though, do consider the Cisco

Re: [cisco-voip] 8832s

Thanks, now I want to watch that movie again. It's been a looong time. I can agree that support is not black and white. Though, do consider the Cisco Partner's perspective, when Customers ask for recommendations on what they should be doing. Our responses should always be motivated by keeping

Re: [cisco-voip] IOS crypto pki certificate pool

Is it running CME with CAPF configured? On Mon, Apr 30, 2018 at 11:44 PM, James Andrewartha < jandrewar...@ccgs.wa.edu.au> wrote: > Hi voipers, > > Has anyone seen an issue where a router will fail to load its config > after a reboot because of "crypto pki certificate pool" configuration > that