Since lbmofo isn't having problems, and you are using the same carrier, try downloading and installing freeware at site http://www.pingplotter.com/freeware.html, and run testing the path to vpn.ooma.com placed in the "Address To Trace" block.lbmofo wrote:We are from the same hood and here is what I reported early last month.pops wrote:Just adding my voice to the mix. We're in our first month of use and are experiencing a significant delay. Our provider is XO Communications in Seattle WA, and delay on 909 test number is approximately 600ms (though it appears much worse in actual conversations than it does in the echo test).
I've adjusted my QoS settings and opened a ticket, but if it doesn't get resolved I'll return the unit to CostCo.
I have the same XO carrier. I am having no issues with my service; if any delays, can't be worse than the cell phones.lbmofo wrote:Nov 2010 Hub 470ms
Apr 2011 Hub 837ms, Telo 1003ms
Today Hub 400-450ms, Telo 500-520ms
This doesn't show the whole path that an Ooma phone call through to a legacy carrier takes, but it does show the approximately first two thirds of the path.
Let the program run for a while. The first Hop, and maybe the second Hop is in your home. These numbers should be zero or a very low number like 1, 2, or 3.
If the trace background color stays green, you have a pretty good connection on your end.
If the Xs along the graph line starts to get in the yellow or red, there are problems in that area.
A couple of other numbers that can be placed in the "Address To Trace" block are XO IP addresses 126.96.36.199 & 188.8.131.52. Note: These IP address aren't always operating, but they do get you farther down the line.