VoIP One-way Audio and Voice drops
-
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
-
Does a Windows VM on the hyper-V server have the same issue?
Also what about a UEFI linux running in a Generation 2 Hyper-V VM? -
Ping results from the Meraki. All of these are on different ports of the Meraki.
.88 is my deskphone, .121 is the PBX and .116 is a Windows server.
-
@coliver said:
Ping results from the Meraki. All of these are on different ports of the Meraki.
.88 is my deskphone, .121 is the PBX and .116 is a Windows server.
That doesn't make sense your out bound pings where fine on the other devices with no issues.
-
@thecreativeone91 said:
@coliver said:
Ping results from the Meraki. All of these are on different ports of the Meraki.
.88 is my deskphone, .121 is the PBX and .116 is a Windows server.
That doesn't make sense your out bound pings where fine on the other devices with no issues.
Yep, that was pinging the same windows server that had pinged it before. I'm going to try a few different phones and PCs around the network to test this.
-
So even the deskphone is losing a lot of packets? That's very, very fishy. Maybe there is a switch issue or something?
-
@scottalanmiller said:
So even the deskphone is losing a lot of packets? That's very, very fishy. Maybe there is a switch issue or something?
I moved the phone I was testing with off a dumb switch I was using and it is now directly attached to the firewall.
.215 is a PC attached to a different switch, which is directly attached the firewall. The Hyper-V host that the PBX resides on is directly attached as well. The other host goes through a switch.
