Review Board 1.7.16

ARI - allow other operations to happen while bridged

Review Request #2726 - Created July 31, 2013 and submitted

David Lee
mjordan, opticron, rmudgett
This patch changes ARI bridging to allow other channel operations to
happen while the channel is bridged.

ARI channel operations are designed to queue up and execute
sequentially. This meant, though, that while a channel was bridged,
any other channel operations would queue up and execute only after the
channel left the bridge.

This patch changes ARI bridging so that channel commands can execute
while the channel is bridged. For most operations, things simply work
as expected. The one thing that ended up being a bit odd is recording.

The current recording implementation will fail when one attempts to
record a channel that's in a bridge. Note that the bridge itself may
be recording; it's recording a specific channel in the bridge that
fails. While this is an annoying limitation, channel recording is
still very useful for use cases such as voice mail, and bridge
recording makes up much of the difference for other use cases.

We may add a /monitor control for channels, which can start a
MixMonitor on a specific channel. But that would be another patch.
* Played to channel
* Recording to channel
* Put channel in bridge
  * Played to channel
  * Recorded from channel
  * Played to bridge
  * Hungup channel from ARI
  * Hungup channel from client
Description From Last Updated Status
Review request changed
Updated (Aug. 27, 2013, 3:41 p.m.)
  • changed from pending to submitted
Committed in revision 397848 runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA.
Please report problems with this site to