> On Nov. 13, 2014, 11:30 a.m., Mark Michelson wrote: > > With the fix being made to the leaked bridge in Asterisk, is this change > > still required? Does hanging up self.channels[1] not result in > > self.channels[3] and the bridge being destroyed as expected?
Still required, I'm guessing that when the first channel hangs up it leaves the second in a single user bridge. I'm not sure if this is a bug in Asterisk or just the way it works. The XMLDOC doesn't specify. - Corey ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/4166/#review13745 ----------------------------------------------------------- On Nov. 11, 2014, 3:37 p.m., Corey Farrell wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviewboard.asterisk.org/r/4166/ > ----------------------------------------------------------- > > (Updated Nov. 11, 2014, 3:37 p.m.) > > > Review request for Asterisk Developers. > > > Repository: testsuite > > > Description > ------- > > self.channels[3] is not hung up, causing the Asterisk graceful shutdown to > timeout. This causes the test to fail under REF_DEBUG mode and prevents > coverage from seeing the code executed by this test. > > > Diffs > ----- > > /asterisk/trunk/tests/bridge/bridge_action/bridge_action.py 5920 > > Diff: https://reviewboard.asterisk.org/r/4166/diff/ > > > Testing > ------- > > > Thanks, > > Corey Farrell > >
-- _____________________________________________________________________ -- 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
