So, I am deeply familiar with the previous posts / threads / documentation regarding moving a 3CX instance to a new machine.
However, is there any issue with moving a virtual 3CX instance by utilizing the hypervisors tools? Specifically, I have an instance installed in a isolated hyper-v install, and would like to move it to my production cluster. The idea is to power down, export from within hyper-v, and then import and power on in the new environment. EDIT: this is a Debian install. EDIT2: I am using DHCP option 66 to deploy configs, all phones are considered in the LAN, just on different subnets.
Internal IP will stay the same, however public IP will change.
I HAVE tried this multiple times so far, and cannot get it to work in the new environment at all. I get to the point where it has been moved, all the phones are back online and can communicate with 3CX, AND the firewall test passes. But when I start testing calls, I get the strangest results that make this difficult to troubleshoot. Sometimes the call will go through, and all i get is dead air, other times I will get the initial attendant. Deeper testing _seems_ to also show that it will only accept one concurrent call. Almost like it takes the first call fine, but then any other calls that come in while that one is still connected, they get dead air (however, even this isn't 100% as I have seen it where ill get 2 concurrent calls working OK).
NOTE: My production phone system is also setup in this cluster, with none of THE ABOVE issues (However it does have this weird bug where a 20 second ring time before going to VM immediatly takes you to their VM, but if I set it for 45 seconds ringing, it will ring for 20-30 seconds before going to VM).
Thoughts?
I do not mind moving it based on the documentation, but from browsing this forum it seems like others have had issues with having to recreate extensions, etc.
I am also worried that doing it the 'proper' way won't work and I'm stuck moving it back, which the documentation doesn't really go into how that should be handled.
Thanks.
However, is there any issue with moving a virtual 3CX instance by utilizing the hypervisors tools? Specifically, I have an instance installed in a isolated hyper-v install, and would like to move it to my production cluster. The idea is to power down, export from within hyper-v, and then import and power on in the new environment. EDIT: this is a Debian install. EDIT2: I am using DHCP option 66 to deploy configs, all phones are considered in the LAN, just on different subnets.
Internal IP will stay the same, however public IP will change.
I HAVE tried this multiple times so far, and cannot get it to work in the new environment at all. I get to the point where it has been moved, all the phones are back online and can communicate with 3CX, AND the firewall test passes. But when I start testing calls, I get the strangest results that make this difficult to troubleshoot. Sometimes the call will go through, and all i get is dead air, other times I will get the initial attendant. Deeper testing _seems_ to also show that it will only accept one concurrent call. Almost like it takes the first call fine, but then any other calls that come in while that one is still connected, they get dead air (however, even this isn't 100% as I have seen it where ill get 2 concurrent calls working OK).
NOTE: My production phone system is also setup in this cluster, with none of THE ABOVE issues (However it does have this weird bug where a 20 second ring time before going to VM immediatly takes you to their VM, but if I set it for 45 seconds ringing, it will ring for 20-30 seconds before going to VM).
Thoughts?
I do not mind moving it based on the documentation, but from browsing this forum it seems like others have had issues with having to recreate extensions, etc.
I am also worried that doing it the 'proper' way won't work and I'm stuck moving it back, which the documentation doesn't really go into how that should be handled.
Thanks.
Last edited:
