<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=iso-8859-1"><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:0cm;
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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=ES-AR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Hi John,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>That does remind me of a similar issue we had with that Avaya implementation too... This happened way after it was deployed, and I donīt remember what triggered the issue…<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Avaya didnīt see any incoming calls. The Avaya engineer was looking into the trunk, just like you, and didnīt see anything.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Analyzing the UCM traces there was a timeout on the call setup due to a lack of response from Avaya to the H225 messages from the UCM. To be sure, we did the same thing you are going to do, we sent someone to sniff the port where the Avaya H323 card was connected Taking a look at those capture we confirmed packets were getting there and after a couple of attempts to setup the H323 call, without having any response from the other peer, the UCM was sending the timeout (exactly the same thing we had seen on the traces). After taking the UCM out of the picture, the Avaya engineers worked further until they found out what was the problem.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>If I remember right the solution from Avaya was to allow all incoming calls from all the ip addresses from the different UCM nodes (Publisher and Subs), and not just allowing one of the IPs (where Avaya was pointing the trunk). <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>For what TAC told you they are seeing the same thing…<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Once again, I donīt know much about Avaya, so if you do, check if thereīs a way of allowing IPs. like some kind of ACL.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>As a personal recommendation, like I said on the previous email, if thereīs an IVR on the Avaya side, test on it, to see if DTMFs are going through. If not, you might be in time to change the trunk from H323 to SIP. There are other ways still using H323 to do that OOB to in-band conversion, but I most definitely wouldn’t recommend them...<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Good luck!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bantz John F [mailto:BantzJohnF@JohnDeere.com] <br><b>Sent:</b> lunes, 02 de mayo de 2011 08:51 p.m.<br><b>To:</b> ATIENZA, Gonzalo; Haas, Neal; cisco-voip@puck.nether.net<br><b>Subject:</b> RE: [cisco-voip] Integration between CM 7 and an Avaya switch<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Thanks for the links and the tips!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>We are working with TAC right now trying to get this up and working.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>We have it setup using H.323 with a trunk on the Avaya side and a Gateway configured on the CM side. It appears that the connection is up. We can place calls from the Avaya side, and they will traverse the IP Trunk and ring on the Cisco phones, but we cannot place calls from Cisco to Avaya. TAC tells us that it looks like CM is trying to place the call, but not getting a response from Avaya. When I watch the Avaya trunk during test calls from CM to Avaya, I don’t see anything hitting it.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Tomorrow we are going to setup port mirroring on the data ports on the Avaya side and the Cisco side and see if we see packets going both ways when we make test calls. If I see packets from the CM IP Address hitting the Avaya CLAN card, but the call is failing, I will assume that TAC is correct and the Avaya side is not responding. If I don’t see any packets hitting the Avaya side coming from CM, we will then look at the port that CM is connected to on the other side, place more test calls and see if CM is sending packets out towards the Avaya side. If it is, then we should be able to assume that we have something odd going on in our LAN/WAN that is blocking the traffic in that direction. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>We will also take a look at the info from the links Neil sent and from Gonzalo’s suggestions and see if we can make it work.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Thanks<br>John Bantz<br>John Deere - Global Infrastructure Services<br>515-267-4628 - office<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>515-314-6478 - cell<br><a href="mailto:BantzJohnF%40JohnDeere.Com"><span style='color:#1E66AE'>BantzJohnF@JohnDeere.Com</span></a><o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='color:#1F497D'><br></span><span lang=EN-US style='font-size:8.0pt;color:#1F497D'>CONFIDENTIALITY. This electronic mail and any files transmitted with it may contain information proprietary to Deere & Company, or one of its subsidiaries or affiliates, and are intended solely for the use of the individual or entity to whom they are addressed, shall be maintained in confidence and not disclosed to third parties without the written consent of the sender. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.</span><span lang=EN-US style='color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ATIENZA, Gonzalo [mailto:Gonzalo.ATIENZA@LA.LOGICALIS.COM] <br><b>Sent:</b> Monday, May 02, 2011 6:25 PM<br><b>To:</b> Haas, Neal; Bantz John F; cisco-voip@puck.nether.net<br><b>Subject:</b> RE: [cisco-voip] Integration between CM 7 and an Avaya switch<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Iīve worked with an integration between Avaya and UCM 7.</span><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The only thing configured on the UCM was H323 GWs pointing to the H323 cards from the Avaya platform, thatīs pretty much all there is...</span><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>There was a problem with DTMFs at some point, Avaya works with in-band DTMFs, and as you may know, with H323 UCM sends them OOB. Somehow the problem was solved by the Avaya engineers, doing something on their platform.</span><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>To avoid that you could try using SIP, configuring on the UCM to use RFC 2833...</span><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Hope it helps!</span><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US 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>Haas, Neal<br><b>Sent:</b> lunes, 02 de mayo de 2011 07:32 p.m.<br><b>To:</b> 'Bantz John F'; cisco-voip@puck.nether.net<br><b>Subject:</b> Re: [cisco-voip] Integration between CM 7 and an Avaya switch<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><a href="http://www.jaymzworld.com/w/images/0/07/Cisco-ses.pdf">http://www.jaymzworld.com/w/images/0/07/Cisco-ses.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><a href="https://devconnect.avaya.com/public/download/interop/CUCM-IPO-SIPtrk.pdf">https://devconnect.avaya.com/public/download/interop/CUCM-IPO-SIPtrk.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US 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>Bantz John F<br><b>Sent:</b> Monday, May 02, 2011 2:43 PM<br><b>To:</b> cisco-voip@puck.nether.net<br><b>Subject:</b> [cisco-voip] Integration between CM 7 and an Avaya switch<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Does anyone have any documentation on integrating an Avaya ACM 4.x and CM 7?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>We are trying to connect the two systems with an H.323 or SIP trunk so we can extension dial between the two systems.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>We have found documents showing us how to integrate a CM 4 and an Avaya, but cannot find anything on CM 7.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Thanks<br>John Bantz<br>John Deere - Global Infrastructure Services<br>515-267-4628 - office<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>515-314-6478 - cell<br><a href="mailto:BantzJohnF%40JohnDeere.Com"><span style='color:#1E66AE'>BantzJohnF@JohnDeere.Com</span></a><o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US><br></span><span lang=EN-US style='font-size:8.0pt'>CONFIDENTIALITY. This electronic mail and any files transmitted with it may contain information proprietary to Deere & Company, or one of its subsidiaries or affiliates, and are intended solely for the use of the individual or entity to whom they are addressed, shall be maintained in confidence and not disclosed to third parties without the written consent of the sender. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p></div></body></html>