Update 5 BETA 2 Issue

[Cornel]

I have updated my On-Premise Debian installation by installing the alpha version first, then beta 1, and finally beta 2.
After update, when I navigate to the "Secure SID" page, all the options are disabled. Although I can see the checkbox marked and the certificate names displayed, none of the settings are editable.

Additionally, all my outgoing calls now fail with the following error: sip:xx.xxx.xx.xx:5061 replied: Request Timeout (408)
For context, I am using Twilio Elastic SIP.

If I change the port in the "Voice and Chat" menu -> Twilio trunk -> Server Detail to 5060 (unsecure), the call is successful.
However, I am specifically aiming to ensure the calls remain secure.

I’d greatly appreciate any insights or troubleshooting steps you could recommend.

 

[Cornel]

Another issue I would like to bring to your attention is regarding the Backup Restore functionality.

I created a backup prior to the update, but when I attempt to restore it, the system still reflects the new version (Beta 2). My expectation was that restoring the backup would revert the system to the previous stable version.

Could you clarify if this is the intended behavior or if there is an issue with the restore process?

 

[YiannisH_3CX]

Although I can see the checkbox marked and the certificate names displayed, none of the settings are editable.

That is correct. If the option is enabled and the certificates listed then you are good to go. Twilio however is not supported for TLS with 3CX as our implementations are not fully compatible so I would recommend sticking to UDP.

I created a backup prior to the update, but when I attempt to restore it, the system still reflects the new version (Beta 2). My expectation was that restoring the backup would revert the system to the previous stable version.

Could you clarify if this is the intended behavior or if there is an issue with the restore process?

That is the correct. The backup does not revert your system to the version the backup was taken. The backup will restore your configuration in your current installation.

 

[Cornel]

That is correct. If the option is enabled and the certificates listed then you are good to go. Twilio however is not supported for TLS with 3CX as our implementations are not fully compatible so I would recommend sticking to UDP.

What I noticed with the old version is that I was able to make calls on the Twilio SIP trunk using the port 5061 setting without needing any additional configuration on the Twilio side to secure the trunk. However, after the update, calls are only successful if I switch the port to 5060 (unsecured). It seems something must have changed in the new version. Could there be a new configuration that I need to set up?

Additionally, could you please elaborate on what using UDP entails?

That is the correct. The backup does not revert your system to the version the backup was taken. The backup will restore your configuration in your current installation.

Thank you so much for the clarification. The reason I initially thought the backup included more than just the configuration is the size of the backup file—it seems to be over 100MB. In my opinion, that should be enough to store the full version of the application.

Is there an option to back up the full system?

 

[SteveITS]

The backup contains XML files, WAV files, phone firmware, etc...the content. Often a backup of an older version won't install onto a newer version so it's a bit surprising it allowed that.

You would need to back up the server itself, for instance, a VM image. Or install the older version and restore. The newer database may have a different structure than the older version expects.

 

[Cornel]

Thank you, @SteveITS. The VM image is probably the best option.

Could you also share your input on the Secure trunk question?

 

[SteveITS]

Could you also share your input on the Secure trunk question?

"Twilio however is not supported for TLS" seems like it's not going to work. That's how they list it at https://www.3cx.com/partners/sip-trunks/usa/ as well. I skimmed through, looks like Voxtelesys is the only one listed with TLS support there.

 

[YiannisH_3CX]

What I noticed with the old version is that I was able to make calls on the Twilio SIP trunk using the port 5061 setting without needing any additional configuration on the Twilio side to secure the trunk. However, after the update, calls are only successful if I switch the port to 5060 (unsecured). It seems something must have changed in the new version. Could there be a new configuration that I need to set up?

Not sure what your configuration was on V18 but TLS has never worked with Twilio. The reason is that Twilio uses a wildcard certificate which 3CX does not support. If you were only using the port 5061 that does not mean you were also using TLS. Nothing has changed in this regard from V18 to V20.

Additionally, could you please elaborate on what using UDP entails?

UDP is the supported transport. It's not secure as TLS but it's what 99% of the industry is using.

Is there an option to back up the full system?

If you are using virtualization then a snapshot of the system is the best option. The 3CX backup mechanism does not work like that.