<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://reviewboard.asterisk.org/r/3063/">https://reviewboard.asterisk.org/r/3063/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On December 10th, 2013, 5:14 p.m. UTC, <b>rmudgett</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I don't think changing this default is a good idea. Enabling it is only useful if you are using the relative channel format. I have yet to see anyone on the Asterisk users list actually use this format.</pre>
</blockquote>
<p>On December 10th, 2013, 5:34 p.m. UTC, <b>Tzafrir Cohen</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">ignore_failed_channels was indeed added to support relative channel format. That is: [/dev/dahdi/]<span-name>/<relative-channnel-number>. We originally thought that this was the only way to guarantee stable channel numbers.
However with recent versions of DAHDI we can provide stable channel numbers through other means (/etc/dahdi/span_assignments.conf ). If those are used, DAHDI will assign the requested span and channel numbers for your dahdi devices independenly of any module load order and device discovery. Furthermore, If you only have a single DAHDI device this is a non-issue anyway.
One by-product of this work on hotplug dahdi is that we noticed that we can do away with the DAHDI init script (this still depends on a non-default setting in the DAHDI kernel module, but I hope it will change in the future). And thus Asterisk may start before some or all of the DAHDI devices have been configured. When a device is configured, the hook script responsible for that eventually runs 'asterisk -rx "dahdi create channels <first> <last>"'.
I'm backporting support for this to wherever I can as it solves some real issues I have. Manually configuring chan_dahdi.conf will work, but I prefer to have sane defaults.</pre>
</blockquote>
<p>On December 11th, 2013, 12:24 p.m. UTC, <b>Tzafrir Cohen</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Should it be included in Asterisk 12 as well?</pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">It should be OK for Asterisk 12 since it has not been released yet and it is a simple default change.</pre>
<br />
<p>- rmudgett</p>
<br />
<p>On December 10th, 2013, 4:25 p.m. UTC, Tzafrir Cohen wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('https://reviewboard.asterisk.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for Asterisk Developers.</div>
<div>By Tzafrir Cohen.</div>
<p style="color: grey;"><i>Updated Dec. 10, 2013, 4:25 p.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
Asterisk
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">If ignore_failed_channels is set to "true" for a channel, the channel will continue to be configured even if configuring it has failed.
One important this This allows Asterisk to start before all the DAHDI initialization is done and thus not force the starting order dahdi -> asterisk.
This patch changes the default of the feature from disabled to enabled.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>/trunk/configs/chan_dahdi.conf.sample <span style="color: grey">(403615)</span></li>
<li>/trunk/channels/chan_dahdi.c <span style="color: grey">(403615)</span></li>
</ul>
<p><a href="https://reviewboard.asterisk.org/r/3063/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>