[asterisk-bugs] [Asterisk 0017864]: Usage of unavailable channels on multi-PRI NT spans

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Aug 31 14:32:00 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17864 
====================================================================== 
Reported By:                wimpy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17864
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.8.0-beta4 
JIRA:                       SWP-2132 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-08-15 11:24 CDT
Last Modified:              2010-08-31 14:32 CDT
====================================================================== 
Summary:                    Usage of unavailable channels on multi-PRI NT spans
Description: 
When Asterisk is (re)started while (only) the primary interface is down, it
correctly activates the secondary D-channel, but non the less selects
B-channels from the unavailable primary interface.
It only happens when the primary interface if unavailable from the
beginning.
If it's been up and fails while Asterisk is running, channel selection
works as expected.
====================================================================== 

---------------------------------------------------------------------- 
 (0126492) wimpy (reporter) - 2010-08-31 14:32
 https://issues.asterisk.org/view.php?id=17864#c126492 
---------------------------------------------------------------------- 
Can be reproduced by unplugging the primary interface and then (re)
starting Asterisk. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-31 14:32 wimpy          Note Added: 0126492                          
======================================================================




More information about the asterisk-bugs mailing list