[asterisk-bugs] [Zaptel 0012405]: bad master selection (2 different ways)
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Apr 10 05:44:31 CDT 2008
The following issue has been SUBMITTED.
======================================================================
http://bugs.digium.com/view.php?id=12405
======================================================================
Reported By: biohumanoid
Assigned To:
======================================================================
Project: Zaptel
Issue ID: 12405
Category: zaptel (the module)
Reproducibility: always
Severity: major
Priority: normal
Status: new
Zaptel Version: 1.4.9.2
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 04-10-2008 05:44 CDT
Last Modified: 04-10-2008 05:44 CDT
======================================================================
Summary: bad master selection (2 different ways)
Description:
Current zaptel 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. ztdummy once loaded will be the master forever.
2. even not-running SPAN can be a master
3. master implementation is ugly...
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
04-10-08 05:44 biohumanoid Zaptel Version => 1.4.9.2
04-10-08 05:44 biohumanoid SVN Branch (only for SVN checkou => N/A
======================================================================
More information about the asterisk-bugs
mailing list