01-18-2016 07:29 PM - edited 03-17-2019 05:32 AM
Hi Gents,
I have an legacy Avaya PBX that requires to works with CUCM. Based on Avaya documentation that I found which based on CM v4, I create a trunk using H323 by creating H323 GW with Avaya IP address. On on the Avaya sides, AGC networks guy has configured on his portion accordingly.
So, from Avaya phone can now call to Cisco phone by dialing full DN (eg: 91011234), however from Cisco phone unable to call Avaya DN (eg: 2345). The avaya dude insists that he could not see any sort of incoming signal from Cisco to his device. However, I could verify my call flow is works by using DNA in CUCM.
Below is the call traces I captured from rtmt. Anyone can shed something here?
01-18-2016 07:51 PM
Hi Hidzwan,
Please provide the complete trace file or at least all messages filtered with the guid '807CB59206C1E501030056A4C6520000'H
Manish
01-18-2016 10:49 PM
01-18-2016 10:56 PM
This one looks to be for the good call as it shows the call connecting and a normal call clearing message.
Manish
01-18-2016 11:01 PM
Does it means on the configuration is fine on CUCM side? Until now I'm still getting busy dial tone when dialing the Avaya extension number. Do u suggest to ask Avaya vendor to check on their end?
01-18-2016 11:04 PM
If we see the Setup message being sent out from cucm towards Avaya system then Avaya needs to confirm if they are receiving it or not. If the setup message is lost somewhere between cucm and Avaya then the underlying gateways / switches need to be checked as per the topology.
Manish
01-18-2016 11:18 PM
That's the weird part as we don't have anything sits in between CUCM and the Avaya server.
The Avaya CM itself does the GW function from the CUCM perspective, however they claimed that they don't see the call signal from their console.
avy phone -- avy CM ------H323 ------- CUCM ------ ip phone
-----------------------------------------> OK
<---------------------------------------- BUSY TONE
01-18-2016 11:22 PM
If we see the setup message going out from cucm then it should ideally reach Avaya with your setup. Try resetting the h323 gateway on cucm to see if that helps. It would be good if you can get on call with Avaya and ask them to collect the traces in real time and show that the call setup has not reached Avaya system.
Manish
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide