[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 23 11:26:04 CDT 2013
> On July 16, 2013, 10:33 p.m., rmudgett wrote:
> > /trunk/main/bridging.c, line 3057
> > <https://reviewboard.asterisk.org/r/2642/diff/7/?file=41488#file41488line3057>
> >
> > Please start putting a blank line between variable declarations and subsequent code. It makes locating declarations a little easier.
I'll add that to my ever-growing lexicon of things to check before posting reviews from now on.
- jrose
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2642/#review9139
-----------------------------------------------------------
On July 15, 2013, 8:40 p.m., jrose wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2642/
> -----------------------------------------------------------
>
> (Updated July 15, 2013, 8:40 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 394388
> /trunk/include/asterisk/bridging.h 394388
> /trunk/main/bridging.c 394388
>
> 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/20130723/6f26e4ae/attachment.htm>
More information about the asterisk-dev
mailing list