diff options
| author | Mark Michelson <mmichelson@digium.com> | 2012-09-11 21:13:26 +0000 |
|---|---|---|
| committer | Mark Michelson <mmichelson@digium.com> | 2012-09-11 21:13:26 +0000 |
| commit | ae5aaefd88224c20d246087b3e4277b6c97545cb (patch) | |
| tree | ccc3d498b445a2afe5c7ba08020e33d26f706951 /main/message.c | |
| parent | 3e17426e89c62486d03a3fbd8ae654faf479e941 (diff) | |
Fix bad channel application data reference.
When channels get bridged due to an AMI bridge action
or a DTMF attended transfer, the two channels that
get bridged have their application data pointing to
the other channel's name. This means that if one channel
is hung up but the other moves on, it means that the
channel that moves on will have its application data
pointing at freed memory.
(issue ASTERISK-20335)
Reported by: aragon
........
Merged revisions 372840 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........
Merged revisions 372841 from http://svn.asterisk.org/svn/asterisk/branches/10
........
Merged revisions 372886 from http://svn.asterisk.org/svn/asterisk/branches/11
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@372887 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'main/message.c')
0 files changed, 0 insertions, 0 deletions