Upgrade from V16 to V18

[EnclustraGmbH]

We discovered that our phone-system is still v16
We now want to upgrade (finally)
Can we setup a new server with 3cx v18 and run it side to side with v16 to be able to test the new version before switching all out employees over?
or can we at least setup v18 parallel without adding it to our network and than switch "quickly"?

 

[SweetAction]

We discovered that our phone-system is still v16
We now want to upgrade (finally)
Can we setup a new server with 3cx v18 and run it side to side with v16 to be able to test the new version before switching all out employees over?
or can we at least setup v18 parallel without adding it to our network and than switch "quickly"?

The problem is the license key can only be active on one installation at a time, although an enterprise key might work because it includes failover mode.

If using a 3CX FQDN you need to also be concerned with the TTL of the IP that the FQDN is bound to. All this to say that side by side isn't the best bet if you wish to use the same key and also same FQDN (if provided by 3CX)

Your best bet if you wish to do this is...

0. Prep a new machine for v18 by installing 3CX and getting to the start of the installation wizard. This is the screen where it asks for your key/backup file.
1. Take a backup of the v16 machine.
2. Disconnect your v16 machine from the internet/network. Begin downtime.
3. Restore the backup and complete the install wizard. Should be under 15 minutes. Change the IP to the old v16 machine address.
4. You are now running v18 and can test all you want. End downtime.

Should you wish to go back to v16, simply disconnect the v18 machine from the network and reconnect the v16 machine to the network.

 

[EnclustraGmbH]

The problem is the license key can only be active on one installation at a time, although an enterprise key might work because it includes failover mode.

If using a 3CX FQDN you need to also be concerned with the TTL of the IP that the FQDN is bound to. All this to say that side by side isn't the best bet if you wish to use the same key and also same FQDN (if provided by 3CX)

Your best bet if you wish to do this is...

0. Prep a new machine for v18 by installing 3CX and getting to the start of the installation wizard. This is the screen where it asks for your key/backup file.
1. Take a backup of the v16 machine.
2. Disconnect your v16 machine from the internet/network. Begin downtime.
3. Restore the backup and complete the install wizard. Should be under 15 minutes. Change the IP to the old v16 machine address.
4. You are now running v18 and can test all you want. End downtime.

Should you wish to go back to v16, simply disconnect the v18 machine from the network and reconnect the v16 machine to the network.

Thanks for the quick answer.
yes, we do indeed have a 3cx FQDN.

But your way of doing the update sounds good aswell.

Bit off this topic:
Is it still possible with v18 to use old deskphones which we had to manualy provision with v16?
specifically yealink t22p
so i mean do we have to redoo everything or will they directly work with the v18 when we change the ip from v16 to v18?

 

[SweetAction]

Thanks for the quick answer.
yes, we do indeed have a 3cx FQDN.

But your way of doing the update sounds good aswell.

Bit off this topic:
Is it still possible with v18 to use old deskphones which we had to manualy provision with v16?
specifically yealink t22p
so i mean do we have to redoo everything or will they directly work with the v18 when we change the ip from v16 to v18?

They should work without any issues if manually provisioned with v16. At the end of the day SIP is SIP and a SIP device that has valid authentication should continue to work.

3CX provisioning may or may not work depending on your settings, but at the very least https://www.3cx.com/sip-phones/yealink-t20p-t22p-t26p-t28p/ still shows this model and I've never had a working phone stop working due to version upgrades.