- Joined
- Oct 9, 2019
- Messages
- 44
- Reaction score
- 19
I needed to set up a paid v18 Pro system using a v16 NFR backup. It's gone pretty well, but there's one glitch I'm not sure how to handle.
I wanted to switch to a 3CX FQDN, so I created a backup of the v16 system without the custom FQDN and without the NFR license.
I bought a v18 Pro license and launched PBX Express on Azure. Either I missed the option to restore a backup during install (docs), or it has been removed.
I uploaded the v16 backup to the v18 instance and did a restore. Looks like everything came over just fine (which is great), but I noticed that the provisioning template in the welcome email still has the old, custom FQCN for the Local addresses. Here is an excerpt:
And in fact, when I look at the account in the legacy 3CXPhone, it shows the old public FQDN as the "In Office" URL.
How do I get 3CX to "forget" the old custom FQDN?
Thanks,
I wanted to switch to a 3CX FQDN, so I created a backup of the v16 system without the custom FQDN and without the NFR license.
I bought a v18 Pro license and launched PBX Express on Azure. Either I missed the option to restore a backup during install (docs), or it has been removed.
I uploaded the v16 backup to the v18 instance and did a restore. Looks like everything came over just fine (which is great), but I noticed that the provisioning template in the welcome email still has the old, custom FQCN for the Local addresses. Here is an excerpt:
Code:
<PBXLocalAddr>oldcustomfqdn.mydomain.com</PBXLocalAddr>
<PBXPublicAddr>mydomain.region.3cx.us</PBXPublicAddr>
<PBXSipPort>5060</PBXSipPort>
<UseStun></UseStun>
<StunServer>mydomain.region.3cx.us</StunServer>
<ProvLink>https://oldcustomfqdn.mydomain.com/provisioning/....xml</ProvLink>
<ProvLinkExternal>https://mydomain.region.3cx.us/provisioning/....xml</ProvLinkExternal>
<MyPhoneServerLocalAddr></MyPhoneServerLocalAddr>
<MyPhoneServerPublicAddr></MyPhoneServerPublicAddr>
<MyPhoneServerLocalSSLAddr>https://oldcustomfqdn.mydomain.com/myphone/MPWebService.asmx</MyPhoneServerLocalSSLAddr>
<MyPhoneServerPublicSSLAddr>https://mydomain.region.3cx.us/myphone/MPWebService.asmx</MyPhoneServerPublicSSLAddr>
<UseCTI>true</UseCTI>
And in fact, when I look at the account in the legacy 3CXPhone, it shows the old public FQDN as the "In Office" URL.
How do I get 3CX to "forget" the old custom FQDN?
Thanks,