Solved Webmeeting has wrong link since update to v18

[Steffen Maier]

Hello,

Since the update to v18 our webmeeting links are internal not external - so eg. http://192.168.50.30/blahblah instead of the xxxxx.3cx.net.
Therefore I cannot start a webmeeting any more.

Is there a way to configure the fqdn?
Under Adcanced / network settings / fqdn, the correct entry is set.

Thanks
Steffen

 

[ChrisC_3CX]

The Webmeeting portal is now local to your 3CX PBX so that would be expected. The Webclient will show the link (Local IP or FQDN) depending on whether you've accessed the webclient from a local or remote location but the email invitation should contain the FQDN.

Have you tried the link and it did not work?

 

[Steffen Maier]

Oh no! I dont want to open ports locally for using that just 3 times a year (security risk is too high).

Is there a way to get the old status?
Or do I have to take another vendor?

 

[Evolute IT]

Oh no! I dont want to open ports locally for using that just 3 times a year (security risk is too high).

Is there a way to get the old status?
Or do I have to take another vendor?

Just open the ports? It's only HTTPS.

Why go with something else suddenly?

 

[Steffen Maier]

When I open a single https port and 3cx has a security bug, then my network may get hacked.
A big risk compared to 3 times a year we use it.

Why taking that risk, when other services are online and not in my network?

 

[ChrisC_3CX]

Do bear in mind that allowing external traffic to your https port would only be required for external participants (remote to your PBX). If by any chance the participants are always local to the PBX, then port forwarding would not be required.

 

[Evolute IT]

When I open a single https port and 3cx has a security bug, then my network may get hacked.
A big risk compared to 3 times a year we use it.

Why taking that risk, when other services are online and not in my network?

Then host the PBX in the Cloud?

Just know that the chances of being hacked through 3CX mostly depends on how much you secured your network, your Windows/Linux host and the security settings in 3CX.

We never got hacked in 4 years. Multiple customers are on 3CX too.