res_pjsip_refer: Fix issue where native bridge may not occur upon completion of a...
authorJoshua Colp <jcolp@digium.com>
Tue, 2 Dec 2014 12:21:34 +0000 (12:21 +0000)
committerJoshua Colp <jcolp@digium.com>
Tue, 2 Dec 2014 12:21:34 +0000 (12:21 +0000)
commit0c1aaa7da524eb4305d8f8c3d8762f38fcf17919
tree347c54e561e25596d3bd946bcd2843268e07d0bc
parentf128ff61ab8f1f2df00a63c1322baa179f9b9b7c
res_pjsip_refer: Fix issue where native bridge may not occur upon completion of a transfer.

There are two methods within res_pjsip_refer for keeping track of the state of a transfer.
The first is a framehook which looks at frames passing by to determine the state. The second
subscribes to know when the channel joins a bridge. In the case when the channel joins the
bridge the framehook is *NOT* removed and this prevents the native RTP bridging technology
from getting used.

This change gets the channel and if it still exists remove the framehook.

Review: https://reviewboard.asterisk.org/r/4218/
........

Merged revisions 428760 from http://svn.asterisk.org/svn/asterisk/branches/12
........

Merged revisions 428761 from http://svn.asterisk.org/svn/asterisk/branches/13

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@428762 65c4cc65-6c06-0410-ace0-fbb531ad65f3
res/res_pjsip_refer.c