sci-fi channel and a busy signal

Discussion:

(too old to reply)

Daniel Damouth

2005-07-29 00:43:39 UTC

Weird thing: for the last two hours, the sci-fi channel has been blank,
dark. All other channels are normal. When I call 695-3220, I get, of
all things, a busy signal!

Is this the beginning of an apocalypse? Is San Diego Time-Warner Cable
having a major technical difficulty? Thousands of calls from daytime
sci-fi watchers overloading their circuits?

-Dan Damouth

Scott Lindner

2005-07-29 14:27:18 UTC

Permalink

Post by Daniel Damouth
Weird thing: for the last two hours, the sci-fi channel has been blank,
dark. All other channels are normal. When I call 695-3220, I get, of
all things, a busy signal!

I've been getting a busy signal trying to have their techs come out to fix
my cable modem for weeks. I send the appropriate email address an email
about the busy signal problem and my service outtage at home and I get no
response. Their billing department is functional though.

Soon I will be asking for a full refund for the past month. There is no way
to contact them at all!

Scott

Scott Lindner

2005-07-29 19:08:27 UTC

Permalink

Wow.. something really is up today. My connection is getting dropped about
once every two minutes. This is almost completely unusable!

I gotta get through to the techs so they can come out or I'm going to make a
serious dispute over my charges for "service".

Scott

PS - You won't believe how many times I had to try to send this!

Daniel Damouth

2005-07-29 22:16:56 UTC

Permalink

Post by Scott Lindner

Post by Daniel Damouth
Weird thing: for the last two hours, the sci-fi channel has been
blank, dark. All other channels are normal. When I call
695-3220, I get, of all things, a busy signal!

I've been getting a busy signal trying to have their techs come
out to fix my cable modem for weeks. I send the appropriate email
address an email about the busy signal problem and my service
outtage at home and I get no response. Their billing department
is functional though.
Soon I will be asking for a full refund for the past month. There
is no way to contact them at all!

This is the first time in my 8 years of being a RR customer that I've
gotten a busy signal. Normally, of course, you'll get put on hold
until a person is available to take your call. Something is amiss with
them.

(The sci-fi channel came back eventually, BTW.)

-Dan Damouth

Scott Lindner

2005-07-29 22:29:17 UTC

Permalink

Post by Daniel Damouth
This is the first time in my 8 years of being a RR customer that I've
gotten a busy signal. Normally, of course, you'll get put on hold
until a person is available to take your call. Something is amiss with
them.

I know. Definitely. I reported the busy signal thing almost three weeks
ago and each time I have called since it is busy. I tried their email
address on their web page but they do not respond to it. I don't know what
to do? The one time I did reach them to schedule an appointment with the
techs they didn't show up and wasted my time. Not even a courtesy call.
Jerks.

Maybe they are striking?

Scott

v***@despammed.com

2005-08-02 00:33:02 UTC

Permalink

Has anyone tried driving over to Ware Court? Maybe someone who is close
by... like someone already in Mira Mesa could go by tomorrow and find out....
and then come back here to the group and let us all know. Something is
definitely amiss. How the heck am I going to call at the 11th hour now about my
digital phone refund? "OK...I was just...checking". 0=)

I looked up a bunch of their office numbers one time (don't ask, my lawyer
has advised me not to say anything more). I'm going to try everyone from head
manager (or fry cooker #1, as I like to call him) on down to the lowly AOL tech
support dude (a position lower than the guy who has to clean out
Porta-Potties)... if I can find where I wrote them.

Ya know... maybe... they're all trapped somewhere inside the building behind
some really high-tech door handle that they can't figure out how to operate,
they're starving, and they've had to start cannibalizing each other....

...maybe... we can send out a specialized team of spammers to track them
down for us... (On a side note... can you believe I get less spam now on my AOL
account than on my RR account?)

--
*****
A Real man holds his woman's hair while she pukes.

Scott Lindner

2005-08-03 00:02:25 UTC

Permalink

Post by v***@despammed.com
Has anyone tried driving over to Ware Court? Maybe someone who is close

I've only received busy signals every time I have called. My wife got
really upset a couple of nights ago when she spent the entire evening trying
to complete a simple order online for something that should have taken 5-10
minutes. We kept getting disconnects. The next day she was still upset and
tried the number over and over and over until it finally rang. Supposedly
the technicians will be here tonight. Of course knowing my luck, the
internet service has been working flawlessly for the past two hours.

Here's what it interesting. The last time I checked the cable modem status
page during an outtage the signals and status all looked great but the logs
had this garbage in it:

2005-08-01 03:53:42 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:42:12 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:42:09 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:42:03 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:41:56 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:41:24 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:40:13 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:40:05 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:40:01 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:39:57 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:39:25 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:38:28 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:38:19 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:38:12 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:38:01 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:37:29 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:34:13 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:34:13 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:34:08 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:34:02 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:33:56 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:33:24 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:29:57 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:29:48 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:29:41 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:29:33 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:29:29 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
2005-08-01 03:29:29 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:29:14 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:29:12 3-Critical R003.0 Init RANGING Critical Ranging Request
Retries exhausted
2005-08-01 03:29:12 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:28:35 3-Critical R003.0 Init RANGING Critical Ranging Request
Retries exhausted
2005-08-01 03:28:35 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:27:52 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:27:20 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:27:03 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:26:59 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:26:26 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:25:28 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:25:20 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:25:18 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:25:13 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:24:41 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:24:10 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:24:10 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:24:04 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:24:03 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:23:59 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:23:27 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:22:31 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:22:26 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:22:17 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:22:13 3-Critical R003.0 Init RANGING Critical Ranging Request
Retries exhausted
2005-08-01 03:22:13 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:21:43 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:38 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
2005-08-01 03:21:38 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:37 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
2005-08-01 03:21:35 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:35 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
2005-08-01 03:21:34 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:34 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
2005-08-01 03:21:31 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:30 3-Critical R003.0 Init RANGING Critical Ranging Request
Retries exhausted
2005-08-01 03:21:30 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:20:59 3-Critical R003.0 Init RANGING Critical Ranging Request
Retries exhausted
2005-08-01 03:20:59 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:20:07 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:19:35 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:19:18 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:19:14 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:18:42 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:12:50 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:12:42 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:12:37 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:12:05 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:08:43 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:08:40 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:08:32 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:08:16 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:07:43 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:06:53 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:06:53 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:06:47 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:06:44 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:06:40 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 03:06:07 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 02:58:48 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 02:58:39 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 02:58:32 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 02:58:00 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 02:57:32 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 02:57:21 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received - T4
timeout
2005-08-01 02:56:48 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 02:55:26 4-Error D004.3 ToD request sent- No Response received
2005-08-01 02:55:26 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 02:55:18 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 02:55:08 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 02:54:59 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
2005-08-01 02:54:55 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing

Obviously this is a problem but when I check right now everything is good.
Ugh... I sure hope the techs are convinced enough to give me a new cable
modem in the least.

Scott

R. J. Salvi

2005-08-03 00:16:57 UTC

Permalink

They must be working on the system because my access is dog slow right now.
--
Robert J. Salvi, Ambiance Acoustics
http://www.ambianceacoustics.com
San Diego, CA USA
(858) 485-7514

Post by Scott Lindner

Post by v***@despammed.com
Has anyone tried driving over to Ware Court? Maybe someone who is close

I've only received busy signals every time I have called. My wife got
really upset a couple of nights ago when she spent the entire evening
trying to complete a simple order online for something that should have
taken 5-10 minutes. We kept getting disconnects. The next day she was
still upset and tried the number over and over and over until it finally
rang. Supposedly the technicians will be here tonight. Of course knowing
my luck, the internet service has been working flawlessly for the past two
hours.
Here's what it interesting. The last time I checked the cable modem
status page during an outtage the signals and status all looked great but
2005-08-01 03:53:42 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:42:12 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:42:09 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:42:03 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:41:56 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:41:24 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:40:13 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:40:05 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:40:01 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:39:57 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:39:25 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:38:28 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:38:19 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:38:12 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:38:01 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:37:29 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:34:13 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:34:13 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:34:08 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:34:02 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:33:56 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:33:24 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:29:57 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:29:48 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:29:41 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:29:33 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:29:29 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2005-08-01 03:29:29 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:29:14 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:29:12 3-Critical R003.0 Init RANGING Critical Ranging
Request Retries exhausted
2005-08-01 03:29:12 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:28:35 3-Critical R003.0 Init RANGING Critical Ranging
Request Retries exhausted
2005-08-01 03:28:35 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:27:52 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:27:20 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:27:03 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:26:59 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:26:26 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:25:28 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:25:20 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:25:18 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:25:13 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:24:41 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:24:10 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:24:10 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:24:04 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:24:03 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:23:59 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:23:27 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:22:31 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:22:26 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:22:17 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:22:13 3-Critical R003.0 Init RANGING Critical Ranging
Request Retries exhausted
2005-08-01 03:22:13 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:21:43 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:38 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2005-08-01 03:21:38 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:37 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2005-08-01 03:21:35 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:35 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2005-08-01 03:21:34 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:34 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2005-08-01 03:21:31 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
2005-08-01 03:21:30 3-Critical R003.0 Init RANGING Critical Ranging
Request Retries exhausted
2005-08-01 03:21:30 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:20:59 3-Critical R003.0 Init RANGING Critical Ranging
Request Retries exhausted
2005-08-01 03:20:59 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:20:07 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:19:35 3-Critical R005.0 Started Unicast Maintenance Ranging -
No Response received - T3 time-out
2005-08-01 03:19:18 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:19:14 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:18:42 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:12:50 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:12:42 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:12:37 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:12:05 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:08:43 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:08:40 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:08:32 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:08:16 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:07:43 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:06:53 4-Error D004.3 ToD request sent- No Response received
2005-08-01 03:06:53 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 03:06:47 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 03:06:44 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 03:06:40 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 03:06:07 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 02:58:48 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 02:58:39 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 02:58:32 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 02:58:00 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 02:57:32 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 02:57:21 3-Critical R004.0 Received Response to Broadcast
Maintenance Request, But no Unicast Maintenance opportunities received -
T4 timeout
2005-08-01 02:56:48 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 02:55:26 4-Error D004.3 ToD request sent- No Response received
2005-08-01 02:55:26 3-Critical D003.0 DHCP WARNING - Non-critical field
invalid in response.
2005-08-01 02:55:18 3-Critical R005.0 Started Unicast Maintenance
Ranging - No Response received - T3 time-out
2005-08-01 02:55:08 3-Critical R002.0 No Ranging Response received - T3
time-out
2005-08-01 02:54:59 3-Critical T002.0 SYNC Timing Synchronization
failure - Failed to acquire FEC framing
2005-08-01 02:54:55 3-Critical T001.0 SYNC Timing Synchronization
failure - Failed to acquire QAM/QPSK symbol timing
Obviously this is a problem but when I check right now everything is good.
Ugh... I sure hope the techs are convinced enough to give me a new cable
modem in the least.
Scott

2005-08-07 00:05:30 UTC

Permalink

Post by Scott Lindner

I have been trying to get through since 8/2 and get either a constant
busy, or when I connect and punch in the correct buttons I go into
hold forever. I have staying on as long as 45 minutes before hanging
up. I have been trying to order more service! This is ridiculous.

I then tried to start and online chat and all I get is the message
"Thank you for choosing Road Runner Technical Chat. We have moved to
an all-new platform. Please clear your Temporary Internet Files and
press the refresh button on your browser so you can be directed to our
new page. Thanks for choosing Road Runner Technical Chat!"

What a mess.

HELLO?!? IS ANYONE HOME????????????????????????

Scott Lindner

2005-08-07 00:30:48 UTC

Permalink

Post by KS
I then tried to start and online chat and all I get is the message
"Thank you for choosing Road Runner Technical Chat. We have moved to
an all-new platform. Please clear your Temporary Internet Files and
press the refresh button on your browser so you can be directed to our
new page. Thanks for choosing Road Runner Technical Chat!"

LOL... I tried the same thing and experienced the same thing. I tried
several different browsers and computers to try to get it to work. Nothing.
I eventually got my issues resolved because Edwin had someone contact me
personally. Maybe he can do the same for you?

Scott

Darren New

2005-08-07 03:34:42 UTC

Permalink

Post by KS
HELLO?!? IS ANYONE HOME????????????????????????

Try not paying your bill. Someone will contact you promptly. ;-)

--
Darren New / San Diego, CA, USA (PST)
"You shouldn't buy ice cream. It's bad
for you and it'll make you fat. Oh,
look. A 2-for-1 sale. Get two."

Scott Lindner

2005-08-07 15:06:03 UTC

Permalink

Post by Darren New
Try not paying your bill. Someone will contact you promptly. ;-)

That won't happen. They'll terminate your service and send you a nasty gram
with a number to call to restore service. Which will result in a busy
signal.

Gotta love government granted monopolites. Without any competition you
can't simply go to another provider.

Scott

HomerHawgsnot

2005-08-09 04:15:06 UTC

Permalink

Post by Scott Lindner

Post by Darren New
Try not paying your bill. Someone will contact you promptly. ;-)

That won't happen. They'll terminate your service and send you a
nasty gram with a number to call to restore service. Which will
result in a busy signal.
Gotta love government granted monopolites. Without any competition
you can't simply go to another provider.
Scott

Sure you can. Ever hear of DirectTV and DSL?

Scott Lindner

2005-08-09 13:56:17 UTC

Permalink

Post by HomerHawgsnot
Sure you can. Ever hear of DirectTV and DSL?

I'm sure you know that those are not using the same technology. Therefore
the performance and quality of service are not even close to the same. What
you may not know is that the government is protecting TWC as a cable
provider monopoly. Why should only one company be capable of providing a
service to people when many others are capable and willing?

If you aren't aware, this very topic has been a very hot debate over the
past couple of years.

Darren New

2005-08-09 16:31:03 UTC

Permalink

Post by Scott Lindner
Why should only one company be capable of providing a
service to people when many others are capable and willing?

The same reason they protected AT&T as a long-distance carrier until
microwave towers were invented. It doesn't really make sense to have
half-a-dozen cables being run down the street for the same one-cable
service.

Which is not to say that's a *good* reason, mind.

--
Darren New / San Diego, CA, USA (PST)
"You shouldn't buy ice cream. It's bad
for you and it'll make you fat. Oh,
look. A 2-for-1 sale. Get two."

Scott Lindner

2005-08-09 17:08:00 UTC

Permalink

Post by Darren New
The same reason they protected AT&T as a long-distance carrier until
microwave towers were invented. It doesn't really make sense to have
half-a-dozen cables being run down the street for the same one-cable
service.

I'm familiar with the historical reasons for government protected
monopolies. Since that policy was put in place ages ago. Heck, it's
approaching a century almost. Technologies have changed. There are other
reasonable approaches to allow for there to be multiple providers without
having multiple sets of telephone poles and wires hanging all over the
place. Heck, how many telephone poles do you see today? Seems like we
found a solution to the original problem but haven't revisisted the original
decision that are still in law today.

Post by Darren New
Which is not to say that's a *good* reason, mind.

I completely agree. The ultimate problem here is government involvement. I
agree with the original involvement of the government. The problem is
things have changed but the policies have been changed in kind.

Scott

Scott Lindner

2005-08-09 17:09:01 UTC

Permalink

Post by Scott Lindner
I completely agree. The ultimate problem here is government involvement.

Post by Scott Lindner
agree with the original involvement of the government. The problem is
things have changed but the policies have been changed in kind.

That was supposed to be "have *not* changed in kind".

2005-08-12 00:03:26 UTC

Permalink

Post by Scott Lindner

I too sent an email. Got a response s few days later saying that
someone would call me. I am glad I did not hold my breath.

I guess all our, errr, pointing out of their current service
deficiencies had some effect - they changed their phone message to
indicate that are making changes to better serve us, to be ready for
delay in reaching someone, and to thank us for our patience.

I finally did get through. Apparently they moved the sales group phone
support to another group in another location. Many are apparently "in
training" and not providing service at this time.

Sounds to me like they got rid of the local call center and figured
they would add a few people somewhere else to handle the load. The
idea may be good, but execution wsa very very bad.

Scott Lindner

2005-08-12 00:38:11 UTC

Permalink

Post by KS
Sounds to me like they got rid of the local call center and figured
they would add a few people somewhere else to handle the load. The
idea may be good, but execution wsa very very bad.

I wonder.. India?

--doubter

2005-08-12 00:56:39 UTC

Permalink

Post by KS

Post by Scott Lindner

I too sent an email. Got a response s few days later saying that
someone would call me. I am glad I did not hold my breath.
I guess all our, errr, pointing out of their current service
deficiencies had some effect - they changed their phone message to
indicate that are making changes to better serve us, to be ready for
delay in reaching someone, and to thank us for our patience.
I finally did get through. Apparently they moved the sales group phone
support to another group in another location. Many are apparently "in
training" and not providing service at this time.
Sounds to me like they got rid of the local call center and figured
they would add a few people somewhere else to handle the load. The
idea may be good, but execution wsa very very bad.

I had to make a billing call several weeks ago. It was a fairly lengthy
call so I had a chance to chat with the rep while he was waiting for
information.

He told me that they had two call centers, one in San Diego and one in the
Palm Springs area. It used to be that both centers handled both billing
and tech support/repair. They consolidated all the billing in the Palm
Springs area and all the tech support/repair in San Diego.

That's what I was told so I can't vouch for its accuracy.

2005-08-12 05:19:41 UTC

Permalink

On Fri, 12 Aug 2005 00:56:39 GMT, --doubter

Post by --doubter

Post by KS

Post by Scott Lindner

I too sent an email. Got a response s few days later saying that
someone would call me. I am glad I did not hold my breath.
I guess all our, errr, pointing out of their current service
deficiencies had some effect - they changed their phone message to
indicate that are making changes to better serve us, to be ready for
delay in reaching someone, and to thank us for our patience.
I finally did get through. Apparently they moved the sales group phone
support to another group in another location. Many are apparently "in
training" and not providing service at this time.
Sounds to me like they got rid of the local call center and figured
they would add a few people somewhere else to handle the load. The
idea may be good, but execution wsa very very bad.

I had to make a billing call several weeks ago. It was a fairly lengthy
call so I had a chance to chat with the rep while he was waiting for
information.
He told me that they had two call centers, one in San Diego and one in the
Palm Springs area. It used to be that both centers handled both billing
and tech support/repair. They consolidated all the billing in the Palm
Springs area and all the tech support/repair in San Diego.
That's what I was told so I can't vouch for its accuracy.

I can vouch that they told me the same thing. Sales/billing call
center function moved to Palm Springs.

Scott Lindner

2005-08-12 13:23:53 UTC

Permalink

Post by --doubter
He told me that they had two call centers, one in San Diego and one in the
Palm Springs area. It used to be that both centers handled both billing
and tech support/repair. They consolidated all the billing in the Palm
Springs area and all the tech support/repair in San Diego.

That makes a lot of sense to do. When the transition is over I'm sure it'll
be better for their efficiency. Somewhere it does seem like they messed up
on the transition plan.

Continue reading on narkive:

Search results for 'sci-fi channel and a busy signal' (Questions and Answers)

replies

What Happend On Raw.........?

started 2009-03-16 22:52:59 UTC

wrestling

replies

why are there still no alien contact with our civilization?

started 2015-12-06 20:29:15 UTC

astronomy & space

666

replies