[asterisk-dev] [Code Review] 726: handle DAHDI_EVENT_REMOVED on a D-Channel

svnbot reviewboard at asterisk.org
Wed Jul 17 11:56:24 CDT 2013

This is an automatically generated e-mail. To reply, visit:

(Updated July 17, 2013, 11:56 a.m.)


This change has been marked as submitted.

Review request for Asterisk Developers and rmudgett.


Committed in revision 394552

Repository: Asterisk


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 'pri destroy span <N>' to destroy the span and its DAHDI channels.

This code seems to be rather DAHDI-generic and thus I opted not to change anything in sig_pri.c .

I use a simplified version of the container_of() macro from the Linux Kernel, which basically returns a pointer to a struct that contains a different struct to which we already have a pointer. Thus I assume this will always be run with on a struct sig_pri_pri that is contained ina s struct dahdi_pri .

I'm not sure what proper locking needs doing.


  /trunk/channels/chan_dahdi.c 394531 

Diff: https://reviewboard.asterisk.org/r/726/diff/


Disconnecting either using the CLI command or with device removal for some E1 and some BRI devices.


Tzafrir Cohen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130717/ba5dbe9f/attachment-0001.htm>

More information about the asterisk-dev mailing list