Ports to open at the client's end when using a hosted by 3cx solution.

[moatley]

Hello All,

I have a client who wishes to use a hosted by 3cx solution, they have a corporate firewall protecting their wan/lan's which has most outbound ports locked down as well as inbound ports.

They wish to use IP phones via the 3cx SBC, 3cx Apps for ios and android via the corporate Wi-Fi that also connects through the wan/lan's and also the 3cx webclient on a number of PC's (WebRTC traffic).

Would I be correct in thinking that I only need to open the following outbound ports from the client side;

Allow any device on inside to connect outbound through the firewall using port 5090 tcp and udp to connect to the hosted 3cx server. (For SBC and 3CX Apps)
Allow any device on inside to connect outbound through the firewall using ports 9000-10999 udp to connect to the hosted 3cx server. (For RTP Audio including Webclient audio)
Allow any device on inside to connect outbound through the firewall using port 443 to connect to the hosted 3cx server. (For provisioning info, https / WebRTC)

Is there any other ports I need to open or anything else I need to consider?
(unfortunately most configuration guides I've seen deal more with having he 3cx server on-site and do not really cover if a firewall is heavily locked down on the outbound ports.)

Any assistance, would be greatly appreciated.

Regards,

Mark.

 

[SteveITS]

Did you find https://www.3cx.com/docs/manual/firewall-router-configuration/ ?

“Inbound” would be from the server’s perspective so use those for outbound from the office. “Outbound” is irrelevant as that would be from the server out, on 3CX’s end.