v18 Upgrade + SBC on Pi3

[cparker_RCT]

I'm starting my upgrades for my customers - the first two went well. However, I am cautious about a medical practice I have hosted in Azure with a Pi3B+ on-prem as the SBC. It was built using the previous method of burning the SD card with the older Raspian OS.

Should I just pre-emptively replace it with a Pi4 or is it safe to upgrade the PBX to v18 and let it tell the SBC to upgrade?
I'll add I am very remote to this customer and going on site is not an option, so if the better option is to just replace the Pi entirely, I need to schedule the replacement instead of risking downtime for a few days waiting on shipping.

Has anyone done the v16 -> v18 upgrade on the other Pi's?

 

[ChrisC_3CX]

It was built using the previous method of burning the SD card with the older Raspian OS.

If it was deployed as per our guide then you should not have nothing to worry about.

Should I just pre-emptively replace it with a Pi4 or is it safe to upgrade the PBX to v18 and let it tell the SBC to upgrade?

As mentioned here, the OS does not get upgraded for the 3CX SBC host so even if something does go wrong, it will most probably just fail to update to the latest version causing no downtime as t will just stay on the current version.

I do have to mention that at some point in the future Debian 9 and possibly the 3B+ too may have to be upgraded to maintain 3CX support but as of yet this is not required.

 

[cparker_RCT]

Thanks! I knew posting those back-to-back would get all the info I needed
Really appreciate it!

 

[ChrisC_3CX]

You're very welcome!

Let us know how it goes!