[asterisk-bugs] [Asterisk 0017444]: Stuck channel after asterisk feature attended transfer

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17444 
====================================================================== 
Reported By:                corruptor
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17444
Category:                   Resources/res_features
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.8 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-06-02 07:16 CDT
Last Modified:              2010-06-02 11:19 CDT
====================================================================== 
Summary:                    Stuck channel after asterisk feature attended
transfer
Description: 
There is a bug in asterisk attended feature transfer. It can be reproduced
with fallowing actions.
For example we have 3 SIP phones: 1105, 1102 and 1108

1105 calls 1102 => 1102 answers
1102 presses # to do an attended transfer and dials 1108
While 1108 is ringing 1105 hangs up.
After that 1102 hangs up.
1102 and 1105 have hung up, their channels are destroyed but 1108 is still
ringing. 
1108 answers and of hears silence of course.
1108 hangs up.
Asterisk doesn't destroy all channels. Such channel as
Local/1108 at testcon-5372;1 is stuck forever and can be seen with command
"core show channels".
I can't hang up this channel with "channel request hangup" command.

I upload the full asterisk log of call scenario described above.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-02 11:19 lmadsen        Description Updated                          
======================================================================