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

jrose reviewboard at asterisk.org
Wed Jul 3 11:40:16 CDT 2013

This is an automatically generated e-mail. To reply, visit:

(Updated July 3, 2013, 4:40 p.m.)

Review request for Asterisk Developers, Matt Jordan and rmudgett.


Address Mark's comments

Bugs: ASTERISK-21922

Repository: Asterisk


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 (updated)

  /trunk/apps/app_bridgewait.c 393517 
  /trunk/include/asterisk/bridging.h 393517 
  /trunk/main/bridging.c 393517 

Diff: https://reviewboard.asterisk.org/r/2642/diff/


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.



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

More information about the asterisk-dev mailing list