Is it possible for 3CX on-premise to ignore internal network (always use external IP)

[ddx]

Hi,

We are a potential customer and we are testing the free version at the moment. I am currently running 3CX Debian version and have it set up in its own network totally separate from our production network for security reasons. The PBX system has 1-1 NAT to a static public IP with 3CX's FQDN and thing works fine externally (if users are out of office). However when users are in the office, all the 3CX clients (web browser, desktop app, mobile app) ring fine but have no audio both ways. After packet capturing, it seems that the clients are attempting to connect RTP via the internal IP address (instead of the external IP / FQDN). To make this work, I had to open UDP ports between our production network and the isolated 3CX PBX network. With the UDP ports open, the system works, but we would rather not have anything open between the two networks. Is there a way for 3CX to ignore its internal IP and always refer to its external IP / FQDN? Thanks

• 3CX Version, 18.0 Update 3 Build 461
• Server OS, Debian
• Is the 3CX Server Hosted and where? on premise
• IP Phone Make/Model/Firmware version, Google Chrome, desktop app, mobile app (Android + iPhone)
• Provisioning Method:
• Trunk Provider or VoIP Gateway Make/Model, Yeastar TE100
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

 

[Saqqara]

i do not think this is possible, you are going to have to allow access to the 3cx server from the required networks

the Issue is the firewall and terminaration points are the same wan IP address - protected network can not go out and back in on the same public network IP’s - reasons you need to allow inter vlan to vlan routing

 

[ddx]

We do have multiple public IP addresses, and two firewalls, but both firewalls share the same primary router, also because the SIP gateway is in the production network, so I guess it is not possible this way. Maybe we should get another firewall just for the 3CX PBX, and have the SIP provider out on the internet, then the 3CX PBX would work external only like we wanted? But at that point we might as well just have it hosted by 3CX