DTMF atxfer: Setup recall channels as if the transferee initiated the call.
authorRichard Mudgett <rmudgett@digium.com>
Mon, 22 Dec 2014 21:20:11 +0000 (21:20 +0000)
committerRichard Mudgett <rmudgett@digium.com>
Mon, 22 Dec 2014 21:20:11 +0000 (21:20 +0000)
commit1c0604e9053be15df631ffe59d8e252b71c90adc
treef17829bd67dfad9f36494fef6b11308a9c32f9f1
parent7d954f4cb1a090a04d5ca0478db18f41bab45078
DTMF atxfer: Setup recall channels as if the transferee initiated the call.

After the initial DTMF atxfer call attempt to the transfer target fails to
answer during a blonde transfer, the recall callback channels do not get
setup with information from the initial transferrer channel.  As a result,
the recall callback to the transferrer does not have callid, channel
variables, datastores, accountcode, peeraccount, COLP, and CLID setup.  A
similar situation happens with the recall callback to the transfer target
but it is less visible.  The recall callback to the transfer target does
not have callid, channel variables, datastores, accountcode, peeraccount,
and COLP setup.

* Added missing information to the recall callback channels before
initiating the call.  callid, channel variables, datastores, accountcode,
peeraccount, COLP, and CLID

* Set callid of the transferrer channel on the DTMF atxfer controller
thread attended_transfer_monitor_thread().

* Added missing channel unlocks and props unref to off nominal paths in
attended_transfer_properties_alloc().

ASTERISK-23841 #close
Reported by: Richard Mudgett

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

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

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