Performed at URL: http://speedtest.phonepower.com/repeat.html
Jitter: 2.4728 ms PLoss: 0.6% Down: 1,188,872 bps Up: 217,744 bps QOS: 87% RTT: 81 ms MaxPause: 418ms Test#: 53681
Jitter: 3.304 ms PLoss: 0% Down: 720,616 bps Up: 216,920 bps QOS: 34% RTT: 82 ms MaxPause: 647ms Test#: 53683
Jitter: 2.696 ms PLoss: 0% Down: 895,480 bps Up: 215,928 bps QOS: 21% RTT: 82 ms MaxPause: 1252ms Test#: 53685
Jitter: 0.712 ms PLoss: 0% Down: 980,904 bps Up: 219,904 bps QOS: 50% RTT: 81 ms MaxPause: 446ms Test#: 53729
Jitter: 0.086 ms PLoss: 0% Down: 752,168 bps Up: 209,248 bps QOS: 7% RTT: 83 ms MaxPause: 563ms Test#: 53731
Jitter: 0.144 ms PLoss: 0% Down: 1,244,312 bps Up: 212,192 bps QOS: 74% RTT: 106 ms MaxPause: 353ms Test#: 53733
Jitter: 0.982 ms PLoss: 0% Down: 994,208 bps Up: 219,576 bps QOS: 49% RTT: 78 ms MaxPause: 645ms Test#: 54107
Jitter: 0.21 ms PLoss: 0% Down: 823,728 bps Up: 220,048 bps QOS: 19% RTT: 79 ms MaxPause: 840ms Test#: 54109
Jitter: 0.066 ms PLoss: 0% Down: 963,864 bps Up: 219,640 bps QOS: 37% RTT: 79 ms MaxPause: 621ms Test#: 54111
After the serviceman cut off 2 loops (down and back Outlook Ledge and from our house to the end of Eagle Rock and return:
(While the printer was creating a PDF file)
Jitter: 4.326 ms PLoss: 0% Down: 1,045,400 bps Up: 219,576 bps QOS: 35% RTT: 77 ms MaxPause: 614ms Test#: 54483
Jitter: 0.346 ms PLoss: 0% Down: 950,000 bps Up: 219,840 bps QOS: 33% RTT: 78 ms MaxPause: 662ms Test#: 54487
Jitter: 2.758 ms PLoss: 0% Down: 1,086,320 bps Up: 216,048 bps QOS: 31% RTT: 80 ms MaxPause: 708ms Test#: 54493
Jitter: 0.114 ms PLoss: 0% Down: 1,175,264 bps Up: 219,512 bps QOS: 79% RTT: 79 ms MaxPause: 417ms Test#: 54508
Jitter: 1.566 ms PLoss: 0% Down: 1,242,912 bps Up: 218,304 bps QOS: 67% RTT: 80 ms MaxPause: 353ms Test#: 54514
Jitter: 0.792 ms PLoss: 0% Down: 803,784 bps Up: 219,840 bps QOS: 20% RTT: 80 ms MaxPause: 657ms Test#: 54519
(After printer was done- confirmed no other use of line and no computer activity- though this shouldn’t make a difference; you’d want a phone to work even when people are using the computer.)
itter: 0.162 ms PLoss: 0% Down: 1,066,088 bps Up: 219,784 bps QOS: 30% RTT: 79 ms MaxPause: 585ms Test#: 54539
Jitter: 0.124 ms PLoss: 0% Down: 1,062,528 bps Up: 219,648 bps QOS: 38% RTT: 79 ms MaxPause: 602ms Test#: 54542
Jitter: 1.174 ms PLoss: 0% Down: 762,368 bps Up: 219,592 bps QOS: 2% RTT: 79 ms MaxPause: 839ms Test#: 54546
These are a lot of numbers, but let me give you some insights.
Jitter is the variation is the delay of packet delivery- it is especially important in VOIP and other "real-time" streaming applications. These measurements show jitter is pretty good, though anything above 1 ms or so may require the software to manage jitter with "buffers" designed for that purpose. Anything above 100ms can't be fixed with buffering software. Note that some of the ISP service level agreement- what they promise for jitter are:
- Qwest: 2ms max
- Viteria: 1ms max
- Several others: .5 ms max
So the variability in the measurements above is a problem!
PLoss is "packet loss" and the number here is great.
Down and Up are the speeds of download and upload respectively. We are told 1.5Mb. You can see I don't get anywhere near that, and in several measurements I've done it is half that. (Except, read on for a fix.)
QOS is "quality of service." This is where ATT does not deliver! On the other hand, some of this may be due to in-house circuits, so read on.
If the QOS number is below about 80%, then you can't have a good audio conference. The sound will "ring" and there will be delays, such that you feel like you are talking over one another. In general, you can't get VOIP service (see another post). As you can see, most of the time our QOS is 30% or below. We are not being given the service we are paying for on the mountain.
Now, let me finish this blog by saying that I called in a service request on this issue. ATT sent someone out the next morning. He did various measurements and here are the findings.
- I had an old modem. This can cause some problems. The serviceman gave me a new modem. It did not solve the QOS problem. As a matter of fact, it performed worse on QOS than the old modem.
- The router did not seem to cause a problem, though I will investigate settings on both the modem and the router later.
- The big problem is the length of the line from the place where our DSL wires plug into their "box" and our house. DSL performance degrades with distance. 3 miles would be really pushing the technology. Well, the boxes are located at the top of the mountain, near the clubhouse. If you are on Eagle Rock, what's the distance to the club house??? 2-3 miles? I haven't measured it, but it is about a mile to Raven. It's got to be at least a mile to the end of Raven. So, the further you are from the clubhouse, the slower your speed and the worse all the performance numbers! I think it is a shame that there is only one location of boxes for the mountain.
- My situation was worse. There were two loops my signal had to follow in addition to the distance from the top of the mountain to my house. My signal went down the length of Outlook Ledge and back and then down to the end of Eagle Rock and back before I "hopped" on. My guess on mileage is an additional 2 miles of length. At that distance, 4-5 miles, it is a wonder I am getting any signal! The repairman reattached my DSL connection so I caught the line as it first went by the house and changed the connection at Outlook Ledge so the signal didn't go down Outlook Ledge first. You'll note the average Down and Up times did pick up significantly. Nothing else seems to have improved. I think we are just too far away to begin with.
I hope this helps you understand some of the limitations we have on the mountain. One is that VOIP will probably not work, at least for us on Eagle Rock. I'm going to do some checking and folks houses at the top of the mountain and see if the readings are better.
No comments:
Post a Comment