When two channels were early bridged in a native_rtp bridge, the RTP description
on one side was not updated when the other side answered.
This patch forbids non-answered channels to enter a native_rtp bridge, and
triggers a bridge reconfiguration when an ANSWER frame is received.
ASTERISK-27257
Change-Id: If1aaee1b4ed9658a1aa91ab715ee0a6413b878df
*/
static int native_rtp_bridge_capable(struct ast_channel *chan)
{
- return !ast_channel_has_hook_requiring_audio(chan);
+ return !ast_channel_has_hook_requiring_audio(chan)
+ && ast_channel_state(chan) == AST_STATE_UP;
}
/*!
*
* \note On entry, bridge is already locked.
*
- * \note The bridge technology must tollerate a failed to join channel
+ * \note The bridge technology must tolerate 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.
+ *
+ * \note A channel may not be answered when joining a bridge technology.
*/
int (*join)(struct ast_bridge *bridge, struct ast_bridge_channel *bridge_channel);
/*!
case AST_CONTROL_ANSWER:
if (ast_channel_state(chan) != AST_STATE_UP) {
ast_answer(chan);
+ ast_bridge_channel_lock_bridge(bridge_channel);
+ bridge_channel->bridge->reconfigured = 1;
+ bridge_reconfigured(bridge_channel->bridge, 0);
+ ast_bridge_unlock(bridge_channel->bridge);
} else {
ast_indicate(chan, -1);
}