[asterisk-bugs] [Asterisk-GUI 0015619]: DAHDI Trunks do not get configured properly

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15619 
====================================================================== 
Reported By:                timeshell
Assigned To:                awk
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   15619
Category:                   General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
Asterisk GUI Version:       SVN 
Asterisk Version:           1.6.0.11-rc1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 4970 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-07-30 19:32 CDT
Last Modified:              2009-07-31 11:58 CDT
====================================================================== 
Summary:                    DAHDI Trunks do not get configured properly
Description: 
1.  In globals, the var is created as trunk_1 = DAHDI/trunk_1.
Observation: Asterisk has no clue what to do with this in chan_dahdi.c

2.  After changing trunk_1 = DAHDI/trunk_1 to trunk_1 = DAHDI/g1, the
first channel in the trunk works, but none of the other ones do.  Asterisk
replies with congestion message in CLI even though the 2 other lines in the
defined trunk are free.

The analog trunk is defined as having ports 1, 2 and 3 using SVN revision
4970 of the gui.
====================================================================== 

---------------------------------------------------------------------- 
 (0108470) timeshell (reporter) - 2009-07-31 11:58
 https://issues.asterisk.org/view.php?id=15619#c108470 
---------------------------------------------------------------------- 
I have a potential work around that I will be trying after hours.

In extensions.conf, I have changed the GUI written global trunk_# =
DAHDI/trunk_# with trunk_# = DAHDI/g#

In users.conf, I have change the GUI written channel options in the trunk
context from channel = 1, channel = 2, channel = 3 to channel = 1:1,
channel = 1:2, channel = 1:3.

This appears to allow the DAHDI trunk to route outbound calls properly.  I
will be doing further testing to confirm. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-31 11:58 timeshell      Note Added: 0108470                          
======================================================================