Raspberry Pi 5 - SBC ?

[Connexium]

Due diligence Disclaimer: I am truly sorry if this has been posted before. Since the forum limits keyword search of 3 characters or less it makes it incredibly hard to find information like this. I also tried using Google without luck.

My question is with the availability of the Raspberry Pi 5. Could it be used for an SBC? I need to purchase several units and was hoping to "future-proof" my purchase with the PI5 variant if possible.

I don't know much about any OS Version limitations for specific Pi models that could affect or prevent the installation of the SBC on a rPi5, but as far as I remember, the current SBC ISO is based on an old version of Debian.

Lastly, I am not talking about 3cx PBX, but only the SBC.

Thank you for any clarifications.

 

[AndyRDIT]

Is the above all you changed in the config file?

Yes, that's all I edited in the file, it filled in the rest itself after the reboot. I'm guessing you could just stop and start the SBC service to do the same thing, but it was easy enough just to reboot.

 

[BennyG]

Awesome. Just done it here and it works too.

Just to note, the above doesn't work if you use a custom FQDN which is why mine wasn't working initially.

 

[AndyRDIT]

Ours are all using 3CX domains, so I'd not tried that. If you have the web interface listening on a different port, for example 5001, you have to do:

ProvLink=https://<3CX PBX hostname>:5001/sbc/<SBC-AuthenticationKey>

 

[BennyG]

Yes, our own PBX is on a custom FQDN. I did try the above, and also copying a config file from a working SBC here and just changing the relevant passwords but it didn't work on our custom FQDN.

Soon as I changed it to our customers 3cx domain which is who they're ultimately for, it worked straight away

 

[SteveITS]

didn't work on our custom FQDN

I'd guess, an intermediate cert or similar issue, perhaps missing from the newer OS

 

[Colorado VoIP]

for your custom FQDN, you will need to import your SSL certificate into the raspberry pi. Some of our older customers are running custom FQDNs and our wildcard SSL cert. So we always have to import that into the device before it'll talk.

https://raspberrypi.stackexchange.com/questions/76419/entrusted-certificates-installation

 

[BennyG]

Yea quite possible that it's a cert issue. Not spent much time on it to be honest, we only have two with custom domains (ours and one other customer).

 

[Alex@SWS]

Hi Guys,

Just wanted to say good job to those that got this working, i will follow suit shortly with my Pi5's and let you know how i get on.

Alex

 

[afit]

Just catching up on this as I've been on annual leave. Well done guys, great work.
I will test with on of my Pi 5s as soon as I need another SBC and report back.
In the meantime, I pulled some strings and got a few PI 4s (luckily).

 

[microtekau]

I've got 15 Raspberry Pi 5 devices that are sitting here gathering dust because the development team are taking way too long to release the SBC for the Pi5.

It's been 7+ months now and no further updates from 3CX. I would appreciate an update and ETA.

 

[Brand0n]

Great job all! Thank you for the step by step guide
This has helped me get 2 pi5's up and running

A note for anyone that was having permission issues changing the config.
Run this command sudo pcmanfm and then you can change the permission from the window that opens

 

[guzzitech]

Ours are all using 3CX domains, so I'd not tried that. If you have the web interface listening on a different port, for example 5001, you have to do:

ProvLink=https://<3CX PBX hostname>:5001/sbc/<SBC-AuthenticationKey>

So for those of us on Digital Ocean hosted 3CX, here's what I did:

0. Logged into 3CX, added SBC. Then go back into it to grab the auth key etc.
1. Use Pi Imager, select Pi 5, and OS Lite x86
2. For config I set my login, hostname and enabled SSH
3. Boot Pi, find IP, ssh into
4. Followed the steps as root, outlined by BennyG on Page 1
5. service 3cxsbc stop
6. Edited /etc/3cxsbc.conf with:

ProvLink=https://xxxx.my3cx.ca/sbc/<authkey>

7. service 3cxsbc start
8. now I see the SBC with green status on 3CX console

V20 hosted