Ooma Forums

thunderbird wrote:4 packet Ping with 32 bites of data for www3.ooma.com = 163ms, 159ms, 169ms, 159ms.

Bill: you sure has a strange set of circumstances. It's hard to determine the common denominator for large delays in two locations, one on the west coast and one on the east coast.

Do you have the same brand and same model number modems and routers in each location?

What are the brand and model numbers of your modems and routers for each location.

You certainly wouldn't think that three Ooma devices would all be defective?

You wouldn't think that routing issues would be the problem for both locations?

It seems impossible for you to have ping times that high to Ooma while measuring audio delay at 170 ms to Ooma's internal test number. My ping is 22 ms. Your ping times are the same as the delay you measured. Are you using Adacity to measure delay? Is it possible you are measuring it wrong?

I'm running a Linksys WRT54G router flashed with Tomato 1.25 here in CA with a Speedstream 4100B modem on AT&T DSL.

In FL I have a D-Link DIR655 router and AT&T U-Verse 2-wire modem (don't know model).

Everything works very well at both sites. I stream TV with a Slingbox and Slingcatcher between sites regularly without a hickup and also stream Netflix movies while on the Ooma phone and it doesn't make a difference in delay test results. At both sites, I have Ooma at the highest QOS priority.

Bill

Bill:
I am thinking that something is a little strange about your 22ms ping time to www3.ooma.com. That seems to be too fast? But I don't Know.

I measured ping times to http://www.yahoo.com 116ms, http://www.google.com 107ms, and https://www.ooma.com 120 ms.

Ping from your computer to the IP address that is issued to your Ooma and see what it is. Mine is 1ms.

I've probably asked you this before but how are your rigs setup? Modem-Ooma-Router or Modem-Router-Ooma?

Yes I use Adacity to measure the delay. I can just listen to the Ooma phone converatations and know it's that good. The voice quality is clear, clean, and crisp. There is no echo, delay, or half-duplex. The Ooma phone quality is so much better than AT&T ever was. My wife takes to China every weekend. She says it's like taking to someone next door.

My average ping time to www3.ooma.com is 90ms.

Average ping to Yahoo is 73ms.

Average ping to Google is 40ms.

Average ping to Ooma.com is 118...

thunderbird wrote:Bill:
I am thinking that something is a little strange about your 22ms ping time to www3.ooma.com. That seems to be too fast? But I don't Know.

I measured ping times to http://www.yahoo.com 116ms, http://www.google.com 107ms, and https://www.ooma.com 120 ms.

Ping from your computer to the IP address that is issued to your Ooma and see what it is. Mine is 1ms.

I've probably asked you this before but how are your rigs setup? Modem-Ooma-Router or Modem-Router-Ooma?

Yes I use Adacity to measure the delay. I can just listen to the Ooma phone converatations and know it's that good. The voice quality is clear, clean, and crisp. There is no echo, delay, or half-duplex. The Ooma phone quality is so much better than AT&T ever was. My wife takes to China every weekend. She says it's like taking to someone next door.

Here's my ping times from southern CA, just double checked again.
http://www.google.com =10 ms
http://www.yahoo.com =56 ms
https://www.ooma.com =256 ms (this is interesting compared to 22 ms below, but this is not the VOIP packets)
www3.ooma.com =22 ms (I believe this is the address that the Ooma VOIP packets use, but I may be wrong)

Internal Ooma IP =1ms

I use Modem-Router-Ooma setup in both CA & FL
I also get good Ooma voice quality. Only problem is long delays like 700 ms the same as I measure.

Bill

thunderbird wrote:Bill: I am thinking that something is a little strange about your 22ms ping time to www3.ooma.com. That seems to be too fast? But I don't Know.

Bill D: Concerning the 22ms, I forgot that you are in California. For you, Ooma is just up the road a little while.

I see that you have double NATs, double firewalls, double everything at both your California and Florida location setups.

I see from the Internet, that Speedstream 4100B and Linksys WRT54G routers, when used together, sometimes have conflicts when it comes to VoIP. They both have to be carefully configured to function together for VoIP.

When you can find some time, try to isolate the delay problem by connecting one of your Ooma Hub's "Internet" port directly to the Speedstream 4100B's LAN port. (For testing don't connect the Linksys WRT54G router).

Connect a computer to the Ooma Hub's "Home" port to be used for testing delay. Reboot and Reboot etc.

Make sure the Ooma Hub is using the "Built-In" MAC Address setting.

Reserve a static IP address for the Ooma Hub in the Speedstream 4100B. Place the Ooma Hub's static IP address in the Speedstream 4100B's DMZ. Reboot and Reboot etc.

Test for delay using both test phone numbers.

Also after you are done testing, you probably won't have to remove the static IP address from the Speedstream 4100B's DMZ, when you reconnect your Linksys WRT54G router. If the router will except the static IP address, try your setup that way also.

thunderbird wrote:When you can find some time, try to isolate the delay problem by connecting one of your Ooma Hub's "Internet" port directly to the Speedstream 4100B's LAN port. (For testing don't connect the Linksys WRT54G router)

I've already tried Hub+Speedstream alone - earlier in this thread viewtopic.php?f=4&t=9569&start=210#p75195 and my measured delay is the same as the full network. I'm stumped. I was just on some calls back to FL to cell phone folks and the delay was painful.

Bill

Bill D:
"I've already tried Hub+Speedstream alone - earlier in this thread."

When you tested the Spredstream connected to the Hub, did you reserve a static IP address for the Ooma hub, and place the Ooma Hub's static IP address in the Speedstream's DMZ?

thunderbird wrote:Bill D:
"I've already tried Hub+Speedstream alone - earlier in this thread."

When you tested the Spredstream connected to the Hub, did you reserve a static IP address for the Ooma hub, and place the Ooma Hub's static IP address in the Speedstream's DMZ?

No, I just let it assign an address. I can't see why it would make a difference.

Bill D:
When the Ooma Hub's static IP address is placed in the Speedstream's DMZ, it allows/exposes the Ooma Hub full access to the Internet, for the Ooma Hub. It's like connecting the Ooma Hub directly to the Internet.

When you get some time, try it.

My Ooma Telo's QoS is very poor when I don't have the Telo's static IP address in my router's DMZ.

lbmofo wrote:

jhphone wrote:My Ooma call quality has been deplorable.
I am extremely disappointed with Ooma's awful performance. It's the worst phone there is.
I live in N Calif in the 650 area code, same as Ooma, and believe that my location cannot be causing the problem.
You cannot blame the long delay, half duplex transmission, echo, and loss of connection on my internet connection. It's in Ooma's system. Absolutely.

I'd bring your ooma to a friend's house with high speed internet and check it out. If still terrible, you may have a point].

There's no "may" about it.

Other posts in this 24 page thread describe the same set of problems -- again and again -- to no good outcome.

I've reported my excellent ping times, voip speed test results, and other pertinent data here many times. They're always good. Regarding high-speed internet availability, here's my Speedtest from a moment ago http://www.speedtest.net/result/1168122507.png 18.55 Mb down, 4.14 up.

Again, no problem on MY end.

I cannot comprehend any reason why my Ooma equipment would work any better if I took it down the street to another Comcast user. The test results mentioned above are objective measurements of my internet capacity. I watch Netflix and Hulu+ on my Roku hours a day with flawless video playback -- including HD video.

On the other hand, Ooma cannot produce even mediocre telephone audio quality.