VoIP One-way Audio and Voice drops
-
@coliver have you checked to see if the NICs in your Hyper-V server actually have VMQ enabled or not?
In Powershell (assuming Server 2012 / R2) try
get-netadapter-vmq
-
@JaredBusch said:
His ISP is the SIP trunk provider for the main SIP service.
He setup a SIP trunk to another provider and experienced the same issues.
With all of the testing done to date, the problem is the ISP based on what we know so far.
Gotcha. Yes, that makes sense. I missed that the ISP and SIP trunk was the same provider.
-
I've seen a lot of issues from those "ISP as SIP trunk providers." Those seem to always be the ones that are willing to have things fail because they have good lock-in.
If you can test the third party SIP provider from home, for example, with the same setup (a bit of work) that would prove a lot.
-
@dafyre said:
@coliver have you checked to see if the NICs in your Hyper-V server actually have VMQ enabled or not?
In Powershell (assuming Server 2012 / R2) try
get-netadapter-vmq
The Hyper-V team was the original network adapter that this was on. Since starting with these issues I have moved that over to a dedicated port Ethernet 2.
-
Have you considered disabling VMQ ?
-
@scottalanmiller said:
I've seen a lot of issues from those "ISP as SIP trunk providers." Those seem to always be the ones that are willing to have things fail because they have good lock-in.
If you can test the third party SIP provider from home, for example, with the same setup (a bit of work) that would prove a lot.
I will bring my phone (the one attached to the Vitelity trunk) home and test it out there. I use a different ISP at my house. Or maybe I should bring it down to my parents who have the same ISP that would allow me to test that out the same network at least.
-
-
I do get this error: Networking driver in PBX loaded but has a different version from the server. Server version 4.0 Client version 3.2 (Virtual machine ID 82638176-8888-46C2-8FF4-6182BA79215C). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
But from what I've read this shouldn't cause any issues with actual connectivity.
-
@coliver said:
I do get this error: Networking driver in PBX loaded but has a different version from the server. Server version 4.0 Client version 3.2 (Virtual machine ID 82638176-8888-46C2-8FF4-6182BA79215C). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
But from what I've read this shouldn't cause any issues with actual connectivity.
Likely means it's suffering performance hit as the NIC might not be fully virtualized.
-
@thecreativeone91 said:
@coliver said:
I do get this error: Networking driver in PBX loaded but has a different version from the server. Server version 4.0 Client version 3.2 (Virtual machine ID 82638176-8888-46C2-8FF4-6182BA79215C). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
But from what I've read this shouldn't cause any issues with actual connectivity.
Likely means it's suffering performance hit as the NIC might not be fully virtualized.
Ok, I will see if there is an update available for that version of Linux.
-
@thecreativeone91 said:
@coliver said:
I do get this error: Networking driver in PBX loaded but has a different version from the server. Server version 4.0 Client version 3.2 (Virtual machine ID 82638176-8888-46C2-8FF4-6182BA79215C). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
But from what I've read this shouldn't cause any issues with actual connectivity.
Likely means it's suffering performance hit as the NIC might not be fully virtualized.
yeah, I would say this could be your whole problem (only the fact that SIP directly to a phone still had the same problem tells us it's not this error that's likely the problem).
-
@coliver I have read that a lot of NIC drivers do the VMQ implementation poorly in drivers which can kill performance, so I usually disable it, just to be safe. Most notably, this problem is especially prevalent on the Broadcom chipsets... I see you have intel.
It may be worth a shot, but there will be a brief blip if you use the powershell command to disable VMQ.
get-help VMQ
will list the commands.
get-netadaptervmq|where {$_.Name -eq 'NIC1'}|disable-netadaptervmq
Just replace NIC1 with whichever NIC is currently running your PBX VM.
-
@dafyre said:
@coliver I have read that a lot of NIC drivers do the VMQ implementation poorly in drivers which can kill performance, so I usually disable it, just to be safe. Most notably, this problem is especially prevalent on the Broadcom chipsets... I see you have intel.
This was the issue I had. Poor performance. and it was a Dell server with Braodcom chipset.
-
@Dashrender said:
yeah, I would say this could be your whole problem (only the fact that SIP directly to a phone still had the same problem tells us it's not this error that's likely the problem).
His VM is not the problem because a PHONE with the credentials directly entered has the same problem.
-
lol maybe the brackets around the second part of my statement made it invisible? lol
-
It is obviously a load issue. After ~3-4 pm I no longer see any issues. During the weekend I also saw no issues.
-
@JaredBusch said:
@dafyre said:
@coliver I have read that a lot of NIC drivers do the VMQ implementation poorly in drivers which can kill performance, so I usually disable it, just to be safe. Most notably, this problem is especially prevalent on the Broadcom chipsets... I see you have intel.
This was the issue I had. Poor performance. and it was a Dell server with Braodcom chipset.
IBM server with Intel NICs.
-
Just in case I've updated the integration services for Linux.
-
Moving the VM to my lab server, trying to see if maybe that will resolve it. Currently nothing is running on the lab server. Wishful thinking I know but worth a shot.
-
Try your phone again directly to the SIP trunk.
