Measuring jitter and packet loss on the LAN for VoIP troubleshooting.
Jitter above 30 ms and packet loss above 1 percent cause audible problems. Measure toward the SBC, not just google.com, because the path can differ.
Try this first
- 1PBX or softphone usually has call stats showing jitter, loss and RTT per call.
- 2Run a long continuous ping to the SBC and watch for spikes, not the average.
- 3Use iperf or pathping when you suspect a bottleneck on a specific hop.
- 4Test at different times of day, congestion often correlates with backup windows or cloud sync.
When to bring us in
Loss is on the WAN segment, not the LAN: bring in the provider with a week of measurement data, otherwise you get blamed.
See also
- Voys, BelXS or RoutIT, which cloud PBX fits?Three popular NL platforms, differences are admin UI, partner model and per-user price.
- Teams Phone: Calling Plan, Direct Routing or Operator Connect?Three ways to connect PSTN to Teams, cost and management differ a lot.
- 3CX: self-host on VPS or take 3CX cloud?Self-host saves licence, but you own SBC, backup and updates.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.