[asterisk-bugs] [Zaptel 0012405]: [patch] bad master selection (2 different ways)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12405 
====================================================================== 
Reported By:                biohumanoid
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   12405
Category:                   zaptel (the module)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Zaptel Version:             1.4.9.2 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-04-10 05:44 CDT
Last Modified:              2008-10-15 00:25 CDT
====================================================================== 
Summary:                    [patch] bad master selection (2 different ways)
Description: 
Current zaptel 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. ztdummy once loaded will be the master forever.
2. even not-running SPAN can be a master
3. master implementation is ugly...

====================================================================== 

---------------------------------------------------------------------- 
 (0093670) biohumanoid (reporter) - 2008-10-15 00:25
 http://bugs.digium.com/view.php?id=12405#c93670 
---------------------------------------------------------------------- 
> Is there any point in moving this forward now that DAHDI has been
released? Is there anything we can do to resolve this issue?

Yes, you can resolve it in DAHDI.
But it's still unresolved... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-15 00:25 biohumanoid    Note Added: 0093670                          
======================================================================