Solved 3cx Server Migration Issues

[jmalin]

Good Morning,

I'm trying to migrate our 3cx system from an older server to a newer one. I've managed to do the migration, but when I got to call in to our system from the outside the call quality is really bad. Static on the line, dropping syllables, really low volume.

What I did to migrate the server was to create a back up of the current 3cx. Then I shut down the VM that the current server was on. I then created a new VM on the new server. Installed Debian and 3cx via the ISO that I got from 3cx. During the install I copied the network information that was used on the current server. When the 3cx installation kicked off, I chose the restore option and pointed it at the back up I had just made. The installation goes fine, and the new server comes up without a problem. I don't see any errors in the Call Manager when I log in.

The problem I'm running in to is when calls come into the office from the outside the call quality is really bad. Calling out has no issues, calls are clear and work great. When we shut down the new server and spin up the current(old) server everything works great, no quality issues. Anyone have any ideas?

 

[cobaltit]

So you haven't mentioned anything about the VM environment or how you get your calls. My guess is a problem with the new server and/or VM configuration.

 

[jmalin]

The old VM was VMware, the new is HyperV. I thought that as well, so I went back and pretty much copied the settings frmo the old VM to the new.

 

[cobaltit]

Make sure you followed this guide:

https://www.3cx.com/docs/installing-microsoft-hyper-v/

The steps that normally catch people are the Broadcom NIC bit or the NTP bit.

 

[jmalin]

I did. I'm sure there's just some soetting or something that I overlooked, but I can't find it for the life of me.

 

[jmalin]

Is the NTP bit something I need to worry about if Debian is installed on the VM?

 

[cobaltit]

Yep. It's there at the bottom of the hyper-v page.

 

[jmalin]

Yep. It's there at the bottom of the hyper-v page.

and this could cause issues with call clarity on incoming calls?

 

[jmalin]

Found out the fix. We had to disable VMQ (virtual Machine Queuing) on the NIC.

 

[cobaltit]

That would be the Broadcom NIC bit I mentioned

Broadcom NetXtreme 1-Gigabit
If the HyperV server uses the above defined network adapter(s), the driver must be updated to the latest version and/or VMq needs to be disabled for those. More information can be found here: https://support.microsoft.com/en-us/kb/2986895