bridge_native_rtp: Fix native bridge tech being incompatible when it should be.
authorJonathan Rose <jrose@digium.com>
Tue, 11 Jun 2013 22:21:36 +0000 (22:21 +0000)
committerJonathan Rose <jrose@digium.com>
Tue, 11 Jun 2013 22:21:36 +0000 (22:21 +0000)
commit723a84dbd98a63951bccdea6b71a0d6c1243ecbe
tree1fb35f5b6cb75f179996423224bc58020cc858b5
parenta1f45147c97128bdbc733b5cfa44b53573cb4619
bridge_native_rtp: Fix native bridge tech being incompatible when it should be.

When checking compatability for the native RTP bridge technology there is a
race condition between clearing framehooks that are destroyed when leaving
certain bridges with certain technologies (such as bridge_native_rtp) and
joining bridges with the bridge_native_rtp technology. Yes, that means a
channel in a native RTP bridge could move to another native RTP bridge and
be considered incompatible with the new native RTP bridge causing it to
revert to a simple bridge technology0. This fixes that bug by ignoring
framehooks that have been marked for destruction when checking for
compatibility with the bridge_native_rtp technology.

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@391453 65c4cc65-6c06-0410-ace0-fbb531ad65f3
bridges/bridge_native_rtp.c
include/asterisk/framehook.h
main/framehook.c