His second test was run while a call was in progress, which is not how the test was intended, I don't think - although it could indicate how well his connection could support two simultaneous calls I suppose.niknak wrote:TCP delay is 571ms - in order for VOIP to work well this number should not be more than 100ms
Also, in your first test the upload QOS is 22% even before making a call - this is why you are having call quality problems
You will need to do some work to investigate these issues and tweak your system. These types of issues are most likely related to your ISP or your internal network settings - not ooma
I believe we're seeing the affects of the hub's built in QoS to give the Ooma calls priority over everything else. Remember, that test is run on a PC and the Ooma Hub only prioritizes traffic that it is generating. IF, these users were using their own routers to support QoS then we'd need to know if this VOIP test is truly simulating a VOIP call, or if it's just mimicking the amount of traffic, but not actually using the same protocols and compression algorithms.Groundhound wrote:His second test was run while a call was in progress, which is not how the test was intended, I don't think - although it could indicate how well his connection could support two simultaneous calls I suppose.
It's hard to say but it's always a good idea to check your modem status/logs to see what it's doing when you have suspicious performance.reserve wrote:Scott, how would I long into my modem. I am running through a simple Motorola surfboard modem. I know how to log onto the router, but not the modem. Could this be an issue with Cox? Thanks again for all your help.
I believe your modem's IP address is 192.168.100.1. Try this link and see if it brings up the status page. http://192.168.100.1
Ok, problem solver, that sounds easy! I don't know exactly how to place it in the router's DMZ so if you can explain that to me I would really appreciate it. Ooma is already behind the router, so I guess all I need to do is put it in the DMZ, so if you could share this trick with me it sounds like I shouldn't have any more issues.atici wrote:Why are you still going through this? All you need to do is connect ooma behind the router, place it in router's DMZ. Voila! Problem solved.
You need to log into your router and look for the DMZ "tab" or "section" (probably an advanced setting), then type in the ooma's IP address... I don't know exactly how to place it in the router's DMZ so if you can explain that to me I would really appreciate it..
What model router do you use? Does your router have packet prioritization (i.e. ability to classify/prioritize outgoing packets) ? If you do, it'd be great if you prioritize ooma outgoing packets. Basically the whole point of ooma being the first in chain after the modem is to ensure this is done. However when ooma is after the modem its throttling is extremely conservative. When ooma is behind the router, and your computers are uploading data, your ooma may not get as much upload bandwidth unless its packets are sent out first.