[Home]

Summary:ASTERISK-16222: getting warning message every 4 seconds
Reporter:andrea lanza (lanzaandrea)Labels:
Date Opened:2010-06-07 03:50:07Date Closed:2010-06-22 06:35:35
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_dahdi
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Follow up of issue ASTERISK-1703270, about lmadsen question:
"2010-05-25 15:06
I'm suspending this issue for now. If this is an issue with DAHDI then please reopen this issue. Thanks!  "

(I was not able to reopen that issue, sorry !)

I am using a pair of asterisk boxes, each one having a 4 span E1 card,
with connected only 2 PRI cable (1-2 on the first box, 3-4 on the second)

Each box have the same cfg regarding all the 4 spans,
and in case of hw failing on one of them the 2 cables are
disconnected from defective box and connected to the free holes on the other.

I am getting the warning message every 4 seconds about configured
but unconnected spans.

[Jun  7 10:45:30] WARNING[2019]: chan_dahdi.c:3365 pri_find_dchan: No D-channels available!  Using Primary channel 78 as D-channel anyway!
[Jun  7 10:45:30] WARNING[2018]: chan_dahdi.c:3365 pri_find_dchan: No D-channels available!  Using Primary channel 109 as D-channel anyway!

I am using dahdi-linux 2.3.0.1 and dahdi-tool 2.3.0 (NO zaptel)


Comments:By: andrea lanza (lanzaandrea) 2010-06-22 06:18:37

asterisk version is 1.6.1.20
you are right, I thought it was a dahdi problem, but I discovered the problem arises from chan_dahdi.c
To workaroud, I just commented out lines 3365 3366
By: Paul Belanger (pabelanger) 2010-06-22 06:32:05

Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch.

More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924
By: Paul Belanger (pabelanger) 2010-06-22 06:35:34

Actually, closing since this is a duplicate (see below).
--
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Thanks!