<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>documentation? you got to be kidding,
right?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>i wish i was joking, but the only way i felt
confident was reviewing the configuration options and comparing them screen by
screen. printing the enterprise parameters as well as all the system parameters.
only then will you catch everything. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>it would be nice if there was documentation that
stated all the changes and differences, but it's just not there (or at least not
accurate).</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>voicemail ports is another thing you will want to
worry about. forwarding from one VM port to the other is handled much
differently.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>depending on what phone load you are running, you
might see differences in phone behaviour. that's what was important for us,
documenting that. a beta group helped us iron all that out.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>what do you mean by shear size of the deployment?
we have over 7200 phones and 8 servers in total. aside from the amount of time
it took, everything went pretty well. aside from the fact that our phones hit
the TFTP server pretty hard and some of them didn't come back with the
ringlists, etc. be prepared to reset your phones a few times after the upgrades
or at least try to upgrade them before the upgrade.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>and plan for your O/S updates in a seperate window.
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=techguy@gmail.com href="mailto:techguy@gmail.com">TechGuy</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, September 20, 2006 7:23
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] Upgrading CM 3.3(5)
to 4.1(3) ?</DIV>
<DIV><BR></DIV>I will be performing an upgrade on CM in a couple of
weeks. Going to<BR>go from 3.3(5) to 4.1(3). I have done this
upgrade before at a<BR>previous employer but much more nervous about this one
due to the<BR>shear size of the deployment. I am nervous about the end
user affect<BR>/ fallout to be honest.<BR><BR>Here they are setup with each
line in a partition, such as Line 1 in<BR>"PAR_Line_1" and Line 2 "PAR_Line_2"
they do this to forward line 1 to<BR>line 2 if line 1 is busy or
something. Now in 4.1(3) each line can<BR>support multiple calls so it
changes things a bit.<BR><BR>Anyone have any docs on what is changed and how
it affects the end<BR>users? How did you manage alot of this? Just
curious.<BR><BR>Thanks!<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">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BODY></HTML>