| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2017-09-06 | stasis/control: Fix possible deadlock with swap channel | George Joseph | |
| If an error occurs during a bridge impart it's possible that the "bridge_after" callback might try to run before control_swap_channel_in_bridge has been signalled to continue. Since control_swap_channel_in_bridge is holding the control lock and the callback needs it, a deadlock will occur. * control_swap_channel_in_bridge now only holds the control lock while it's actually modifying the control structure and releases it while the bridge impart is running. * bridge_after_cb is now tolerant of impart failures. Change-Id: Ifd239aa93955b3eb475521f61e284fcb0da2c3b3 | |||
| 2013-07-25 | A great big renaming patch | Matthew Jordan | |
| This patch renames the bridging* files to bridge*. This may seem pedantic and silly, but it fits better in line with current Asterisk naming conventions: * channel is not "channeling" * monitor is not "monitoring" etc. A bridge is an object. It is a first class citizen in Asterisk. "Bridging" is the act of using a bridge on a set of channels - and the API that fulfills that role is more than just the action. (closes issue ASTERISK-22130) git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@395378 65c4cc65-6c06-0410-ace0-fbb531ad65f3 | |||
 |
index : asterisk.git | |
| Unnamed repository; edit this file 'description' to name the repository. | Tzafrir Cohen |
| summaryrefslogtreecommitdiff |