Restrict access to a 3CX hosted system except specific IP address range?

[PBX_Programmer]

Hi,

I'm trying to find out if 3CX has the ability to restrict all remote remote access to a 3CX hosted PBX, apart from access attempts coming from a pre-determined IP address or range of addresses? We've got a few customers who now have 3CX hosted systems for which we are the partner. I have been asked to investigate whether 3CX can set their firewall etc to allow browser access only from our own IP address range. Based on what I've seen so far, it appears that this is not possible and anyone from anywhere is able to get to the login page and attempt to log in. Is that actually the case, though? Or can we make a request to 3CX that nobody even gets as far as the login page unless they're coming from behind our own public IP address?

I don't know if I've explained myself very well. In brief, we don't want anyone being able to browse to the hosted 3CX's admin page and get a response apart from us, ever. Is that possible?

Thanks!

 

[Charles_3CX]

This is not possible, as 3CX hosted systems are deployed with predefined ports and access configurations. This setup does not allow for the addition of custom network rules for individual clients.


You can, however, apply console restrictions to limit access to the Admin Console to specific IP addresses. Please note that while this will restrict console access, the login page will still be publicly reachable, and web clients will remain accessible from any address.

 

[SteveITS]

@PBX_Programmer They could move off 3CX hosting and then set access rules in the firewall in front of 3CX.

Restricting access that tightly may affect webmeeting links.

 

[PBX_Programmer]

This is not possible, as 3CX hosted systems are deployed with predefined ports and access configurations. This setup does not allow for the addition of custom network rules for individual clients.


You can, however, apply console restrictions to limit access to the Admin Console to specific IP addresses. Please note that while this will restrict console access, the login page will still be publicly reachable, and web clients will remain accessible from any address.

Ok thanks @Charles_3CX , I thought that was probably the case but just needed to check. I guess that will have to do, we'd just better make sure there are strong passwords set, 2FA applied and no loose ends.

Thanks!

 

[PBX_Programmer]

@PBX_Programmer They could move off 3CX hosting and then set access rules in the firewall in front of 3CX.

Restricting access that tightly may affect webmeeting links.

Ok thanks @SteveITS ,

Moving them off hosted isn't really an option for us, we're trying to work towards getting them all moved off on-premise systems and onto hosted eventually. We don't use webmeeting links and none of our customers do either but yes you're right, that might be affected if it were locked down too tightly.

 

[Alphabetic]

Ok thanks @SteveITS ,

Moving them off hosted isn't really an option for us, we're trying to work towards getting them all moved off on-premise systems and onto hosted eventually. We don't use webmeeting links and none of our customers do either but yes you're right, that might be affected if it were locked down too tightly.

I think what @SteveITS meant was, host them in your own VPS and lock it down.

 

[PBX_Programmer]

I think what @SteveITS meant was, host them in your own VPS and lock it down.

I reckon you're right @Alphabetic , thanks for that.