3cx Upgrade queries

[jmp28]

I have a client running 3CX v18 on premises and I want to move them to 3cx hosted.
Firstly, their license does not include hosting. If I renew the license to include hosting, will it change it to the hosted automatically or will it wait for me to manually switch it.
Second, when I do go to switch it to hosting, can it be done from v18 or do I have to upgrade the on prem version to v20 first.
Thanks in advance.

 

[NicholasP_3CX]

Once you include 3CX hosting in the subscription, it will not automatically migrate the machine. You will need to do this through your customer portal, by clicking on Switch to hosted.



or if you go into the subscription itself



Since you are going from Version 18 to version 20, just ensure that you are on Version 18, update 9A. Ensure you have a system owner defined WITH A UNIQUE emal address. Ensure you can access the web client of this account, as this will now be your way of managing this.

The checklist of updating from Version 18 to Version 20 can be found at: https://www.3cx.com/blog/releases/v20-upgrade-checklist-faq/

When you switch to hosting, just upload your backup into the wizard, stand back, and let it install. Your configuration will be restored, upgraded to version 20 all in one go.

 

[jmp28]

Thanks Nicholas, appreciate it.

 

[jmp28]

HI Nichloas
Sorry, another query. After upgrading the client to the hosted license and then switching their 3CX system into the 3CX hosted system. Will they still appear in my partner portal. The reason I ask that is because I was a partner but since I did not hit the partner selling requirements I have been downgraded to a client. I had another client that was already migrated to the 3CX hosted prior to my partnership being downgraded and after I was downgraded I can no longer see that client in my partner portal. So, will that happen with this current client as well?

 

[Heath]

I have an enterprise license and in addition to the primary server where I run the PBX I also have a failover server.. Am in the process of upgrading from v18 to V20. Now since both use the FQDN with the failover taking over if the active goes down, what do I do with the split DNS on both the Active and the Failover (Passive). Does the split get setup on both.. Currently as was the failover (passive) was on standby and if the active went down and was out for 4 minutes the passive comes online and activates and automatically takes over the FQDN.

 

[Guillaume Bourgeois]

I can no longer see that client in my partner portal

Make sure the license is registered to the email address you use with 3CX.
You can update this email address directly in the PBX under the “License Info” section.

 

[Guillaume Bourgeois]

I have an enterprise license and in addition to the primary server where I run the PBX I also have a failover server.. Am in the process of upgrading from v18 to V20. Now since both use the FQDN with the failover taking over if the active goes down, what do I do with the split DNS on both the Active and the Failover (Passive). Does the split get setup on both.. Currently as was the failover (passive) was on standby and if the active went down and was out for 4 minutes the passive comes online and activates and automatically takes over the FQDN.

You have a PBX installed locally, on the same network as the phones, and in case of a failure, you switch to a cloud setup? Correct?

 

[Heath]

You have a PBX installed locally, on the same network as the phones, and in case of a failure, you switch to a cloud setup? Correct?

No. Both the active and the passive failover are a windows server and both are offsite in 2 different locations. 2 different IP addresses

 

[Guillaume Bourgeois]

Do you have VPN connections for these two remote PBXs?

 

[jmp28]

Make sure the license is registered to the email address you use with 3CX.
You can update this email address directly in the PBX under the “License Info” section.

Thanks Guillaume. Email address fixed it.

 

[Heath]

Do you have VPN connections for these two remote PBXs?

No. The active and passive failover were all working on v18. But now I’m upgrading both to v20. So all checks are done. The only issue is the split DNS settings. And there is nothing in the forum, blog, or anywhere on on this topic on enterprise version with a failover.

 

[Guillaume Bourgeois]

Split DNS does not apply to your situation. The purpose of Split DNS is to resolve the local IP address instead of the public IP address.
If your PBXs are remote and you cannot reach them via their local IP, then you won’t configure Split DNS.
https://www.3cx.com/docs/creating-fqdn-split-dns/

The automatic public IP change behavior for 3CX FQDNs has not been changed.
If you switch to the slave PBX, the propagation of the new public IP will occur as before, provided it’s a 3CX FQDN.

 

[Heath]

Thanks Guillaume. Email address fixed it.

Split DNS does not apply to your situation. The purpose of Split DNS is to resolve the local IP address instead of the public IP address.
If your PBXs are remote and you cannot reach them via their local IP, then you won’t configure Split DNS.
https://www.3cx.com/docs/creating-fqdn-split-dns/

The automatic public IP change behavior for 3CX FQDNs has not been changed.
If you switch to the slave PBX, the propagation of the new public IP will occur as before, provided it’s a 3CX FQDN.

Split DNS does not apply to your situation. The purpose of Split DNS is to resolve the local IP address instead of the public IP address.
If your PBXs are remote and you cannot reach them via their local IP, then you won’t configure Split DNS.
https://www.3cx.com/docs/creating-fqdn-split-dns/

The automatic public IP change behavior for 3CX FQDNs has not been changed.
If you switch to the slave PBX, the propagation of the new public IP will occur as before, provided it’s a 3CX FQDN.

Both servers use the same license key and the same FDQN. The active is set to active and the failover is set to passive to listen for the active. It’s set that if the active goes out for 4 minutes the passive will activate and take over the FQDN. My FQDN is a 3CX.us

 

[Guillaume Bourgeois]

Both servers use the same license key and the same FDQN. The active is set to active and the failover is set to passive to listen for the active. It’s set that if the active goes out for 4 minutes the passive will activate and take over the FQDN. My FQDN is a 3CX.us

Alright, no further action is needed. It will continue to work as expected.