Fix DTMF blind transfer continuing to execute dialplan after transfer.
authorRichard Mudgett <rmudgett@digium.com>
Thu, 13 Oct 2011 23:08:48 +0000 (23:08 +0000)
committerRichard Mudgett <rmudgett@digium.com>
Thu, 13 Oct 2011 23:08:48 +0000 (23:08 +0000)
commitcabf08b511211902d1df13c3a16cdd5c18a68aad
tree33bbabda749b10234925f9e80cab1ab499836ebb
parentd0ab521e613a4d57f29d46b14fa3a335346883a6
Fix DTMF blind transfer continuing to execute dialplan after transfer.

Party A calls Party B.
Party A DTMF blind transfers Party B to Party C.
Party A channel continues to execute dialplan.

* Fixed the return value of builtin_blindtransfer() to return the correct
value after a transfer so the dialplan will not keep executing.

* Removed unnecessary connected line update that did not really do
anything.

* Made access to GOTO_ON_BLINDXFR thread safe in check_goto_on_transfer().

* Fixed leak of xferchan for failure cases in check_goto_on_transfer().

* Updated debug messages in builtin_blindtransfer() and
check_goto_on_transfer().

(closes issue ASTERISK-18275)
Reported by: rmudgett
Tested by: rmudgett
........

Merged revisions 340809 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........

Merged revisions 340810 from http://svn.asterisk.org/svn/asterisk/branches/10

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@340813 65c4cc65-6c06-0410-ace0-fbb531ad65f3
main/features.c