<!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.2900.3243" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>How many out there have actually installed a new
cluster for the IPCCx installation so they don't have to go through the upgrades
each time they upgrade callmanager?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </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=svoll.voip@gmail.com href="mailto:svoll.voip@gmail.com">Scott
Voll</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=d4rkf1ber@gmail.com
href="mailto:d4rkf1ber@gmail.com">d4rk f1br</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</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, January 30, 2008 3:47
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] Moving /
Upgrading 4.1(3) to CallManager 6.0 ?</DIV>
<DIV><BR></DIV>
<DIV>you have to upgrade IPCC at the same time as CM. see if you can get
one more server out of the budget. ;-)</DIV>
<DIV> </DIV>
<DIV>Unity is just the TSP update.</DIV>
<DIV> </DIV>
<DIV>you should be OK with the licensing so long as you do a DMA out of CM 4.1
then do the import. this will convert your current phones / licensing
over.</DIV>
<DIV> </DIV>
<DIV>if you like what you have... you may wait for CM 7.x. last I heard
is that it will be OS independant. Meaning you can run windows or
appliance.</DIV>
<DIV> </DIV>
<DIV>I find most of my info out at CIPTUG. Take with the CM BU (Wade)
and I aslo told him that the IPCC upgrade with every CM upgrade is a
problem. He seem to think a Version +1 should be a viable option but
didn't know when they will get to it. Not in CM 6.x maybe 7.x.</DIV>
<DIV> </DIV>
<DIV>we also talked about how fast the new versions are coming out.
Cisco is going to slow the releases. Currently they have been running
new Version every 12 months and a minor 6 months after. they are
going to change that to 18 months and 9 months. he heard our biggest
issue is keeping the versions that are coming out stable.</DIV>
<DIV> </DIV>
<DIV>Based on the feed back at CIPTUG most users are waiting for CM 6.1 for
there upgrade. only CM 5.x installs were new installs.</DIV>
<DIV> </DIV>
<DIV>Hope that helps.<BR></DIV>
<DIV>Scott<BR><BR></DIV>
<DIV class=gmail_quote>On Jan 30, 2008 12:27 PM, d4rk f1br <<A
href="mailto:d4rkf1ber@gmail.com">d4rkf1ber@gmail.com</A>> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV>Starting to 'look' at what all is involved with moving or
upgrading to CM 6.0. Currently running CM 4.1(3) on two older MCS
servers, just a publisher and subscriber. If the budget allows I am
hoping to actually purchase new hardware for this and possibly run both
versions in parrallel for testing and what not.</DIV>
<DIV> </DIV>
<DIV>Couple of things though I am concerned with is that I seem to recall
hearing something about licensing on 6.0 for phones? Apparently Cisco
has introduced some new licensing stuff with 6.0 that reminded me of unity
licensing in a way.</DIV>
<DIV> </DIV>
<DIV>I suspect that by moving to 6.0 I would also have to look into Unity
and IPCCX compatibility issues and the best way to address dealing with all
things at once. If CM 6.0 requires IPCCX 6.0 and Unity ? well thats a
pretty big deal and really makes upgrading a huge pain in the arse
obviously. Its often difficult enough to upgrade one thing and deal
with those repercussions for a while, but to have to do all together well
thats just gonna suck. :-)</DIV>
<DIV> </DIV>
<DIV>To me upgrading to 6.0 is really not something I believe is worthwhile
as I don't see what we are really going to gain from it. However I am
a tad concerned about letting things age you know, both hardware and
software. I do see some possible benefits and features in some of the
newer versions of either IPCCX and Unity, but those typically say you need
your CallManager to be a new version. So as long as I stay humming
along with 4.x, which in itself may be sufficient I can't leverage some new
feature I see available in one of the other products.</DIV>
<DIV> </DIV>
<DIV>And finally I guess I would have to ask does anyone know the latest
news on 7.0 ? I have heard and read about release dates in early 2009,
but obviously nothing is concrete of course. It does however leave the
person like me wondering what to do of course. Even if I were to
dedicate myself to saying yes I am going to move to 6.0 this year, well it
would like not happen to Q3 or Q4 at which time we may very well be hearing
about actual 7.0 release dates being only months away.</DIV>
<DIV> </DIV>
<DIV>Its sad that things have become what they are if you ask me. So
many versions in so a relatively short time. Whats worst is the people
on the fringes of things, the people who happen to hear about this release
or that and so they question why we are "so far behind" on our callmanager
versions, or who hear about an upcoming callmanager release and wonder when
will we move to this or that. Its gotten to be about as bad as trying
to keep up with Windows versions almost. Never thought the phone
system would become like this. Is it the price you pay for
innovation? And is there really all that much innovation to warrant
it? Who
knows..</DIV><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"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR></BLOCKQUOTE></DIV><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR></BLOCKQUOTE></BODY></HTML>