<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PlaceName"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:blue;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
/* List Definitions */
@list l0
        {mso-list-id:433594841;
        mso-list-template-ids:1504101688;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Once again to echo:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>4.1 ---- features ------ 5.0<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>4.2 -----features ----- 5.1<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;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)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;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.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Scott<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>PS. The last “dot oh” upgrade
I did, took 23 hours, 3 tac engineers and 6-7 developers.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <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> <st1:PersonName w:st="on">candace_holman@harvard.edu</st1:PersonName>;
cisco-voip@puck.nether.net<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</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:
10.0pt'>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><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:
10.0pt'>It comes down to:</span></font><o:p></o:p></p>
</div>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>feature availability (SIP, etc)</span></font><o:p></o:p></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>upgrade issues (current features not supported in
future version target)</span></font><o:p></o:p></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>bleeding edge factor -or- the "dot oh"
syndrome</span></font><o:p></o:p></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>support issues (how much experience does the TAC
have)</span></font><o:p></o:p></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>stability (are there all the patches you want in
there)</span></font><o:p></o:p></li>
</ul>
<div>
<p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:
10.0pt'>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><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>--------------------------------------------------------------------------------<br>
Lelio Fulgenzi, B.A.<br>
Network Analyst (CCS) * <st1:PlaceType w:st="on">University</st1:PlaceType> of <st1:PlaceName
w:st="on">Guelph</st1:PlaceName> * <st1:place w:st="on"><st1:City w:st="on">Guelph</st1:City>,
<st1:State w:st="on">Ontario</st1:State> <st1:PostalCode w:st="on">N1G 2W1</st1:PostalCode></st1:place><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<o:p></o:p></span></font></p>
</div>
<blockquote style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>----- Original Message ----- <o:p></o:p></span></font></p>
</div>
<div style='font-color:black'>
<p class=MsoNormal style='background:#E4E4E4'><b><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial;font-weight:bold'>From:</span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> <a
href="mailto:candace_holman@harvard.edu" title="candace_holman@harvard.edu">Candace
Holman</a> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><b><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial;font-weight:bold'>To:</span></font></b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> <a
href="mailto:cisco-voip@puck.nether.net" title="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><b><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial;font-weight:bold'>Sent:</span></font></b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> Thursday, April
13, 2006 12:11 PM<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><b><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial;font-weight:bold'>Subject:</span></font></b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> Re: [cisco-voip]
Torn apart by choices - old or new solutions? Simply speaking: CM5.0 or CM4.x<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>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">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">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 <st1:place
w:st="on"><st1:PlaceName w:st="on">Call</st1:PlaceName> <st1:PlaceType w:st="on">Center</st1:PlaceType></st1:place><br>
> g. Cisco IPCC replacement of the existing <st1:place w:st="on"><st1:PlaceName
w:st="on">Nortel</st1:PlaceName> <st1:PlaceName w:st="on">Call</st1:PlaceName>
<st1:PlaceType w:st="on">Center</st1:PlaceType></st1:place>, 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">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><o:p></o:p></span></font></p>
</blockquote>
</div>
</body>
</html>