[asterisk-bugs] [Asterisk 0017525]: handle DAHDI_EVENT_REMOVED on a D-Channel
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jun 17 16:50:42 CDT 2010
The following issue is now READY FOR REVIEW.
======================================================================
https://issues.asterisk.org/view.php?id=17525
======================================================================
Reported By: tzafrir
Assigned To: tzafrir
======================================================================
Project: Asterisk
Issue ID: 17525
Category: Codecs/codec_dahdi
Reproducibility: always
Severity: feature
Priority: normal
Status: ready for review
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link: https://reviewboard.asterisk.org/r/726/
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 270972
Request Review:
======================================================================
Date Submitted: 2010-06-17 16:50 CDT
Last Modified: 2010-06-17 16:50 CDT
======================================================================
Summary: handle DAHDI_EVENT_REMOVED on a D-Channel
Description:
When a DAHDI device is removed at run-time it sends the event
DAHDI_EVENT_REMOVED on each channel. This is intended to signal the
userspace program to close the respective file handle, as the driver of the
device will need all of them closed to properly clean-up.
This event has long since been handled in chan_dahdi (chan_zap at the
time). However the event that is sent on a D-Channel of a "PRI" (ISDN) span
simply gets ignored.
This code adds handling for closing the file descriptor (and shutting down
the span, while we're at it). It also adds a CLI command to help test it.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-06-17 16:50 tzafrir Assigned To => tzafrir
2010-06-17 16:50 tzafrir Status new => ready for review
======================================================================
More information about the asterisk-bugs
mailing list