<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3429" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=578121414-18112008><FONT face="Lucida Sans"
color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=578121414-18112008><FONT face="Lucida Sans"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=578121414-18112008><FONT face="Lucida Sans"
color=#0000ff size=2>If you are happy to let the phones upgrade themselves after
the ES install then there is no need to upgrade them
beforehand.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=578121414-18112008><FONT face="Lucida Sans"
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=578121414-18112008><FONT face="Lucida Sans"
color=#0000ff size=2>-Ryan</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Scott
Voll<BR><B>Sent:</B> Tuesday, November 18, 2008 12:17 AM<BR><B>To:</B> Ed
Leatherman<BR><B>Cc:</B> cisco voip<BR><B>Subject:</B> Re: [cisco-voip] CUCM -
Engineering Special firmware versions<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>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?</DIV>
<DIV> </DIV>
<DIV>Scott<BR><BR></DIV>
<DIV class=gmail_quote>On Fri, Nov 7, 2008 at 11:56 AM, Ed Leatherman <SPAN
dir=ltr><<A
href="mailto:ealeatherman@gmail.com">ealeatherman@gmail.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">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.
<DIV class=Ih2E3d><BR><BR>
<DIV class=gmail_quote>On Fri, Nov 7, 2008 at 2:48 PM, Wes Sisk <SPAN
dir=ltr><<A href="mailto:wsisk@cisco.com"
target=_blank>wsisk@cisco.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV bgcolor="#ffffff" text="#000000">ES usually includes a device
pack. If a devicepack is included then loads will be updated.
example from the 6.1.2 train:<BR><BR>6.1.2 base<BR>6.1.2.1101-2:
7941_7961-sccp.8-3-5<BR>6.1.2.1123-1:
7941_7961-sccp.8-4-1SR1<BR><BR>So yes, device loads can change with
ES. As ryan stated, the ES readme should be included in the zip
file.<BR><BR>Regards,<BR><FONT
color=#888888>Wes</FONT></DIV></BLOCKQUOTE></DIV><BR clear=all><BR></DIV>
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c>-- <BR>Ed Leatherman<BR>Assistant Director, Voice
Services<BR>West Virginia University<BR>Telecommunications and Network
Operations<BR></DIV></DIV><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR></BLOCKQUOTE></DIV><BR></BODY></HTML>