v18 not updating to v5

[alexgray]

I have clients with V18 Build 2 and SBC on Raspberry Pi 4 boxes. I've received the emails about the urgency of updating to v5, but I can't find any way to do it. The systems are set to auto-update, but have not done, and if I try for a manual update it says there are no updates available. How can I resolve this?

 

[Nathan@Voxtelesys]

IIRC, RPi is not supported for PBX after update 2.
https://www.3cx.com/blog/releases/v18-update-3-final/

Update 3 unavailable on Raspberry Pi PBX​

Raspberry is undergoing some changes which will bring future builds of its operating system in line with Debian. When 3CX supports Debian 11 (bullseye) we will look at supporting Raspberry once again. For the moment update 3 will not be available for Raspberry Pi.

3CX SBC will remain supported on Raspberry Pi devices. As a solution to stay on the latest update, move to Hosted by 3CX and use the Pi device as a 3CX SBC.

 

[k.lee]

Hi,

Quite by chance, I was asking if the config files in a Raspberry PI was the same as in the debian PC, I learnt about Raspberry obsolesces and how to do the migration.

Here's the thread:
https://www.3cx.com/community/threa...ed-into-a-debian-intel-pc.117772/#post-546057

I've ordered a refurbished mini-desktop and once it arrives, will do the porting to it with Debian. Should arrive in a couple of days time.

rgds
Kenneth

 

[alexgray]

IIRC, RPi is not supported for PBX after update 2.
https://www.3cx.com/blog/releases/v18-update-3-final/

Thanks, I recall seeing somehting about the lack of support for RPi but I took it to mean the devices could continue on their existing update level until 3CX supported Debian 11 - ie a temporary situation.

It now sounds as if 3CX is abandoning all RPi systems indefinitely and that they soon won't continue to work (in 2 months?). If so, that's really poor behaviour - for an infrastructure system such as a PBX there should be at least a few year's 'sunset period' during which a system continues to be operable, albeit with limited support. Even Microsoft sticks to that!

I sold the system on the basis of its low cost standalone nature and from a reputable stable company. Now I have to go have a difficult conversation with my client to explain that for no fault of their own they have to shell out for new hardware and my time to set it up, even though to them the present system is working perfectly well.

Not good.

 

[SweetAction]

Thanks, I recall seeing somehting about the lack of support for RPi but I took it to mean the devices could continue on their existing update level until 3CX supported Debian 11 - ie a temporary situation.

It now sounds as if 3CX is abandoning all RPi systems indefinitely and that they soon won't continue to work (in 2 months?). If so, that's really poor behaviour - for an infrastructure system such as a PBX there should be at least a few year's 'sunset period' during which a system continues to be operable, albeit with limited support. Even Microsoft sticks to that!

I sold the system on the basis of its low cost standalone nature and from a reputable stable company. Now I have to go have a difficult conversation with my client to explain that for no fault of their own they have to shell out for new hardware and my time to set it up, even though to them the present system is working perfectly well.

Not good.

3CX recommends you switch to Hosted by 3CX and use the Pi as an SBC. Cost of hosting should be built in to license cost