Current Android Beta: no connection over Tunnel

Status
Not open for further replies.

Daniel Hermann

Customer
Joined
Feb 5, 2019
Messages
7
Reaction score
0
Hello,

I have an android phone where I use the 3cx app. Whenever in the local lan (wifi) it works.
However when I am not in the local lan it does not connect (Waiting for network).

I activated "Use 3CX Tunnel for remote connections (3CX Client only)" on that extension.
I have (ONLY!) the Port 5090 forwarded on the firewall.
I get a lot of "icmp" packages on port 84 on the firewall (from my external phone ip), but no connection on port 5090.
The FQDN is resolved correctly (checked by pinging it from the android device).

I provisioned the android client with the QR-Code. In settings on the android client "Use 3CXTunnel when Out of office" is activated.

any tips?

thanks
Daniel


EDIT: in the app at "3CX Tunnel" it says "Requires 3CX Phone System for Windows".
I run my 3cx on a debian host. Is that the problem? I thought there was feature parity?
 
Beside the TCP and UDP port 5090, you also need the HTTPs port (443 or 5001 depending on your installation). Could you send me where you found "EDIT: in the app at "3CX Tunnel" it says "Requires 3CX Phone System for Windows" please. Just upfront, your PBX is just fine on Debian, tunnelling works on both.
 
I found that under Settings -> accounts -> (select account)

9499



I do not have the HTTPS-Port forwarded, I thought that the advantage of the tunnel was tunneling all over the one port?

I also found out that I can be called outside the office, but I can make no calls.


EDIT: with 5001 also forwarded it works.
 
Last edited:
the single port is for Voice (SIP + RTP streams), the Presence / Provisioning still req. a separate connection to the PBX HTTPs port.
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,832
Messages
589,286
Members
164,662
Latest member
DejanMDS