V20 Upgrade - SBC on V18 ok?

[steve66]

I have a 3CX hosted configuration with 2 SBC's: one as a VM on a server and another on a Raspberry Pi. I believe both are using default images provided by 3CX for an SBC. They don't have any updates available on the SIP trunks page and are on V18.1.36.

Will these SBC's continue to function correctly after the V20 update? I may need to plan physical site visits in different cities next weekend potentially so I am hoping to find out in advanced! Do I need to worry about the split DNS issue for my scenario? I used SBC's to avoid issues with the firewalls in the first place. All phones are currently routing through an SBC.

Will my other SIP trunk 'provider' entries/configuration copy over and work in V20? Has the configuration changed where this poses a potential risk of provider configurations not working in V20?

 

[Charles_3CX]

Using the current SBC version on v20 should be no issue. In fact, this is the only SBC version available, as we are still working on releasing the newer version; we do not yet have an ETA for when it will be.

Additionally, there is no need for a Split DNS configuration when using SBC, as the Split DNS requirements are only for systems installed on-premise and phones or apps communicating with the 3cx system on the same LAN.

 

[Roberto.Fasola]

Hi, but if I install the SBC by ISO V20, what does it actually install?
Because debian is 12 but on PBX it doesn’t give me information about the software version..