This forum includes tips for maintaining the best audio quality possible with the Ooma System. If your Ooma system is having issues with dropped calls, static audio or echo, look here for assistance.
#77141 by Dandolo
Sun Mar 13, 2011 9:58 am
Thanks for any help you can offer.

I have had Ooma for about six months and never had a problem. I have ATT U-Verse and it is plugged directly into the RG (combo moden and router). About a week ago, though, people began complaining that my voice was so broken up that it was unintelligible. I often do radio interviews and have had several hosts have to take a break so that the engineer can call me back on my cell phone! It has become so bad that it is almost impossible to have a conversation on the Ooma line any more.

Here are my numbers:

VoIP test statistics
--------------------
Jitter: you --> server: 64.7 ms
Jitter: server --> you: 3.6 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.3 %
Packets out of order: 0.0 %
Estimated MOS score: 3.6

Speed test statistics
---------------------
Download speed: 3215576 bps
Upload speed: 1106232 bps
Download quality of service: 4 %
Upload quality of service: 37 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 257 ms
Average download pause: 7 ms
Minimum round trip time to server: 204 ms
Average round trip time to server: 234 ms
Estimated download bandwidth: 28000000bps
Route concurrency: 8.707616
Download TCP forced idle: 92 %
Maximum route speed: --

What I have tried:

Rebooted the RG and the Ooma numerous times.

Moved the Ooma to the DMZ on the RG.

Set upload and download to 0 on the Ooma setup.

The jitter is so bad, I'm not really sure what to do to fix it. Any suggestions will be much appreciated.
#77148 by murphy
Sun Mar 13, 2011 10:42 am
All of these are bad

Jitter: you --> server: 64.7 ms (less than 5 ms)
Packet discards: 0.3 % (packets should never be discarded)
Download quality of service: 4 % (75% or more)
Upload quality of service: 37 % (75% or more)
Maximum TCP delay: 257 ms (less than 100 ms)

Connect a computer directly to the RG and run the test with nothing else connected to the RG.
Then connect a computer to the Ooma home port and run the test again with only Ooma connected to the RG.
Compare the two results.
#77174 by danlisman
Sun Mar 13, 2011 1:10 pm
If you have Ooma Telo (as opposed to core Hub) you can enter *98 before the number of each outgoing call. This will force G711 codec instead of using Ooma Purevoice proprietary codec. Like murphy said, your numbers are less than ideal. My AT&T DSL has similar numbers to yours, but AT&T says that all is within tolerences. G711 codec seems to be much more forgiving.
#77177 by Dandolo
Sun Mar 13, 2011 1:44 pm
Thanks for the suggestions!

OK. I disconnected everything (including WiFi) from the RG except one computer and ran the speedtest. It looks much better!

VoIP test statistics
--------------------
Jitter: you --> server: 11.1 ms
Jitter: server --> you: 3.6 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Estimated MOS score: 3.9

Speed test statistics
---------------------
Download speed: 6628408 bps
Upload speed: 1270664 bps
Download quality of service: 89 %
Upload quality of service: 86 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 162 ms
Average download pause: 3 ms
Minimum round trip time to server: 75 ms
Average round trip time to server: 75 ms
Estimated download bandwidth: 24000000bps
Route concurrency: 3.620779
Download TCP forced idle: 72 %
Maximum route speed: 6990400bps


Then (as suggested) I connected only the Ooma Telo and ran the test through the Home port. Even better!

VoIP test statistics
--------------------
Jitter: you --> server: 0.1 ms
Jitter: server --> you: 4.0 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Estimated MOS score: 4.0

Speed test statistics
---------------------
Download speed: 9755528 bps
Upload speed: 1488016 bps
Download quality of service: 96 %
Upload quality of service: 99 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 54 ms
Average download pause: 2 ms
Minimum round trip time to server: 76 ms
Average round trip time to server: 76 ms
Estimated download bandwidth: 12800000bps
Route concurrency: 1.3120766
Download TCP forced idle: 47 %
Maximum route speed: --


I then reconnected the cables for the wired connections -- there are four, one of which runs to a switch. AFter all were reconnected I tested from a computer plugged directly into the RG. Still not bad.

VoIP test statistics
--------------------
Jitter: you --> server: 11.8 ms
Jitter: server --> you: 3.5 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Estimated MOS score: 3.9

Speed test statistics
---------------------
Download speed: 6624824 bps
Upload speed: 1262576 bps
Download quality of service: 92 %
Upload quality of service: 92 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 155 ms
Average download pause: 3 ms
Minimum round trip time to server: 75 ms
Average round trip time to server: 75 ms
Estimated download bandwidth: 24000000bps
Route concurrency: 3.6227376
Download TCP forced idle: 72 %
Maximum route speed: 6990400bps


The last thing to restore was the Wifi, which has a variety of things connected to it -- four laptops, a Roku box, Squeezebox, and probably some things I have forgotten. Testing from the Ooma Home port after WiFi was restored on the RG gave me poor numbers:

VoIP test statistics
--------------------
Jitter: you --> server: 28.0 ms
Jitter: server --> you: 3.6 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Estimated MOS score: 3.7

Speed test statistics
---------------------
Download speed: 5208280 bps
Upload speed: 817040 bps
Download quality of service: 43 %
Upload quality of service: 80 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 273 ms
Average download pause: 4 ms
Minimum round trip time to server: 76 ms
Average round trip time to server: 83 ms
Estimated download bandwidth: 12000000bps
Route concurrency: 2.3040235
Download TCP forced idle: 48 %
Maximum route speed: 6898416bps


And testing from a computer plugged directly into the RG was even worse:

VoIP test statistics
--------------------
Jitter: you --> server: 43.6 ms
Jitter: server --> you: 3.5 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Estimated MOS score: 3.7

Speed test statistics
---------------------
Download speed: 6414184 bps
Upload speed: 907280 bps
Download quality of service: 79 %
Upload quality of service: 67 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 333 ms
Average download pause: 3 ms
Minimum round trip time to server: 75 ms
Average round trip time to server: 85 ms
Estimated download bandwidth: 27200000bps
Route concurrency: 4.2406015
Download TCP forced idle: 77 %
Maximum route speed: 6990400bps


So, it seems that the Wifi is adding the jitter... Just to make sure I disabled it on the RG one more time and ran the test from a computer connected to the RG. The jitter went back down:

VoIP test statistics
--------------------
Jitter: you --> server: 10.8 ms
Jitter: server --> you: 3.6 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Estimated MOS score: 3.9

Speed test statistics
---------------------
Download speed: 6624192 bps
Upload speed: 1283512 bps
Download quality of service: 90 %
Upload quality of service: 88 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 153 ms
Average download pause: 3 ms
Minimum round trip time to server: 75 ms
Average round trip time to server: 75 ms
Estimated download bandwidth: 24000000bps
Route concurrency: 3.6230834
Download TCP forced idle: 72 %
Maximum route speed: 6990400bps


WiFi does seem like the culprit. Is there something I can do to make it play nice? Or should I begin disconnecting WiFi devices and putting them back one by one to see if a particular device is at fault?

Thanks again.
#77178 by murphy
Sun Mar 13, 2011 1:58 pm
Is your WiFi locked down so your neighbors can't use it?
Have (can) you implement QOS in the RG to give the Ooma top priority.
Those tests are not valid if something else is using the connection while they are running.
#77235 by Dandolo
Mon Mar 14, 2011 3:11 am
Yes, the WiFi is locked down. No, I can't use QoS on a U-Verse 2Wire RG. Regarding other things running... there will always be other things running. The test run on the Ooma Home port with everything else disconnected had excellent numbers. However, its when I add everything else (especially the WiFi connection) that the numbers go south.

Thanks again.
#77249 by thunderbird
Mon Mar 14, 2011 8:33 am
Dandolo wrote:Yes, the WiFi is locked down. No, I can't use QoS on a U-Verse 2Wire RG. Regarding other things running... there will always be other things running. The test run on the Ooma Home port with everything else disconnected had excellent numbers. However, its when I add everything else (especially the WiFi connection) that the numbers go south.

Thanks again.

There was only one test that had acceptable jitter. The other tests, depending on loads, was all over the place. That would make me think that the Modem is intermittent, starting to fail ,and is not handling VoIP traffic very well. The wiring coming into your home may be defective.

The easiest would be if you rent your modem/router from your Internet provicer, make them give you another one.
#77270 by Dandolo
Mon Mar 14, 2011 11:13 am
thunderbird wrote:There was only one test that had acceptable jitter. The other tests, depending on loads, was all over the place. That would make me think that the Modem is intermittent, starting to fail ,and is not handling VoIP traffic very well.


That one test was with the Ooma alone on the network and everything else turned off. I tried this again today and, sure enough, the numbers are excellent as long as Ooma can have the whole network to itself. As soon as other machines (some of which are uploading dating for cloud backups) are added back to the network the jitter increases and the choppiness becomes unbearable. I wish I knew what happened several weeks ago to suddenly make this a problem.

I'm starting to think this is just a QoS problem that I am not going to be able to fix with an ATT U-Verse RG. As far as the RG (modem/router combo) is concerned, the Ooma is just one more device with no priority. I can't rewire my house to distribute everything via the Ooma Home port. It looks like I'm being pushed, much against my will, to U-Verse's own VOIP service, which is integrated into the RG.

Thanks everyone.
#77273 by thunderbird
Mon Mar 14, 2011 11:48 am
Dandolo:
It looks like you have enough capacity, but your Internet connection just deteriorates under load (Jitter Increases, but shouldn't). It could be the wiring coming in from the street, but it's probably the Modem/Router.

The problem that you are having will show up first with VoIP, but will continue to deteriorate and spread to devices later.

I would change the Modem/Router. If you own your own Modem/Router and want to be sure, just borrow someone else's for testing. If you rent your Modem/Router, get an exchange unit.

Look at the reviews at:
http://www.amazon.com/2701HG-B-2Wire-Wi ... B001W9ASMS
#77330 by Dandolo
Tue Mar 15, 2011 6:11 am
Thanks for the suggestions. It could well be the wiring into the house, which is carried from the NID box on two slim, old POTS copper wires...

Before throwing in the towel I tried to reconfigure everything with the Telo running QoS. I found an old Netgear b/g wireless router, that still works pretty well. I then setup everything like this:

2Wire RG --> Ooma Telo --> Wireless Router

The Telo is the only thing plugged into the RG LAN ports and it is set on the RG to DMZPlus. The wireless function on the RG is completely disabled. The Telo is set for "use built in" MAC address and has the wireless router in its DMZ. I also set the upload speed to 1100, which is about what I usually get on speedtests. The router, then, provides the firewall for all of the wired and wireless connections of the LAN, which now run through it.

How does it work? Well, running the VOIP speedtest from a computer on the LAN (now downstream from the Telo, but still run through the router) still gives lots of jitter. So, no change there. However, I think that is because of its location on the network. So far the call quality on the Ooma seems to be fine! I'll give it a few weeks and see if the call quality remains good. If so, I'm good with this set up (although the wireless coverage on the Netgear is not as strong as the 2Wire). If not, then I'll just chuck the Ooma and the router and call ATT for their U-Voice. It's $15 more a month, but a lot less trouble...

Thanks again.

Who is online

Users browsing this forum: No registered users and 15 guests