Bug/Feature with newer iOS not connecting to locally hosted 3CX

caldwell

Bronze Partner
Joined
Nov 8, 2010
Messages
98
Reaction score
28
Inside a customer's building on their wifi and LAN, some users (especially news ones set up recently) have issues where the 3CX app on iPhone goes unregistered randomly.

I've verified the standard Apple "limit IP address tracking" is turned off. This WILL break split-DNS resolution on a local LAN. (Rules out their squirrelly, idiotic default settings.)

Turning off wifi and forcing cellular data ALWAYS fixes it. (Rules out "is the phone system up and connected to the LAN"?)

On desktop/laptops, the issue is that Apple has begun enforcing their own policy restrictions. I discovered this was the issue with Brave browser no longer being able to connect to the phone system until I would "allow Brave to discover devices on the local network." This is under Settings -> Privacy and Security -> Local Network -> Brave (turn on).

In researching this, guess what. Yes, they have a similar setting now on Apple iOS devices. Same thing: Settings -> Privacy and Security -> Local Network -> 3CX (turn on).

Mine was OFF. I'm not sure I ever was asked on the phone to allow this for 3CX App at any point. I asked one of the customer employees to check the same setting and to turn 3CX On. If her phone stays registered for a week, we have probably found the culprit.

For 3CX Developers, here's what AI said. I'm not sure if you are currently editing this .plist file to turn this Local Network access ON, but you probably should.

What to check​

To fix this, you must grant the permission on a per-app basis. Apple does not provide a global "Always Allow Local Network" switch for security reasons.
You can verify and change these settings here:

Settings > Privacy & Security > Local Network

If you are a developer or maintaining custom apps, you must ensure the Info.plist includes the NSLocalNetworkUsageDescription key with a purpose string. Without this, the system will effectively block your app from reaching the local subnet, regardless of your intent.

In a professional/IT environment, this creates a significant hurdle for managing internal infrastructure, but it is fundamentally a sandbox restriction baked into the OS. You are correct that it is the exact same "feature" (nuisance) present on macOS.
 

Forum statistics

Threads
112,001
Messages
590,224
Members
164,939
Latest member
soteris 2