VIEW TOPIC

I have the top tier RoadRunner service. My router is the TrendNet TEW-633GR. My Ooma hub is between the cable modem and router.

Here is my benchmark when not in a call...


Here is my benchmark when in a call...


Ouch! I don't remember this always being the case. BTW, my download speed is typically closer to 30Mbps. Scored low today. Not sure why.

What gives? I thought the CODEC sipped bandwidth.

What QoS settings in the hub do you have?

What QoS settings in the hub do you have?

Good question. I don't know. I would think the default. How can I sign in? Remember, it's between the modem and router, not behind the router.

... also, is it the Telo you have or the older hub?

try rebooting the router and the ooma?

Good question. I don't know. I would think the default. How can I sign in? Remember, it's between the modem and router, not behind the router.

http://setup.ooma.com

The default iLBC codec uses about 30kbs each direction, when forcing g.711 it's around 70kbs each direction but I do not believe this is the issue. The issue I believe is that you are asking the ooma device to pass high bandwidth in both directions AND process packets as well as compressing and decompressing with codecs during a phone call. I just can't imagine a hub or telo having that much processing power but I could be underestimating them.

I can only suggest hooking it behind the router.

Okay. Some additional information...

This is the old hub. The modem, hub, and router and have been power cycled a few times.

The QoS is set to 384 upstream and 0 downstream. I don't think 0 is right. And if 384 is correct, still doesn't explain the dramatic drop in upstream. Not sure if either explains the insanely high ping.

What are the recommended values?

https://www.ooma.com/support/knowledgeba ... ty-service

I forgot to mention my reserved bandwidth is 130Kbps. If I reading this right, then an active Ooma call should never exceed 130Kbps.

https://www.ooma.com/support/knowledgebase/configuring-quality-service

That is interesting information, but I am still unclear how the default up and downstream values are bad.

I went ahead and changed downstream to 2048Kbps just to test and see. This is what happened.