[cisco-voip] Upgrading CCM 4.x to CM Express?

[Bill Talley]

First question would be, what kind of maintenance did they buy on their
existing system?  Do they have SASU or UCSS?  If so, the costs to upgrade
the software would mostly be eliminated and considerations would primarily
be potential hardware upgrades and labor.

Additionally, what kind of feature requirements do they have?

How many call manager servers do they have now (i.e. redundant servers)?
How do they use Unity from a call handling/routing perspective (unity can
use call handlers, CUE will use scripts)?   Do they use call routing rules
in Unity?  Again, I think functionality is provided through scripting in CUE
unless call input, routing rules are included in CUE now on mailboxes.

What are their conferencing requirements?  Unless I'm mistaken, UCME
supports 3 conference participants unless sufficient DSPs are available to
support more and depending on what kind of PSTN access they have (T1 or
multiple T1s) they may not have enough DSPs on the router to do enhanced
conferecing.

UCME will require a larger router to support 70 phones on UCME, so expect to
replace the 2801 if you go that route.

That's just a few things that come to mind.


On Fri, May 15, 2009 at 11:07 AM, Todd Franklin <toddnh65 at gmail.com> wrote:

> I have a client that is financially challenged right now, like a lot of
> them!
> He has an install of maybe 70 phones, spread out over 4 buildings, linked
> up by fiber.
> 3560s and 2801s, mostly 7940s and 7960s.
> He is looking to move to V7.
>
> His question is, wouldn't it be more cost effective for him to move to CM
> Express and the lower end Unity?
> He does not integrate with Exchange at all, he uses IMail for email.
>
> What are your thoughts?
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090515/d476bfa8/attachment.html>