[asterisk-bugs] [Zaptel 0011611]: channel slave status not correctly cleared

noreply at bugs.digium.com noreply at bugs.digium.com
Fri Jan 11 18:34:21 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11611 
====================================================================== 
Reported By:                richvdh
Assigned To:                sruffell
====================================================================== 
Project:                    Zaptel
Issue ID:                   11611
Category:                   zaptel (the module)
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Zaptel Version:              1.4.7  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-20-2007 11:22 CST
Last Modified:              01-11-2008 18:34 CST
====================================================================== 
Summary:                    channel slave status not correctly cleared
Description: 
If I configure a batch of channels to be slaved together (via zaptel.conf
and ztcfg), then try to reset them to individual channels, the master
channel gets stuck with a master status.

====================================================================== 

---------------------------------------------------------------------- 
 sruffell - 01-11-08 18:34  
---------------------------------------------------------------------- 
This can be worked around by running ztcfg with the -f command to force the
update.

In step 1 each channel is set as it's own master, but it is not reported
since they do not have any slaves.

In step 2 channel 1 is set to the master with slaves.

In step 3 ztcfg sees that channel 1 is already it's own master, and
therefore doesn't reconfigure it, so the nextslave field never gets
cleared. 

Now how to fix it... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-11-08 18:34  sruffell       Note Added: 0076780                          
======================================================================




More information about the asterisk-bugs mailing list