[cisco-voip] CCM fantasy request list...

Justin Steinberg jsteinberg at gmail.com
Thu May 8 22:04:23 EDT 2008


7931 phone does a good job of emulating a key system.

check out my cool youtube video!
http://youtube.com/watch?v=lh72TwOe0mM

Also, for outbound calls, check out the service parameter
'matchingcgpnwithattendantflag'.  I've not actually used this parameter
before, but it's been something I've wanted to try. I think this parameter
is still in current versions of CM.  anybody tried it before?


On Thu, May 8, 2008 at 1:42 PM, Jonathan Charles <jonvoip at gmail.com> wrote:

> I am willing to bet that most (if not all) the people on this board
> have thrown their lot in with Cisco. We want Cisco to succeed because
> their success and ours are tied, inextricably, together.
>
> To that end, we want Cisco's products to be the best they can be. We
> never want a customer to say to us, 'your kidding, I have to give up
> core feature X if I get this system???' or worse, have to buy more
> hardware to do it.
>
> I want to be in a position to never have to say, 'no that isn't
> supported in the new system...' and I have a LOT of customers with
> giant sites that need full-scale giant PBX features, and remote sites
> that need key system functionality. The goal here is to unify the
> entire enterprise voice system, which means I need to support both
> large-scale and small-scale deployments on the same system.
>
> And we do that.
>
> But if I have a customer that wants to page through the phone (cuz
> they have that feature on their legacy PBX), and they have a bunch of
> remote sites, they do NOT want to have to buy 30 or 40 servers to
> support that feature... It is silly to even tell them that that is
> what they would need to do. It also sends the sale straight to Avaya
> or Nortel.
>
>
>
> Jonathan
>
> On Thu, May 8, 2008 at 1:36 PM, Ed Leatherman <ealeatherman at gmail.com>
> wrote:
> >
> > I respectfully disagree..
> >
> > When Cisco started out in this arena with the call manager product it was
> > lacking many features that traditional PBX's had for years, it still is
> but
> > getting much better because they're constantly adding features. They
> can't
> > just throw up their collective hands and say a particular feature isn't
> > valid, go buy another product. Now, there might be a business case or
> > technical reason why or why not to include something, but thats a
> different
> > story.
> >
> > I have a ton (literally) of traditional PBX and hybrid systems on campus
> > right now that
> > A) Have zone paging
> > B) Can configure key system buttons
> >
> > I don't expect CCM to do everything, but putting in feature requests etc
> > certainly doesn't hurt.
> >
> >
> >
> >
> > >
> > >
> > > Lines:
> > > UCCM is not a key system so don't complain about it not working like
> one.
> > If you need a key system put in express. This product needs to scale to
> > thousands and thousands of phones. Something a key system can not do.
> > >
> > > There are several products to accomplish paging. Again it is a PBX
> system
> > that must scale to a very high number of devices. You know it does not do
> > paging when you install it so if your customer needs that either put in
> the
> > correct system like express or if they want paging purchase the correct
> > third party product.
> > >
> >
> >
> > --
> > Ed Leatherman
> > Senior Voice Engineer
> > West Virginia University
> > Telecommunications and Network Operations
> > _______________________________________________
> >  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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080508/66c7f037/attachment-0001.html 


More information about the cisco-voip mailing list