No D-channels available!

Dear all,

We have a OpenVox card (D410P), the card was in E1 mode.
3 spans is connected.
We use asterisk-1.6.2-13,dahdi-linux-complete-2.4.0+2.4.0,libpri-1.4.11.4

The problem we are having is that, the pri going down everyday after some calls.
After restart dahdi and asterisk all OK,but in next day the PRI went down again.
Cli asterisk :

[Oct 26 10:51:47] WARNING[29132]: chan_dahdi.c:4169 pri_find_dchan: No D-channels available! Using Primary channel 16 as D-channel anyway!
[Oct 26 10:51:47] WARNING[29133]: chan_dahdi.c:4169 pri_find_dchan: No D-channels available! Using Primary channel 47 as D-channel anyway!
[Oct 26 10:51:51] WARNING[29134]: chan_dahdi.c:4169 pri_find_dchan: No D-channels available! Using Primary channel 78 as D-channel anyway!


PRI span 1/0: Provisioned, Down, Active
PRI span 2/0: Provisioned, Down, Active
PRI span 3/0: Provisioned, Down, Active

Alarms IRQ bpviol CRC4 Fra Codi Options LBO

T4XXP (PCI) Card 0 Span 1 OK 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1)

T4XXP (PCI) Card 0 Span 2 OK 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1)

T4XXP (PCI) Card 0 Span 3 OK 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1)

T4XXP (PCI) Card 0 Span 4 UNCONFI 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)

--------------------------- PRI Debug ---------------------------------------------------

TEI: 0 State 5(Awaiting establishment)
V(A)=49, V(S)=49, V®=21
K=7, RC=1, l3initiated=1, reject_except=0, ack_pend=0
T200_id=0, N200=3, T203_id=0
[ 00 01 7f ]
Unnumbered frame:
SAPI: 00 C/R: 0 EA: 0
TEI: 000 EA: 1
M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
0 bytes of data
– Starting T200 timer
t200_expire
TEI: 0 State 5(Awaiting establishment)
V(A)=116, V(S)=116, V®=42
K=7, RC=3, l3initiated=1, reject_except=0, ack_pend=0
T200_id=1, N200=3, T203_id=0
TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
Changing from state 5(Awaiting establishment) to 4(TEI assigned)
q931.c:7700 q931_dl_indication: link is DOWN
– T203 requested to stop when not started
– Restarting T200 timer
TEI=0 Sending SABME

TEI: 0 State 4(TEI assigned)
V(A)=116, V(S)=116, V®=42
K=7, RC=0, l3initiated=1, reject_except=0, ack_pend=0
T200_id=1, N200=3, T203_id=0
[ 00 01 7f ]
Unnumbered frame:
SAPI: 00 C/R: 0 EA: 0
TEI: 000 EA: 1
M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
0 bytes of data
Changing from state 4(TEI assigned) to 5(Awaiting establishment)

< TEI: 0 State 5(Awaiting establishment)
< V(A)=109, V(S)=109, V®=32
< K=7, RC=1, l3initiated=1, reject_except=0, ack_pend=0
< T200_id=1, N200=3, T203_id=0
< [ 02 01 7f ]
< Unnumbered frame:
< SAPI: 00 C/R: 1 EA: 0
< TEI: 000 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
TEI=0 Got SABME from network peer.
TEI=0 Sending UA

TEI: 0 State 5(Awaiting establishment)
V(A)=109, V(S)=109, V®=32
K=7, RC=1, l3initiated=1, reject_except=0, ack_pend=0
T200_id=1, N200=3, T203_id=0
[ 02 01 73 ]
Unnumbered frame:
SAPI: 00 C/R: 1 EA: 0
TEI: 000 EA: 1
M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ]
0 bytes of data
Done handling message for SAPI/TEI=0/0
t200_expire
TEI: 0 State 5(Awaiting establishment)
V(A)=109, V(S)=109, V®=32
K=7, RC=1, l3initiated=1, reject_except=0, ack_pend=0
T200_id=1, N200=3, T203_id=0
TEI=0 Sending SABME

TEI: 0 State 5(Awaiting establishment)
V(A)=109, V(S)=109, V®=32
K=7, RC=2, l3initiated=1, reject_except=0, ack_pend=0
T200_id=0, N200=3, T203_id=0
[ 00 01 7f ]
Unnumbered frame:
SAPI: 00 C/R: 0 EA: 0
TEI: 000 EA: 1
M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
0 bytes of data
– Starting T200 timer
t200_expire
TEI: 0 State 5(Awaiting establishment)
V(A)=49, V(S)=49, V®=21
K=7, RC=1, l3initiated=1, reject_except=0, ack_pend=0
T200_id=1, N200=3, T203_id=0
TEI=0 Sending SABME


We used the following configuration:

dahdi system.conf

span=1,1,0,ccs,hdb3
bchan=1-15
dchan=16
bchan=17-31
echocanceller=mg2,1-15,17-31

span=2,2,0,ccs,hdb3
bchan=32-46
dchan=47
bchan=48-62
echocanceller=mg2,32-46,48-62

span=3,3,0,ccs,hdb3
bchan=63-77
dchan=78
bchan=79-93
echocanceller=mg2,63-77,79-93

loadzone = us
defaultzone=us


chan_dahdi.conf

[channels]
language=en
context=inbound
switchtype=euroisdn
pridialplan=unknown
prilocaldialplan=unknown
internationalprefix = 00
nationalprefix =967
privateprefix = 967
signalling=pri_cpe
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
amaflags = billing
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
group=1
context=inbound
signalling=pri_cpe
switchtype=euroisdn
channel => 1-15
channel => 17-25
group = 2
context=inbound
signalling=pri_cpe
switchtype=euroisdn
channel => 32-46
channel => 48-56
group = 3
context=inbound
signalling=pri_cpe
switchtype=euroisdn
channel => 63-77
channel => 79-87
group = 4
signalling=pri_cpe
switchtype=euroisdn
channel => 26-31
channel => 57-62
channel => 88-93

Can you please help me solve this problem???
Thank you

Hi all, i see this message today in asterisk console

NOTICE[17963]: chan_dahdi.c:12706 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2
NOTICE[17963]: chan_dahdi.c:12706 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2
NOTICE[17963]: chan_dahdi.c:12706 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 3
NOTICE[17963]: chan_dahdi.c:12706 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 3

after restart and after some calls in AMI console i see following messages:

Event: PRIEvent
Privilege: system,all
PRIEvent: HDLC Abort
PRIEventCode: 6
D-channel: Primary
Span: 2

Event: PRIEvent
Privilege: system,all
PRIEvent: HDLC Abort
PRIEventCode: 6
D-channel: Primary
Span: 2

Event: PRIEvent
Privilege: system,all
PRIEvent: HDLC Abort
PRIEventCode: 6
D-channel: Primary
Span: 2

Event: PRIEvent
Privilege: system,all
PRIEvent: HDLC Abort
PRIEventCode: 6
D-channel: Primary
Span: 2

Event: PRIEvent
Privilege: system,all
PRIEvent: HDLC Bad FCS
PRIEventCode: 8
D-channel: Primary
Span: 2

HDLC aborts and frame check sequence errors indicate a hardware fault, excessive electrical noise on the line, or just possibly a timing source problem.

Thanks for your reply
I will check the line for electrical noise.

Best regards.