[asterisk-bugs] [Asterisk 0013443]: rc5: chan_dahdi doesn't recognize TDM400P channels

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13443 
====================================================================== 
Reported By:                seandarcy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13443
Category:                   Channels/chan_dahdi
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-08 19:47 CDT
Last Modified:              2008-09-12 14:23 CDT
====================================================================== 
Summary:                    rc5: chan_dahdi doesn't recognize TDM400P channels
Description: 
using dahdi-linux-rc4 and 1.6.0-rc5, no dial tone or answer on TDM400P
channels. Nothing on CLI.

dahdi-linux seems to work, but chan_dahdi sees only the card not the
channels.
====================================================================== 

---------------------------------------------------------------------- 
 (0092444) seandarcy (reporter) - 2008-09-12 14:23
 http://bugs.digium.com/view.php?id=13443#c92444 
---------------------------------------------------------------------- 
got your note. Revised chan_dahdi.conf

cat chan_dahdi.conf
[trunkgroups]

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

group=1
callgroup=1
pickupgroup=1

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=auto     ; fxo_ks Use FXO signalling for an FXS channel - as
set in sytem.conf.conf
;channel => 1          ; Telephone attached to port 1
;channel => 2          ; Telephone attached to port 2
dahdichan => 1,2

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

Now rc6 sees channel 4 , pstn, but _not_ 1 or 2:

 Parsing '/etc/asterisk/chan_dahdi.conf':   == Found
  == Parsing '/etc/asterisk/users.conf':   == Found
    -- Registered channel 4, FXS Kewlstart signalling
    -- Automatically generated pseudo channel
  == Registered channel type 'DAHDI' (DAHDI Telephony Driver)
  == Manager registered action DAHDITransfer
  == Manager registered action DAHDIHangup
  == Manager registered action DAHDIDialOffhook
  == Manager registered action DAHDIDNDon
  == Manager registered action DAHDIDNDoff
  == Manager registered action DAHDIShowChannels
  == Manager registered action DAHDIRestart
 chan_dahdi.so => (DAHDI Telephony)

dahdi show status
Description                              Alarms  IRQ    bpviol CRC4   Fra
Codi Options  LBO
Wildcard TDM400P REV I Board 5           OK      0      0      0      CAS
Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)
*CLI> dahdi show channels
   Chan Extension  Context         Language   MOH Interpret        Blocked
   State     
 pseudo            incoming-pstn-l            default                     
   In Service
      4            incoming-pstn-l            default                     
   In Service

But then I ;'d out the pstn stanza, that is everthing after dahdichan =>
1,2
and:

Parsing '/etc/asterisk/chan_dahdi.conf':   == Found
  == Parsing '/etc/asterisk/users.conf':   == Found
    -- Registered channel 1, FXO Kewlstart signalling
    -- Registered channel 2, FXO Kewlstart signalling
    -- Automatically generated pseudo channel
  == Registered channel type 'DAHDI' (DAHDI Telephony Driver)
  == Manager registered action DAHDITransfer
  == Manager registered action DAHDIHangup
  == Manager registered action DAHDIDialOffhook
  == Manager registered action DAHDIDNDon
  == Manager registered action DAHDIDNDoff
  == Manager registered action DAHDIShowChannels
  == Manager registered action DAHDIRestart
 chan_dahdi.so => (DAHDI Telephony)
dahdi show channels
   Chan Extension  Context         Language   MOH Interpret        Blocked
   State     
 pseudo            internal                   default                     
   In Service
      1            internal                   default                     
   In Service
      2            internal                   default                     
   In Service

so it looks like chan_dahdi is only parsing the last dahdichan it finds. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-12 14:23 seandarcy      Note Added: 0092444                          
======================================================================