Incoming voice is garbled, they can hear me just fine...

[motleyruse]

From the speed test on whichvoip.com:


VoIP test statistics
--------------------
Jitter: you --> server: 0.5 ms
Jitter: server --> you: 4.3 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: 15237040 bps
Upload speed: 6684568 bps
Download quality of service: 97 %
Upload quality of service: 23 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 36 ms
Average download pause: 1 ms
Minimum round trip time to server: 40 ms
Average round trip time to server: 41 ms
Estimated download bandwidth: 24000000bps
Route concurrency: 1.5751091
Download TCP forced idle: 48 %
Maximum route speed: --

I'm highly surprised that I'm having bad incoming call quality. Any ideas? I up'ed the reserved bandwidth to 215 kb/s from 130 kb/s(default).

It's really frustrating to spend hundreds of dollars on equipment that doesn't seem to function well.

[bw1]

From the speed test on whichvoip.com:

Jitter: server --> you: 4.3 ms

Upload quality of service: 23 %

Your jitter could have an affect, but it seems to be within an acceptable range.

Your Upload QOS doesn't look good, but that should only affect your outgoing, not the incoming.

How do you have the hub set up - before or after your router?

I'm highly surprised that I'm having bad incoming call quality. Any ideas? I up'ed the reserved bandwidth to 215 kb/s from 130 kb/s(default).

I don't think that will have any affect. Have you changed your upstream or downstream QOS from the default?

It's really frustrating to spend hundreds of dollars on equipment that doesn't seem to function well.

Most call quality issues are caused by the user's internet connection or network configuration, which is out of Ooma's control.

Most of us have excellent call quality, in many cases, "better" than a landline.

Many here have had issues that they've been able to resolve through trial and error and posting here.

Do you have cable ISP or DSL?

[motleyruse]

How do you have the hub set up - before or after your router?

I have it setup as specified in the Ooma manual, before the wireless router.

Have you changed your upstream or downstream QOS from the default?

No

Do you have cable ISP or DSL?

Cable.

[bw1]

How do you have the hub set up - before or after your router?

I have it setup as specified in the Ooma manual, before the wireless router.

Have you changed your upstream or downstream QOS from the default?

No

Do you have cable ISP or DSL?

Cable.

The first thing you can try is to run several tests to get an idea of your average upload and download bandwidth and set the upstream and downstream QOS to an average of those values or you can use the cable ISP's advertised speeds. With the default value of 384 in the upstream QOS, you are restricting the available bandwidth.

You'll need to divide the value from the tests by 1000, because the Ooma setup is looking for Kbps.

With these values:
Download speed: 15237040 bps
Upload speed: 6684568 bps

You would enter 15000 in downstream QOS and 6500 in upstream QOS.

After updating, make some calls to test.

With that much bandwidth, it shouldn't be an issue, so the problem is probably with jitter or the QOS your internet connection is experiencing. With cable those values can change drastically at different times of the day since you share bandwidth with your neighbors.

Ooma uses a VPN connection to their servers and buffers the data stream to reduce the affects of jitter but there's only so much that is in their control.

You may need to contact your cable ISP.

The other thing you could try is to put your Ooma hub after the router. Some here have had better results with that.