[asterisk-bugs] [Asterisk 0014056]: [patch] chan_dahdi effectively ignores dahdichanname while looking for a configuration file

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14056 
====================================================================== 
Reported By:                dsedivec
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   14056
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.22 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 162868 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-12-10 16:51 CST
Last Modified:              2009-03-17 15:13 CDT
====================================================================== 
Summary:                    [patch] chan_dahdi effectively ignores dahdichanname
while looking for a configuration file
Description: 
Zaptel-to-DAHDI.txt says:

  The configuration for the channel driver will be read from
  /etc/asterisk/chan_dahdi.conf unless 'dahdichanname' has been set to
  'no' in asterisk.conf; if that is done, then the configuration will
  be read from /etc/asterisk/zapata.conf, just as it was in previous
  versions.

Unfortunately this doesn't seem to work in 1.4.22.  Culprit seems to be a
couple places where dahdi_chan_mode is not dereferenced.  Please see
attached patch.

====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-17 15:13 svnbot         Status                   assigned => resolved
2009-03-17 15:13 svnbot         Resolution               open => fixed       
======================================================================