99 times out of 100 when you have 1 way voice path you have either a codec mismatch or packets from one direction not making it back through the proper path through the proper ports.
For the first, list trace the stations and see what they are negotiating.
For the second you will probably need some packet captures.
Do a list tra station and check to see where the audio path is going (also available via a status station). If the two endpoints can't communicate due to a firewall rule this will stop the audio. This data could change with every call (med pros, shuffled calls etc) so make sure you account for all call flows.
All of our testing for vpn to lan is always one way audio. And we do a list trace and all packets is looks find. No jitter and packet lost. All port in the VPN server is open.
In which direction doesn't the audio flow?
Is the CM on the LAN or are the IP Phones on a separate network? In that case can you ping an IP Phone on the LAN.
If you call a VDN can you hear announcements?
In the IP-Network Region where the VPN phones are located turn of Inter direct-IP and shuffling. This will cause the call to "anchor" and should resolve your 1-way issue. It does impact the number of DSP resources used so make sure you're not over committing.
If all works well you have a firewall issue. Assuming these might be something like a Cisco ASA?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.