[asterisk-bugs] [Asterisk 0016106]: [patch] Hangup extension executed twice in 1.6.2 RC2

[Asterisk Bug Tracker]

The following issue is now READY FOR REVIEW. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16106 
====================================================================== 
Reported By:                ajohnson
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16106
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for review
Target Version:             1.6.2.1
Asterisk Version:           1.6.2.0-rc3 
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-10-20 16:09 CDT
Last Modified:              2009-10-30 11:04 CDT
====================================================================== 
Summary:                    [patch] Hangup extension executed twice in 1.6.2 RC2
Description: 
When a user hangs up a call, in certain circumstances, the hangup extension
can end up being executed twice.

If I comment out this section of my dialplan, the hangup extension is only
executed once:

exten => _X.,n,Goto(s-${DIALSTATUS})

exten => s-CONGESTION,1,Congestion(5)
exten => s-BUSY,1,Busy(5)
exten => s-.,1,Congestion(5)

Otherwise, the hangup extension is executed twice.  The odd thing is that
the console output does not display that the code above is being executed.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-30 11:04 ebroad         Status                   ready for testing =>
ready for review
======================================================================