Hi All,
I have not found a solution in the forums to my particular problem but have found a few people who have asked.
The 3CX app for Android was not able to connect to server when I was on the work WiFi while it would work on LTE and home Wifi.
The solution provided in the docs is to use internal DNS resolution for the PBX server (dual DNS). This caused problems for my workplace as we do not run internal DNS servers.
I investigated the topic of NAT reflection (aka "hairpining") with my pfSense router.
I found when configuring the NAT port forwarding rules setting "NAT reflection" set to "Enable (NAT + proxy)" the app has full connectivity (but "Enable (Pure NAT)" does not).
I hope this helps others out! I'm glad to have my coworkers stop asking why their office number doesn't work while at work!
Maybe 3CX might even update their documentation for pfSense configuation(?).
thanks,
Justin Ng
I have not found a solution in the forums to my particular problem but have found a few people who have asked.
The 3CX app for Android was not able to connect to server when I was on the work WiFi while it would work on LTE and home Wifi.
The solution provided in the docs is to use internal DNS resolution for the PBX server (dual DNS). This caused problems for my workplace as we do not run internal DNS servers.
I investigated the topic of NAT reflection (aka "hairpining") with my pfSense router.
I found when configuring the NAT port forwarding rules setting "NAT reflection" set to "Enable (NAT + proxy)" the app has full connectivity (but "Enable (Pure NAT)" does not).
I hope this helps others out! I'm glad to have my coworkers stop asking why their office number doesn't work while at work!
Maybe 3CX might even update their documentation for pfSense configuation(?).
thanks,
Justin Ng
Last edited:
