[cisco-voip] Integration between CM 7 and an Avaya switch

Mon May 2 21:15:54 EDT 2011

Hi John,

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...

Avaya didn´t see any incoming calls.  The Avaya engineer was looking into the trunk, just like you, and didn´t see anything.

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.

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). 

For what TAC told you they are seeing the same thing...

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.

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...

Good luck!

From: Bantz John F [mailto:BantzJohnF at JohnDeere.com] 
Sent: lunes, 02 de mayo de 2011 08:51 p.m.
To: ATIENZA, Gonzalo; Haas, Neal; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Integration between CM 7 and an Avaya switch

Thanks for the links and the tips!

We are working with TAC right now trying to get this up and working.

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.

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. 

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.

Thanks
John Bantz
John Deere - Global Infrastructure Services
515-267-4628 - office

515-314-6478 - cell
BantzJohnF at JohnDeere.Com <mailto:BantzJohnF%40JohnDeere.Com> 

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.

From: ATIENZA, Gonzalo [mailto:Gonzalo.ATIENZA at LA.LOGICALIS.COM] 
Sent: Monday, May 02, 2011 6:25 PM
To: Haas, Neal; Bantz John F; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Integration between CM 7 and an Avaya switch

I´ve worked with an integration between Avaya and UCM 7.

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...

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.

To avoid that you could try using SIP, configuring on the UCM to use RFC 2833...

Hope it helps!

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Haas, Neal
Sent: lunes, 02 de mayo de 2011 07:32 p.m.
To: 'Bantz John F'; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Integration between CM 7 and an Avaya switch

http://www.jaymzworld.com/w/images/0/07/Cisco-ses.pdf

https://devconnect.avaya.com/public/download/interop/CUCM-IPO-SIPtrk.pdf

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bantz John F
Sent: Monday, May 02, 2011 2:43 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Integration between CM 7 and an Avaya switch

Does anyone have any documentation on integrating an Avaya ACM 4.x and CM 7?

We are trying to connect the two systems with an H.323 or SIP trunk so we can extension dial between the two systems.

We have found documents showing us how to integrate a CM 4 and an Avaya, but cannot find anything on CM 7.

Thanks
John Bantz
John Deere - Global Infrastructure Services
515-267-4628 - office

515-314-6478 - cell
BantzJohnF at JohnDeere.Com <mailto:BantzJohnF%40JohnDeere.Com> 

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110502/e5d057dd/attachment.html>