Te110P and HDLC errors

Greetings all,

We’ve recently purchased a Te110xp and have it installed in a Gentoo platform (2.6 kernel). We’ve got a PRI back to a Nortel DMS100 and my CO guys tell me that everything looks good on their end (I work for an ILEC). However, Anytime I bring the span up I’m receiving the following:

May 26 09:11:28 WARNING[15157] chan_zap.c: No D-channels available! Using Primary channel 24 as D-channel anyway! May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 May 26 09:11:29 NOTICE[15157] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1

Now off the Asterisk CLI my “pri show span 1” shows the circuit as provisioned, up, and active. The output of my hdparm is as follows:

[code]/dev/hda:

Model=WDC WD2000JB-00KFA0, FwRev=08.05J08, SerialNo=WD-WCAMT1374678
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=65
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: device does not report version:

  • signifies the current active mode[/code]

My interrupts output indicates…

CPU0 0: 6561550 IO-APIC-edge timer 1: 4686 IO-APIC-edge i8042 8: 2 IO-APIC-edge rtc 12: 379276 IO-APIC-edge i8042 14: 115131 IO-APIC-edge ide0 15: 26 IO-APIC-edge ide1 16: 213822 IO-APIC-level Intel 82801BA-ICH2 17: 61526 IO-APIC-level eth0 18: 62683200 IO-APIC-level wcte11xp 20: 0 IO-APIC-level acpi NMI: 0 LOC: 6561892 ERR: 0 MIS: 0

Output of zttool gives me an “OK” with no alarms.

ztcfg shows…

[code]Zaptel Configuration

SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Slaves: 01)
Channel 02: Clear channel (Default) (Slaves: 02)
Channel 03: Clear channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: Clear channel (Default) (Slaves: 06)
Channel 07: Clear channel (Default) (Slaves: 07)
Channel 08: Clear channel (Default) (Slaves: 08)
Channel 09: Clear channel (Default) (Slaves: 09)
Channel 10: Clear channel (Default) (Slaves: 10)
Channel 11: Clear channel (Default) (Slaves: 11)
Channel 12: Clear channel (Default) (Slaves: 12)
Channel 13: Clear channel (Default) (Slaves: 13)
Channel 14: Clear channel (Default) (Slaves: 14)
Channel 15: Clear channel (Default) (Slaves: 15)
Channel 16: Clear channel (Default) (Slaves: 16)
Channel 17: Clear channel (Default) (Slaves: 17)
Channel 18: Clear channel (Default) (Slaves: 18)
Channel 19: Clear channel (Default) (Slaves: 19)
Channel 20: Clear channel (Default) (Slaves: 20)
Channel 21: Clear channel (Default) (Slaves: 21)
Channel 22: Clear channel (Default) (Slaves: 22)
Channel 23: Clear channel (Default) (Slaves: 23)
Channel 24: D-channel (Default) (Slaves: 24)

24 channels configured.
[/code]

And my /proc/zaptel/1 output is as follows:

[code]Span 1: WCT1/0 “Digium Wildcard TE110P T1/E1 Card 0” B8ZS/ESF

   1 WCT1/0/1 Clear (In use) 
   2 WCT1/0/2 Clear (In use) 
   3 WCT1/0/3 Clear (In use) 
   4 WCT1/0/4 Clear (In use) 
   5 WCT1/0/5 Clear (In use) 
   6 WCT1/0/6 Clear (In use) 
   7 WCT1/0/7 Clear (In use) 
   8 WCT1/0/8 Clear (In use) 
   9 WCT1/0/9 Clear (In use) 
  10 WCT1/0/10 Clear (In use) 
  11 WCT1/0/11 Clear (In use) 
  12 WCT1/0/12 Clear (In use) 
  13 WCT1/0/13 Clear (In use) 
  14 WCT1/0/14 Clear (In use) 
  15 WCT1/0/15 Clear (In use) 
  16 WCT1/0/16 Clear (In use) 
  17 WCT1/0/17 Clear (In use) 
  18 WCT1/0/18 Clear (In use) 
  19 WCT1/0/19 Clear (In use) 
  20 WCT1/0/20 Clear (In use) 
  21 WCT1/0/21 Clear (In use) 
  22 WCT1/0/22 Clear (In use) 
  23 WCT1/0/23 Clear (In use) 
  24 WCT1/0/24 HDLCFCS (In use) 

[/code]

And here’s my zaptel.conf and zapata.conf files:

zaptel.conf

[code]span=1,0,0,esf,b8zs

bchan=1-23
dchan=24

loadzone = us

defaultzone=us
[/code]

zapata.conf

[code][trunkgroups]

trunkgroup => 1,24

spanmap => 1,1,1

[channels]

context=default

; rxwink=300 ; Atlas seems to use long (250ms) winks

usecallerid=yes

hidecallerid=no

callwaiting=yes

usecallingpres=yes

callwaitingcallerid=yes

threewaycalling=yes

transfer=yes

cancallforward=yes

callreturn=yes

echocancel=yes

echocancelwhenbridged=yes

rxgain=0.0
txgain=0.0

group=1

callgroup=1
pickupgroup=1

immediate=no

jitterbuffers=24

switchtype = dms100
signalling = pri_cpe
group = 1
channel => 1-23
[/code]

For the life of me I can’t seem to resolve this problem. Any insight would be greatly appreciated. I read a thread with a similar problem on this board that stated the board was faulty. I hope that’s not the case here and it’s simply something that I’ve either overlooked or misconfigured. TIA :smile:

Additionally, here’s the output from zttest…

Opened pseudo zap interface, measuring accuracy... 99.987793% 100.000000% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% --- Results after 13 passes --- Best: 100.000000 -- Worst: 99.987793

How did you get that issue fixed?

I have pretty much the same problem but spontaniously. Today only 4 times, but with the same errors:

My config is almost the same as yours.

i was facing the same problem, apparently it can be cased by a conflict with onboard intel nic’s.

a support call with digium and they kindly set up an advanced RMA for me and replaced the cards with the TE120P, sorted it instantly.

HTH