- Anzeige -

Telefongespräche brechen nach wenigen Minuten ab

In vielen Netzen von Unitymedia sind Internet und Telefonie bereits verfügbar.
Wichtig:
  • Kunden aus Hessen und Nordrhein-Westfalen können über die Rufnummer 0221 / 466 191 00 Hilfe bei allen Problemen in Anspruch nehmen.
  • Kunden aus Baden-Württemberg können über die Rufnummer 0711 / 54 888 150 Hilfe bei allen Problemen in Anspruch nehmen.

Telefongespräche brechen nach wenigen Minuten ab

Beitragvon RisinG Sun » 10.10.2008, 08:31

Hallo zusammen...

trotz vieler Kritik habe ich mich für UM entschlossen und habe mir das 3Play Paket zugelegt. Man muss ja auch sagen, dass die Preise nicht zu topen sind. Leider musste ich jedoch feststellen, dass es Probleme mit meiner Telefonleitung gibt. Diese bricht mal nach 2 Minuten, mal nach 10 Minuten und manchmal nach einer knappen halben Stunde ab. Da ich mich nicht wirklich mit der Materie auskenne wollte ich euch mal fragen ob ihr mir nicht zu helfen wisst. Ich habe es noch unterlassen, den Kundendienst zu benachrichtigen, da hier geschrieben wurde, dass dieser doch meist inkompetent ist.

Noch ein paar Infos: Ich habe das Scientific Atlanta EPC 2203 als Modem und dazu ein Netgear WLAN Router. Jedesmal wenn die Telefonleitung abbricht, bricht auch die Internetleitung zusammen. Daraufhin blinken alle Leuchten des Modems wild vor sich her und versuchen, teils mit Erfolg,teils mit weniger Erfolg eine neue Verbindung herzustellen. Manchmal dauert das ganze wenige Sekunden, manchmal aber auch einige Minuten.

Das die Internetleitung von sich abbricht habe ich noch nicht mitbekommen. Die Werte die ich aus dem Modem gelesen habe, waren meiner Meinung nach alle in Ordnung. Stell sie jedoch trotzdem nochmals rein vielleicht fällt ja jemandem eine Anomalie auf.


About Your Modem
This page provides the basic information about your cable modem.

System
The data shown in the table below provides information about the system of your cable modem.

Name
SA EPC2203

Modem Serial Number
215780151

Cable Modem MAC Address
00:1e:6b:15:74:8b

Hardware Version
1.1

Receive Power Level
-0.4 dBmV

Transmit Power Level
41.7 dBmV

Cable Modem Status
Operational

Vendor
Scientific Atlanta - A Cisco Company

Boot Revision
2.1.6lR6

Software File Name and Revisions
The data shown in the table below provides information about the firmware of your cable modem.

Firmware Name
epc2203-P10-5-v202r1262-080402c.bin

Software Revision
epc2203-P10-5-v202r1262-080402c


Signal
This page provides important information about the status and quality of the communications between your cable modem and the cable modem network.

Downstream Channel
The data shown in the table below provides information about the signal coming from the network to your cable modem.

Downstream Status
Operational

Channel ID
1

Downstream Frequency
594000000 Hz

Modulation
256QAM

Bit Rate
42884296 bits/sec

Power Level
-0.5 dBmV

Signal to Noise Ratio
36.8 dBmV

Upstream Channel
The data shown in the table below provides information about the signal being transmitted to the network from your cable modem.

Upstream Status
Operational

Channel ID
2

Upstream Frequency
48000000 Hz

Modulation
64QAM

Symbol Rate
2560 Ksym/sec

Power Level
41.7 dBmV


was mich jedoch interessiert ob diese Logangaben "normal" sind:

DOCSIS (CM) Events
The data shown in the table below provides information about the Docsis events of your cable modem.
Time ID Level Description
Fri Oct 10 06:23:07 2008 69020600 Error (4) Improper Configuration File CVC Format
Fri Oct 10 06:04:16 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Fri Oct 10 06:04:10 2008 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Fri Oct 10 05:32:18 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Fri Oct 10 05:32:12 2008 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Fri Oct 10 01:18:58 2008 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Fri Oct 10 01:18:58 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Fri Oct 10 01:18:16 2008 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Fri Oct 10 01:18:16 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Fri Oct 10 01:17:41 2008 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Fri Oct 10 01:17:41 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Fri Oct 10 01:16:58 2008 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Fri Oct 10 01:16:58 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Fri Oct 10 01:15:16 2008 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Fri Oct 10 01:19:01 2008 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Fri Oct 10 01:13:34 2008 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Fri Oct 10 01:13:34 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Fri Oct 10 01:13:04 2008 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Fri Oct 10 01:13:04 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Fri Oct 10 01:12:14 2008 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Fri Oct 10 01:11:44 2008 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Oct 10 01:11:28 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Fri Oct 10 01:11:23 2008 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Thu Oct 09 22:20:59 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Thu Oct 09 22:20:53 2008 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Thu Oct 09 20:33:48 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Thu Oct 09 20:33:44 2008 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Thu Oct 09 17:48:37 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Thu Oct 09 17:48:32 2008 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Thu Oct 09 17:41:43 2008 82000200 Critical (3) No Ranging Response received - T3 time-out
Thu Oct 09 17:41:38 2008 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Thu Oct 09 17:31:35 2008 82000200 Critical (3) No Ranging Response received - T3 time-out

PACKETCABLE (MTA) Events
The data shown in the table below provides information about the PacketCable events of your cable modem.
Time ID Level Description MAC Address Endpoint Name
10/10/2008 06:23:19 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 06:23:16 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 06:07:23 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 06:04:37 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 06:04:35 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 06:04:10 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 05:32:40 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 05:32:39 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 05:32:12 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 01:19:36 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 01:19:29 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 01:12:14 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/10/2008 01:11:23 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 22:21:26 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 22:21:22 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 22:20:53 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 20:34:18 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 20:34:10 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 20:33:44 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 18:56:27 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 18:31:03 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 18:30:58 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:48:32 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:42:34 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:42:19 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:42:14 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:41:38 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:32:00 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:31:59 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:31:30 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:30:06 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:30:01 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 17:29:31 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:43:37 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:43:33 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:43:01 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:27:34 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:21:23 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:21:21 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:19:53 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:12:19 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:02:33 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 16:02:26 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 15:52:15 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 15:44:36 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 15:44:28 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 15:39:52 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 15:32:48 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 15:32:46 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 15:32:19 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 14:25:06 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 14:25:06 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 14:24:40 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 14:19:18 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 14:19:15 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 14:18:48 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 13:20:22 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 13:20:22 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 13:19:55 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:51:03 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:51:01 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:50:32 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:49:37 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:49:37 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:49:11 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:38:13 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:38:12 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:37:45 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:09:32 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:09:31 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:08:59 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:02:01 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:02:00 54 Information (5) INFO: Endpoint is not connected to CMS 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 12:01:27 52 Critical(1) Loss of RF 00-1E-6B-15-74-8D AALN/1:***************************************
10/09/2008 11:40:17 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-1E-6B-15-74-8D



dann warte ich mal auf einpaar schlaue Köpfchen die mir weiterhelfen können... :kafffee:

KostA
RisinG Sun
Kabelneuling
 
Beiträge: 1
Registriert: 10.10.2008, 08:12

Re: Telefongespräche brechen nach wenigen Minuten ab

Beitragvon Moses » 10.10.2008, 09:49

RisinG Sun hat geschrieben:Ich habe es noch unterlassen, den Kundendienst zu benachrichtigen, da hier geschrieben wurde, dass dieser doch meist inkompetent ist.


Auch wenn diese Aussage wahr sein sollte, sollte dich das bei solchen Problemen nicht davon abhalten eine Störung zu melden. Wenn die Lämpchen am Modem plötzlich anfangen zu blinken, ist entweder etwas mit dem Modem oder mit deinem Kabelanschluss nicht in Ordnung und da muss ein Techniker vorbei kommen. Den bekommst du nur über die Störungshotline ( 01805 660 100 ). Jede Minute, die du noch abwartest zögert quasi die Lösung des Problems hinaus. ;)

Wenn man von einer bekannten Großstörung betroffen ist, dann macht es tatsächlich meistens keinen Sinn bei der Hotline anzurufen...
Moses
Moderator
 
Beiträge: 7262
Registriert: 06.03.2007, 16:49
Wohnort: Bonn


Zurück zu Internet und Telefon über das TV-Kabelnetz

Wer ist online?

Mitglieder in diesem Forum: Bing [Bot], MSNbot Media und 15 Gäste