| Review by compuguybna |
member for 3.9 years, 1854 visits, last login: a few hours ago
updated 157 days ago
- $5 per month
- about 1 days
- "Cheap Home Phone Service if you have a FAST broadband connection"
- "Call quality generally, but sometimes choppy with heavy internet usage."
- "Fair Voip Quality Overall, Taxes Went up to $4.72."
Ease of Installation:
Value for money:
(ratings match consensus)
11/30/12 - - CANCELLED OOMA. bundled internet and phone from the local cable co. Phone for $14.99 taxes included. better quality.
UPDATE 10/8/12. Had OOMA for over a year now. Most of the startup bugs have been worked out. TAXES have gone up to $4.72 a month.. Downgraded ISP speed, but still works ok on a 15mbps connection.
Decided to just go with OOMA BASIC. Over a month and a half passed, I got my first bill... $3.47.
still solid. Charter gave us a speed bump. now 30mbps down / 4 up. no problems with QOS.
UPDATE 11/12/11 . . . .
Received new FIRMWARE about a week ago. the "robotic voice" seems to be corrected. AT&T landline issue seems to be corrected. Unit seems solid. Calls get choppy with heavy downloading on the network at the same time. Have devoted about 1500down and 900up as QOS priority, and that seems to be sufficient for phone calls with normal web surfing. will probably NOT renew the Premier service. Not sure the 9.99 extra is worth it ((( I like free service too much))). If any thing changes, I'll be sure to update.
UPDATE 10/19/11 . . . .
Up and running for 15 days here without an issue. The calling AT&T landlines appears to have been resolved.. Call quality seems to be ok, Although gets "robotic" about 20 minutes into a call. Overall, second time around seems alot better than the first unit. Will update next month.
UPDATE 10/4/11 . . . . .
Trying another OOMA box and new phone number. Exchanged the other unit.
The AT&T landline seems to be resolved for now. I'm still testing the new unit for now. Only a few calls not received so far. VoiceMail is sometimes very choppy and laggy.
Thought I'd take a minute to review the OOMA TELO device.
Advertised as "FREE HOME PHONE SERVICE".
Its a VOIP device, so you have to have a pretty steady consistent fast internet connections. I had Charter 18 down / 2 up service, so bandwidth was NOT an issue..
Setup was pretty easy, but I have to add, you really have to be a little computer savy and know what functions a modem, router, and IP address performs.
Register the device online using the Activation Code (last few digits of the MAC address).
Put in your local area code and prefix (like if you have a landline #), and it will suggest local numbers that you can choose in YOUR area code (and prefix)..
A few configurations you can have the device in, including where the device is in your configuration. You can plug the internet directly into the device, then your home network (router) into the "home" port. Or you can hook the device into your router ports (this configuration requires a little more tweaking, and a little knowledge of IP address, etc).
I found the optimal configuration was for the device to be plugged into the router, and provide the device reserved bandwidth from the router. I reserved 5000 down and 1000 up for QOS rules.
Up and working, we called several numbers back and forth to determine the call quality. Mostly, the calls were clear, but on occassion, the calls were fuzzy with a strange "echo" in the background (on a call that was previously crystal clear).
All the sudden we could not call local #'s in our local town (SPECIFICALLY AT&T landline #'s). For example, the OOMA device was 931-422-xxxx, and our local # was 931-359)
When we called 931-359-xxxx from our OOMA device, we could tell when the caller answered BUT, we could hear the caller (outgoing call). Likewise, on incoming calls from 931-359, everything was ok. After speaking for about an hour troubleshooting with someone in the Phillippies, I was transferred to Level 2 tech support, after a while of investigating states that there were some issues DIALING at&t landlines with this device, (and obviously had been for a while, since people from late 2010 had reported this issue in their forums).... The "workaround" was to dial *99 before the #, but this basically was a "fax" mode. the call worked and you could hear on both ends, BUT all the sudden, there was a "double echo" on both ends.
I am taking this specific unit back to the retail store for an exchange, and i'll start the registration progress again and hopefully get a new #. Will report back later the exchange.
This seemed interesting This seemed interesting. My family has used Ooma for a very long time. I used Google to search for 931-359 and the first hit was on »phones.whitepages.com/931-359 .
Off the first page was a link for Walgreens, it is pasted below:
758 N Ellington Pkwy
Lewisburg, TN (0.2 mi)
I picked up my phone, and used Ooma to call Walgreens. Got a robot voice menu, then music while waiting for customer service. I asked what hours the pharmacy was open on Sunday, and got an answer from a very polite woman.
No echo, the call went right through, no problem. We don't dedicate anything in QOS to our Ooma device, it is just plugged into the router.
Did you ever post your concern on the Ooma forum at ooma.com?
Re: This seemed interesting No, using Charter HSI.
said by pandora:
Are you using AT&T DSL?