[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
Fri Aug 7 12:36:00 CDT 2009
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-08-07 12:35 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...
======================================================================
----------------------------------------------------------------------
(0108778) timking (reporter) - 2009-08-07 12:35
https://issues.asterisk.org/view.php?id=14031#c108778
----------------------------------------------------------------------
OK try this. It doesn't seem to break anything on my test rig.
Move case 03 out from where it was.
case 0x3: /* TE state F3:
Deactivated */
/* If we're in F3 receiving INFO0, start T3 and
jump to F4 */
if (state & V_INFO0) { /* Activate and start
timer */
b4xxp_setreg_ra(b4, R_ST_SEL, s->port,
A_ST_WR_STA, V_ST_ACT_ACTIVATE);
s->hfc_timers[HFC_T3] = b4->ticks +
timer_3_ms;
s->hfc_timer_on[HFC_T3] = 1;
if (DBG_ST)
dev_info(b4->dev, "port %d:
receiving INFO0 in state 3, setting T3 and jumping to F4\n", s->port + 1);
hfc_force_st_state(b4, s->port, 4, 1);
}
/* Otherwise the network has shut us down */
else {
b4xxp_setreg_ra(b4, R_ST_SEL, s->port,
A_ST_WR_STA, V_ST_ACT_DEACTIVATE);
s->hfc_timer_on[HFC_T3] = 0;
hfc_force_st_state(b4, s->port, 3, 1);
}
s->newalarm = 0;
break;
and then remove the code in the test for !nt and sta=3 and INFO0 lower
down as we have already done it.
V_ST_ACT_(DE)ACTIVATE are the 40 and 60 you see.
Issue History
Date Modified Username Field Change
======================================================================
2009-08-07 12:35 timking Note Added: 0108778
======================================================================
More information about the asterisk-bugs
mailing list