[Home]

Summary:ASTERISK-18496: 1.8.7.0-rc1 breaks dahdi
Reporter:Sean Darcy (seandarcy)Labels:
Date Opened:2011-09-10 09:14:02Date Closed:2011-09-14 11:00:40
Priority:MajorRegression?Yes
Status:Closed/CompleteComponents:Channels/chan_dahdi
Versions:1.8.7.0 Frequency of
Occurrence
Constant
Related
Issues:
must be completed before resolvingASTERISK-18393 Asterisk 1.8.7.0 Blockers
Environment:fedora 14Attachments:( 0) jira_asterisk_18496_v1.8.patch
Description:dahdi_cfg -vv
DAHDI Tools Version - 2.3.0

DAHDI Version: 2.5.0
Echo Canceller(s): HWEC, OSLEC
Configuration
======================


Channel map:

Channel 01: FXO Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 02)
Channel 04: FXS Kewlstart (Default) (Echo Canceler: oslec) (Slaves: 04)

3 channels to configure.

Setting echocan for channel 1 to oslec
Setting echocan for channel 2 to oslec
Setting echocan for channel 4 to oslec

dahdi restart
Destroying channels and reloading DAHDI configuration.
   -- Unregistered channel -2
 == Parsing '/etc/asterisk/chan_dahdi.conf':   == Found

BUT,

dahdi show channels
  Chan Extension  Context         Language   MOH Interpret        Blocked    State    
pseudo            default                    default                         In Service


cat chan_dahdi.conf
[trunkgroups]

[channels]
usecallerid=yes
callwaiting=no
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=yes

;;group=1
callgroup=0
pickupgroup=0

callprogress=yes
progzone=us
tonezone =0 ; 0 is US
jbenable = yes              ; Enables the use of a jitterbuffer on the receiving side of a
                             ; DAHDI channel. Defaults to "no".

[home-phones]
context=internal      ; Uses the [internal] context in extensions.conf
;;signalling=fxo_ks     ; fxo_ks not auto  Use FXO signalling for an FXS channel - as set in sytem.conf
group=0
dahdichan => 1,2    ; home phones attached to ports 1 and  2

[pstn]
context=incoming-pstn-line  ; Incoming calls go to [incoming-pstn-line] in extensions.conf
;;signalling=fxs_ks     ; fxs_ks not auto Use FXS signalling for an FXO channel - use as set in system.conf
faxdetect=both
faxbuffers=>6,full
busydetect=yes
dahdichan => 4          ; PSTN attached to port 4


Works under 1.8.6.0.

Comments:By: Michael Keuter (mkeuter) 2011-09-11 06:03:02.239-0500

Maybe it is related: when I try to to cross-compile 1.8.7.0-rc1 for AstLinux, the configure script throws this error (although libpri 1.4.12 is installed):

checking for LOG_SYSLOG in syslog.h... yes
checking for LOG_UUCP in syslog.h... yes
checking for mandatory modules:  DAHDI ISDNNET LIBXML2 LTDL MISDN PRI PRI_L2_PERSISTENCE PRI_MWI PRI_MCID PRI_CALL_WAITING PRI_AOC_EVENTS PRI_TRANSFER PRI_CCSS PRI_HANGUP_FIX PRI_SUBADDR PRI_CALL_HOLD PRI_CALL_REROUTING PRI_SETUP_KEYPAD PRI_INBANDDISCONNECT PRI_PROG_W_CAUSE PRI_SERVICE_MESSAGES PRI_REVERSE_CHARGE SQLITE3 SRTP SUPPSERV TONEZONE... fail

configure: ***
configure: *** The PRI_L2_PERSISTENCE installation appears to be missing or broken.
configure: *** Either correct the installation, or run configure
configure: *** including --without-pri.
make: *** [/home/mk/source-control/astlinux-0.7/build_i586/asterisk-1.8.7.0-rc1/.configured] Error 1

It also worked with 1.8.6.0.


By: Richard Mudgett (rmudgett) 2011-09-13 09:55:02.985-0500

The PRI_L2_PERSISTENCE option is only available with libpri SVN at the moment.  It has nothing to do with this issue.  You need to rerun ./configure.

By: Michael Keuter (mkeuter) 2011-09-13 10:51:08.105-0500

Hi Richard,
I definitely use libpri 1.4.12. And this issue is new in 1.8.7.0-rc1. I rerun configure several times.


By: Richard Mudgett (rmudgett) 2011-09-13 11:07:20.202-0500

[^jira_asterisk_18496_v1.8.patch] fixes the missing DAHDI channels when using the newer chan_dahdi.conf sections for channel configuration.  Used the wrong variable.

Michael, your issue is not related to the issue reported here.  Please open a new issue.

By: Sean Darcy (seandarcy) 2011-09-13 19:31:35.688-0500

The patch works. Thanks.

By: Leif Madsen (lmadsen) 2011-09-19 11:48:38.550-0500

r335851 | rmudgett | 2011-09-14 10:53:25 -0500 (Wed, 14 Sep 2011)