So I called. BIG, big big mistake!
The woman I talked to actually flat refused to help. She said I didn't meet the minimum requirements for Ooma, cuz I didn't have 384 upload speed, can't help you, goodbye. Wonderful customer service, huh?
Since when is this a requirement??? I bought it because the Amazon ads say 256, my Ooma box says 256, the stuff on Google says 256. Have I been screwed?? I certainly would not have bought it if I knew it was 384, and not what they have in print since my internet access is limited to UVerse and 1.5/380, and i have absolutely no way to get it increased.
The tests at phonepower give me all greens... says I can use high quality VOIP with no problems.
Linetest at Ooma says:
Download 1442 kbps
upload 358 kbps
Latency 71 milliseconds
Jitter 1 milliseconds
packet loss 0
Linetest gives me a yellow light - says I "can use Ooma, but I may want to contact my internet provider"
So, do I now have to scrap this whole thing, chalk up $300 lost in costs, and re-port my phone number back to a land line????
Your low upload Internet speed shouldn't be causing delay. Usually the low Internet speeds will cause garbled voice, one way conversation and some other problems.
By the way, the current default Ooma Telo upload speed is 512 kbps. But the Ooma Telo will still work properly with the lower upload speeds if there is a constant "clean" Internet signal reaching the Ooma Telo.
Usually a delay problem is caused by the phone connected to the Ooma Telo or the modem operating at half duplex.
For testing, try a different corded phone.
If you are using cordless phones in the house, even if the cordless phone set is not connected to the Ooma Telo, remove power from all cordless phone bases located in your home. Very important, while doing the test with the corded phone, remove power from all cordless phone bases in the home.
Make sure the Ooma Telo is located at least three to four feet away from all other electrical and electronic devices while testing with the corded phone.
If you don't hear a difference while testing with the corded phone, check your Modem owner's manual to see if there is a reset procedure for your Modem. If there is, do a Modem reset per the Modem owner's manual. Note: Some modems contain a battery that must be temporarily removed to have a successful Modem Reset or Modem Reboot. Check your Modem owner's manual to see if your Modem contains a battery. If so remove the battery per the Modem owner's manual. Do a Modem Reset, but if there isn't a battery in the Modem, do a Modem Reboot. Then test.
Seems you are at lower end DSL speeds. Uverse should be much faster I thought. If you have "lite" version of internet, the way the ISPs slow down the speed maybe VoIP killers.ntarvin wrote:my internet access is limited to UVerse and 1.5/380, and i have absolutely no way to get it increased.
Since the minimum for Ooma is now 512 kbps (unbelievable!), there's no way i can even come remotely close to it. And, though I had the UVerse tech come out and check and repair all the lines, I cannot get anything better or more stable than I have now, so it looks like the Ooma goes back into it's box in the closet, I re-port my number back to a land line, and eat all the lost costs. (Can't even sell the thing with that $80 reactivation fee. (sigh)) Well, on second thought, I could leave it hooked up and use it as a kind of backup/second phone using my second number.
Who knows - maybe Google will come to Tulsa, and lay down some fiber! (Hey, it *could* happen...LOL!)
If it cleans up the problems, great! If they don't, well, I'm no worse off than I am now, and right now the Ooma makes me feel like I should be saying "Breaker, Breaker!" and "over" at the end of each sentence... it's usable, but barely, and my wife cannot stand the delays... I'm also getting what I call "dead air" whenever I'm speaking on the phone -kind of like no background sounds at all - and can only hear something when the other person is speaking. It makes me feel like I've been disconnected and the other person is no longer on the line... very odd.
The vast majority of inexpensive speakerphones operate in half-duplex mode which is what you are describing.
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
I don't hold out much hope for it - I think we just have 40 year old phone lines that are not up to the job. We happen to live in a subdivision that was just "thrown up" in a hurry in the 70's with little or no concern for common sense and building codes. (One example? They unnecessarily ran our sewer lines *uphill*... Can I really believe they were any more careful with the phone lines? We need "Mike" to come fix our house! LOL!)
Generally, with consumer grade ethernet devices you should leave the "Ethernet procedure by which two connected devices choose common transmission parameters" set to Auto-Negotiation. This is because with consumer devices in many cases the consumer does not have an administrative User interface to set up the transmission parameters for both ends of the ethernet connection. The OOMA Telo, for example, does not provide an administrative User interface to setup its ethernet transmission parameters.ntarvin wrote:No speakerphones. I thought half-duplexing was the problem, too, so one of the first things I tried was to take my router off "auto" and specify full duplex. The only thing I have NOT tried lately is switching the position of the Ooma and the router - which I will be doing today. Currently I have it modem >> Ooma >> router (and I did it that way when the other setup did not work when I first installed the Ooma.) ...
With LAN (local area network) devices, you should never turn off "Auto" negotiation on just one end of a connection between two ethernet-connected devices. That is, you should not set one end of the connection to "Full-Duplex" unless you have an administrative interface to the other end of the connection so that you could also set the other end of the connection to Full-Duplex, as well. If you take one end of the connection off of Auto-Negotiation and set it to Full-Duplex while the other end of the connection is still set to Auto-Negotiation, the connection will be forced into a "Half-Duplex" communication protocol. This is because the end of the connection which is still set to Auto-Negotiation cannot determine the Duplex capabilities of the other end of the connection (because its not auto-negotiatiing) and the protocol rules dictate that under this circumstance the protocol should be configured by the devices as Half-Duplex.
Here's a link to Wikipedia for a discussion of ethernet Auto-Negotiation and some text from that discussion:
"... Autonegotiation is an Ethernet procedure by which two connected devices choose common transmission parameters, such as speed, duplex mode, and flow control. In this process, the connected devices first share their capabilities regarding these parameters and then choose the highest performance transmission mode they both support. ...
... Parallel detection is used when a device that is capable of autonegotiation is connected to one that is not. This happens if the other device does not support autonegotiation or autonegotiation is administratively disabled. In this condition, the device that is capable of autonegotiation can determine and match speed with the other device. This procedure cannot determine the presence of full duplex, so half duplex is always assumed. ..."
Ooma Premier, two phone numbers
AT&T DECT-6.0 two-line base with four remotes & headset
Cyberchat wrote:If you take one end of the connection off of Auto-Negotiation and set it to Full-Duplex while the other end of the connection is still set to Auto-Negotiation, the connection will be forced into a "Half-Duplex" communication protocol.
I've wondered about this...thunderbird wrote:Some routers have a Duplex setting in the router WAN settings area, which is usually set to Auto Duplex (wording may be slightly different for different Routers). If possible set this setting to Full Duplex. This setting should force the Modem to operate in the Full Duplex mode.