Fix recalled party B feature flags for a failed DTMF atxfer.
authorRichard Mudgett <rmudgett@digium.com>
Wed, 25 Apr 2012 01:26:44 +0000 (01:26 +0000)
committerRichard Mudgett <rmudgett@digium.com>
Wed, 25 Apr 2012 01:26:44 +0000 (01:26 +0000)
commit7f0dce3bd1f1b2d520ac8e4cd96903513a7b40ab
tree90e1915121c69d65db2cfb45dc46cdcbc11c3187
parent56d10c56779c48a4118bfeab2a5a8a7d33055609
Fix recalled party B feature flags for a failed DTMF atxfer.

1) B calls A with Dial option T
2) B DTMF atxfer to C
3) B hangs up
4) C does not answer
5) B is called back
6) B answers
7) B cannot initiate transfers anymore

* Add dial features datastore to recalled party B channel that is a copy
of the original party B channel's dial features datastore.

* Extracted add_features_datastore() from add_features_datastores().

* Renamed struct ast_dial_features features_caller and features_callee
members to my_features and peer_features respectively.  These better names
eliminate the need for some explanatory comments.

* Simplified code accessing the struct ast_dial_features datastore.

(closes issue ASTERISK-19383)
Reported by: lgfsantos
........

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

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

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