DLeese at LStelcom.com
2010-May-31 12:46 UTC
[asterisk-users] Suddenly "HDLC Bad FCS (8)" errors on ISDN-PRI, changed nothing
Hi fellow asterisk users,
I am running Asterisk 1.4.29 with an Digium TE121 card (wcte12xp kernel
module) an approx. 100 snom320. The whole installation is running
without issues since 5 months.
Without having changed anything on the asterisk server for at least 2
months, i noticed "clicking sounds" at external calls over the PRI.
Asterisk constantly throws the following messages:
...
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
[May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got
event: HDLC Bad FCS (8) on Primary D-channel of span 1
...
At first (last week) there where only a few of these messages per
minute, but today their intervall inceased dramatically. The
"clicking"
also increased.
Can this be caused by problems of the telco (Deutsche Telekom)? If so,
could anybody please provide some additional information about it? Does
anybody have any experiences with this issue?
For sake of completeness i have included the relevant .conf files, but i
highly doubt it's a configuration issue:
---
cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
CPU6 CPU7
0: 63 0 0 0 0 0
0 1 IO-APIC-edge timer
1: 0 0 0 0 0 0
0 8 IO-APIC-edge i8042
6: 0 0 0 0 0 0
0 2 IO-APIC-edge floppy
7: 1 0 0 0 0 0
0 0 IO-APIC-edge
8: 0 0 0 0 0 0
0 19 IO-APIC-edge rtc0
9: 0 0 0 0 0 0
0 0 IO-APIC-fasteoi acpi
12: 0 0 0 0 0 0
0 105 IO-APIC-edge i8042
14: 0 0 0 0 0 0
0 76 IO-APIC-edge ide0
18: 0 0 1 2922 0 150
648815 506811268 IO-APIC-fasteoi wcte12xp0
19: 0 0 0 153 0 7
4563 285489 IO-APIC-fasteoi arcmsr
20: 0 0 0 0 0 0
0 0 IO-APIC-fasteoi sata_nv
21: 0 0 0 0 0 0
0 0 IO-APIC-fasteoi sata_nv
22: 0 0 0 0 0 0
0 0 IO-APIC-fasteoi ohci_hcd:usb2
23: 0 0 0 0 0 0
0 1 IO-APIC-fasteoi ehci_hcd:usb1, sata_nv
219: 0 0 0 86 0 371
2576954 97457996 PCI-MSI-edge eth0
220: 0 0 0 0 0 0
0 0 PCI-MSI-edge aerdrv
221: 0 0 0 0 0 0
0 0 PCI-MSI-edge aerdrv
222: 0 0 0 0 0 0
0 0 PCI-MSI-edge aerdrv
223: 0 0 0 0 0 0
0 0 PCI-MSI-edge aerdrv
NMI: 0 0 0 0 0 0
0 0 Non-maskable interrupts
LOC: 11726262 1551452 1834726 1534833 2262834 1499777
4073035 39704316 Local timer interrupts
RES: 858017 180201 132730 205234 129387 128549
688861 667641 Rescheduling interrupts
CAL: 166 206 221 214 208 213
187 126 function call interrupts
TLB: 13298 4915 2847 3680 10646 1067
14320 9156 TLB shootdowns
TRM: 0 0 0 0 0 0
0 0 Thermal event interrupts
SPU: 0 0 0 0 0 0
0 0 Spurious interrupts
ERR: 1
MIS: 0
---
cat /etc/dahdi/system.conf:
# Autogenerated by /usr/sbin/dahdi_genconf on Wed Nov 4 13:37:30 2009
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCT1/0 "Wildcard TE121 Card 0" (MASTER)
span=1,1,0,ccs,hdb3,crc4
# termtype: te
bchan=1-15,17-31
dchan=16
echocanceller=mg2,1-15,17-31
# echocanceller=no
# Global data
loadzone = de
defaultzone = de
---
cat /etc/asterisk/dahdi-channels.conf:
; Autogenerated by /usr/sbin/dahdi_genconf on Wed Nov 4 13:37:30 2009
; If you edit this file and execute /usr/sbin/dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is
intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global
settings
;
; Span 1: WCT1/0 "Wildcard TE121 Card 0" (MASTER)
immediate=no
callprogess=yes
;busydetect=yes
busydetect=no
context=from-pstn
switchtype=euroisdn
signalling=pri_cpe
group=0
channel => 1-15,17-31
---
Regards
Daniel Leese
Gareth Blades
2010-Jun-01 08:44 UTC
[asterisk-users] Suddenly "HDLC Bad FCS (8)" errors on ISDN-PRI, changed nothing
DLeese at LStelcom.com wrote:> Hi fellow asterisk users, > > I am running Asterisk 1.4.29 with an Digium TE121 card (wcte12xp kernel > module) an approx. 100 snom320. The whole installation is running > without issues since 5 months. > > Without having changed anything on the asterisk server for at least 2 > months, i noticed "clicking sounds" at external calls over the PRI. > Asterisk constantly throws the following messages: > > ... > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got > event: HDLC Bad FCS (8) on Primary D-channel of span 1 > ... > > At first (last week) there where only a few of these messages per > minute, but today their intervall inceased dramatically. The "clicking" > also increased. > > Can this be caused by problems of the telco (Deutsche Telekom)? If so, > could anybody please provide some additional information about it? Does > anybody have any experiences with this issue? > > > Regards > > Daniel Leese >FCS = Frame Check Sequence and is basically a checksum. You probably have crc4 or similar specified on the span line in the configuration file. Sometimes there can be an incompatability with the telco which can cause this error in which case you can simple disable it. You might want to try disabling it by removing that parameter from the span line but I suspect there is a problem somewhere and removing it will remove the error message but you will still hear the clicks. When I had the problem I removed the option but still got the occasional yellow and red alarm which caused all calls to be dropped. It ended up being a fault with the card in the telephone exchange. If you still have issues then try a new ISDN cable and perform a loopback test on the card. If that doesnt fix it you will need to report a fault with the telco.
Maybe Matching Threads
- TE110P with Qsig
- PTMP BRI Unable to receive TEI from network in state 2(Assign awaiting TEI) - Asterisk 1.6.2, Latest DAHDI, LibPRI
- busy hangup HDLC Bad FCS (8) on Primary D-channel
- HDLC Bad FCS (8) on Primary D-channel
- PRI got event: HDLC Abort (6) on Primary D-channel of span 1