[cisco-voip] CUCM - Engineering Special firmware versions

[Ryan Ratliff]

If you want to make it as seamless as possible then either make sure the
phones are on the new load prior to the ES install, or change device
defaults back to the current versions after ES install.
 
If you are happy to let the phones upgrade themselves after the ES install
then there is no need to upgrade them beforehand.
 
-Ryan

  _____  

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Scott Voll
Sent: Tuesday, November 18, 2008 12:17 AM
To: Ed Leatherman
Cc: cisco voip
Subject: Re: [cisco-voip] CUCM - Engineering Special firmware versions


maybe better answered by Wes, but if all the ES now come with DP (Device
Packs) what is the best way to upgrade.  Download all the firmware, upgrade
phones then upgrade to the ES?
 
Scott


On Fri, Nov 7, 2008 at 11:56 AM, Ed Leatherman <ealeatherman at gmail.com>
wrote:


Even easier, they put the readme right below the final download link so you
don't need to pull the whole ISO down and mess with it to look thru the
change info. 


On Fri, Nov 7, 2008 at 2:48 PM, Wes Sisk <wsisk at cisco.com> wrote:


ES usually includes a device pack.  If a devicepack is included then loads
will be updated.  example from the 6.1.2 train:

6.1.2 base
6.1.2.1101-2:  7941_7961-sccp.8-3-5
6.1.2.1123-1:  7941_7961-sccp.8-4-1SR1

So yes, device loads can change with ES.  As ryan stated, the ES readme
should be included in the zip file.

Regards,
Wes



-- 
Ed Leatherman
Assistant Director, Voice Services
West Virginia University
Telecommunications and Network Operations


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081118/8c57331e/attachment.html>