Solved Error Migration from Azurepbxexpress to Hosted

Status
Not open for further replies.

thetissot

Bronze Partner
Basic Certified
Joined
May 20, 2020
Messages
23
Reaction score
2
Hello,
I try to migrate my NFR instance (self-hosted on azure) to hosted by 3CX.
During the migration i have the error :"Error in XML file. RequestCode = 'OperatorEmail': Invalid reply."
Type d’hébergement : 3CX
Hébergeur : DigitalOcean (NFR)

Now in my customer webpage / key i can see for my NFR KEY:
Deployment: Not Deployed ( [Deploy to Hosted] )

I use this intance so i try to reboot the Azure VM, all is fine on here if i connect by IP but the FQDN : mycompany.3cx.fr not updated.

How can i do to get this instance work back (update the fqdn ... ) ?

Thanks.
 
In the emergency, I had to:
- Deploy in hosted mode a new instance of my NFR KEY (with a new FQDN)
- Restore a backup of old instance (azure) (without license or FQDN).

I am now asking myself this question, I am planning to switch this instance to Pro version with 16 channels for our internal use (at the moment it is a 4 channel NFR).

What should I do if I don't want to change the FQDN yet (because with the hosted mode, the release option is not available and on the instance I can't touch the key)?

thank you in advance
 
Last edited by a moderator:
Dear @thetissot

from the extended log error, we believe you are using an IVR as operator extension.
The operator extension must be a natural person (user extension) and the web interface does not allow to select anything else.

To fix, open from management console settings -> general -> press OK (which will set the selected operator extension, the current configured system extension will not be indicated)
 
Dear @thetissot

from the extended log error, we believe you are using an IVR as operator extension.
The operator extension must be a natural person (user extension) and the web interface does not allow to select anything else.

To fix, open from management console settings -> general -> press OK (which will set the selected operator extension, the current configured system extension will not be indicated)

Hello Thanks for your reply, i check and the operator was 00 (the first extension).

Does the problem can be that my old fqdn was mycompany.3cx.fr ans xxx.3cx.fr is no longer avalaible ?
The other msg error was : Looks like you did not setup your DigitalOcean (NFR) Account with DigitalOcean (NFR) Cloud features.
 
as I stated before, the interface would not show you any other "forced" system extension but will auto-select the first actions of your system by number. If you have still bound X.3cx.fr on your license you can remain using it until your release the FQDN. In this case, you cannot claim it back and need to switch to my3cx.fr.
 
as I stated before, the interface would not show you any other "forced" system extension but will auto-select the first actions of your system by number. If you have still bound X.3cx.fr on your license you can remain using it until your release the FQDN. In this case, you cannot claim it back and need to switch to my3cx.fr.

Thanks for you reply StefanW
 
Welcome, let us know if the deployment after this works. Enjoy and merci
 
Yesterday when the deploiement to hosted crash the state of my licence automaticly switch to : Deployment: Not Deployed .
So i don't release the fqdn but i loose it.
For that i start with a new FQDN
 
@thetissot as I can see the A Record of your FQDN change, you did not loose it.
It is impossible to loose your FQDN, unless if you release it from our license key and as I can see you have not done something like that.. PM me please if you need more information.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,962
Messages
589,986
Members
164,867
Latest member
swegner