Not sure if anyone has come across this and really, this is just an FYI.
We ran hosted 3cx v18 Linux server with no issues whatsoever. Locally, all desk phones (PoE) and mobiles (WiFi) worked great. NAT hairpin properly enabled on our Watchguard Firebox and working. The v20 release came so I upgraded with relatively minor issues. It messed up a few settings which I quickly resolved. Maybe a few days later I noticed the Android client when connected to local wireless just sat at "connecting". The v20 upgrade was the ONLY change made to anything that matters.
Read up on v20 requirements to find split DNS is required. No problem there so I set up, confirmed it resolves, but no change. Disabled NAT hairpin on the firewall thinking one is interfering with the other, but still not able to connect. Interestingly today, I performed a few tests while in the "connecting" state. The application would ring and even show the call was picked up when answered, but the desk phone making the call just kept ringing the extension.
Purged 3CX from the phone and all data associated with it. Installed anew and added both extensions back to it. No change.
I have always used private DNS (Cloudflare) on the device and even with v18 there were no issues. Only when I upgraded to v20 did this crop up. Disabled private DNS on the device and boom, online. Tried several other private DNS providers (Quad9 etc.) and same result with all. No connection for 3CX.
Though this is not an Android issue (no issue before v20 server upgrade), I can confirm this exists on Android 14. Upgraded to Android 15 today and still an issue. Oddly, the web version of the client works fine on the device with same conditions where the native app fails.
We ran hosted 3cx v18 Linux server with no issues whatsoever. Locally, all desk phones (PoE) and mobiles (WiFi) worked great. NAT hairpin properly enabled on our Watchguard Firebox and working. The v20 release came so I upgraded with relatively minor issues. It messed up a few settings which I quickly resolved. Maybe a few days later I noticed the Android client when connected to local wireless just sat at "connecting". The v20 upgrade was the ONLY change made to anything that matters.
Read up on v20 requirements to find split DNS is required. No problem there so I set up, confirmed it resolves, but no change. Disabled NAT hairpin on the firewall thinking one is interfering with the other, but still not able to connect. Interestingly today, I performed a few tests while in the "connecting" state. The application would ring and even show the call was picked up when answered, but the desk phone making the call just kept ringing the extension.
Purged 3CX from the phone and all data associated with it. Installed anew and added both extensions back to it. No change.
I have always used private DNS (Cloudflare) on the device and even with v18 there were no issues. Only when I upgraded to v20 did this crop up. Disabled private DNS on the device and boom, online. Tried several other private DNS providers (Quad9 etc.) and same result with all. No connection for 3CX.
Though this is not an Android issue (no issue before v20 server upgrade), I can confirm this exists on Android 14. Upgraded to Android 15 today and still an issue. Oddly, the web version of the client works fine on the device with same conditions where the native app fails.
Last edited:
