<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>You
don’t need a 7931 to “emulate” a key system. Looks better with a 796x with a
7914.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Paper
inlays? Come on….<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Justin Steinberg<br>
<b>Sent:</b> Thursday, May 08, 2008 9:04 PM<br>
<b>To:</b> Jonathan Charles<br>
<b>Cc:</b> CiscosupportUpuck<br>
<b>Subject:</b> Re: [cisco-voip] CCM fantasy request list...<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>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>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Thu, May 8, 2008 at 1:42 PM, Jonathan Charles <<a
href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>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>
<span style='color:#888888'><br>
<br>
<br>
Jonathan</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><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<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal>> _______________________________________________<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><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<DIV><P><HR>
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
</P></DIV>
</body>
</html>