v15.5 to v16 Upgrade Procedure

[kraichle]

Is there a particular recommended procedure to upgrade from v15.5 to v16? Or any other pointers before I upgrade?

Thanks!

 

[jcostlow]

It should be just backup the system, uninstall and then install version 16 with restore. You do need to be on 15.5 SP6 and have a valid license.

https://www.3cx.com/docs/upgrading-pbx-v16/

 

[kraichle]

I'm running Windows Server 2012 R2. I noticed this note in the procedure,

"Windows compatibility for 3CX V16 Update 5 and later is restricted to Windows 10 or Server 2016/2019"

I'm assuming this means I'll have to upgrade my server OS before I do the PBX upgrade? Or is this only needed to support the Apple Push Notifications?

 

[jcostlow]

It will probably install on 2012 R2 but would be best to upgrade the OS or you can use Debian. You will need to upgrade the OS for the Apple Notifications for sure.

 

[AWS2P]

just do complete backup from V15.5 SP6, save it out of 3CX computer.

do a fresh v16 SP6 install on supported OS and restore during install.( 2012 R2 is no more supported)

 

[JohnS_3CX]

I'm running Windows Server 2012 R2. I noticed this note in the procedure,

"Windows compatibility for 3CX V16 Update 5 and later is restricted to Windows 10 or Server 2016/2019"

I'm assuming this means I'll have to upgrade my server OS before I do the PBX upgrade? Or is this only needed to support the Apple Push Notifications?

Hi,

We no longer support that OS. This means that we do not test the PBX on that OS for quality assurance, and any problems that might exist there will not be found or patched. If you have reasons that mandate you stay on that OS, the best I can recommend is to build a VM on that system, and deploy our 3CX Debian ISO.

Supported hypervisors can be seen here: https://www.3cx.com/docs/manual/phone-system-installation-windows/#h.5hoy5wwhhk5c

 

[sbrammer]

We were on 2012 when v16 came out. We ended up building up a new 2019 vm, then installed v16 with the backup from the old server.