- Joined
- Dec 16, 2024
- Messages
- 17
- Reaction score
- 3
Hi,
We recently moved our own 3CX Enterprise cloud instance from one cloud service to A Microsoft Aruze VM.
We used the VM from the Azure marketplace for this.
We made a complete backup from our V20 3CX running machine to restore on our new clean Azure image.
This is a production running 3CX with SIP Trunk that are working correctly with the correct E164 settings, switched off for our Belgian SIP Trunk in the advanced settings.
We restore the backup but then we discovered that the "E164 processing settings" under advanced settings was turned back on, which caused issues with our number format for our main Belgian Trunk, our French trunk that we have was not impacted offcourse.
How could this happen, we trusted that the backup from a V20 production 3CX would include every setting for the whole wide system to restore to a new clean image of V20 which apparently isn't the cause!?!
Can someone tell me how this is even possible because if this is a problem how can we even trust the backups we daily make in cause of a new restore?
Best regards
Kristof
We recently moved our own 3CX Enterprise cloud instance from one cloud service to A Microsoft Aruze VM.
We used the VM from the Azure marketplace for this.
We made a complete backup from our V20 3CX running machine to restore on our new clean Azure image.
This is a production running 3CX with SIP Trunk that are working correctly with the correct E164 settings, switched off for our Belgian SIP Trunk in the advanced settings.
We restore the backup but then we discovered that the "E164 processing settings" under advanced settings was turned back on, which caused issues with our number format for our main Belgian Trunk, our French trunk that we have was not impacted offcourse.
How could this happen, we trusted that the backup from a V20 production 3CX would include every setting for the whole wide system to restore to a new clean image of V20 which apparently isn't the cause!?!
Can someone tell me how this is even possible because if this is a problem how can we even trust the backups we daily make in cause of a new restore?
Best regards
Kristof