[asterisk-bugs] [DAHDI-linux 0013205]: [patch] bad master selection
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Mar 6 16:03:35 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-06 16:03 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...
======================================================================
----------------------------------------------------------------------
(0101321) madrouter (reporter) - 2009-03-06 16:03
http://bugs.digium.com/view.php?id=13205#c101321
----------------------------------------------------------------------
Another thought about solving the support issue. Why not let Asterisk ask
for the dahdi_dynamic module to load? If Asterisk starts and figures out
that there's no dahdi spans at all (can't open /dev/dahdi/pseudo??) then it
tries to load dahdi_dummy and then tries to open /dev/dahdi/pseudo again.
If there's still no /dev/dahdi/pseudo (maybe the user didn't install dahdi)
then it throws warnings about not having a timing source.
Issue History
Date Modified Username Field Change
======================================================================
2009-03-06 16:03 madrouter Note Added: 0101321
======================================================================
More information about the asterisk-bugs
mailing list