SBC build 16.0.389 - beta or not beta?

[jvivona]

Started getting calls from self-managed clients this morning. they see an update for the SBCs to 16.0.389. If I look at the build notes - it's says it's a beta build. Is it really a beta build or is it good to go.

If beta, is there anyway we can change the interface so that beta updates for the SBC don't get "flagged/appear" similar to how alpha & beta builds for the core 3cx system don't appear as an update unless you go to the update screen & purposefully select it?

 

[Evolute IT]

Started getting calls from self-managed clients this morning. they see an update for the SBCs to 16.0.389. If I look at the build notes - it's says it's a beta build. Is it really a beta build or is it good to go.

If beta, is there anyway we can change the interface so that beta updates for the SBC don't get "flagged/appear" similar to how alpha & beta builds for the core 3cx system don't appear as an update unless you go to the update screen & purposefully select it?

Yes it's a Beta. It is specified in the changelog.

@StefanW Should we update production systems to that SBC build?

 

[StefanW]

https://www.3cx.com/blog/change-log/3cx-session-border-controller-build-history/

3CX Session Border Controller, Build 16.0.389 Beta, September 2019 (Linux, Raspberry Pi & Windows)

• Fixed issue with loopbacks selecting wrong interface.
• Added RTP Loss packet statistics.

(we use it our self but it is only in use with Beta U3 v16)

 

[jvivona]

I had read that but I wanted to make sure. will add to the ideas forum about hiding beta SBC updates just like beta/alpha core updates

 

[StefanW]

I don't see the point for the idea as it is clearly labelled what it is... And you know what the risk is (or not) to use them...

 

[Evolute IT]

I don't see the point for the idea as it is clearly labelled what it is... And you know what the risk is (or not) to use them...

Why is it suggested to install it on a production system? shouldn't those appear only on Alpha/Beta installs to prevent confusion?

I too was confused to whether install or not.

 

[jvivona]

I don't see the point for the idea as it is clearly labelled what it is... And you know what the risk is (or not) to use them...

@StefanW - maybe there's an easier solution then - instead of just having UPDATE in the UI on the SIP screen for the SBC, maybe tag it as BETA UPDATE. The reason we need something like this is because folks (our customers) don't take the time to go read the release notes (I know - that's wrong & shame on them) - but even a small flag in the UI that says "don't do this unless you are really, really sure" will help stop the support calls or the accidental update of a production system to a BETA release. Everyone is all excited on how easy 3CX has made it to do all these updates from 1 place & they want to jump on updates - but we have to protect people from themselves sometimes - we did it for the BETA for the core 3cx software, isn't this just a extension of the justification for that change?

I really wish everyone would read all the release notes and made intelligent decisions about updates they really need vs shouldn't install - it would make our IT business a ton easier.

 

[AWS2P]

On a demo pbx i've got the update for SBC but nothing happens when i want to apply update to Béta 16.0.389

From trunk i tick the SBC line and apply to update , popup comes , then pressed follow to apply and then nothing. SBC stay in previous 16.0.386.
I've rebooted SBC with no change. SBC works fine but don't update.