Solved New Webmeeting URL with v18 - security concerns

[mdsmm]

Hi,
with v18 the Webmeeting URLs changed as mentioned here: https://www.3cx.com/community/threads/ip-not-url.84128/post-393254

I have two considerations to this decision:
1. Everybody who wants to use this feature must have a DMZ because no one wants to give access from the Internet directly to a server within his LAN. In case of a vulnerability an attacker may be able to get access to the whole LAN.
2. The default destination port 5001 can't be reached by people behind a proxy or a firewall because these ports are often filtered.

Is it possible to get back the same behavior as in the previous version?

 

[StefanW]

Is it possible to get back the same behavior as in the previous version?

No, the pure cloud-hosted option was removed for the privacy benefits of the new version.

1) I would assume that over 90% of our customers open the HTTPs port to product services, such as Exchange OWA or 3CX. It is also needed to work remotely on a 3CX System (3CX Apps). Therefore it is nothing just related to 3CX VC.

2) You can install 3CX on 443 given that your internet access has this port not already in use.

Alternative to mitigate both of your requests, you can relocate 3CX into the cloud.