Ooma Cycling On/Off

[geo999]

I have checked the power cables and all are snuggly inserted into the receptors. Ooma boots up for varying time periods and appears to be working. Have noticed that cycling on/off seems to occur more frequently when I have my computer on and and surfing the net. Seems to happen more when I have multiple tabs open in Firefox. I have re-set my WRT54GS v. 6 Linksys wireless router QOS w the MAC address of the Ooma Telo set to port 2 on the router (where Oooma is plugged in to the router) and assigned it high priority. I also manually adjusted my upstream bandwith in the router to 800 kb/s to reflect 20% below the actual upstream bandwith of my internet connection. As I am typing this my Ooma just cycled off and is re-booting - this is a maddening problem!!

Geo999

[jacque]

I don't know enough about this to really help, but I had the same issue except that my Telo would lose the connection and couldn't reboot, it just blinked red. Turned out to be a bad wiring connection, and bypassing that fixed it. You could try swapping out your cables for new ones. (If this is a stupid suggestion, just ignore it. Like I said, I'm a novice. But that's what fixed mine.)

[sfhub]

I have checked the power cables and all are snuggly inserted into the receptors. Ooma boots up for varying time periods and appears to be working. Have noticed that cycling on/off seems to occur more frequently when I have my computer on and and surfing the net. Seems to happen more when I have multiple tabs open in Firefox. I have re-set my WRT54GS v. 6 Linksys wireless router QOS w the MAC address of the Ooma Telo set to port 2 on the router (where Oooma is plugged in to the router) and assigned it high priority. I also manually adjusted my upstream bandwith in the router to 800 kb/s to reflect 20% below the actual upstream bandwith of my internet connection. As I am typing this my Ooma just cycled off and is re-booting - this is a maddening problem!!

From experience I would say if your Ooma turns blue, then sometime later turns red and reboots, 90% chance there is some network issue between the Ooma and the servers (could be cables, router, modem, ISP, etc.).

10% chance it is the Ooma hardware, which isn't 0%, but it wouldn't be the first place I looked.

How long does it usually take to turn red? Can you run an experiment and connect Ooma to your modem with nothing else connected overnight when you don't need the connection. See if it avoids going red.

[geo999]

Will give it a try tonight and let you know.

Would the VOIP Broadband Test be of any help? Here are 3 tests I ran.

VoIP test statistics
--------------------
Test 1 - PC (Dell Dimension 8100)-Router(wrt54gs v. 6.0)- Ooma Telo

Jitter: you --> server: 16.8 ms
Jitter: server --> you: 54.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.6

Speed test statistics
---------------------
Download speed: 4556592 bps
Upload speed: 299544 bps
Download quality of service: 72 %
Upload quality of service: 23 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 481 ms
Average download pause: 11 ms
Minimum round trip time to server: 102 ms
Average round trip time to server: 103 ms
Estimated download bandwidth: 27200000bps
Route concurrency: 5.9693737

Test 2 - PC (Dell Dimension 8100)-Router(wrt54gs v. 6.0)- Ooma Telo
VoIP test statistics
--------------------
Jitter: you --> server: 10.5 ms
Jitter: server --> you: 50.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: 3.7

Speed test statistics
---------------------
Download speed: 5554776 bps
Upload speed: 209488 bps
Download quality of service: 83 %
Upload quality of service: 0 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 350 ms
Average download pause: 8 ms
Minimum round trip time to server: 102 ms
Average round trip time to server: 103 ms
Estimated download bandwidth: 29600000bps
Route concurrency: 5.3287477
Download TCP forced idle: 83 %
Maximum route speed: --
Download TCP forced idle: 81 %
Maximum route speed: 5140000bps

Test 3 - PC (Dell Dimension 8100)-Router(wrt54gs v. 6.0)- Ooma Telo
VoIP test statistics
--------------------
Jitter: you --> server: 8.7 ms
Jitter: server --> you: 56.2 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.6

Speed test statistics
---------------------
Download speed: 5608544 bps
Upload speed: 320056 bps
Download quality of service: 86 %
Upload quality of service: 24 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 338 ms
Average download pause: 8 ms
Minimum round trip time to server: 102 ms
Average round trip time to server: 103 ms
Estimated download bandwidth: 27200000bps
Route concurrency: 4.8497434
Download TCP forced idle: 81 %
Maximum route speed: --

[sfhub]

IMO there is something wrong with your connection. Those latency #s are very high and quite variable.

Try connecting your PC directly to the cable modem (and rebooting the cable modem so it resets the MAC address it is attached to) and rerun the voip test.

[geo999]

Here are two VOIP Tests w PC direct to Cable Modem - (No Ooma or Router)

PC w Cable Modem (no router or Ooma)

Test 1
VoIP test statistics
--------------------
Jitter: you --> server: 3.0 ms
Jitter: server --> you: 64.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: 3.6

Speed test statistics
---------------------
Download speed: 4446552 bps
Upload speed: 1070680 bps
Download quality of service: 53 %
Upload quality of service: 96 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 424 ms
Average download pause: 11 ms
Minimum round trip time to server: 103 ms
Average round trip time to server: 167 ms
Estimated download bandwidth: 20000000bps
Route concurrency: 4.497867
Download TCP forced idle: 84 %
Maximum route speed: 5090096bps

Test 2
VoIP test statistics
--------------------
Jitter: you --> server: 35.9 ms
Jitter: server --> you: 2107.2 ms
Packet loss: you --> server: 23.2 %
Packet loss: server --> you: 54.6 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Estimated MOS score: 2.9

Speed test statistics
---------------------
Download speed: 2408184 bps
Upload speed: 796056 bps
Download quality of service: 0 %
Upload quality of service: 31 %
Download test type: socket
Upload test type: socket
Maximum TCP delay: 1018 ms
Average download pause: 20 ms
Minimum round trip time to server: 100 ms
Average round trip time to server: 106 ms
Estimated download bandwidth: 19200000bps
Route concurrency: 7.9728127
Download TCP forced idle: 74 %
Maximum route speed: 5242800bps

Test 2
Flunked QOS UP/DOWN PACKET LOSS

[murphy]

You have a serious problem with your internet connection.

[geo999]

My thoughts as well. There is a company called VisualWare selling some products to help diagnose issues like this http://www.myconnectionpc.com/index.html. You can download trial software for 15 days

MyConnection PC
* Test your Internet connection speeds and quality
* See the level of VoIP call quality your connection provides

VisualRoute®
* Network route testing pinpoints where problems occur
* See the geographical path of your connection

Collecting lots of data before I call my ISP. I don't want them to tell me that it isn't their problem. From what I can gather ISP's trust the information that the testing software from this company provides. The take home for me if this type of cycling issue occurs would be to test with the cable modem and PC only. Had I done this at the beginning I would have called my ISP a lot sooner. Live and learn!! Thanks to all who have tried to help. This is the best customer forum I have ever been on.

geo999

[sfhub]

Just keep in mind, don't assume the problem is on Charter's side. All you know is somewhere between your PC and the voip test server there is a problem. That could be your PC ethernet card, the ethernet cable, the cable modem, the coax cable, the splitter, any amplifiers you might use, the neighborhood HFC transition point, the ISP, something along the router to the servers, etc.

[geo999]

Will switch out any lines that I can and re-test. Am going to collect a lot of data via the software from VisualWare for Charter and have them come out to check everything. The cable modem is brand new from Charter so that is not likely the issue. Will hopefully have a resolution soon. At least I feel that we are isolating the problem and the Ooma Telo is looking less and less like the culprit.

geo999