[asterisk-dev] [Code Review] chan_dahdi: create and destroy channels at run-time

Tzafrir Cohen reviewboard at asterisk.org
Sat Dec 17 07:46:28 CST 2011

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

(Updated Dec. 17, 2011, 7:46 a.m.)

Review request for Asterisk Developers.


Fixed previous comments. The filtering is still not applied in prepare_pri() and likely neither in the SS7 code.

Right now the behaviour when starting a bunch of channels from the CLI is different than having them all configured: even if there's a problem with one, the next one will be parsed (this is indeed the behaviour we need with pinned-spans). Should it indeed be this way? For normal startup as well?


This code adds chan_dahdi the command 'dahdi create channels <range>' (where <range> is a single <n>-<m>) and updates 'dahdi destroy channel' with a similar 'dahdi destroy channels'.

'dahdi create channels' acts as a filter for process_dahdi() and such in DAHDI: it re-parses the whole configuration, but only attempts to create channels in the range.

Right not this patch disables the initial probing at module load time (workaround: run 'dahdi create channels 1-10000' at startup through cli.conf). This is for debugging, mainly and should be removed later on.

This changeg is intended to provide a hook for a script running from udev once a span has been assigned ("registered") / unassigned ("unregistered") for its channels. The udev hook configures the span's channels with dahdi_cfg -S, and can then ask Asterisk to create ethe channels.

See: https://gitorious.org/~tzafrir/asterisk-tools/tzafrirs-dahdi-tools/commits/pinned-spans

This means that a separate DAHDI init script (running before the Asterisk one) would no longer be required. There is no longer a need to run a single command after all DAHDI devices are up.

Diffs (updated)

  /trunk/channels/chan_dahdi.c 348303 

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


Works well with analog devices. Seems to work with ISDN ones as well. Not fully complete, though.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20111217/456d936a/attachment.htm>

More information about the asterisk-dev mailing list