[asterisk-bugs] [DAHDI-linux 0013205]: [patch] bad master selection
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Mar 9 10:59:33 CDT 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-09 10:59 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...
======================================================================
----------------------------------------------------------------------
(0101389) madrouter (reporter) - 2009-03-09 10:59
http://bugs.digium.com/view.php?id=13205#c101389
----------------------------------------------------------------------
I really don't like this whole weighting thing. It makes assumptions about
how the user's network is built that may not be valid. Going back to some
live deployments I have - I have both dynamic ethernet spans and PRI spans.
I WANT the dynamic spans to be the master and to have the PRIs clocked by
Dahdi (and have had to replace all my Digium/Sangoma cards with Xorcom kit
as a result). With the weighting I would have to artificially make my PRI
spans less desirable as a clock source, which would result in a VERY
confusing system.conf!!
Issue History
Date Modified Username Field Change
======================================================================
2009-03-09 10:59 madrouter Note Added: 0101389
======================================================================
More information about the asterisk-bugs
mailing list