[asterisk-bugs] [DAHDI-linux 0013205]: [patch] bad master selection
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Mar 7 02:26:48 CST 2009
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-07 02:26 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...
======================================================================
----------------------------------------------------------------------
(0101329) madrouter (reporter) - 2009-03-07 02:26
http://bugs.digium.com/view.php?id=13205#c101329
----------------------------------------------------------------------
Having thought about it a bit deeper you're right - probably nothing would
break. On the machine that I want to be the master clock source under
normal running the dynamic spans would be configured not to be a timing
source so it would use dahdi_dummy. On the machine that is meant to be
receiving clock from the dynamic spans, the dynamic spans would be
configured with non-zero timing priority so if they weren't in alarm it
would use those but if it lost the network it would switch to it's local
dahdi_dummy.
Ok - I obviously didn't think about it properly before thinking it could
break something :(
Issue History
Date Modified Username Field Change
======================================================================
2009-03-07 02:26 madrouter Note Added: 0101329
======================================================================
More information about the asterisk-bugs
mailing list