Actually, I think this problem maybe deeper than just the App not loading recents. Answering calls on the mobile over WiFi with a local IP address on the LAN is fine, but as with the Recents not loading, answering an incoming 3CX call on the mobile over 4G while away does not work either.... You can answer, but the result is silence and the caller does not know that the call has been answered.
I suspect this is part of a deeper problem, on which I've spend hours with no success; attempting access to our 3CX system from outside the LAN does not work. Attempting to access
https://xxxxxx.3cx.uk:5001/ gets a "connection refused" error, and on the LAN we can only access it using the local IP address. nslookup does not resolve the server IP address either.
Ports are open on our router as attachment below. The firewall has a green tick, *BUT* fails the full cone NAT tests when run.
Now I suspect our setup might be the problem. Our Internet access is via a leased fibre shared with another company, delivered to each of us via a Ubiquiti EdgeRouter 6p - one ethernet port connecting to our router, another to theirs.
So - the question is, do I need to have ports on the EdgeRouter open too? (As in, is that why the full cone NAT tests fail, and correspondingly, why we are having trouble with the Android app?) I'd be terrified to somehow screw up their settings!! (unsure whether the NAT can be done for one ethernet port on it only, without affecting the other....)
I would point out that all the on-premise phones are working just fine, doing everything they should, incoming and outgoing calls, voicemail, etc.... just no external access to the FQDN and not able to answer calls/see Recents list on the Android app off-premises.
Sorry this is long winded, thanks for reading this far!
