[asterisk-bugs] [DAHDI-linux 0011611]: channel slave status not correctly cleared
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Sep 25 22:27:54 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11611
======================================================================
Reported By: richvdh
Assigned To: kpfleming
======================================================================
Project: DAHDI-linux
Issue ID: 11611
Category: zaptel (the module)
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2007-12-20 11:22 CST
Last Modified: 2008-09-25 22:27 CDT
======================================================================
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.
======================================================================
----------------------------------------------------------------------
(0092884) sruffell (administrator) - 2008-09-25 22:27
http://bugs.digium.com/view.php?id=11611#c92884
----------------------------------------------------------------------
I made the following commit because it was possible to cause a kernel oops
if the master channel was cleared, and then DAHDI_GET_PARAMS was called.
This was occuring for me if placing a tdm400 in a system with 2 FXO ports,
misconfiguring those ports as fxoks, then changing the configuration to
fxsks and rerunning dahdi_cfg.
http://svn.digium.com/view/dahdi?view=rev&revision=4990
Issue History
Date Modified Username Field Change
======================================================================
2008-09-25 22:27 sruffell Note Added: 0092884
======================================================================
More information about the asterisk-bugs
mailing list