[cisco-voip] Thoughts on 5.X CCM

[Ed Leatherman]

Bernhard,

In your implementations of IPCC-X 4.5, did you do an upgrade (reinstall)
from 4.0 or was it from scratch? If you did, how did that process go for
you?

We currently run IPCCX 4.0 and the migration process from 4.0 to the version
4.5 which supports CCM 5 is the biggest roadblock I have right now to
upgrading callmanager. From everything I've been told there is no "upgrade"
path and we will have to do a complete reinstallation to get to 4.5, and we
have to do it at the same time we upgrade callmanager since 4.5 only
supports ccm 5. what a mess! If I thought I would have this much trouble
upgrading callmanager+IPCCX, i'd have put our call centers on a smaller
seperate CCM cluster.

Thanks!

On 12/6/06, Bernhard Albler <balbler at nts.at> wrote:
>
>  Hi Folks,
>
>
>
> I have two implementations of CCM 5.0(4) and IPCC-X 4.5 (both ipcc-x
> premium)
>
> Worked pretty fine, no issues with IPCC-X so far. CCM has a few bugs. Some
> smaller some larger. There is something a bit annoying with regard to CTI
> with 5.0(4): CTI Callrequests (from agent desktop for example) will wait
> for a 20 second overlap dialing timeout. But that is fixed since ES 17 or
> so.
>
> If you happen to run 7825H1 Servers: very nasty bug there with the HP raid
> driver: IO Starvation spikes every 5 hours will sometimes cause the CCM
> Service to core dump. Ouch.
>
> Otherwise, call control is really quite stable on 5.0.
>
>
>
>
>
> Regards
>
> Bernhard
>
>
>
> ------------------------------------------
>
> DI (FH) Bernhard Albler, NTS AG
>
> Tel.: +43 (316) 405 455 -0, email: balbler at nts.at
>
>
>   ------------------------------
>
> *Von:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *Im Auftrag von *Voll, Scott
> *Gesendet:* Mittwoch, 06. Dezember 2006 00:45
> *An:* Vince Loschiavo; Wydra, Jason; cisco-voip at puck.nether.net
> *Betreff:* Re: [cisco-voip] Thoughts on 5.X CCM
>
>
>
> In any of the implementations have they been using IPCCx or Unity.  If so,
> what versions.
>
>
>
> Scott
>
>
>
>
>
>
>  ------------------------------
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Vince Loschiavo
> *Sent:* Tuesday, December 05, 2006 3:27 PM
> *To:* Wydra, Jason; cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Thoughts on 5.X CCM
>
>
>
> Yeah, I have a couple of 5.0(4) implementations.
>
>
>
> The call control and functionality of the phones is rock solid.
>
>
>
> The Admin Web page needs a little work....ran into a few bugs...but
> nothing major.
>
>
>
> I'm anxiously awaiting the 5.1 release...available on CCO next week.
> Hopefully they fixed those admin page bugs!  :P
>
>
>
>
>  ------------------------------
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Wydra, Jason
> *Sent:* Tuesday, December 05, 2006 6:22 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Thoughts on 5.X CCM
>
> I'm curious how much 5.X is being deployed. I haven't heard too much buzz
> about it. Is it because it's unstable, scary, unappealing or what? I'm
> trying to get an idea before I start recommending it or building it in my
> lab. Any war stories? Most of the deployments I see today are 4.1.3because it's a trusted/stable version. Is
> 5.X still too immature even though it's been available for some time?
>
>
>
> Thanks,
>
>
>
> Jason Wydra
>
> Berbee
>
> Cisco Voice Engineer
>
> 8725 West Higgins Road, Suite 700
>
> Chicago, Il. 60631
>
> IP phone 773.867.6084
>
> Cell 630-209-9792
>
> Jason.Wydra at berbee.com
>
> www.berbee.com
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>


-- 
Ed Leatherman
Senior Voice Engineer
West Virginia University
Telecommunications and Network Operations
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061206/1ca1a220/attachment-0001.html