<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000066">
Thanks Lelio,<br>
i understood what you said about licensing and contracts.<br>
But, i would like to know apriori if possible that, if i have
upgraded to 7.1.5 i would have to wait for the 8.5 because you
cannot upgrade from 7.1.5 to 8.0.<br>
Is this info for the next versions of 8.5 somewhere?<br>
<br>
Thanks a lot<br>
Anthony<br>
<br>
<blockquote
cite="mid:679049508.422535.1295622031373.JavaMail.root@simcoe.cs.uoguelph.ca"
type="cite">There are two sides to this question, licensing and
technical.<br>
<div style="font-family: Verdana; font-size: 10pt; color: rgb(0,
0, 0);"><br>
Technically speaking, you'll have to look at the CUCM
compatibility matrix to see what versions can upgrade to what
versions. Cisco hasn't been too bad at making upgrades work
especially from an n-1 release, however, there are occasions
depending on how far into the N-1 train you venture you will not
be able to upgrade to the next release. For example, you can't
upgrade from 7.1.5 to 8.0 I believe, but you can upgrade from
7.1.5 to 8.5 (please check the matrix for exacts).<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html</a><br>
<br>
Licensing is another matter and handles the legality of
upgrades. An "Essential" contract allows you access to minor
upgrades, i.e. N.x to N.y. A UCSS contract allows you access to
major upgrades, i.e. N.x to N+1.y. In actuality, you can upgrade
to the latest version, not just N+1. ;)<br>
<br>
Hope that helps, I'm sure others will offer up some comments as
well.<br>
<br>
<span><br>
<span name="x"></span>---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr.
Popeil)<br>
<span name="x"></span><br>
</span><br>
<hr id="zwchr"><b>From: </b>"Anthony Kouloglou"
<a class="moz-txt-link-rfc2396E" href="mailto:akoul@dataways.gr"><akoul@dataways.gr></a><br>
<b>To: </b><a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck-nether.net">"cisco-voip@puck-nether.net"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><br>
<b>Sent: </b>Friday, January 21, 2011 9:52:01 AM<br>
<b>Subject: </b>[cisco-voip] Upgrading to 8.5(1) CUCM<br>
<br>
Hi All,<br>
i was wondering, if i upgrade to CUCM 8.5(1), will i be then
able to upgrade to the upcoming 8.x or 9.0 versions?<br>
Is there a roadmap for that?<span style="font-size: 10pt; color:
silver;" lang="EN-US"></span><br>
<br>
Kind Regards<br>
Anthony<span style="font-size: 12pt;" lang="EN-US"></span>
<div class="moz-signature">
<div class="Section1"> </div>
</div>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div>
</blockquote>
</body>
</html>