For me, I have no issues with delay because my Ooma performs better than my cell phones. This should be true with everyone that uses cell phones.Bill D wrote:Its possible the that both the happy & unhappy users have exactly the same delay on their Oomas, but the happy users are "polite talkers". Maybe IBmofo and his 20+ family and friends are all very polite talkers.jhphone wrote:I am still holding on because users like you demonstrate that there IS A SOLUTION.
I've noticed that polite talkers don't seem to have a problem with excessive delay on the phone. I've had a few conversations with folks where the delay could have been several seconds and they wouldn't have even noticed. Their style seems to be "I won't talk until I'm really really sure you're done". Of course when I talk with folks like this, I do the same thing they do.
I've also been on calls with "interrupters" where we end up stopping and both say "go ahead" at the same time and then each wait for each other, only to them both respond at the same time. Business calls and group conference calls are the worse. There's a big difference between 400 ms and 600 ms on these calls.
lbmofo wrote:Confirming:lbmofo wrote:For me, I notice no difference between ooma and my cell when calling this number to test echo delay.
tkeppell wrote:I found this helpful information on another website and am sharing here.
To test voice quality dial the echo back number 909-390-0003
Note: It may not ring, and no one says hello. Just wait a few seconds for it to connect, then talk and it will echo back your voice.
Ooma Hub 470ms
AT&T Blackberry Bold 560ms
AT&T iPhone 3G 550ms
Ooma iPhone app via WiFi 470ms
Ooma iPhone app via 3G 900ms
I see no issues as long as Ooma delay is cellphone like or better.
I agree and feel a little guilty complaining about something that is such a great value.lbmofo wrote:I see no issues as long as Ooma delay is cellphone like or better.
AT&T calls on my iPhone 4 echo test at 400 ms and my Hub used to be the same, but the Hub has increased to 600 ms and is annoyingly noticeable on some calls as I described above.
Even though I miss my Hub's good old 400 ms, if both parties on the call are aware of the extra delay and are "polite", 600 ms is tolerable.
How can I determine my "ms" response time number?Bill D wrote: Even though I miss my Hub's good old 400 ms, if both parties on the call are aware of the extra delay and are "polite", 600 ms is tolerable.
Ooma Telo & handset
Ooma provisioned tel no.
AT&T (Formerly SBC) DSL (integrated router/modem)
* Upload speed > 5MB / Download speed ~.4MB
* Jitter 4ms / Packet Loss = 0% / Ping 62ms
I have seen occasional delay problems, which can result in both callers stepping on each other. Most of the time that is not an issue. If the other party is on a cell phone there can be a little echo. Most callers never know I have changed systems.
I have discovered a problem with call waiting. The 2nd call seems to wait out the time for voice mail to pick up before it rings in. In my case that is 45 seconds and people will hang up by then. Hopefully Tech Support can get this ironed out.
I have spoken with two people in Tech Support, which is overseas. One was excellent at handling a setup question. The other was a little slower on the uptake but she solved my problem, which was related to the carrier I ported from.
The tech support people do not repeat your name every minute, they do not seem to read from a script, and they also do not apologize for everything. They seem well trained and I hope they are adequately paid so they will want to stay on board. If they can provide good support I really do not care if they have an accent or a name I may not recognize.
I am a little over a month into my Ooma experience and so far it has been good. I do not expect perfection, though. After all, this is VoIP using the Internet and by definition it is subject to all sorts of trouble. That the Ooma Telo can handle most of those troubles most of the time is a tribute to its designers.
Since there's always some callers that don't leave messages, your comment caused me to test for this bug but I found no problem (I have a Hub without Premier).BackupBob wrote:I have discovered a problem with call waiting. The 2nd call seems to wait out the time for voice mail to pick up before it rings in. In my case that is 45 seconds and people will hang up by then.
My 2nd callers hear ringing right away, the same is if the line was not in use. The number of rings before VM picks is also the same either way.
Is it possible you are mistaken?
Anyone else have this problem?
To the remarks about "polite talkers" and "impolite talkers" I would reply, nonsense! The problem occurs even with talkers that you would surely characterize as "polite". If two very polite talkers each wait, say, about five seconds for the other to speak, but the one who last spoke waits slightly longer (by an amount equal to the delay), they will collide, just as if they were face-to-face and started simultaneously. Politeness, or the lack of it, has little to do with it.
I actually hate talking on cellphones and holding a rectangular blob up to my head but I need the ability to be reached. You'd think that I would not own one, wrong! I use a flagship Nokia N900 because of the cool non cellular stuff. It has a built in fm transmitter so on Christmas I decided to stream shoutcast over my car fm radio from Everett, Wa to Olympia, Wa (82 miles) using Tmo 3G. I had it drop to buffering on me once. My theory is if you haul ass through a dead spot you can beat the buffer timeout.
I was not speeding your honor, I was avoiding a buffer under-run.Davesworld wrote:The delay for good voip is seldom more than 150ms VOICE round trip delay and certainly not over 200ms. Some of that is jitter buffering and codec lag but only about 20ms with most of that being buffering. The bulk of it is likely caused by call routing.
Cheap Routing - - I have 2 Hubs and when I call Hub-to-Hub, I measure 300 ms one way, which would equal 600 ms round trip. I believe that test is without any VOIP routing outside of Ooma. Cheap routing may not be causing the delay because when I call 909-390-0003 from one Hub, I also measure 600 ms roundtrip delay. (My ping time to www3.ooma.com is 75 ms).