Re: [cisco-voip] 8832s

, in > DRS .tar backups too. > > > > *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf > Of *Anthony Holloway > *Sent:* Monday, April 30, 2018 9:07 AM > *To:* Charles Goldsmith > *Cc:* cisco-voip (cisco-voip@puck.nether.net) > *Subject:* Re: [cisco-v

Re: [cisco-voip] 8832s

backups too. From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Anthony Holloway Sent: Monday, April 30, 2018 9:07 AM To: Charles Goldsmith Cc: cisco-voip (cisco-voip@puck.nether.net) Subject: Re: [cisco-voip] 8832s I wish CUCM didn't ship with newer phone firmware. Since

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] 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] 8832s

Since Cisco already drops support for all firmware older than the most recent firmware: “You keep using that word, I do not think it means what you think it means”. In all seriousness, and as the author of the document you quoted, there’s a reason why the bulk of that document is dedicated to

Re: [cisco-voip] 8832s

01.png] > > > > *From:* cisco-voip <cisco-voip-boun...@puck.nether.net> *On Behalf Of *Anthony > Holloway > *Sent:* Monday, April 30, 2018 9:07 AM > *To:* Charles Goldsmith <wo...@justfamily.org> > *Cc:* cisco-voip (cisco-voip@puck.nether.net) <cisco-voip@puck.neth

Re: [cisco-voip] 8832s

net> On Behalf Of Anthony Holloway Sent: Monday, April 30, 2018 9:07 AM To: Charles Goldsmith <wo...@justfamily.org> Cc: cisco-voip (cisco-voip@puck.nether.net) <cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] 8832s I wish CUCM didn't ship with newer phone firmware. Since Cisc

Re: [cisco-voip] 8832s

puck.nether.net) <cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] 8832s I wish CUCM didn't ship with newer phone firmware. Since Cisco already drops support for all firmware older than the most recent firmware: - For each IP Phone model, once Cisco releases a new firmware version, the olde

Re: [cisco-voip] 8832s

I wish CUCM didn't ship with newer phone firmware. Since Cisco already drops support for all firmware older than the most recent firmware: - For each IP Phone model, once Cisco releases a new firmware version, the older versions are no longer supported. - Cisco expects customers who encounter a

Re: [cisco-voip] 8832s

Since the 8832 is a dual bank phone, shouldn't it have the old image on it in the backup bank? Maybe hardcoding the old image on the phone configuration and doing a reset will cause it to boot from it? On Sun, Apr 29, 2018 at 7:06 PM Ryan Huff wrote: > Sounds like the

Re: [cisco-voip] 8832s

Sounds like the ole’ ‘step upgrade’ issue that plagued the 79xx series back in the 8.x days My guess is they don’t actually need RMA’ed, just the easiest way to deal with it I’d flash the phones and advertise an isolated tftp server to them with the firmware load and XML bootstrap

[cisco-voip] 8832s

I have a customer with four 8832 conference room phones. Their CUCM was running version 12.0.1 of the 8832 firmware. These phones shipped with version 12.0.1SR2. When they registered the first two phones they downgraded from 12.0.1SR2 to 12.0.1 and are now unusable. They sit on “Connecting”