[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-09 10:53 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0101387) KNK (reporter) - 2009-03-09 10:53
 http://bugs.digium.com/view.php?id=13205#c101387 
---------------------------------------------------------------------- 
yes <timing source> value in system.conf ... for wct4xpp i have added
"span->syncprio = lc->sync;" in t4_spanconfig only

For analog cards you have that set to 0 and they will not be master if
there are other cards or dummy and in case you do not have any of them you
will still have no timing.

With weight 0 for PRI, weight 1 for BRI and weight 5 for eth: if they are
all (+ dummy) present, up and set to timing=1 you get 1 for PRI, 11 for BRI
and 51 for eth - that's the order we want and if none of them is up dummy
comes to play with prio 100 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-09 10:53 KNK            Note Added: 0101387                          
======================================================================