[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:              2010-11-06 15:58 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...
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013206 [patch] ztdynamic double buffering on r...
====================================================================== 

---------------------------------------------------------------------- 
 (0128680) sruffell (administrator) - 2010-11-06 15:58
 https://issues.asterisk.org/view.php?id=13205#c128680 
---------------------------------------------------------------------- 
Just making a note that I find myself re-reading this discussion. 
Yesterday I realized that DAHDI_CONFIG_CORE_TIMER doesn't work with "spans
that provide no timing at all" from tzafrir's comment
[https://issues.asterisk.org/view.php?id=13205#99672].

I was trying to demonstrate to someone how to use dynamic_loc spans to
simulate a PRI link on a local machine and it wasn't working since one of
the dynamic spans became the master.  The call chain was 'coretimer_func()'
->  'process_masterspan()' -> 'dahdi_dynamic_ioctl(0,0)' ->
'__ztdynamic_run()' -> 'dahdi_receive()' -> 'process_masterspan()' -> XXX

So if DAHDI should be able to do masterspan processing out of the context
of a span, I think the best way is to (finally) close out this issue and
among other things implement a way to mark a span as never providing
timing.

If anyone has any new thoughts please add them....  otherwise I'll update
some of these patches, post some candidates. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-06 15:58 sruffell       Note Added: 0128680                          
======================================================================