Posted: Mon Feb 21, 2005 1:02 pm Post subject: [ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort
Eric Wieling wrote:
> 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?
>
Yes, I've read then.
They say it can be caused by interruptions.
I tried asterisk on kernels 2.4.29 and on 2.6.10 and I got the same errors.
At this moment, I am running the latest version available on cvs on kernel
2.6.10 and I took off all other cards (4 FXO - Intel Ambient 3200) and still
get the errors.
The TE405P card is not loosing interruptions any more...
73 TE4/0/4/1 Clear (In use)
74 TE4/0/4/2 Clear (In use)
[...]
I contacted Digium Instalation Support and I am waiting for their response.
[]s
Alex Robertson
Quote:
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.
Posted: Mon Feb 21, 2005 1:38 pm Post subject: [ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort
Alex G Robertson wrote:
Quote:
Eric Wieling wrote:
> 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?
>
Yes, I've read then.
They say it can be caused by interruptions.
Did you confirm you are not running graphics? (X, frame buffer, etc).
Did you confirm you have unmasked IDE interrupts (-u1 to haparm)?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum