bridge_native_rtp: Handle case where channel joins already suspended.
authorJoshua Colp <jcolp@digium.com>
Mon, 27 Feb 2017 13:02:38 +0000 (13:02 +0000)
committerJoshua Colp <jcolp@digium.com>
Mon, 27 Feb 2017 18:12:22 +0000 (12:12 -0600)
commitff2b4308d1ab605861fb7a0931dc36ae1edff9fc
tree5be2e53fed5d4b81b3b6a0d42c06dc726860f661
parentdf22d297a64ee2ef53ea0296a353a5c90ae70ba2
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
bridges/bridge_native_rtp.c
include/asterisk/bridge_technology.h