[asterisk-dev] [Code Review] 2642: app_bridgewait: Add a name argument so that multiple holding bridges may be used

jrose reviewboard at asterisk.org
Tue Jul 2 17:54:50 CDT 2013



> On July 2, 2013, 7:55 p.m., opticron wrote:
> > /trunk/apps/app_bridgewait.c, lines 381-384
> > <https://reviewboard.asterisk.org/r/2642/diff/3/?file=40353#file40353line381>
> >
> >     This is the second time an error message is produced for this NULL holding bridge.

Removed the error message from holding_bridge_wrapper_get_bridge.


> On July 2, 2013, 7:55 p.m., opticron wrote:
> > /trunk/apps/app_bridgewait.c, line 247
> > <https://reviewboard.asterisk.org/r/2642/diff/3/?file=40353#file40353line247>
> >
> >     This is already locked outside of this function call.

So it is.  Removed.


- jrose


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2642/#review9051
-----------------------------------------------------------


On June 25, 2013, 5:06 p.m., jrose wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2642/
> -----------------------------------------------------------
> 
> (Updated June 25, 2013, 5:06 p.m.)
> 
> 
> Review request for Asterisk Developers, Matt Jordan and rmudgett.
> 
> 
> Bugs: ASTERISK-21922
>     https://issues.asterisk.org/jira/browse/ASTERISK-21922
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> Previously the holding bridge used for bridgewait was a single bridge that once created would stick around until the application was unloaded.
> 
> Now things are a little more complicated. Each holding bridge has a name and will be destroyed when it is empty. Since it's theoretically possible to have channels enter a holding bridge without going through the bridge wait application, it isn't always possible to deliberately control when the bridge will be destroyed, so the bridge can effectively be abandoned and set to be destroyed once it empties out.
> 
> 
> Diffs
> -----
> 
>   /trunk/apps/app_bridgewait.c 392721 
>   /trunk/include/asterisk/bridging.h 392721 
>   /trunk/main/bridging.c 392721 
> 
> Diff: https://reviewboard.asterisk.org/r/2642/diff/
> 
> 
> Testing
> -------
> 
> Tested multiple simultaneous holding bridges, multiple channels in the same holding bridge, what would happen if one channel entered as another one was leaving but before the bridge was destroyed, tested bridges emptying out, tested module unload and module load after unload.
> 
> 
> Thanks,
> 
> jrose
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130702/48bcb759/attachment.htm>


More information about the asterisk-dev mailing list