New SBC Beta Release Available for Download

[ivank]

Could someone please clarify that for the HA cluster you no longer need to have ICMP enabled to the PBX, you can use any IP or FQDN to get a ping response.

So for the PBX I have hosted in Lightsail where ICMP isn't enabled this will allow the HA Cluster to function correctly?

Thanks in advance

The answer is yes to both questions.

The pinging mechanism is intended to promote the node which still has connectivity to the outer world.
One can use Google DNS 8.8.8.8, 8.8.4.4 if PBX is not pingable (as in Lightsail), or disable ping facility completely.

 

[ivank]

Does this mean you have scanned the app to ensure it does not contain a virus?

We build this app from the trusted source code so for sure it doesn't contain viruses.

 

[wys]

The answer is yes to both questions.

The pinging mechanism is intended to promote the node which still has connectivity to the outer world.
One can use Google DNS 8.8.8.8, 8.8.4.4 if PBX is not pingable (as in Lightsail), or disable ping facility completely.

Great enhancement, thanks for the reply ivank

 

[mariosM_3CX]

Can beta SBC releases please be indicated as such in the console?

@SteveITS @jvivona

Could be that we make it more clear, but for now, when you click on Update it is indicated as a beta release

 

[cmp1]

RPI SBC Cluster upgrade issues.
In manual it states to click upgrade, it will take currently active node & upgrade, reboot. Then click upgrade again - and the second, not active due to reboot of first, will upgrade and reboot.

I cannot seem to get mine upgrade... has anyone successfully upgraded their HA cluster?

The cluster shows as version:

16.1.114

 

[mariosM_3CX]

The cluster shows as version:
16.1.114

It might be an issue with the repositories configured on your machine
Can you please collect the following files in a zip and send me a PM to have a look?
/var/log/3cxsbc/*
/etc/apt/sources.list.d/*

 

[jmatano]

Can someone please confirm the max number of extensions and sim calls that can be run through the latest version of the SBC. The last doc I saw is aged a bit and shows only 100 sim calls through it, so I was curious if this is still the case or has capacity increased?

 

[greychain]

I am running a Ubuntu 20 workstation with a Vmware workstation running a 3CX debian SBC. The SBC can login into the 3CX server OK but phones can not see the SBC. I am also running a WIndows SBC on my other workstation and this can login to 3CX and can register phones. My expectation is that when the Windows PC is shutdown the phones will use the Debian SBC.

I have tried turning off the windows machine then rebooting the local phones but they still don't register via the Debian SBC.

The network device for the VM is set to bridged and has the same network segment as the phones. Would this stop multicast messages?

Any thoughts of what to look for?

 

[Saqqara]

Check out this thread - 3CX are saying both SBC should be running on the same device - https://www.3cx.com/community/threads/sbc-cluster-between-debian-vm-and-debian-pi.74608/#post-336425

Also HA SBC only works on Debian or PI currently - https://www.3cx.com/docs/sbc-high-availability-cluster/

 

[JohnS_3CX]

I am running a Ubuntu 20 workstation with a Vmware workstation running a 3CX debian SBC. The SBC can login into the 3CX server OK but phones can not see the SBC. I am also running a WIndows SBC on my other workstation and this can login to 3CX and can register phones. My expectation is that when the Windows PC is shutdown the phones will use the Debian SBC.

I have tried turning off the windows machine then rebooting the local phones but they still don't register via the Debian SBC.

The network device for the VM is set to bridged and has the same network segment as the phones. Would this stop multicast messages?

Any thoughts of what to look for?

This is not possible, please read the prerequisites that say you need to have the same version of Debian on both devices.

As for running the SBC on a VM (without high availability, just as a regular SBC) try using the stable first rather than this beta. You can see whether the multicast group is actually joined:
https://www.3cx.com/docs/plug-and-play-ip-phone/#h.vimqlwec6uwc

 

[greychain]

What was causing my phones not to pickup the other SBC was that the phone binds itself to a SBC and you need to manually change it.

So to confirm. Windows 10 SBC and Debian SBC (running as a VMware VM on Ubuntu 20) with both SBC's on same subnet can auto-provision and call each other. May not be supported but does work. Just need to change the phones

 

[JohnS_3CX]

When not running in HA mode, then yes. Because you can have multiple independent SBCs even at a single site, and each phone will be bound to its own SBC.

I think you were not running in HA mode in your original post.

 

[PhilK]

@JohnS_3CX will there be a FINAL Version for SBC in this year? Why don't you continue here after the beta is released in May?

 

[JohnS_3CX]

Hi Phil,

It is getting very close to release, keep an eye out next week