One way audio between Avaya PBX, Cisco GW and Service provider
I have a one way audio issue while calling the PSTN from the Avaya PBX. I have the following topology:
Avaya PBX --- Cisco GW --- CPE Service Provider
192.168.108.100 : Router Cisco (Gateway)
192.168.108.1 : Avaya Extreme (Switch)
192.168.109.2 : Media GW Avaya
192.168.108.3 : PBX Avaya
192.168.108.11: IP Phone
18.104.22.168 : IP Address for Signaling of CPE SP
22.214.171.124 : IP Address for Media of CPE SP
So the main problem is we can ONLY receive the service of the SP on our Cisco GW since Avaya does not support that interface. Since the Cisco GW loopback0 (126.96.36.199) is the one registered with the Service Provider, they only accept calls from that IP Address.
I made a NAT to announce everything with the loopback, the call is completed since the h.323 signaling is done with the loopback but the media is connected using the IP address of the avaya, so there is no audio.
Is there something that can be done on the Cisco GW to announce only the Loopback and avoid that one way audio? I'm not quite a Routing guru so any help will be appreciated.
Attached are the Sh run of the Cisco GW, a trace on the Service Provider CPE and a sniffer trace on the phone (eventhouhg is saved as a txt it needs to be open with ethereal or any other sniffer program)
Re: One way audio between Avaya PBX, Cisco GW and Service provid
From the avaya trace, I see:
Media Channel Address: 192.168.108.2:2056
Since Avaya I assume is sending under H245 OR channel ack an IP address not reachable, Cisco GW is not the one that originates this signalling| recognizing H.323 packets, it simply forwards the message.
Our Cisco GWs support this through NAT
NAT/PAT will change the IP headers but unless it is aware of H.323, SIP or SCCP signaling will not modify the embedded addresses in
the UDP or TCP payload used for signaling the media addresses resulting in one way or no way audio.
You may double check the PAT configuration or try using IPIP GW feature.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...