Questions about v15.5 SP6 and upgrading to v16

[Michael Menor]

We've got several PBXs still on v15.5 SP6. Over a dozen of them are for a single client and are running 4SC Standard. I think v16 was released around early 2018, and with that the "Bridging" feature was no longer available on the Standard license and only available in Pro and Enterprise.

That being said, I've got a few questions about v15.5 and this push to v16:

1. What will happen to any remaining v15.5 SP6 PBXs after July 1, 2020? Will they continue to run if maintenance has been renewed?
2. If we trade in our Perpetual licenses to Annual licenses, will we need to immediately perform the v16 upgrade? Or will the v15.5 instance continue to run?
3. Is the "Trade In" program available after July 1, 2020? Or is that the cutoff date?

Thanks in advance for your time!!

 

[AWS2P]

As you are Partner, why don't you ask this directly to your 3CX customer channel ?

 

[Michael Menor]

@aws2p We have, but they didn't know the answers either....

 

[CentrexJ]

I would upgrade asap.

They said that the lets encrypt technology that v15.5 uses will have issues renewing in July I believe. If you are using 3CX FQDN this will be a problem. If you are using custom FQDN, there are still several other reasons to upgrade to v16 that I won't go into here because they are well covered.

If you have v15.5 licenses that are standard and not expired, when you upgrade to v16 they auto upgrade to professional for the remaining term of the license. So you won't drop the bridges when you upgrade.

They have not announced any end date for trade-in licenses, in fact it was just improved from 1 year to 2 years so I can't see this going away soon but you never know.

While I have done a trade-in of a v15.5 license from perpetual to annual, it worked, but that was months ago. However this is possibly not the case any more, since you can't upgrade a v15.5 license size until you upgrade to v16 now it is possible that you can't trade it in until it is upgraded but i'm not sure.

 

[Michael Menor]

@CentrexJ - That's the response I was looking for! Thank you so much!