System upgrade from ver 16 to ver 18 test

[Kane Wong]

Hi;

I am planning to upgrade from ver 16 to ver 18 for on premise server which is in Debian 9. 3CX version 18 upgrade will upgrade Debian from version 9 to version 10 also, when I check the 3CX community site, I saw some users have issues during upgrade. Is there any pre-requisite test that I can go through in order to make sure the upgrade process complete without error?

I have a production server only, so I need to make sure the upgrade process is no issue raised. What is your suggestion?

I am using version 16.0.8.9,

Or, I can just upgrade to V16 8A (16.0.8.16) for short-term fix - until November 2022.

I believed, the V16 8A also address the requirement of "connectivity to activate.3cx.com", right?

Also, after upgrade to version 18, if I need to do something on 3CX mobile app? Like, we scan the QR code?

thanks!

 

[ChrisC_3CX]

There is no test you can do but do bear in mind that if you have deployed and configured this machine as per our guides using the 3CX ISO and have not made any modifications to it that are outside of 3CX's recommendations then you should be fine. IF it does still fail it should rollback to v16 so the PBX will stay operational. In any case, we always recommend performing such tasks outside of office hours and of course take a backup and move it away from the machine before doing anything.

Also, after upgrade to version 18, if I need to do something on 3CX mobile app? Like, we scan the QR code?

If you do not have a failover server that also needs upgrading then there's nothing else you should need to do.

 

[Kane Wong]

For backup, just using the built-in backup function and copy out the backup file is good enough, right?

When I received an email from 3CX dated 20 Nov 21 in regards to "Change of FQDN Endpoint", the ver 16 A8 will address this issue temporary until Nov 2022, correct?

 

[cobaltit]

If the email says the same thing as this blog post then yes:

https://www.3cx.com/blog/releases/fqdn-endpoint-change/

Keep in mind that stay on v16 until Nov 2022 only makes any upgrade more likely to break which seems to be your primary concern.

 

[Kane Wong]

thanks!

Is it possible to build a new 3CX server with the v18, then restore the configuration which was backup in v16?

 

[Saqqara]

thanks!

Is it possible to build a new 3CX server with the v18, then restore the configuration which was backup in v16?

Yes, you can use a v16 backup , during the 3cx v18 installation restore from backup

 

[ChrisC_3CX]

For backup, just using the built-in backup function and copy out the backup file is good enough, right?

That is correct.

 

[the_jackal_br2001]

Hi folks,

Sorry for the inconvenience. I have a customer who is on the 16v version, and I have been trying since October 2021, to convince him to migrate to 18v.

I believe this is a good argument to convince him. One question, are there updates in the 16v version that he has not done yet, do I need to do all these updates and then upgrade to 18v?

Obviously I will make a complete backup of the configurations first.

Best regards

 

[NickD_3CX]

That last V16 Update that was released was V16 U8A. You can see all V16 updates that were released here:
https://www.3cx.com/blog/change-log/phone-system-change-log/

It is best to upgrade V16 all the way, before going to V18.

So, my suggestion:

1. Take a backup now
2. Install all V16 updates
3. Take another backup.
4. Upgrade to V18: https://www.3cx.com/docs/upgrading-pbx/

 

[the_jackal_br2001]

That last V16 Update that was released was V16 U8A. You can see all V16 updates that were released here:
https://www.3cx.com/blog/change-log/phone-system-change-log/

It is best to upgrade V16 all the way, before going to V18.

So, my suggestion:

1. Take a backup now
2. Install all V16 updates
3. Take another backup.
4. Upgrade to V18: https://www.3cx.com/docs/upgrading-pbx/

Hi NickD_3CX

We have upgrade all release 16v this weekend, and after that we cannot see more the upgrade v18.
I think the version my partner installed is not based on the official 3CX ISO, he must have mapped the repositories and installed it manually on the Cloud machine he provisioned.

Or you can use the CLI access to apply this command sudo lsb_realease -a and check if the version OS and V18 appears?

 

[NickD_3CX]

Hi NickD_3CX

We have upgrade all release 16v this weekend, and after that we cannot see more the upgrade v18.
I think the version my partner installed is not based on the official 3CX ISO, he must have mapped the repositories and installed it manually on the Cloud machine he provisioned.

Or you can use the CLI access to apply this command sudo lsb_realease -a and check if the version OS and V18 appears?

Now that you have installed all V16 updates, here are the instructions on how to go to V18.

Today specifically, we have disabled the update button that exists in the Management Console for Linux installations, but by tomorrow it should be there again:
https://www.3cx.com/community/threads/3cx-v18-upgrade-button-removed-again.87983/#post-416810

 

[the_jackal_br2001]

Hi NickD_3CX

Okay.

From your experience, do you think there might be a package dependency problem?

 

[NickD_3CX]

Hi NickD_3CX

Okay.

From your experience, do you think there might be a package dependency problem?

We know it is as I say in the other thread too, we are working to verify that it's OK to upgrade the affected packages and re-enable it.

 

[the_jackal_br2001]

Okay. II'll wait with no problem. I will only align the expectations of my end customer.