Strange Hyper V Issue

[SY]

To exclude "RTC" from the discussion please try to do following:
1. open 3CXPhoneSystem.ini file and remove semicolon before "Msusetickcount" entry in [General] section. (it is at the beginning of file)
2. save the file
3. restart "media server" service.

If it doesn't alter quality of audio delivery then you need to dig into configuration of "networking"/driver layer of either the host or the Hyper-V virtal machine

Thanks

 

[captivateglobal]

As for other server loads interfering, I'm not so sure. One could test that with the stripped-down, free version of Hyper-V Server 2008 R2 (almost no UI) compared to the full Windows Server 2008 R2 running Hyper-V.

I'm not entirely sure how Hyper-V works, but as I understood the basic Hyper-V software is something you load on top of W2K8's kernel. I would imagine the kernel has virtualization technology in it; however not to the same bare-metal spec as an ESX server.

However I didn't know a product like 'Hyper-V Server 2008 R2' existed - which would probably be much closer in performance to ESX and have less of these kind of issues as a result. If you were to be running a PBX in a virtual environment, the best choice for the hypervisor is the one with the best timing. I must admit I am partial to VMWare as I've been using it since the early days, and I tend to stick with products I know. The same challenges apply across all vendors, of course.

On a side note, I've had some limited success in getting TDM telephony working in a virtualized environment via PCI passthrough, but the RTC is not solid enough to keep sync with something like TDM - SIP/RTP is hard enough!

 

[SY]

Stepan,

Can you explain a little more about the purpose of the "Msusetickcount' entry? How does 3CX interact with the system clock when this value is and is not set?

Thanks,

It is a "safe mode"...

 

[tworhythms]

Great feedback! I've been away on business and just now have been able to read the posts.

The RTC timing sounds like it could be the culprit! It could certainly explain why some people have had absolutely zero problems with the exact same setup and why my Server 2003 worked as well as it did.

Also, it's my understanding that ASUS has used different techniques on their Z8NA-D6 motherboard to achieve the dual Xeon configuration on an ATX from factor (i.e. different length buses to/from the memory controller to correct timing issues). I wonder if some of these hardware modifications could be coming into play as well?

Unfortunately, I have already completely replaced my Hyper-V infrastructure with ESXi so testing this theory is not going to be easy. Is anybody else running this motherboard with Hyper-V and 3CX running Server 2008 64 Bit?

Thanks everyone for the help! These forums are invaluable! If I ever go back to Hyper-V with this setup then I will certainly try these suggestions.