[cisco-voip] Moving / Upgrading 4.1(3) to CallManager 6.0 ?
Matthew Saskin
matt at saskin.net
Wed Jan 30 16:29:13 EST 2008
Enterprise has some very strict versioning requirements as it relates to
CallManager. In some cases a JTAPI update is all that is needed, but
occasionally there will be some defect that requires patching (on the
IPCC CM cluster side of things) where we don't want to patch within the
primary IPT environment.
With most of these environments we're talking 1000+ agents and
significant revenue generation, so anything that can be done to keep a
stable environment usually is :)
-matt
>
> So doesn Enterprise need to be upgraded everytime CCM is upgraded? It
> has been that way with Express.
>
> Carlos
>
>
> *Matthew Saskin <matt at saskin.net>*
> Sent by: cisco-voip-bounces at puck.nether.net
>
> 01/30/2008 03:54 PM
>
>
> To
> Lelio Fulgenzi <lelio at uoguelph.ca>
> cc
> cisco-voip at puck.nether.net
> Subject
> Re: [cisco-voip] Moving / Upgrading 4.1(3) to CallManager 6.0 ?
>
>
>
>
>
>
>
>
> Every single IPCC (enterprise) environment I work with runs a dedicated
> CallManager cluster.
>
> A very small handful of my larger IPCCx environments are on dedicated
> clusters, but they are few and far between.
>
> -matt
>
> Lelio Fulgenzi wrote:
> > 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?
> >
> >
> >
> > ----- Original Message -----
> > *From:* Scott Voll <mailto:svoll.voip at gmail.com>
> > *To:* d4rk f1br <mailto:d4rkf1ber at gmail.com>
> > *Cc:* cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> > *Sent:* Wednesday, January 30, 2008 3:47 PM
> > *Subject:* Re: [cisco-voip] Moving / Upgrading 4.1(3) to CallManager
> > 6.0 ?
> >
> > you have to upgrade IPCC at the same time as CM. see if you can get
> > one more server out of the budget. ;-)
> >
> > Unity is just the TSP update.
> >
> > 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.
> >
> > 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.
> >
> > 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.
> >
> > 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.
> >
> > 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.
> >
> > Hope that helps.
> > Scott
> >
> > On Jan 30, 2008 12:27 PM, d4rk f1br <d4rkf1ber at gmail.com
> > <mailto:d4rkf1ber at gmail.com>> wrote:
> >
> > 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.
> >
> > 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.
> >
> > 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. :-)
> >
> > 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.
> >
> > 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.
> >
> > 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..
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
More information about the cisco-voip
mailing list