[asterisk-bugs] [Asterisk 0014031]: [patch] "pri_find_dchan: No D-channels available!" error on console when using wcb4xxp

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14031 
====================================================================== 
Reported By:                sruffell
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14031
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 160386 
Request Review:              
====================================================================== 
Date Submitted:             2008-12-08 14:55 CST
Last Modified:              2009-06-17 02:50 CDT
====================================================================== 
Summary:                    [patch] "pri_find_dchan: No D-channels available!"
error on console when using wcb4xxp
Description: 
When a wcb4xxp is connected as a BRI span in TE mode, you get errors like:

[Dec 2 22:02:48] WARNING[4759]: chan_dahdi.c:3008 pri_find_dchan: No
D-channels available! Using Primary channel 6 as D-channel anyway!
[Dec 2 22:02:49] WARNING[4758]: chan_dahdi.c:3008 pri_find_dchan: No
D-channels available! Using Primary channel 3 as D-channel anyway!
[Dec 2 22:03:19] WARNING[4759]: chan_dahdi.c:3008 pri_find_dchan: No
D-channels available! Using Primary channel 6 as D-channel anyway!

On your asterisk console and in your asterisk log. 
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0014617 HFC-s card cannot initiate outgoing calls
related to          0012757 [branch] when BRI span go down cannot m...
====================================================================== 

---------------------------------------------------------------------- 
 (0106539) nenadr (reporter) - 2009-06-17 02:50
 https://issues.asterisk.org/view.php?id=14031#c106539 
---------------------------------------------------------------------- 
OK, I've just had a situation when I start asterisk and connected BRI port
doesn't go up immediatly, but after a while (this time it was after apx. 40
to 50 seconds, but sometimes it is much longer). Tested on same setup
mentioned in note 0106533, telco is Telekom Srbija and NT box asterisk is
connected to in PtMP, is Intracom NetMod+. I've started asterisk and same
moment I've got prompt I started pri debug span 1, and got this:

*CLI> pri debug span 1
Enabled debugging on span 1
*CLI> 
*CLI> 
*CLI> Sending TEI management message 1, TEI=127
Sending TEI management message 1, TEI=127
Sending TEI management message 1, TEI=127
Sending TEI management message 1, TEI=127
[Jun 17 09:34:10] NOTICE[11761]: chan_dahdi.c:11077 pri_dchannel: PRI got
event: No more alarm (5) on Primary D-channel of span 1
q921.c:852 q921_reset: q921_sate now is Q921_LINK_CONNECTION_RELEASED
Sending TEI management message 1, TEI=127
[Jun 17 09:34:10] NOTICE[11765]: chan_dahdi.c:8227 handle_init_event:
Alarm cleared on channel 1
[Jun 17 09:34:10] NOTICE[11765]: chan_dahdi.c:8227 handle_init_event:
Alarm cleared on channel 2
Received MDL message
TEI assiged to 113
q921.c:852 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
Sending Set Asynchronous Balanced Mode Extended
q921.c:211 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH
-- Got UA from network peer  Link up.
q921.c:801 q921_dchannel_up: q921_state now is
Q921_LINK_CONNECTION_ESTABLISHED
  == Primary D-Channel on span 1 up
Received MDL message
Sending TEI management message 5, TEI=113
Received MDL message
Sending TEI management message 5, TEI=113

Hope this might help. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-17 02:50 nenadr         Note Added: 0106539                          
======================================================================