Raspberry Pi no longer supported / update 5 ssl cert email

[james1787]

Hi, I've been running 3cx pbx on-premise with a pi 4 8gb for a year or so without issue. I'm aware that support for the pi with 3cx pbx is going away. I had thought that I might be able to continue to run as-is, but just not have any new updates / features until I switch over to a supported platform.

I saw an email come in regarding needing update 5 to get the latest ssl certs so that I can continue using 3cx uninterrupted but clearly that isn't an option for the pi. Will my 3cx pbx stop working after Dec 31 this year? Are there other options for 3cx on-premise if my 3cx pbx pi stops working Jan 1?

Thanks!

James

 

[SteveITS]

You can restore a backup to Debian or Windows. Debian can be lower end hardware or a VM.
https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/

 

[AlexanderReichert]

It is even more severe: the SSL update happens on November 30th.
this is totally ridiculous. Everyone who runs on Pi is left in the dark with struggling to move to a different platform with no time!

 

[james1787]

It is even more severe: the SSL update happens on November 30th.
this is totally ridiculous. Everyone who runs on Pi is left in the dark with struggling to move to a different platform with no time!

Oh man, that pushes up the urgency just a bit. Well, on the plus side I'll free up a few pi's if I spin up an esx/vmware server to run a debian vm.

 

[PierreS_3CX]

Hi,
If your PBX is not in v5 @30november 2022, it will not be able to contact our server's activation. Without contact with your PBX, we keep your FQDN active for two months. After that, you can lose your FQDN.

If you are using static IP, you will be able to use it for 2 months without being too much impact.

 

[james1787]

Hi,
If your PBX is not in v5 @30november 2022, it will not be able to contact our server's activation. Without contact with your PBX, we keep your FQDN active for two months. After that, you can lose your FQDN.

If you are using static IP, you will be able to use it for 2 months without being too much impact.

Thanks Pierre for your reply. I'm working on spinning up a debian Linux host in the next day or so. I see that we use a debian iso image that you provide.

So would this be the basic upgrade process?
1. Stop all 3cx services on the raspberry pi
2. Perform a backup of the configuration
3. Spin up the 3cx iso image
4. Import the configuration from the backup, start services
5. Reset/reboot all ip phones on the network
6. Now that my raspberry pi4 8gb is no longer needed (they are currently unobtanium), sell it and perhaps retire or buy a ferrari, private island, etc..? :-D

I see for running off a VM, you prever VMware or KVM. Would Proxmox also work? Or does it specifically need to be one of the VM types you require?

Thanks!

 

[PierreS_3CX]

Yes full backup, with license information.
Stop raspberry
Install 3cx via iso + import backup.
if Ip PBX change:
Reset/reprovisioning all IP phones on the network.
6. You still can use raspberry as SBC. Buy a Ferrari, private island is a valid option too.

In case you need support you should follow prerequisites :

https://www.3cx.com/3cxacademy/videos/basic/installing/

 

[MattLUK]

I looked at moving to the free cloud option provided but wasn't able to add my SIP trunk into it so that was a no go, has anyone managed to install 3CX from ISO onto a Pi, does it run or not rather than using the Raspberry Pi version I was just going to look at the Debian route? I don't want to purchase/spin up bigger hardware if I can still run it on a Pi, I've only got 3 or 4 phones running on my network at home.

 

[SteveITS]

The Pi is an ARM CPU so an x64 install won't work.

 

[MattLUK]

What a pain, its ideal hardware for what I need. Back to the drawing board I think.

 

[58voip]

Hi,
If your PBX is not in v5 @30november 2022, it will not be able to contact our server's activation. Without contact with your PBX, we keep your FQDN active for two months. After that, you can lose your FQDN.

If you are using static IP, you will be able to use it for 2 months without being too much impact.

Hi @PierreS_3CX, how about the situation for a perpetual license key? One customer deployed a 32SC perpetual license on-premise on V18 update 2, they had CFDs built on the 3CX system, and the CRM system integrated. So they need to prepare for the upgrade very carefully.

What would happen to this 3CX system if they don't upgrade to update 5 after Nov. 30th? Still two months for them as the annual license key? Will there be any difference for the perpetual license system?

 

[bitn2]

Hi @PierreS_3CX, how about the situation for a perpetual license key? One customer deployed a 32SC perpetual license on-premise on V18 update 2, they had CFDs built on the 3CX system, and the CRM system integrated. So they need to prepare for the upgrade very carefully.

What would happen to this 3CX system if they don't upgrade to update 5 after Nov. 30th? Still two months for them as the annual license key? Will there be any difference for the perpetual license system?

There is not difference between any license. The activation server is not reachable anymore for this pbx, doesnt matter which license.

 

[58voip]

In the past, we had the request to use 3CX without an Internet connection. We were told that the annual license key needs a constant Internet connection. However, the customer could buy a perpetual license key with multiple years of maintenance. So they are able to disconnect the Internet after the license key is activated. They only need an Internet connection to buy the MA next time.

It seems that the activation policy of the perpetual license and annual license would be different. I know things would be changed the time by time. So I have to check it again.

 

[bitn2]

In the past, we had the request to use 3CX without an Internet connection. We were told that the annual license key needs a constant Internet connection. However, the customer could buy a perpetual license key with multiple years of maintenance. So they are able to disconnect the Internet after the license key is activated. They only need an Internet connection to buy the MA next time.

It seems that the activation policy of the perpetual license and annual license would be different. I know things would be changed the time by time. So I have to check it again.

Ok, when you use the 3cx without FQDN and internet, just for internal calls, it could work for you.

 

[58voip]

Ok, when you use the 3cx without FQDN and internet, just for internal calls, it could work for you.

The customer doesn't need FQDN, remote ext., 3CX APPs. Just worried about if the license key would be changed to a free key if they don't upgrade to update 5 after 2 months over Nov. 30th.

 

[bitn2]

The customer doesn't need FQDN, remote ext., 3CX APPs. Just worried about if the license key would be changed to a free key if they don't upgrade to update 5 after Nov. 30th.

No, but you cant call external anymore.

 

[58voip]

No, but you cant call external anymore.

AudioCodes E1 gateway had been deployed on-premise with 3CX together. Only needs the call via the E1 gateway.

 

[bitn2]

AudioCodes E1 gateway had been deployed on-premise with 3CX together. Only needs the call via the E1 gateway.

Its getting more special... Why not give us such information at the beginning. It could be possible that you can use it that way for ever, but no one knows.

 

[james1787]

Well, I managed to scrape up a box that would sufficiently run esxi 6.5 and was finally able to get everything moved over with using a backup file from the pi. Most everything is back to normal. Didn't plan on running an esx host at home but I need my phone system so my pi4 8gb is freed up (will wait a bit before wiping it).. unless I decide to sell it and buy a private island lol.. I'll figure something to do with that (I have many other pi's around doing things... but none as hefty as that one). Anyways, hopefully no major changes for a while for on-premise setups so I can keep this one running a while.

 

[bitn2]

Well, I managed to scrape up a box that would sufficiently run esxi 6.5 and was finally able to get everything moved over with using a backup file from the pi. Most everything is back to normal. Didn't plan on running an esx host at home but I need my phone system so my pi4 8gb is freed up (will wait a bit before wiping it).. unless I decide to sell it and buy a private island lol.. I'll figure something to do with that (I have many other pi's around doing things... but none as hefty as that one). Anyways, hopefully no major changes for a while for on-premise setups so I can keep this one running a while.

ESXI 6.5 is really old! Why not use 7.x? When migrate to another system, dont use old stuff...