<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2838" name=GENERATOR><!--[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 name="PlaceType"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="PlaceName"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="PostalCode"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="State"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="City"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="place"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="PersonName"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</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 lang=EN-US vLink=blue link=blue bgColor=white>
<DIV><SPAN class=230130616-13042006><FONT face=Arial color=#0000ff size=2>IPCC
4.5 is for CM 5.0. Its probably in New Product Hold right now, but the
documentation is available.</FONT></SPAN></DIV>
<DIV><SPAN class=230130616-13042006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=230130616-13042006><FONT face=Arial color=#0000ff size=2>-Dylan
Vanderhoof</FONT></SPAN></DIV>
<DIV><SPAN class=230130616-13042006><FONT face=Arial color=#0000ff
size=2>Semaphore Corporation</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Voll, Scott
[mailto:Scott.Voll@wesd.org] <BR><B>Sent:</B> Thursday, April 13, 2006 8:55
AM<BR><B>To:</B> Lelio Fulgenzi; netfortius@gmail.com;
cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] Torn apart by
choices - old or newsolutions?Simplyspeaking: CM5.0 or
CM4.x<BR><BR></FONT></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I will echo
Lelio.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Go with CM 4.2.
I don’t know if CM 5.0 even has a IPCCx version yet. 4.x is very stable
and works very well. I tend to be a little too bleeding edge and I would
not start with 5.0 unless you have to. I really like the upgrade/patch
process of 5.0 but I don’t think it’s worth the TAC calls just for that or
SIP. <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">IMHO go with 4.x and
upgrade in a year or so to 5.x after they have had enough time to test it out
in the real world.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Scott<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; 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 8:38 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
<st1:PersonName w:st="on">netfortius@gmail.com</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?Simplyspeaking: CM5.0 or
CM4.x</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=2><SPAN
style="FONT-SIZE: 10pt">Personally speaking, I'd go with 4.2. 4.x is a more
mature product than 5.0 and I'd never install a "dot oh" of anything. 4.2 has
a very large feature set (more than 5.0) so you have to weigh what you would
be losing if you don't go with 5.0. SIP is a big one for sure. Appliance model
is another. There may be others. The biggest thing you want to look out for
when migrating is not so much new features but existing feature replacement
and of course stability. I think you would get that with 4.2, not sure about
5.0. Look at upgrading in two years to 5.1 or 5.2 when you're not the guinea
pig.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">--------------------------------------------------------------------------------<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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; 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 face=Arial
size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">From:</SPAN></FONT></B><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> <A
title=netfortius@gmail.com href="mailto:netfortius@gmail.com">Netfortius</A>
<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><B><FONT face=Arial size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">To:</SPAN></FONT></B><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> <A
title=cisco-voip@puck.nether.net
href="mailto: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 face=Arial size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">Sent:</SPAN></FONT></B><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
Thursday, April 13, 2006 11:33 AM<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><B><FONT face=Arial size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">Subject:</SPAN></FONT></B><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
[cisco-voip] Torn apart by choices - old or new solutions? Simplyspeaking:
CM5.0 or CM4.x<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">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>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></BLOCKQUOTE></BODY></HTML>