<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:11.0pt;
font-family:"Calibri","sans-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;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>If CUC drops the message into the single inbox, will avaya VM really see it as a VM? I have my doubts on that one. This pilot seems to be setting up Cisco to fail. Someone how, you need to get this to be a fair test, and find out what the customers evaluation/criteria for success.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:black'>Dennis Heim<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Sr. UC Engineer<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>World Wide Technology<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Office: 314.212.1814<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>Email: <a href="mailto:dennis.heim@wwt.com"><span style='color:blue'>dennis.heim@wwt.com</span></a><o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><a href="http://www.wwt.com/"><span style='color:blue'>www.wwt.com</span></a><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p><div><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>Gregory Wenzel<br><b>Sent:</b> Wednesday, May 23, 2012 8:06 AM<br><b>To:</b> cisco-voip@puck.nether.net<br><b>Subject:</b> [cisco-voip] Anyone hear of Avaya with CUPS integration?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have a client who is working backwards to go forwards. Mgmt wants to compare Avaya to Cisco so a pilot is in works starting today but call control will stay Avaya. There are no immediate plans on going Cisco. We are involved to help push the pilot as we are not an Avaya reseller. There are Cisco phones but the users whom will be evaluating this only have Sip Avaya and legacy Avaya phones. There will be test phones in the pilot lab area but these will not be made available to the evaluation users. Maybe ip communicator phones will be available to the eval users not sure.<o:p></o:p></p><p class=MsoNormal>A remote cucme site does have h323 peer to Clan / Med card on the Avaya switch so 4 digit dial works both ways is currently in use but that brings nothing to the pilot.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We are thinking to have CUC for store with Single inbox integrated to exchange 2010, Avaya system will get mwi and so will Cisco test phones in the lab and have Jabber client but call control of Avaya sip phones is where we fall short. I don’t see how that could work. Lync is not an option.<o:p></o:p></p><p class=MsoNormal>I am thinking of SME integration with Avaya but not sure as I have little exp with SME.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What will SME buy us?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Versions<o:p></o:p></p><p class=MsoNormal>Avaya (not sure model)<o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Communication Manager Reports as: R015x.02.1.016.4<br>Modular Messaging 5.2<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cisco v8.6.2x<o:p></o:p></p><p class=MsoNormal>CUCM<o:p></o:p></p><p class=MsoNormal>CUC<o:p></o:p></p><p class=MsoNormal>CUP<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Any comments welcomed <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>TIA<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Greg Wenzel<o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br>This message w/attachments (message) is solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any products. <o:p></o:p></span></p></div></body></html>