v18 with 2 digit users. Upgrade to v20 with 3 digit. Self hosted to hosted

[tripleu]

Hi, hope someone can confirm.
I had a v18 Pro whic was setup with 2 digit extns.
The licence came for renewal so we purchased and applied - all ok.

However we wished to move to 3 digit extns and there is no way to migrate so I did te following...

Created hosted instance ov v20 with 3 digit on the 60 days trial.
recreated all the extns/users and moved trunks over.
Move all the phones and 3cx users over.

All working fine.

I now need to close the old v18 instance and have the licence on the v20.

Is it just a case of shutting down the old v18 and replacing the licence on the v20 with our recently renewed one?
Of course the new v20 is a different FQDN.

Or have I messed up the process?

Thanks.

 

[OlegR_3CX]

Hi there.
So the FQDN will not be replaced when you swap the keys (it will remain the same as now), and the new key that you use for the replacement, should not have any FQDN.
Another thing there is that you will not be able to use 3CX hosting and swap the key that was already activated, and in your case based on what you described it was.

 

[tripleu]

so is there a way to release the key assigned to uuu.3cx.com.au and reuse it on this instance?

If it can’t be done on hosted I could create a new self hosted version if that’s what’s required.
Otherwise I assume i need to buy a second licence and waste the existing one.

As I mentioned I only did it this way to minimise user outage and to convert 2 digit to 3.

I Couldn’t see any other way to do it.

thanks. Again.

 

[OlegR_3CX]

So the key can be Disconnected from the portal, but to use the same FQDN you will need to reinstall the system with that FQDN from the start. If you will need to use the same FQDN, then just set up a new system when it's out of ours and it will be easier for you.
If FQDN was not the case (you didn't need to use the same one), you could swap the keys if it was your own hosting/on-premise install.

 

[tripleu]

Thanks.
My scenerio is that the new fqdn is in use now. I don’t need to keep the old one that’s on self hosting v18. I can shut that one down.
In the portal I see both systems at the moment. The v18 self hosted and the new hosted one with different fqdn.

All I wish to achieve is to delete the old v18 self hosted and then use the key that was on the v18 fqdn and reuse it on the v20 new fqdn.

I’m just being carful as I don’t want to stuff it all up.

Thanks again

 

[Evolute IT]

Setup your v20 hosted properly. Shutdown the v18 one.

When done, release the FQDN of the v18 license and go into your v20 > Admin > System > License, and click the "Change License Key" to set the v18 one in there. It will assign the instance and the FQDN to that license.

Keep in mind the other license needs to have Hosted addon paid already. Otherwise it won't work.

 

[tripleu]

Ok. I was doing the correct steps then. Just that we havnt paid add on for hosted yet. I’ll have to work out how to pay for that seperate.
Thanks again for your advise.

 

[Evolute IT]

Ok. I was doing the correct steps then. Just that we havnt paid add on for hosted yet. I’ll have to work out how to pay for that seperate.
Thanks again for your advise.

Simply upgrade from the customer portal. Choose "add hosted" and set the size accordingly.

I highly recommend going through partners to help you understand those processes as well as encourage said partners

 

[tripleu]

The process seemed simple to be honest. I used to be a partner but as I didn’t have many sales I lost the status. Of course v20 then arrived.
If there was a way to change number of digits on extns I wouldn’t be going this route.

So with wanting to change digits. Needing to upgrade os and add extra core for v20 there were risks. Hence building a seperate system gave me a way to move the users over slowly without much outage.

I have been running a couple of 3cx instances on a VPS for nearly 8 years now so this was more a playing it safe method.

This particular client is a non profit community radio station and I do heaps of stuff for them. The pbx is just a small part of the puzzle I manage.

Thanks again. I’ll have a look at the upgrade tomorrow.

I appreciate your time.

Thanks.

 

[OlegR_3CX]

@tripleu
Let us know if everything went fine and if you were able to migrate your system to a new server.

 

[tripleu]

I’ll be trying later today or tomorrow. I have to work around risk of issues when the radio station has announcers on site.

Thanks.

 

[OlegR_3CX]

Sure, with the above feedback, you should be fine.

 

[tripleu]

Thanks here is what I did.
Remove the key off original system.
Shutdown my self hosted VPS.
Removed the reference to the old instance in portal.
Tried to use the purchaed key that has about 11months left to the newer hosted instance which of course has a differnt fqdn to the older one.
It failed so I have contacted the partner that purchaed the licence for us.

I have a few weeks left to fix this.

Thanks

 

[Evolute IT]

Thanks here is what I did.
Remove the key off original system.
Shutdown my self hosted VPS.
Removed the reference to the old instance in portal.
Tried to use the purchaed key that has about 11months left to the newer hosted instance which of course has a differnt fqdn to the older one.
It failed so I have contacted the partner that purchaed the licence for us.

I have a few weeks left to fix this.

Thanks

Normally you just need to release the FQDN on the new key and replace license in the console. It will transfer the current FQDN and all to the new key.

 

[tripleu]

Indeed. It didn’t work

 

[Evolute IT]

Indeed. It didn’t work

What's the process you took? It should definitely work as we've done it often.

 

[tripleu]

so in portal I had:
uuu. as a self hosted v18. Recenty had new licence key appied
tripleu . as a 3cx hosted on 2 minth trial.

I rebuilt all things in the 3cx hosted v20 instance. moved everything over. This was to convert from 2 digit extn to 3 digit,

Last night I removed the key from v18 self hosted.
Shutdown my self hosted v18 instance.
Removed the v18 self hosted entry ftom portal.
The did a 'replace' licence key on v20

Pasted in the key that was on v18
I then hit save and get this:
The installed license key cannot be replaced with this key because the key is disabled or has already been replaced. Contact your Partner.

Just tried it again - same error.

I contacted the partner who is sending emai to 3cx.

This really should be easy but clearly I did something wrong!

 

[bitn2]

You deleted the key, thats the problem.

 

[Evolute IT]

Removed the v18 self hosted entry ftom portal

You delete the license. You don't "remove" anything. You just "Release" the FQDN. Not the same thing.

I think you killed your key.

 

[Evolute IT]

This really should be easy but clearly I did something wrong!

It is easy and the partner should have helped you. They were probably too busy just selling you the license and letting you deal with it.