VoIP One-way Audio and Voice drops
-
You don't have a Broadcom NIC, by chance?
-
-
I really think it's related to the Hyper-V Nic Driver & Linux. Make sure the Hyper-V host has all windows updates installed. You could also Disable VMQ and Disable Large Send Offload Version 2
-
@thecreativeone91 said:
I really think it's related to the Hyper-V Nic Driver & Linux. Make sure the Hyper-V host has all windows updates installed. You could also Disable VMQ and Disable Large Send Offload Version 2
I moved to a different host last night. I disabled VMQ, not Large Send Offload though, I will look into that.
-
@scottalanmiller said:
So no issues hitting the local firewall. Now the other wise of the WAN but still "local"?
This is the WAN access IP address.
PBX
Desktop
-
Tested that ping and did not see any errors.
-
Yup, testing from here and not seeing packet loss. Looks good at the WAN side, as far as the pure WAN link.
-
I've tested it from my house as well and it works fine. So that tells me it is something internal.
Have people had issues running a PBX on Hyper-V? I've heard about the linux driver issues that 2008 had, but I was fairly certain that those had been resolved.
-
I run PBX in a Flash and Free PBX on Hyper-V no issues.
I have ran Elastix 2.4 as a demo on Hyper-V.
-
@coliver said:
I've tested it from my house as well and it works fine. So that tells me it is something internal.
Have people had issues running a PBX on Hyper-V? I've heard about the linux driver issues that 2008 had, but I was fairly certain that those had been resolved.
Are you running it as a Generation 1 or Generation 2 VM?
-
@thecreativeone91 said:
@coliver said:
I've tested it from my house as well and it works fine. So that tells me it is something internal.
Have people had issues running a PBX on Hyper-V? I've heard about the linux driver issues that 2008 had, but I was fairly certain that those had been resolved.
Are you running it as a Generation 1 or Generation 2 VM?
Generation 1
-
More ping data all started at about the same time for about the same length.
VM Host 1 - Windows and Linux Server
Windows Server
Linux Server
VM Host 2 - PBX
PBX
-
That really makes it seem like a driver or similar issue. Very weird.
-
I'm really concerned as to why it would pop up 5 months after the original deployment. Even if it were a driver issue. Could a Linux update have caused this?
-
A Linux update could have, of course. But were both of these systems patches recently? It is far more likely to be a HyperV issue. But either is certainly possible.
-
@scottalanmiller said:
A Linux update could have, of course. But were both of these systems patches recently? It is far more likely to be a HyperV issue. But either is certainly possible.
No, neither were updated prior to last Friday.
-
Seems pretty unlikely to be Linux then if multiple, non-patched systems were impacted.
-
From the Meraki GUI I can do a similar ping test. It shows no loss of packets and a 1-4ms response time. To the 204 IP address.
-
What Linux is the "other" one?
-
@scottalanmiller said:
What Linux is the "other" one?
CentOS 6.6 final. FreePBX runs on CentOS 6.5 final.
This is one running OpenSuse
