Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Internet Connection is Unstable
For the past several months my internet connection has been dropping many times per day. The duration is short, maybe a minute or so. Since I work from home and use a micro cell for a better Cell signal, when the internet drops, so does my phone call.
I COX tech came to the house yesterday and changed out a few connections even though the signal strength was fine. He also said something was "BROKEN" at the street access. The street guys came this am. Nothing has changed. I accessed the modem event log which revealed the following. I NEED reliable service to do my job and COX HSI, is failing.
| Wed Apr 09 14:30:59 2014 | Error (4) | Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 14:30:59 2014 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 14:30:58 2014 | Error (4) | Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 08:24:22 2014 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 08:24:08 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 08:24:07 2014 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 08:24:06 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 08:23:52 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 08:23:52 2014 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 08:23:37 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 08:23:37 2014 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Wed Apr 09 08:22:20 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.1;CM-VER=3.0; |
| Tue Apr 08 10:10:13 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:10:09 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:10:09 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:10:06 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:10:05 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:10:03 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:10:02 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:10:00 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:09:59 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:09:57 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:09:56 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Apr 08 10:09:55 2014 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=20:e5:2a:b1:bd:dc;CMTS-MAC=64:00:f1:40:00:74;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Notice (6) | WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT |
ChrisL
Former Moderator
•
0
0
Dave_P
New Contributor
•
I'm using an ATT supplied Micro Cell because my cell signal is weak without it. It connects to my router via a cable and provides excellent cell signal strength. When my COX HSI is interrupted, the call that I'm on with my cell phone is dropped. I'll say it again, the instability in my COX HSI services is to the point of being unusable. I rely on it too heavily for my business. A tech has come to my house which was a joke and he sent other techs to fix something is the junction box in the street. Another joke. Century Link may be my only option. It won't have the bandwidth, but at least I won't be continuously losing my connection.
0
0
Dave_P
New Contributor
•
Thanks for the response Tiffany. Since the problem had not been resolved, I called tech support. We went through the WiFi channel procedure and I downloaded WiFi analyzer for my Android phone. Changing the channel to the one suggested by the app had no impact. This morning I watched to shows on NetFlix totaling maybe 80-90 minutes. My internet connection dropped at least 5 times. This forces me to restart whatever I was watching. This is really getting frustrating.
0
0