summaryrefslogtreecommitdiff
path: root/include/asterisk
diff options
context:
space:
mode:
authorJoshua Colp <jcolp@digium.com>2017-02-27 13:02:38 +0000
committerJoshua Colp <jcolp@digium.com>2017-02-27 13:02:38 +0000
commiteac818801b8d566138791550329326ac5c84fb83 (patch)
treef1c32e2207d216878ff5d606982c46a26e3b5841 /include/asterisk
parent9d3ab062cccc5d545648dd65beb817c37f439c2f (diff)
bridge_native_rtp: Handle case where channel joins already suspended.
The bridge_native_rtp module did not properly handle the case where a smart bridge operation occurs while a channel is suspended. In this scenario the module would incorrectly set up local or remote RTP bridging despite the media having to flow through Asterisk. The remote endpoint would see two media streams and experience wonky audio. The module has been changed so that it ensures both channels are not suspended when performing the native RTP bridging and this requirement has been documented in the bridge technology. ASTERISK-26781 Change-Id: Id4022d73ace837d4a293106445e3ade10dbc7c7c
Diffstat (limited to 'include/asterisk')
-rw-r--r--include/asterisk/bridge_technology.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/include/asterisk/bridge_technology.h b/include/asterisk/bridge_technology.h
index 7f5d746f8..402b54e98 100644
--- a/include/asterisk/bridge_technology.h
+++ b/include/asterisk/bridge_technology.h
@@ -110,6 +110,9 @@ struct ast_bridge_technology {
*
* \note The bridge technology must tollerate a failed to join channel
* until it can be kicked from the bridge.
+ *
+ * \note A channel may be in a suspended state already when joining a bridge
+ * technology. The technology must handle this case.
*/
int (*join)(struct ast_bridge *bridge, struct ast_bridge_channel *bridge_channel);
/*!