PBX accessing 3cx.net

[ayachem]

Hi,

We are working on eliminating insecure SSL/TLS protocols on our network. It appears that every 10 minutes or so, the 3CX server connects to https://3cx.net:433 using TLS 1.0, which is one of the protocols we want to stop using.

Does anyone know if this is for updates, license check, webmeeting, etc? And whether 3CX.net is the correct address that should be used? Most websites have already added TLS 1.2 support, so I'm surprised that this one does not appear to use it. Or it's possible the PBX server is coded to not support it.

We are running version: 15.0.57336.0.

Thanks,

Michelle

 

[LeonidasG_3CX]

Thanks for the feedback.

There is a 2 way channel between webmeeting.3cx.net and this is used for WebMeeting functionality. Without it, WebMeeting won't work.
In regards to the TLS 1.0 part, we'll look into this and get back to you.

 

[LeonidasG_3CX]

We will be upgrading this connection to 1.2 quite soon.
You need to do nothing on your side other than to wait for a few days. The connection will then be automatically upgraded on our side.

 

[LeonidasG_3CX]

TLS 1.2 will be in fact delayed as it's not a priority at the moment.
Much more important and interesting features are currently in development. For the moment TLS 1.0 will remain and will be revisited at a later time.