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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13205 
====================================================================== 
Reported By:                biohumanoid
Assigned To:                kpfleming
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   13205
Category:                   dahdi (the module)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2008-07-31 00:11 CDT
Last Modified:              2009-03-11 11:30 CDT
====================================================================== 
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...
====================================================================== 

---------------------------------------------------------------------- 
 (0101550) KNK (reporter) - 2009-03-11 11:30
 http://bugs.digium.com/view.php?id=13205#c101550 
---------------------------------------------------------------------- 
back to weights sorry ... but instead of weight better name is hwprio ...
in case no preferred sync master is found, which is not in alarm and is not
dummy, re-walk the non alarm spans for built-in hwprio.

and quick and dirty one ... sync-clock-order line at the end of
dahdi/system.conf with coma separated list of span numbers configured
previously, which stores the info in dedicated list inside dahdi-base which
is walked in order for non alarm state and starts it's own 'ticks' only if
no master was found and stops them before selecting a new master the next
time 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-11 11:30 KNK            Note Added: 0101550                          
======================================================================