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

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Jan 15 13:33:27 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14031 
====================================================================== 
Reported By:                sruffell
Assigned To:                sruffell
====================================================================== 
Project:                    Asterisk
Issue ID:                   14031
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     confirmed
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-01-15 13:33 CST
====================================================================== 
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. 
====================================================================== 

---------------------------------------------------------------------- 
 (0097958) francesco_r (reporter) - 2009-01-15 13:33
 http://bugs.digium.com/view.php?id=14031#c97958 
---------------------------------------------------------------------- 
Ok, i have misinterpreted the pmp_l1_check option. Now if i load the module
wcb4xxp with teignorered parameter enabled all works well and all leds are
always green. I had to manually edit base.c and recompile the module
because if i do "modprobe wc4xxp teignorered=1" i have "wcb4xxp: Unknown
parameter `teignorered'".
So to resume: pmp_l1_check works correctly (i have no more layer up/down)
and with teignorered if i disconnect the cable from one port to another i
can call immediately after the TEI is assigned. But i have still stability
problem, asterisk crash often when i connect/reconnect the cable, see
http://bugs.digium.com/view.php?id=13931, and the span remains always up, even
if the cable is not connected.
So if i try to dial in this span, asterisk try to call-out endlessly.

For example this is the output of "pri show spans":
PRI span 1/0: Provisioned, Up, Active
PRI span 2/0: Provisioned, Down, Active
PRI span 3/0: Provisioned, Down, Active
PRI span 4/0: Provisioned, Up, Active

but in this case the cable is only connected in the port 4.

So if in extensions.conf i have:
exten => _XX.,1,Dial(DAHDI/g0/${EXTEN}) ; bri 1-2
exten => _XX.,1,Dial(DAHDI/g1/${EXTEN}) ; bri 4-5
exten => _XX.,1,Dial(DAHDI/g2/${EXTEN}) ; bri 7-8
exten => _XX.,1,Dial(DAHDI/g3/${EXTEN}) ; bri 10-11

and i dial the number 190, in the console asterisk stay forever in this
state:
-- Requested transfer capability: 0x00 - SPEECH
-- Called g0/190
and do not continue to g1 or g2 or g3.

However i think you can close the old http://bugs.digium.com/view.php?id=12757
issue i have open sometimes
ago.
Thank you 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-15 13:33 francesco_r    Note Added: 0097958                          
======================================================================




More information about the asterisk-bugs mailing list