[asterisk-bugs] [DAHDI-linux 0013205]: [patch] bad master selection

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=13205 
====================================================================== 
Reported By:                biohumanoid
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   13205
Category:                   dahdi (the module)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2008-07-31 00:11 CDT
Last Modified:              2011-02-16 02:07 CST
====================================================================== 
Summary:                    [patch] bad master selection
Description: 
Current dahdi master handling work in the following way:
The first SPAN become a master
If a new registered !!! SPAN is preferred , it is the new master
If a span is unregistered - the new master is the first available span
If master SPAN is in alarm state - the new master is the first non in
alarm state SPAN

So
1. dahdi-dummy once loaded will be the master forever.
2. even not-running SPAN can be a master
3. master implementation is ugly...
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013206 [patch] ztdynamic double buffering on r...
====================================================================== 

---------------------------------------------------------------------- 
 (0132007) sruffell (administrator) - 2011-02-16 02:07
 https://issues.asterisk.org/view.php?id=13205#c132007 
---------------------------------------------------------------------- 
biohumaniod: I'm happy that you're commenting on this issue again!

You bring up some good points, but instead of addressing them
(specifically about the details in the code) perhaps we should just focus
only on flow charting how the master span and timing sync for the different
potential clock domains should be selected?  There's the global master, the
sync source on multiport cards, and cards that can potentially share timing
via cables.  Am I missing any others?

Did you happen to see this recent thread:
http://thread.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/45223/focus=45233

And I hate to say this, but given all the different thoughts, perhaps this
should be taken to the asterisk-dev list in general so we can reply inline
to the different threads? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-16 02:07 sruffell       Note Added: 0132007                          
======================================================================