Were you having any voice issues during the time you were collecting PingPlotter data?

Based on the one minute image you shared here, I'd guess that you were not having any network-related voice issues during that minute - it looks great. The final destination has a maximum latency of 5ms and no lost packets - that's beyond ideal. Most voice protocols have an internal latency (by design!), so the latency you're seeing here is about perfect - even with a bit of jitter (which is not significant *at all* with the latency you're seeing).

The jitter you're seeing at the intermediate hops is a bit higher, but is not being represented at the final destination, so it's not an issue - even if it was high enough to be an issue, which it isn't.

This is pretty dreamy, based on the one minute sample you're showing - close enough to perfect that it would be considered perfect by many people.

Back to the question, though, if you experienced any voice problems during that period. The value of PingPlotter in a voice scenario is that it can capture problems over time. Maybe you didn't experience voice problems during the period you were collecting data, but you did at some other time - keep running PingPlotter until you experience voice problems, and then see what PingPlotter looks like.

If you *were* experiencing voice problems during this period, what were they? Maybe your voice issues are not network related.

If you do sometimes experience voice problems, but you weren't during this period, keep collecting data until you have voice issues - then look at PingPlotter to see what your network looked like during the voice issues.