We upgraded to 4.0, and had quite a few bugs and issues with it until we got on 4.1. The upgrade itself went very smoothly, but the problems lingered for about 6months for us.<br><br>My 2 cents would be to hound your SE for a clear picture of the feature sets of each version, and make your decision based on that, keeping in mind what everyone has pretty much said about the dot oh (no!). If theres some killer feature that you can't live without, then maybe you should explore going to
5.0, depending on what your schedule looks like... still might want to wait for a maintenance release or so. <br><br>I think we are going to hold off until 5.1.somethinggreaterthan0 - depends on how bad we need those busy lamp fields by the end of the summer I think.
<br><br>Ed<br><div><span class="gmail_quote">On 4/13/06, <b class="gmail_sendername">Voll, Scott</b> <<a href="mailto:Scott.Voll@wesd.org">Scott.Voll@wesd.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;">
<div>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">Once again to echo:</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">4.1 ---- features ------ 5.0</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">4.2 -----features ----- 5.1</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">I think I heard 5.1 is slated for end of
this year, (But it's Cisco, so probably beginning of 2007)</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">I will be waiting for 5.2 personally, but
am really looking forward to the patching / upgrade process of the 5.x train
with active and standby partitions.</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">Scott</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">PS. The last "dot oh" upgrade
I did, took 23 hours, 3 tac engineers and 6-7 developers.</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<div>
<div style="text-align: center;" align="center"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr align="center" size="2" width="100%">
</span></font></div>
<p><b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma; font-weight: bold;">From:</span></font></b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma;">
<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
cisco-voip-bounces@puck.nether.net</a>] <b><span style="font-weight: bold;">On Behalf Of </span></b>Lelio Fulgenzi<br>
<b><span style="font-weight: bold;">Sent:</span></b> Thursday, April 13, 2006
9:19 AM<br>
<b><span style="font-weight: bold;">To:</span></b> <a href="mailto:candace_holman@harvard.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">candace_holman@harvard.edu</a>;
<a href="mailto:cisco-voip@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cisco-voip@puck.nether.net</a></span></font></p></div><font face="Tahoma" size="2"></font><div style="direction: ltr;">
<span class="e" id="q_10a9426b60549a26_1"><font face="Tahoma" size="2"><br>
<b><span style="font-weight: bold;">Subject:</span></b> Re: [cisco-voip] Torn
apart by choices - old or new solutions?Simply speaking: CM5.0 or CM4.x</font></span></div><div style="direction: ltr;"><p></p>
</div></div><div style="direction: ltr;"><span class="e" id="q_10a9426b60549a26_3">
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
<div>
<p><font face="Times New Roman" size="2"><span style="font-size: 10pt;">Agreed on those points. Sticking with 4.1(3) should provide an easier
feature upgrade to 5.0. But from what I hear, the 4.2 features will be
available in 5.1 and that was slated for release in 2007 or something like
that. But you are right....I would use several years as a guide line. 2 to 3
years.</span></font></p>
</div>
<div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
</div>
<div>
<p><font face="Times New Roman" size="2"><span style="font-size: 10pt;">It comes down to:</span></font></p>
</div>
<ul type="disc">
<li><font face="Times New Roman" size="2"><span style="font-size: 10pt;">feature availability (SIP, etc)</span></font></li>
<li><font face="Times New Roman" size="2"><span style="font-size: 10pt;">upgrade issues (current features not supported in
future version target)</span></font></li>
<li><font face="Times New Roman" size="2"><span style="font-size: 10pt;">bleeding edge factor -or- the "dot oh"
syndrome</span></font></li>
<li><font face="Times New Roman" size="2"><span style="font-size: 10pt;">support issues (how much experience does the TAC
have)</span></font></li>
<li><font face="Times New Roman" size="2"><span style="font-size: 10pt;">stability (are there all the patches you want in
there)</span></font></li>
</ul>
<div>
<p><font face="Times New Roman" size="2"><span style="font-size: 10pt;">and I would also add, product availability. It's probably alot easier
to get 4.1(3) install media than it would be 4.2 or 5.0.</span></font></p>
</div>
<div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
</div>
<div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;">--------------------------------------------------------------------------------<br>
Lelio Fulgenzi, B.A.<br>
Network Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <br>
Sanity First : Number of days with fewer than<br>
50 messages in my inbox at the end of the day: buffer overrun</span></font></p>
</div>
<blockquote style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color black; border-width: medium medium medium 1.5pt; margin: 5pt 0in 5pt 3.75pt; padding: 0in 0in 0in 4pt;">
<div>
<p><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">----- Original Message ----- </span></font></p>
</div>
<div>
<p style="background: rgb(228, 228, 228) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"><b><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; font-weight: bold;">
From:</span></font></b><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> <a href="mailto:candace_holman@harvard.edu" title="candace_holman@harvard.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Candace
Holman</a> </span></font></p>
</div>
<div>
<p><b><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; font-weight: bold;">To:</span></font></b><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> <a href="mailto:cisco-voip@puck.nether.net" title="cisco-voip@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
cisco-voip@puck.nether.net</a>
</span></font></p>
</div>
<div>
<p><b><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; font-weight: bold;">Sent:</span></font></b><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> Thursday, April
13, 2006 12:11 PM</span></font></p>
</div>
<div>
<p><b><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; font-weight: bold;">Subject:</span></font></b><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> Re: [cisco-voip]
Torn apart by choices - old or new solutions? Simply speaking: CM5.0 or CM4.x</span></font></p>
</div>
<div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
</div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;">To some extent I agree with Lelio and Scott, but it may be worth it to <br>
you to consider some other points:<br>
<br>
* 4.x will not have SIP lines for several years at best<br>
* 5.x has the option for SIP and SCCP<br>
* it could be difficult to upgrade 4.2 -> 5.x because
some of the<br>
user features in 4.2 are not duplicated in 5.x
for several years<br>
at best<br>
* 5.x is a RH Linux train, 4.2 is windows so your
considerations for<br>
hardware, organizational policies or tech
philosophies,<br>
engineering skillset, etc _may_ be different<br>
<br>
Candace<br>
<br>
> Subject:<br>
> [cisco-voip] Torn apart by choices - old or new solutions? Simply <br>
> speaking: CM5.0 or CM4.x<br>
> From:<br>
> Netfortius <<a href="mailto:netfortius@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">netfortius@gmail.com</a>><br>
> Date:<br>
> Thu, 13 Apr 2006 10:33:58 -0500<br>
><br>
> To:<br>
> <a href="mailto:cisco-voip@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cisco-voip@puck.nether.net</a><br>
><br>
><br>
> You may have already gotten used to my last string of questions here,
which - <br>
> I am not hiding it - are part of my attempt to gain info from the more <br>
> experienced people, on this subject, regarding a project I am working on
for <br>
> deployment of multi-site IPT & VoIP. I have gone into some details,
for some <br>
> questions I had, but now - reading tons of material every day, I have
become <br>
> very worried about the full blown solution chosen, vs. what is being
promised <br>
> just "around the corner". Here is where I would appreciate any
comments, of <br>
> any nature, thoughts, experience, "what-if" - anything you can
share about <br>
> this subject:<br>
><br>
> Scenario: multi-site deployment of Cisco CM, with the following objectives
in <br>
> mind:<br>
><br>
> 1. Replacement of existing old telephony solution, Nortel-based,
consisting of <br>
> PBX in each location, with Cisco-based IP-based communication systems (and
<br>
> not only one-to-one replacement of phones, but also steps toward unified <br>
> communications)<br>
><br>
> 2. Installation of Cisco solution consisting of:<br>
> a. CM 4.x (advised by Cisco) at the HQ + Unity integrated with Exchange
2003 <br>
> and a handful of IP phones (major testers of the technology) and
integration <br>
> with existing Nortel PBX at the HQ (PHASE 1)<br>
> b. IP phones in the remote location (complete replacement of everything
old, <br>
> including PBX) + SRST + standalone (storage-wise) Unity (PHASE 1)<br>
> c. Unified messaging at the HQ, in the "pilot" group, to the
best of the <br>
> abilities and availability of products around CM 4.x (e.g. PA, among
others, <br>
> as an example of what I am getting at) (PHASE 1)<br>
> d. Experience from c> ==> full implementation of unified messaging
at the <br>
> first remote ("upgrade" of the standalone Unity into an
Exchange-tied one - <br>
> is this even possible?!?) (PHASE 2)<br>
> e. remote site used as template fro all other sites (PHASE 2)<br>
> f. full upgrade at the HQ (PHASE 2), with the exception of Call Center<br>
> g. Cisco IPCC replacement of the existing Nortel Call
Center, after the <br>
> entire VoIP and IPT has proven reliable to sustain a Customer Service
(PHASE <br>
> 3)<br>
><br>
> 3. The unified communications (including messaging) will eventually
adddress <br>
> various business needs, primarily focused on mobility and real-time <br>
> communications and sharing<br>
><br>
> Having said all of the above, here are the issues I am struggling with:<br>
><br>
> - I have (and nobody in my network geeks group) no real experience with
Cisco <br>
> VoIP/IPT;<br>
> - the suggested solution, from Cisco, revolves around a CM 4.2 and,
gradually, <br>
> as explained above, updates to the point of full unified messaging - still
<br>
> 4.2-based<br>
> - I am getting conflicting messages from our Cisco group - they advise us
to <br>
> do the install with CM 4.2 (which would end up as a cluster of multiple <br>
> servers, at the HQ), not CM 5.0, but:<br>
> - I am reading and reading, and it appears to me that some features
associated <br>
> with CM 4.2 are dying (e.g. PA), while CM 5.0 seems to open the door for
much <br>
> more, but not everything backward compatible with 4.x<br>
> - tons of features are being advertised as related to CM 5.0, only, but
are <br>
> not ready yet, and are to be released this year (majority in second
quarter)<br>
><br>
> Bottom line - I am struggling with one major question (with no easy answer
- <br>
> thus appreciating any comments this list may have): should I move ahead as
<br>
> started, with the one site + pilot HQ, on CM 4.2 (PHASE 1), then go over
all <br>
> phases, then analyze what would need to be upgraded to a 5.0 environment,
if <br>
> certain additional features would become available and needed, and not <br>
> backward compatible<br>
> OR<br>
> should I just put a stop to the CM 4.x analysis and planning, and redo <br>
> everything (with the delay caused by various products availability) around
CM <br>
> 5.0?<br>
><br>
> As I said - any $0.02-$64K comments will be really appreciated. I will try
to <br>
> consolidate this type of info, in something useful, if enough data
warrants <br>
> it.<br>
><br>
> Thanks,<br>
> Stefan<br>
><br>
> <br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span></font></p>
</blockquote>
</span></div><div style="direction: ltr;"></div>
</div><br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br></blockquote></div><br>
<br clear="all"><br>-- <br>Ed Leatherman<br>IP Telephony Coordinator<br>West Virginia University<br>Telecommunications and Network Operations