VoIP One-way Audio and Voice drops
-
That's a lot of drops for a LAN. Should basically be zero.
-
@scottalanmiller said:
That's a lot of drops for a LAN. Should basically be zero.
It just seems to be the firewall. Pinging anything on a different switch through the firewall results in 0ms response (or less than 1). Which brings it back to maybe the firewall isn't working correctly?
-
@coliver said:
@scottalanmiller said:
That's a lot of drops for a LAN. Should basically be zero.
It just seems to be the firewall. Pinging anything on a different switch through the firewall results in 0ms response (or less than 1). Which brings it back to maybe the firewall isn't working correctly?
The Meraki? I'm not surprised. Their router/firewalls are underpowered.
-
@thecreativeone91 said:
The Meraki? I'm not surprised. Their router/firewalls are underpowered.
But didn't the issue exist with the Ubiquiti too, which should be orders of magnitude more powerful.
-
I know ping isn't the best indicator but it really is the best I have at the moment. Here are two captures taken at almost the same time:
PBX
Meraki
-
Here is the PBX pinging both the Meraki and the remote switch at the same time.
Meraki
Remote Access Switch
-
Sorry, the remote switch is "through" the Meraki?
-
@scottalanmiller said:
Sorry, the remote switch is "through" the Meraki?
Yes, switch isn't the right term. It is the access to the rest of the internet.
-
@scottalanmiller said:
Sorry, the remote switch is "through" the Meraki?
I think he Means Phone Switch.. As in sip provider.
-
I think I agree with Scott.. I wonder if you have a failing switch. Can you replace it.. or for starters.. move the meraki to a different port on that switch?
-
@Dashrender said:
I think I agree with Scott.. I wonder if you have a failing switch. Can you replace it.. or for starters.. move the meraki to a different port on that switch?
Switch? The PBX is directly connected (ok it is going through a hyper-v virtual switch but it is the only on it) to the Meraki firewall which is our internet gateway.
At the suggestion of NTG support I directly connected the PBX server to the internet (which is a bit of a chore here) and there was no packet loss and ping/response times were marginally better. I forgot to grab a screen shot of it though.
That pretty much means it is the firewall correct?
-
Well before jumping to that (hopefully correct) solution, have you tested calls to ensure that packet loss is correlating to bad phone calls?
-
Have you looked at wireshark any using port mirroring?
-
@scottalanmiller said:
Well before jumping to that (hopefully correct) solution, have you tested calls to ensure that packet loss is correlating to bad phone calls?
I wasn't able to test the calls outside of the network I didn't have enough time. It takes a good 15-30 minutes to swap out devices with our ISP and I only had an hour to test.
-
I see
That sucks, but it does suggest that the issues are all on the network. -
Should have gone hosted... I would still see these problems but at least people could bring their phones somewhere else to use them.
-
@coliver said:
Should have gone hosted... I would still see these problems but at least people could bring their phones somewhere else to use them.
Sorry that it has to be BUT.... great example use case for where hosted can protect you
-
@scottalanmiller said:
@coliver said:
Should have gone hosted... I would still see these problems but at least people could bring their phones somewhere else to use them.
Sorry that it has to be BUT.... great example use case for where hosted can protect you
I would have done it originally but I couldn't get the numbers from anywhere else and until ~3 days prior to the go live date it was going to be over a PRI.
-
Considering my internet bandwidth (10/10) NTG just suggested that I go locally hosted for my PBX.
How many phones do you have @coliver, how often are they used for internal to internal calling? and what size pipe to the internet?
-
@coliver said:
@Dashrender said:
I think I agree with Scott.. I wonder if you have a failing switch. Can you replace it.. or for starters.. move the meraki to a different port on that switch?
Switch? The PBX is directly connected (ok it is going through a hyper-v virtual switch but it is the only on it) to the Meraki firewall which is our internet gateway.
At the suggestion of NTG support I directly connected the PBX server to the internet (which is a bit of a chore here) and there was no packet loss and ping/response times were marginally better. I forgot to grab a screen shot of it though.
That pretty much means it is the firewall correct?
Oh yeah, well in that case, it's definitely sounding like the firewall - but I thought you swapped the firewall yesterday and it made no difference?
