Preview the all New SBC in V16 Update 2 Beta

[MichaelB_3CX]

Edited: I see you upgrade the 3CX system, then apt upgrade the SBC and that should create the trunk in the 3CX.

However, I get this when doing the upt update then the testing upgrade

Reading package lists... Done
E: The value 'testing' is invalid for APT::Default-Release as such a release is not available in the sources

It seems that you do not have testing repository so this is why its failing to install.

Add the following;

Incase you have Rasberry build:

echo "deb [arch=armhf] http://downloads-global.3cx.com/downloads/debian stretch-testing main" | sudo tee /etc/apt/sources.list.d/3cxpbx-testing.list

Incase you have Debian build:

echo "deb [arch=amd64] http://downloads-global.3cx.com/downloads/debian stretch-testing main" | sudo tee /etc/apt/sources.list.d/3cxpbx-testing.list

 

[MichaelB_3CX]

Hi Guys,

I’ve been having issues with the 3CX SBC, specifically with DNS resolution and committing changes to the SBC Beta Config file.

With the SBC installed on Windows, I have been unable to resolve any of the FQDN’s used (I’ve tried with multiple PBX’s & FQDNs). After changing the FQDN to the WAN IP of the PBX, the SBC would work as expected. After changing the logging levels, I noted that the SBC was trying to use 192.168.1.1 to resolve the FQDN, the issue here is that this is not a valid IP on our subnet (we use 192.168.0.0/24) and has not been used on our network at any point.

I have updated the SBC to the beta version to see if this issue has been resolved however now I am unable to change the logging level from ERR to DEBUG. Once the file has been updated, it will default back to ERR logging. I have noted that in the .conf file, is the following comment;
# This file is rewritten on every restart so don't try to edit it.

It appears as though the SBC is reloading every 10 seconds and re-writing the config so we cannot perform accurate debugging on the SBC locally.

Is there a way to stop the logging level from being changed automatically?

This is by design, new SBC provisions and takes latest configurations settings from PBX. If you want to change the logging you need to go to SIP Trunks, click on the SBC Trunk, Settings Page and change the Logging Level from there and press OK. Push Config so SBC will get the latest configuration.

 

[nitrox]

This is by design, new SBC provisions and takes latest configurations settings from PBX. If you want to change the logging you need to go to SIP Trunks, click on the SBC Trunk, Settings Page and change the Logging Level from there and press OK. Push Config so SBC will get the latest configuration.

When you push the config what does it happen to the call which are "passing through" the SBC? Are they disconnected?

 

[MichaelB_3CX]

@nitrox when pushing config the 3cxsbc will be restarted therefore if you have calls they will get disconnected. In the next releases we will add a check that incase there are calls on going Push Config will not be allowed or postponed until calls are free.

 

[pmterp]

This is great, thank you.

Question: If you enable Verbose logging under the Settings tab, are those logs pushed to/accessible from the 3CX server or do they still have to be retrieved from the SBC?

Suggestion: Since the new interface reports the SBC's local IP address, it would be pretty handy to have a dropdown in the extension's Provisioning tab that allows you to select the SBC by name (as opposed to entering the local IP). 1) It would eliminate keying errors and 2) if the SBC were to change IP addresses, the phone's provisioning file could be automatically updated with that info requiring only a reboot/reprovision of the phone to get it back online.

 

[MichaelB_3CX]

I was never able to get the SBC to update, I get the same error posted by Nick W.

@Carlos Alvarez due that old sbc scripts never supported ability to install from testing repository its normal you dont see the beta builds of SBC. This ability to upgrade Legacy SBC will be available when we release SBC Build in Final i.e main repositories. So if you would like to try this out as mentioned above run the following;

Incase you have Rasberry build:

echo "deb [arch=armhf] http://downloads-global.3cx.com/downloads/debian stretch-testing main" | sudo tee /etc/apt/sources.list.d/3cxpbx-testing.list

Incase you have Debian build:

echo "deb [arch=amd64] http://downloads-global.3cx.com/downloads/debian stretch-testing main" | sudo tee /etc/apt/sources.list.d/3cxpbx-testing.list

 

[Gunnar Brynjólfsson]

Great work, was missing this a lot.

 

[Rhys Haskell]

After some testing it looks very good especially the email alerts when an SBC goes down. The one thing we have noticed is when a SBC is unplugged it takes around 5 mins to send the email, is there any way of adjusting this time so it polls more regularly?

 

[JonnyM]

This all looks very promising. Is there any possibility of getting the SBC packaged and in the app stores for the common NAS vendors (Synology, Qnap) as I think the occasions where the only infrastructure on a site might be a device like that are pretty high.

 

[sar2]

Guys,

We have over 120 SBC in the field.

Do we need to upgrade them as well or not?

If we do, what is the upgrade path?

Also,
Have you guys considered working with a 3rd party SBC providers or creating an SBC that could be installed in the cloud?

Being local to each site presents a huge challenge for us with mobile workers that go from one office to another, or work from home. Most of our clients have mobile workers with hardware phones that occasionally take their phones in the office. Each time we have to reconfigure the phones.

 

[JMK]

New SBC.... Bravo! Thank you, Thank you.

 

[MichaelB_3CX]

After some testing it looks very good especially the email alerts when an SBC goes down. The one thing we have noticed is when a SBC is unplugged it takes around 5 mins to send the email, is there any way of adjusting this time so it polls more regularly?

By default its 5 mins yes. We made this for a reason because for example when you update or push config which eventually restart SBC it does not make sense to send an email about SBC is down. You would want to know if an SBC is really down for some time.

 

[datamerge]

The problem of a VPN is that it's much slower because of the encryption. For example, I use a IPSec VPN and barely get 10mbps in download, when connected via SBC or STUN, I get my full 60mbps since the PBX can deliver it (10GbE connection).

You definitely have an issue with your VPN. If you are getting 10Mbs through your tunnel on a 60Mbs connection, you have a fundamental problem with your VPN that you need to fix.You can lose up to around 10% of your throughput, but that is 54Mps in your case.

An IPSEC ESP tunnelling VPN adds an overhead of around 128 bytes to the payload. If you have a 60mbs connection, the extra time for a packet to arrive at the destination would be around 16uS.

 

[datamerge]

The new SBC looks great. When we upgrade the PBX, will the old SBCs continue to operate without being upgraded?

On another subject. There is a small bug with Zoho CRM integration where all calls are showing as answered even when they are not. We were hoping to see the fix in SP2. Can you please tell me if this is fixed yet?

 

[JohnS_3CX]

The old SBCs will continue to work so you will have a chance to upgrade them, but you should do it as soon as you can in order to keep compatibility with future updates and of course to enjoy the benefits of the new version.

 

[Evolute IT]

You definitely have an issue with your VPN. If you are getting 10Mbs through your tunnel on a 60Mbs connection, you have a fundamental problem with your VPN that you need to fix.You can lose up to around 10% of your throughput, but that is 54Mps in your case.

An IPSEC ESP tunnelling VPN adds an overhead of around 128 bytes to the payload. If you have a 60mbs connection, the extra time for a packet to arrive at the destination would be around 16uS.

DM me so we can investigate further.

 

[treefiddy]

This is great, thank you.

Question: If you enable Verbose logging under the Settings tab, are those logs pushed to/accessible from the 3CX server or do they still have to be retrieved from the SBC?

Suggestion: Since the new interface reports the SBC's local IP address, it would be pretty handy to have a dropdown in the extension's Provisioning tab that allows you to select the SBC by name (as opposed to entering the local IP). 1) It would eliminate keying errors and 2) if the SBC were to change IP addresses, the phone's provisioning file could be automatically updated with that info requiring only a reboot/reprovision of the phone to get it back online.

This is a great suggestion! Especially regarding the SBC changing IP since we often deploy SBCs with remote phones on home networks where we can't set static IP addresses.

 

[accentlogic]

By default its 5 mins yes. We made this for a reason because for example when you update or push config which eventually restart SBC it does not make sense to send an email about SBC is down. You would want to know if an SBC is really down for some time.

I have noticed that we do get an UP alert when an SBC status changes to UP, even if it has been less than five minutes. Is that working as intended?