[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 03:01 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0101514) KNK (reporter) - 2009-03-11 03:01
 http://bugs.digium.com/view.php?id=13205#c101514 
---------------------------------------------------------------------- 
Well i don't think weights are necessary (even the opposite - better not to
have them) and simply making the code do what the docs (comments inside
system.conf) say is the right think.

biohumanoid: Yes all dahdi drivers should be updated to set syncprio, but
without this there is no guarantee which span will be master.
For example one may have two PRI boards - to PSTN and to PBX, but if the
one to PBX is registered first it will be chosen as master, while you must
sync to the PSTN in this case. The same will happen if PSTN is just on the
second port of the same card 

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