topic One way audio or no audio are in Collaboration Applications

Jabber problem over VPN

meneamgbr — Mon, 18 Mar 2019 01:56:02 GMT

I have a problem with jabber clients. Jabber to Cisco IP phone and Jabber to Jabber calls work fine within our LAN.

The problem is when someone from outside the LAN trying to use Jabber over VPN connection we encountered these symptoms :

1- When the call is between 2 IPhone clients or an IPhone and cisco IP phone everything works just finee .

2- when one of the 2 call parties or both are android or pc ==> the call is successful " meaning: the caller can ring the receiver " but when the receiving party answer the call there's no voice and they can't hear each other

Appreciate your help

One way audio or no audio are

Jaime Valencia — Thu, 22 Jun 2017 23:25:56 GMT

One way audio or no audio are most usually routing issues, there is no direct RTP path between the endpoints.

What approach should i take

meneamgbr — Sat, 24 Jun 2017 23:44:38 GMT

What approach should i take to solve this problem ?.. could it be a firewall-related issue or NAT issue ?

we are using Microsoft TMG firewall,, everything was working just fine but suddenly some calls have no audio and this problem happens only when using jabber clients on android or windows over vpn connection

Re: What approach should i take

D12- — Wed, 01 Apr 2020 20:40:55 GMT

did you ever get this figured out?

Re: What approach should i take

Ayodeji Okanlawon — Fri, 03 Apr 2020 05:26:35 GMT

Issues like this are always firewall related. Get your network team involved.

Re: Jabber problem over VPN

stevenle — Fri, 03 Apr 2020 19:28:44 GMT

There needs to be a NAT rule in your VPN connection that allows connectivity between the connected clients. Otherwise they will experience this audio issue. You didn't specify the type of VPN equipment your were using. Had this same issue with my ASA and Anyconnect clients when connected. Resolved with a NAT rule in the ASA firewall configuration section. Can't say why android is affected though, I only had this issue with connected PC's and their local Jabber client.