3/3/2023 0 Comments Pingplotter pro![]() ![]() ![]() A low jitter number indicates a solid, good connection. Jitter is a measurement of how much latency changes, from sample to sample. If we sent out 100 samples and received back 97, then total all latencies and divide by 97 to get the average. The average latency is the total of all latencies, divided by the number of samples that we're measuring. The average latency (in PingPlotter) is the average (mean) time it takes a packet to get from your computer, to the target server, and then back again. If we sent out 100 packets and only recieved 97 back (3 didn't make it), then we have 3% packet loss. Remember that PingPlotter lets you pick a 'window' of samples to examine - we call this 'Samples to Include'.įor the sample set, this is the percentage of packets that never made it from us, to the target server (or intermediate hop) and then back again. So, the question is: How do we convert packet loss, latency and jitter numbers to an MOS score? That's a great question! We've built one model for this, but we'd certainly love participation from anyone who wants to improve this formula!įirst, let's define our 3 metrics: Packet Loss, Latency and Jitter. One advantage of estimating MOS with PingPlotter is that we also know Latency, Packet Loss and Jitter at any intermediate hops, so we should be able to estimate MOS for not just the final destination, but also for each intermediate hop! This would give us an easy way to see at which hop MOS is deterioriating, and can help us identify where the problem is. Is there any way to put these three values together and come up with a MOS 'guess' that has some similarity to real life? We think there is, and PingPlotter Pro attempts to do so. There are 3 factors that significantly impact call quality:Īll of these are well known by PingPlotter, covering the samples we take. MOS is an interesting number, though, and if we take a few variables that we know negatively impact call quality, we can put together a very rough approximation of what the voice call quality might be over that line. We're also measuring only once every second - or possibly less often, depending on the trace interval. It might be a web server, or a game server, or any variety of things, none of which care to collaborate on estimating how a person would measure voice quality over that connection. ![]() PingPlotter's collection methods are a bit different from all of this - we're sitting on one side of a connection, and the other end has no idea that we're measuring anything. For best results, you might take samples from the line at a similar rate to what a voice call might send data (numerous times a second). This is usually done by having both sides of the connection measure certain characteristics of the connection, and collaborate on the quality of the line and connection. There are a number of factors that play into an MOS rating, and some hardware and tool vendors have put formulas in place that can 'estimate' an MOS, based on a number of variables. In fact, there's probably not even a voice call going on over your network much of the time for us to measure. Obviously, with PingPlotter we don't have someone doing a voice call on your line all the time, and then giving an opinion number. In reality, this number is a subjective 'opinion' rating of call quality given by someone who was just on a voice call. It is used by the VoIP industry to put a number on voice quality. MOS (mean opinion score) is a voice call quality metric. PingPlotter Pro now has an 'MOS' column and alert. How is MOS calculated in PingPlotter Pro?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |