The Android Apps no longer connect on Wifi- Connecting...

Status
Not open for further replies.

vankampen

SOHO User
Joined
Aug 29, 2023
Messages
22
Reaction score
2
The Android app (Version 20.0.0.44) does not connect to the 3cx server (V18 update 9) over WIFI anymore. It connects and works without wifi.
There is split DNS set up, and this resolves the FQDN to the local server, also from the mobile phone on wifi
The Firewall checker works and is green.

On Android, on the WIFI the FQDN resolves to the local 3cx Ip address, without wifi, it resolves to the public IP address.

The webclient works, both on Android and on Windows. During setup of the 3cx server, I was chose a mydomain.my3cx.nl fqdn for the installation, and a myhost.mydomain.nl for local users. Both work locally.

Is there a way to view a log to see what is going wrong?
 
Last edited:
Hi there.
Android app itself have logs, and you can also set verbose logging level on, and its in the advanced settings of the app.
 
Thank you, I did that.
I see an error when logging in to 3CXPhone.MyPhoneLoginManager when trying this on the local lan when trying to reach https://mydomain.com/ (domain name and ip address changed for privacy)

06-28 18:22:03.551 10305 10305 W 3CXPhone.MyPhoneLoginManager: Error connecting to UrlSet(baseUrl=https://mydomain.com, myPhoneUrl=https://mydomain.com/myphone/MPWebService.asmx, myPhoneStreamUrl=https://mydomain.com/myphone/a.MyPhoneAsyncHandler) (SocketTimeoutException) - failed to connect to mydomain.com/001.001.001.001 (port 443) from /10.138.153.234 (port 55890) after 5000ms

That error does not appear when logging in outside the local network. Can it be that this is the error? Is V20 of the Android app working with V18 of the server?

I can't reach that page from chrome either (not internal and not externa to the lan), while https://mydomain.com goes to the 3cx configuration page, both from internal and external.
 
So your app needs to resolve your FQDN and your local DNS must have A record that will point to the local IP of the server, this is a 3CX requirement for V20.
 
So your app needs to resolve your FQDN and your local DNS must have A record that will point to the local IP of the server, this is a 3CX requirement for V20.
Thank you, it does resolve the fqdn. But the server is v18. A web browser does resolve the fqdn and starts the web client without problems. It is just the app that does not work. The page https://mydomain.com/myphone/MPWebService.asmx does not resolve internally an publicly.
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK