[asterisk-bugs] [DAHDI-linux 0013205]: [patch] bad master selection
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Feb 15 23:06:07 CST 2011
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: 2011-02-15 23:06 CST
======================================================================
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...
======================================================================
----------------------------------------------------------------------
(0132003) biohumanoid (reporter) - 2011-02-15 23:06
https://issues.asterisk.org/view.php?id=13205#c132003
----------------------------------------------------------------------
If you feel my suggestions is good - let me know, I'll produce a patch and
will test it on a hardware before posting.
I't prefer to implement STEP1, then STEP2.
STEP2 will also require to patch dahdi_dynamic (remove checkmaster
function, as long as it's going to be implemented in dahdi-base in a good
way).
Then there will be only one checkmaster in the whole DAHDI driver, as it
must be in TDM system.
I don't want to make produce patches if you don't like the idea :-)
Issue History
Date Modified Username Field Change
======================================================================
2011-02-15 23:06 biohumanoid Note Added: 0132003
======================================================================
More information about the asterisk-bugs
mailing list