[cisco-voip] CUCM Upgrade

[Paul]

You could've always enabled peer to peer firmware upgrades for remote sites to 
lessen the burden on your WAN lines/TFTP server in general. . . 



________________________________
From:"H, Tim" <TimH at trstone.com>
To:"Buchanan, James" <jbuchanan at presidio.com>; Lelio Fulgenzi 
<lelio at uoguelph.ca>
Cc:"cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Sent: Mon, February 21, 2011 4:27:18 AM
Subject: Re: [cisco-voip] CUCM Upgrade

  
I ended up looking at the ReadMe for the upgrade.  I went ahead and upgraded all 

of the phones to the version it will be at upgrade time to avoid all phones 
downloading the new firmware at once.
 
Thanks for the suggestions!
 
From:Buchanan, James [mailto:jbuchanan at presidio.com] 
Sent: Saturday, February 19, 2011 1:22 PM
To: Lelio Fulgenzi
Cc:H, Tim; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CUCM Upgrade
 
Yes, you could do that and that would definitely keep your phones from getting 
the new firmware. Good idea! 

 
James Buchanan |Technology Manager, UC |South Region |Presidio Networked 
Solutions 

12 Cadillac Dr, Suite 130, Brentwood, TN 37027 |jbuchanan at presidio.com
D: 615-866-5729| F: 615-866-5781| www.presidio.com
CCIE #25863, Voice
 
From:Lelio Fulgenzi [mailto:lelio at uoguelph.ca] 
Sent: Saturday, February 19, 2011 12:20 PM
To: Buchanan, James
Cc:H, Tim; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM Upgrade
 
If I'm not mistaken, you can upgrade the publisher first, change the device 
defaults, then upgrade the subs. We've been doing something similar on 4.1 for 
years. 

Sent from my iPhone

On Feb 19, 2011, at 1:13 PM, "Buchanan, James" <jbuchanan at presidio.com> wrote:
No, that won’t do it because the upgrade will change it to the latest version. 
It would need to be changed on the phones.
> 
>James Buchanan |Technology Manager, UC |South Region |Presidio Networked 
>Solutions 
>
>12 Cadillac Dr, Suite 130, Brentwood, TN 37027 |jbuchanan at presidio.com
>D: 615-866-5729| F: 615-866-5781| www.presidio.com
>CCIE #25863, Voice
>
>
> 
>From:Lelio Fulgenzi [mailto:lelio at uoguelph.ca] 
>Sent: Saturday, February 19, 2011 12:10 PM
>To: Buchanan, James
>Cc: H, Tim; cisco-voip at puck.nether.net
>Subject: Re: [cisco-voip] CUCM Upgrade
> 
>You could also change the device defaults firmware config parameters. 
>
>Sent from my iPhone
>
>On Feb 19, 2011, at 1:07 PM, "Buchanan, James" <jbuchanan at presidio.com> wrote:
>I had a customer do this last Sunday. The only change was the firmware. 
>Attendant Console was unaffected. If you don’t want to deal with the firmware, 
>you could hard code the firmware on the phones until you are ready for the jump 

>because the old firmware will stay on the server. 
>
>> 
>>James Buchanan |Technology Manager, UC |South Region |Presidio Networked 
>>Solutions 
>>
>>12 Cadillac Dr, Suite 130, Brentwood, TN 37027 |jbuchanan at presidio.com
>>D: 615-866-5729| F: 615-866-5781| www.presidio.com
>>CCIE #25863, Voice
>>
>>
>>
>> 
>>From:cisco-voip-bounces at puck.nether.net[mailto:cisco-voip-bounces at puck.nether.net]
>>
>> On Behalf Of H, Tim
>>Sent: Saturday, February 19, 2011 8:13 AM
>>To: cisco-voip at puck.nether.net
>>Subject: [cisco-voip] CUCM Upgrade
>> 
>>All,
>> 
>>I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15.  I'm aware of 

>>the firmware jump as you have to upgrade to 8.52sr1 or whatever, but is there 
>>anything else I need to be cautious about?  Looks like the attendant console 
>>might change a bit in the version jump, but should still function?
>> 
>>Any other caveats that anyone have ran into would be helpful.
>> 
>>Thanks,
>>Tim
_______________________________________________
>cisco-voip mailing list
>cisco-voip at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-voip