[Asterisk-Users] HDLC Bad FCS / HDLC Abort

Eric Wieling eric at fnords.org
Sat Feb 19 11:49:32 MST 2005


Yes.  There are lots of messages in the mailing list archives 
regarding this problem, some of them even include things to try.  You 
didn't see these messages when you searched the mailing list archives?

Alex G Robertson wrote:

> Some news.....
> 
> It is not caused by transmission lines, conectors or anything like that.
> 
> The telco tecnician just came here and analyzed the circuit and he got 
> no erros!
> 
> 
> He sugested me to loop my PRI port in the balum attached in my asterisk 
> box. And.... Surprise...
> 
> I got the same errors!
> The error is on my hardware/software.
> 
> []s
> Alex Robertson
> 
> Alex G Robertson wrote:
> 
>> Hi everybody,
>>
>> I just installed asterisk, but this NOTICE dont stop appearing on my 
>> log file;;
>>
>>
>> Feb 17 18:30:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:29:42 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary 
>> D-channel of span 4
>> Feb 17 18:29:41 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary 
>> D-channel of span 4
>> Feb 17 18:29:41 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:27:11 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary 
>> D-channel of span 4
>> Feb 17 18:26:51 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:25:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:24:41 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary 
>> D-channel of span 4
>> Feb 17 18:22:21 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary 
>> D-channel of span 4
>> Feb 17 18:21:16 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary 
>> D-channel of span 4
>> Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:13 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary 
>> D-channel of span 4
>> Feb 17 18:21:12 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>> Feb 17 18:21:01 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
>> Primary D-channel of span 4
>>
>>
>> And from time to time this is happening....
>>
>>     -- B-channel 0/1 successfully restarted on span 4
>>     -- B-channel 0/2 successfully restarted on span 4
>>     -- B-channel 0/3 successfully restarted on span 4
>>     -- B-channel 0/4 successfully restarted on span 4
>>     [...]
>>     -- B-channel 0/29 successfully restarted on span 4
>>     -- B-channel 0/30 successfully restarted on span 4
>>     -- B-channel 0/31 successfully restarted on span 4
>>
>> And the conversation stops.
>>
>>
>> Telco, with a traffic analyzer, says that the clock is sliding.
>>
>> Does anybody knows what can it be? Hardware, software, transmission 
>> (conectors) etc.... ?
>>
>>
>> Thanks in advance.
> 
> 




More information about the asterisk-users mailing list