This forum includes tips for maintaining the best audio quality possible with the Ooma System. If your Ooma system is having issues with dropped calls, static audio or echo, look here for assistance.
#79232 by vicw
Wed Apr 13, 2011 9:30 am
thunderbird wrote:... I measured approximately 350 ms using 909-390-0003 from China. ...


How are you (and others on this thread) measuring the delay time? Is there some kind of tool for that purpose, or by using a a stopwatch - or swag? Seems to me that it would be pretty difficult to measure it with any accuracy on a stopwatch.

I tried that echo number several times, and the voice quality was wretched each time. I know our regular calls sound pretty clear in both directions. Is that poor audio typical for that number?
#79234 by kdawgud
Wed Apr 13, 2011 10:19 am
vicw wrote:
thunderbird wrote:... I measured approximately 350 ms using 909-390-0003 from China. ...


How are you (and others on this thread) measuring the delay time? Is there some kind of tool for that purpose, or by using a a stopwatch - or swag? Seems to me that it would be pretty difficult to measure it with any accuracy on a stopwatch.

I tried that echo number several times, and the voice quality was wretched each time. I know our regular calls sound pretty clear in both directions. Is that poor audio typical for that number?

Vicw -

See here: viewtopic.php?f=4&t=9569&start=30
#79284 by thunderbird
Wed Apr 13, 2011 7:45 pm
Just Information:

Connecting to the Ooma Forum today, from China, has been extrimely slow. I can connect to Google, Yahoo, Amazon just fine.

So I've been ping-ing and tracert-ing.

It seems that on the way to www.ooma.com there are hops that are dead (hops that timed out), and some hops that are very, very slow. I used the following: tracert -d www3.ooma.com, tracert -d www.ooma.com, tracert -d vpn.ooma.com.

Everyone of these address had dead hops and very slow hops along the way. While Google, Yahoo and Amazon had no dead or slow hops at all.

I wonder if the dead and slow hops add to the cronic delay problems that some people have?

Maybe some of the delay people can test the same way and see if you get the same results as I do from China.
#79467 by kdawgud
Sat Apr 16, 2011 3:47 am
traceroute -n www3.ooma.com
traceroute to www3.ooma.com (208.83.244.196), 30 hops max, 60 byte packets
1 192.168.2.1 1.597 ms 2.027 ms 2.314 ms
2 172.27.35.1 8.188 ms 8.764 ms 9.147 ms
3 192.168.1.254 9.507 ms 9.951 ms 11.440 ms
4 OMITTED 732.649 ms 733.128 ms 734.168 ms
5 OMITTED 34.054 ms 36.423 ms 36.798 ms
6 151.164.94.56 32.725 ms 32.112 ms 34.025 ms
7 151.164.55.178 85.896 ms 80.417 ms 79.768 ms
8 151.164.46.86 35.484 ms 36.461 ms 129.250.9.73 36.885 ms
9 129.250.4.201 34.961 ms 33.980 ms 33.736 ms
10 129.250.3.107 88.842 ms 87.575 ms 87.263 ms
11 129.250.5.13 87.162 ms 90.599 ms 84.471 ms
12 128.241.219.130 86.534 ms 90.122 ms 88.829 ms
13 66.151.144.13 86.734 ms 66.151.144.75 90.730 ms 84.768 ms
14 74.217.77.122 86.277 ms 85.131 ms 87.058 ms
15 208.83.244.196 85.096 ms 86.074 ms 83.473 ms


I believe slow or missing tracert nodes don't necessarily mean anything. If you can ping ooma directly, then your packets are routed just fine. It's possible the intermediate nodes don't respond to or place low priority on ICMP responses (since they just need to propagate packets to other places - they are not a hosting server).
#79692 by kdawgud
Mon Apr 18, 2011 3:28 pm
kdawgud wrote:
thunderbird wrote:kdawgud:
Thanks for the information. Have you had any luck with your delay issue?

Negative. Haven't heard anything back from cust support. I will try to ping them again this week.

Speaking of cust support, I got an email back this afternoon saying their carrier couldn't find a problem and asked me for more test results. I ran some more tests (which hadn't really changed) and hope to hear back again in a day or two.
#79693 by kdawgud
Mon Apr 18, 2011 3:30 pm
Thunderbird -
What is your round-trip delay when calling 925-259-0082? I know you said the 909 number was 350ms. Just curious if you actually see any difference between the internal vs external numbers. My latest time to 925-259-0082 is 350ms, but the 909 number is 800-900ms.
#79835 by thunderbird
Wed Apr 20, 2011 3:01 am
kdawgud wrote:Thunderbird -
What is your round-trip delay when calling 925-259-0082? I know you said the 909 number was 350ms. Just curious if you actually see any difference between the internal vs external numbers. My latest time to 925-259-0082 is 350ms, but the 909 number is 800-900ms.

This morning my delay test for phone number 925-259-0082 was approximately 220 ms.
#79946 by kdawgud
Thu Apr 21, 2011 8:03 am
Status update:

I've been working with level 3 cust support and yesterday they tried a route change with my carrier. This resulted in a mild improvement in the delay to my landline (800ms dropped to 660ms), but didn't improve the delay to my cell phone. Hoping I hear back today that another change is ready for me to try. I still haven't gotten the latest firmware update... not sure whether that will actually deliver the expected improvement or not (has anyone else noticed improvement?). I will certainly test again when I do get the newest firmware.

Cheers!

Who is online

Users browsing this forum: No registered users and 8 guests