3CX SBC Update Adds Raspberry Pi 5 & Debian 12 Bookworm Support

[MichaelB_3CX]

Latest 3CX SBC with Raspberry Pi5 support & OS upgrades.​

We’ve upgraded the Raspberry Pi OS for 3CX SBCs to Lite Bookworm, both for arm64 and armhf(32 bit) architectures.

Upgrading your Raspberry 3 or 4​

To install the latest upgrade, you need to flush your SD card and install the new image below:

• Download arm

...

Continue reading the Original Blog Post.

 

[jclark]

What does upgrading Raspberry Pi need to be a manual process. This make t hard for ones that are at remote sites are away.

For non Raspberry Pi devices, can't there be a more automated process?

 

[illcsales]

Tried this on buster pi 4 ends with kernel failure:
kernel: [ 525.995163] Voltage normalised (0x00000000)
::FAIL::

 

[JS Picard]

Is there any word on how long older versions of the 3CX SBC on previous versions of Raspbian (On Raspberry Pi) are going to be supported?

Or if there's an increase in performance in using the latest version of Raspbian?

Upgrading or replacing the Pis will be a long term project.

 

[MichaelB_3CX]

Tried this on buster pi 4 ends with kernel failure:
kernel: [ 525.995163] Voltage normalised (0x00000000)
::FAIL::

The message "kernel: [ 525.995163] Voltage normalised (0x00000000) ::FAIL::" on your Raspberry Pi 4 indicates an issue with the power supply or voltage regulation. This often leads to instability, unexpected shutdowns, or even failure to boot. Here's what you can do:

Troubleshooting Steps:

1. Power Supply:
   • Ensure you're using the official Raspberry Pi 4 power supply (5.1V, 3A minimum) or a high-quality, reputable alternative.
   • Check the cable for any damage or loose connections. Try a different USB-C cable.
   • If possible, test with another power supply to see if the issue persists.
2. Under-Voltage Detection:
   • The Raspberry Pi 4 has built-in under-voltage detection. The rainbow square in the top-right corner of the screen indicates a low voltage warning.
   • If you see this warning frequently, even with a good power supply, try these:
     • Use shorter and thicker gauge USB-C cables to minimize voltage drop.
     • If you have many USB peripherals connected, try disconnecting some to reduce power consumption.
     • Consider adding a powered USB hub to provide additional power to your peripherals.
3. Hardware Issues:
   • In rare cases, the issue could be with the Raspberry Pi's power circuitry itself. If none of the above solutions work, you might need to replace the Raspberry Pi.

 

[illcsales]

@MichaelB_3CX we were able to duplicate the issue on other pi's which we have not done any customizations.
We will try your recommendations and let you know, thankfully most of our sbc have been shifted to router phones or the windows sbc so our exposure is not that great.

 

[mariosM_3CX]

@illcsales As outlined in the blog post, the SBC OS upgrade script is intended to be used only on Linux Debian machines. Not on Raspberry PI
For Raspberry PI you will need to flush your SD card and install the new bookworm image

 

[illcsales]

@mariosM_3CX thanks for the clarification did not catch "Not on Raspberry PI" perhaps putting it in the bold headline would be helpful to others.

 

[accentlogic]

@MichaelB_3CX this is great news! Many thanks. We have hundreds of SBC units out there and glad to see the Pi will remain supported. It does look like we'll need to ship newly configured SD cards to client sites, but that is a better option than a full device replacement.

Does the HA Cluster fix mentioned address the issue where local network connectivity is lost for both SBC units and both nodes attempt to become active at the same time?

Will you also be updating the 3CX Hardware Requirements page to include the ARM/Pi based devices again? We use the Pi for up to 20 or maybe 25 devices. Fine with me if 50 was pushing them and the guidance is lower going forward.

 

[SteveITS]

FWIW, I upgraded our VM today (3 cores, 1.5 GB RAM). It worked but took about 45 minutes.

 

[mariosM_3CX]

FWIW, I upgraded our VM today (3 cores, 1.5 GB RAM). It worked but took about 45 minutes.

Except from upgrading the sbc to latest bookworm version, the rest is merely OS upgrade procedure.
In theory it would take more or less the same time as if you would manually do a distro upgrade.
Note that if you are upgrading from stretch, the script is upgrading first to bullseye and then to bookworm so it may taka a while.
Also note that except from CPU, Network plays a big role here cause this procedure will need to download a huge number of packages.

 

[SteveITS]

Oh sure, I’m just providing a reference point for others.

A new install (same IP) might actually be shorter…it’s been a while so I don’t remember that timing…but this is certainly easier.

 

[AWS2P]

is there in V20 a place where we can check SBC info and relesase like it was in V18?
How to know which sbc are Windows and which are raspbian or debian ?
Perhaps i'm blind but connected to the PBX, the only info available in Voice &chat is how many SBCs are there.

Once a SBC is upgraded to V20 is there a way it is displayed as up to date release on the PBX ?

 

[SteveITS]

I think that’s in u3? Or at least it was posted that it was coming soon.

 

[AWS2P]

Thanks Steve,
On SP3 Alpha, I can see more details but not the OS kind, if it's Debian, Windows, Raspbian ? is that the kind of details coming soon?
could it be also some more details on the SBC hardware ? Drive Space, Ram....?