Need extra help installing your Ooma Hub or Telo system? Let us know.
#5122 by blphu
Sat Mar 21, 2009 8:11 am
lohertz wrote:Could you be a little more specific. What's actually happening, i.e. downloading something and it stops when a call is coming in?


That's exactly what happens.

I don't have such problem if I make outgoing calls.
#5123 by blphu
Sat Mar 21, 2009 8:13 am
WayneDsr wrote:We need to know more....

I'm going to assume you have dsl, correct?
And do you have a Scout connected?
What setup are you using?
-->modem -->ooma hub-->router
or
-->modem-->router-->ooma hub

Wayne


I have cable modem and my current setup is: modem -->hub-->router.
#5126 by lohertz
Sat Mar 21, 2009 8:28 am
Is the QoS running on your OOMA? With your current configuration go to setup.ooma.com to look at your settings.

Also, go to the link below and run the test. When completed, go to the advance tab and click on the hyperlink with that says view text. Click that and copy the results and paste in a reply. That will help others see where the problem may lie.
#5128 by WayneDsr
Sat Mar 21, 2009 8:40 am
I can't understand why it would only effect incoming calls vs outgoing calls. Once the call is established, should be the same.......

Are you using ooma integrated WITH a landline, or just ooma by itself.

Wayne
#5133 by blphu
Sat Mar 21, 2009 9:40 am
Below is the results of my test:


Speed test statistics
---------------------
Download speed: 6370352 bps
Upload speed: 367512 bps
Quality of service: 84 %
Download test type: socket
Upload test type: socket
Maximum download pause: 66 ms
Average download pause: 5 ms
Minimum round trip time to server: 70 ms
Average round trip time to server: 91 ms

VoIP test statistics
--------------------
Jitter: you --> server: 8.6 ms
Jitter: server --> you: 6.1 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Number of supported VoIP lines: 6
Estimated MOS score: 3.9

I just tried with both QoS enabled and disabled and it's doing the same thing.
#5145 by lohertz
Sat Mar 21, 2009 11:36 am
At what speed was the QoS applied at?

It appears you have a cable connection 6Mbps down and 384Kbps up.

If the QoS is wide open, its as useless as if it wasn't on. What could be happening is when the OOMA server connects to your hub, its hogging all the bandwith coming down the pipe, as if QoS isn't on (or wide open). This in turn would/could make other connections to a crawl, because, by default, the ooma is gonna take priority over all other connections. However, when your hub initiates the connection to the server, the QoS limits the connection UPspeed to 384Kbps. This is a drop in the bucket compared to the available 6 Meg pipe down.

This is part of the reason why I prefer the OOMA after the router, and use a more robust QoS in the router and set priorities there.

Try moving the ooma behind the router and re-running (Everything, incoming, outgoing calls, and diagnostics.) Also, what type of router do you have?
#5710 by blphu
Wed Apr 01, 2009 7:56 am
lohertz wrote:At what speed was the QoS applied at?

It appears you have a cable connection 6Mbps down and 384Kbps up.

If the QoS is wide open, its as useless as if it wasn't on. What could be happening is when the OOMA server connects to your hub, its hogging all the bandwith coming down the pipe, as if QoS isn't on (or wide open). This in turn would/could make other connections to a crawl, because, by default, the ooma is gonna take priority over all other connections. However, when your hub initiates the connection to the server, the QoS limits the connection UPspeed to 384Kbps. This is a drop in the bucket compared to the available 6 Meg pipe down.

This is part of the reason why I prefer the OOMA after the router, and use a more robust QoS in the router and set priorities there.

Try moving the ooma behind the router and re-running (Everything, incoming, outgoing calls, and diagnostics.) Also, what type of router do you have?


I tried connecting the hub behind my Linksys router (with nothing plugged into Home on the hub) and the problem still persists.

Who is online

Users browsing this forum: No registered users and 12 guests