<!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.2800.1479" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>It seems that there is a conflict in documentation
here. The Q&A says one thing and the compatibility mattrix says another. I
will be opening a case with the TAC tomorow to try and clear things up and see
what can be done about getting TAC support for a 3.3(3) -> 4.1(2) upgrade.
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><FONT face=Arial size=2>According to the
<A
href="http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_qanda_item0900aecd80199e9a.shtml"><SPAN
class=contenttitle>Cisco CallManager 4.1 Q&A</SPAN> reference page
</A>you can order an upgrade package for 3.X to 4.1. In
particular:</FONT>-----
-----<BR><FONT face=Arial size=2><STRONG></STRONG></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><FONT face=Arial size=2><STRONG>Q.
What is the price of the upgrade to Cisco CallManager 4.1?<BR>A.
</STRONG>Customers with a Software Application Support plus Upgrades (SASU)
contract who currently are running Cisco CallManager 3.2, 3.3, or 4.0 and
desire to upgrade to Cisco CallManager 4.1 can order their free upgrades
using the PUT tool located at <A
href="http://www.cisco.com/upgrade">http://www.cisco.com/upgrade</A>.<BR></FONT><FONT
face=Arial size=2></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE>
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><FONT face=Arial size=2>According to <A
href="http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_installation_guide_chapter09186a00802e4192.html#wp1038571">Upgrading
Cisco CallManager Release 4.1(2)-Preinstallation Information </A>some
information regarding which versions are supported. 3.3 is mentioned, but when
you go to the <A
href="http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm#MinimumVersions">compatibility
matrix</A>, it's only 3.3(4) that is supported. </FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV dir=ltr style="MARGIN-RIGHT: 0px">
<H3 class=p_H_Head2><FONT face=Arial size=2>From which versions of Cisco
CallManager can I upgrade to Cisco CallManager Release 4.1(2)?
</FONT></H3><A name=wp1038456></A>
<P class=pB1_Body1><FONT face=Arial size=2>To verify which versions of
Cisco CallManager are compatible for upgrade, refer to the <EM
class=cEmphasis>Cisco CallManager Compatibility Matrix</EM>. To obtain
the most recent version of this document, go to
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
</FONT></P><A name=wp1042937></A>
<P class=pB1_Body1><FONT face=Arial size=2>If your server runs a version of
Cisco CallManager Release 3.2 or earlier, you must first upgrade every
server in the cluster to the latest version of Cisco CallManager
Release 3.3 before you can upgrade to a version of Cisco CallManager
Release 4.1. For information on upgrading to Cisco CallManager Release 3.3
or 4.0, refer to the appropriate version of the <EM
class=cEmphasis>Upgrading Cisco CallManager</EM> document. You cannot
upgrade directly from Cisco CallManager Release 3.2 or earlier to Cisco
CallManager Release 4.1. </FONT></P><A name=wp1038462></A>
<P class=pB1_Body1><FONT face=Arial size=2>Before you perform any upgrade
procedures, Cisco strongly recommends that you install the latest operating
system upgrade/service release, SQL service releases/hotfixes, and Cisco
CallManager service release for the versions that currently run in the
cluster. Cisco provides the service release and corresponding readme
documentation on cisco.com. To obtain these documents, go to <SPAN
class=cXRef_Color><A
href="http://www.cisco.com/public/sw-center/sw-voice.shtml">http://www.cisco.com/public/sw-center/sw-voice.shtml</A></SPAN>.
</FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE>
<DIV dir=ltr style="MARGIN-RIGHT: 0px"><FONT face=Arial size=2> </DIV>
<DIV>So, your (and our) upgrade path seems like it will be 3.3(3) -> 3.3(4)
-> 4.1(2). This seems a little odd, since we were told that the 3.3(4) would
be a train of it's own, and 3.3(3) is moving to the 4.x train. This might
actually buy us something, since 3.3(4) is compatible with current and some of
the later versions of IPCC express and CRS that 3.3(3) is not compatible with,
giving us a migration path to upgrade CRS/IPCC after our 3.3(4) upgrade.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------</DIV>
<DIV> </DIV>
<DIV>Caution Cisco recommends that you only upgrade to Cisco CallManager 4.1(2)
from a version that is compatible for upgrade to 4.1(2). Versions that are not
compatible for upgrade to 4.1(2) may contain features that are not supported in
4.1(2). If you upgrade from an unsupported version, you will not be able to
access those features that are not supported in 4.1(2) and you will lose the
data that is associated with those features.
<BR>--------------------------------------------------------------------------------</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>Lelio Fulgenzi,
B.A.
<A href="mailto:lelio@uoguelph.ca.eh">lelio@uoguelph.ca.eh</A><BR>Network
Analyst (CCS)<BR>University of
Guelph
FAX:(519) 767-1060 JNHN<BR>Guelph, Ontario N1G
2W1
TEL:(519) 824-4120
x56354<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>
remove the 1st letter of the canadian alphabet from my email, eh!</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=mfa@crec.ifas.ufl.edu href="mailto:mfa@crec.ifas.ufl.edu">Mike
Armstrong</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, December 29, 2004 9:42
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] Chaining CCM
upgrades</DIV>
<DIV><BR></DIV>We want to go from 3.3(3) to 4.1(2), which really could involve
a <BR>3.3(3)->4.0(1)->4.0(1)sr2a->4.0(2a)->4.0(2a)sr1a->4.1(2)
chain. I'd like to <BR>shorten the process by<BR><BR>a) not installing
the interim service releases, and<BR>b) ignoring the subscriber altogether
until the publisher is up to 4.1(2), <BR>then simply building a new 4.1(2)
subscriber and linking it up. Service <BR>interruption is not a
problem.<BR><BR>Any thoughts/wisdom/comments/advice?<BR><BR>Mike
Armstrong<BR>UF/IFAS CREC
<BR><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>