[asterisk-bugs] [Asterisk 0015558]: Bridged channels doesn't free after call termination

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15558 
====================================================================== 
Reported By:                kayakru
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15558
Category:                   Core/Channels
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-07-23 03:17 CDT
Last Modified:              2010-06-23 11:47 CDT
====================================================================== 
Summary:                    Bridged channels  doesn't free after call
termination
Description: 
Channel A (all channels - iax2) waiting in queue, channel B and C in some
MeetMe room. I make Bridge between channels A and B by AMI interface,
channel C stay in MeetMe. After termination of the call between A and B -
pair bridged channels still in list of active channels.

If I send soft hangup to one of pair - both channels hangup. In the log I
see that Asterisk after soft hangup continue dialplan execution from
positions where channels was bridged. 
Tested on versions 1.6.1.7-rc1,1.6.0.9,1.6.0.11-rc1  
System - Centos 5.3 x64 
====================================================================== 

---------------------------------------------------------------------- 
 (0123760) lmadsen (administrator) - 2010-06-23 11:47
 https://issues.asterisk.org/view.php?id=15558#c123760 
---------------------------------------------------------------------- 
As this issue is quite old now, is there any chance the reporter can retest
on the latest 1.6.2 version to determine if this is still an issue?

Both 1.6.0 and 1.6.1 branches are now in security only mode and are no
longer receiving maintenance support. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-23 11:47 lmadsen        Note Added: 0123760                          
2010-06-23 11:47 lmadsen        Status                   acknowledged =>
feedback
======================================================================