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