> On Dec. 10, 2013, 8:46 p.m., rmeyerriecks wrote: > > Ship It!
After talking with rmudgett about this, I feel pretty confident that the risks would be low. From what I understand, in order to get Asterisk to generate invalid channels you would need to have multiple cards/devices and either change modprobe order or physical device locations and not have assigned spans enabled. - rmeyerriecks ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/3063/#review10372 ----------------------------------------------------------- On Dec. 10, 2013, 4:25 p.m., Tzafrir Cohen wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviewboard.asterisk.org/r/3063/ > ----------------------------------------------------------- > > (Updated Dec. 10, 2013, 4:25 p.m.) > > > Review request for Asterisk Developers. > > > Repository: Asterisk > > > Description > ------- > > 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. > > > Diffs > ----- > > /trunk/configs/chan_dahdi.conf.sample 403615 > /trunk/channels/chan_dahdi.c 403615 > > Diff: https://reviewboard.asterisk.org/r/3063/diff/ > > > Testing > ------- > > > Thanks, > > Tzafrir Cohen > >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
