As a note to anyone at ooma who's listening:
This is the kind of issue that simply can't be happening if you want this product to fly. If I'm Joe Voipuser, I'm bringing the ooma home from Best Buy, setting it up per reccommendations, and noticing "hey, my internet connection is really slow when I'm on the phone", then I'm returning it the next day and telling my friends not to buy it because it totally screws up your internet connection. Being able to change the QoS settings on the ooma from setup.ooma.com is great, but for one thing, the fact that there is such a url is not mentioned anywhere in the quick start guide, and on exactly one page in the full manual. I'm sure that many potential users have never heard of QoS, let alone have a clue what it is. I'm not sure the option to put the ooma on the router instead of between the router and modem is even mentioned anywhere in the documentation (altho this isn't exactly hard to figure out if you have some experience and some technical ability). My understanding is that this product has been out for over a year, and I'm kind of shocked if this kind of issue is occurring for a significant number of users at this stage of the game. In my opinion if this product is going to appeal to a mass market it's got to be bulletproof and work flawlessly with optimal performance out of the box for the vast majority of non-technical users, and judging from my brief experience, I don't see that happening.
When I first bought ooma I hooked it up per the instructions and without setting QOS or anything it fired right up and worked great out of the box.
I guess it depends on individual setups.
I moved it behind the router to see if it would work ok, it's easier to remove, like a pc, in case I want to take it with me to the office.
Being someone who's paid big bucks for 25 years to the phone company, when I have an issue I always remind my self what I'm paying now for the same or better service.
- Bobby B
- Ooma Moderator
- Posts: 1457
- Joined: Mon Feb 18, 2008 8:41 pm
- Location: Palo Alto, CA
Thanks for the feedback. Hopefully we'll have some sort of "auto-QoS" available in the future that'll automatically adjust the QoS settings without user intervention.
Also, we'll try to mention QoS in the Quickstart guide as an option to optimize voice quality AND the Internet connection.
zeke wrote:Being able to change the QoS settings on the ooma from setup.ooma.com is great, but for one thing, the fact that there is such a url is not mentioned anywhere in the quick start guide, and on exactly one page in the full manual. I'm sure that many potential users have never heard of QoS, let alone have a clue what it is. I'm not sure the option to put the ooma on the router instead of between the router and modem is even mentioned anywhere in the documentation (altho this isn't exactly hard to figure out if you have some experience and some technical ability). My understanding is that this product has been out for over a year, and I'm kind of shocked if this kind of issue is occurring for a significant number of users at this stage of the game. In my opinion if this product is going to appeal to a mass market it's got to be bulletproof and work flawlessly with optimal performance out of the box for the vast majority of non-technical users, and judging from my brief experience, I don't see that happening.
Well, this is the thing. I'm testing out another voip provider and in my initial tests w/ that service, straight out of the box, I'm seeing virtually no effect on network thruput, and very good to excellent call quality, maybe with a little less artifact than ooma. The bandwidth used by voip should be relatively small. I believe the estimate I saw was something like 30-40Kbs w/ compression. I mean, the total analogue bandwidth is only like a few KHz, and you only need 2x sampling rate, etc. What I'm seeing from ooma is that it's essentially using like 800Kbs both ways. So, it makes me wonder how efficiently ooma uses its network bandwidth, which make me wonder how well it will scale if and when it becomes truly popular, and so on, not to mention the impact on my particular situation in the long run. You are evidently the user that is targeted by ooma in that you don't seem to have a pressing need for high-speed internet performance. However, there are people (I would wager a lot) who need to have both decent data performance and decent calling performance - at the same time! The user who brought up this topic said it slowed his connection to dialup-like performance. This would no doubt be unacceptable to most people. I'm really kind of impressed by the ooma experience as it were, and I'd really like to like it, but I'm kind of wondering how much substance there is behind the curtain. Long term, it makes me wonder if the gamble on ooma is worth the risk, not so much in the money upfront, but in the hassle when one is left w/ no carrier if they don't make it.WayneDsr wrote:In fact I did see a drop in upload speed while on a call, connected either way. That's the nature of the beast. My prority is the phone, internet second. Most of my internet activity is in the download direction anyway, hardly effected by the voip.
Keep in mind my Linksys is set to AUTO on the QOS.
I did a speed test (speedtest.net)
No activity except random access by 5 pc's connected to network
5048 kbits download 636 kbits upload.
With phone call in progress.
5043 kbits download, 588 kbits upload.
Hardly an internet stopper. It appears that the upload speed the ooma uses is close to what you were saying, 48 kbits.
Also although I indicated that the phone will always take priority (my priority) over web, my son is a web designer, and he is always doing something up or download. We also have a total of 4 users (6 pc's) as I supply our little apartment building with wifi. (no, not for free ).
At one time I did lose internet speed and it turned out to be an issue with DSL on the line that connected the Scout, but that can't be your problem because you have cable. (I think)
I am using OPEN DNS instead of the DNS supplied by AT&T.
This may help your internet speed since you'll be bypassing your isp's own dns.
Also a good VOIP test site is:
Hope I've helped some.
Here's my update:
As expected, the modem>router>ooma configuration works much better. As I learn more about the subject I'm kind of mystified about the choices made in this area in terms of both design and documentation. I stumbled across a how-to in the support area which was actually informative. I gather there is only a static bandwidth parameter on the ooma that is set by default to 384Kbps, and I gather that QoS scheduling basically delays packets to give them a net speed that is some percentage of this "maximum" speed based on their priority. I don't know how close to accurate that description is, but it is consistent w/ my experience that my normally 1Mbps uplink speed drops to a fraction of 384Kbps when I'm using the phone, with the system set up according to recommendations. I guess the assumptions made by ooma are
1) Nobody who uses this device has a high-speed internet connection
2) Nobody wants to do something crazy like actually make a phone call and use the internet at the same time
3) Any wacko who wants to do the above is happy to dig around in the web site support area to find out why their network performance sucks when they set up the device as recommended by the manufacturer.
For one thing, I really don't understand why the designers didn't include auto-detection of network speed. It seems pretty common in consumer equipment - my inexpensive dlink router has it, for example - and would go a long way to making this device fail-safe to set up for non-technical users, or those who want (expensive) devices they buy to just work w/o having to monkey around w/ them. Failing this, since QoS is apparently pretty crucial in determining overall network performance, especially when you set the characteristic parameter to some arbitrarily low value by default, you'd think the written manuals would at least mention the subject. The how-to on the web site should most definitely be included in the device manuals.
Anyway, there's my rant on the subject. Hopefully there isn't too much there I'll regret saying tomorrow.
I have Vonage back in place while we wait for the porting to finish but the only problem I've noticed when ooma was in place is that it takes 5 or 10 seconds for my home PC to connect with the internet with the cable > ooma > home router setup. I don't see that delay with the cable > home router > Vonage setup. I know its not much but, believe me,, it's a big deal to my wife with home any hint of imperfection with computers is a big deal...haha. Thanks