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

Asterisk Bug Tracker noreply at bugs.digium.com
Mon May 9 14:07:03 CDT 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16106 
====================================================================== 
Reported By:                ajohnson
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   16106
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.0-rc3 
JIRA:                       SWP-392 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-10-20 16:09 CDT
Last Modified:              2011-05-09 14:07 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.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016548 [patch][regression] Macro executes &quo...
====================================================================== 

---------------------------------------------------------------------- 
 (0134687) svnbot (reporter) - 2011-05-09 14:07
 https://issues.asterisk.org/view.php?id=16106#c134687 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 318282

U   branches/1.8/main/features.c

------------------------------------------------------------------------
r318282 | rmudgett | 2011-05-09 14:07:02 -0500 (Mon, 09 May 2011) | 24
lines

Hangup extension executed twice.

When a user hangs up a call, in certain circumstances, the hangup
extension can end up being executed twice:

1) If a call is bridged and the 'h' extension executes the Hangup
application, then the 'h' extension will be executed twice.

2) If a call is bridged within a macro (Dial or Queue), it has its own 'h'
extension, the main context also has an 'h' extension, and the macro 'h'
extension executes the Hangup application, then both 'h' extensions will
be executed.

* Revert originally commited fix for
https://issues.asterisk.org/view.php?id=16106 and just set
AST_FLAG_BRIDGE_HANGUP_RUN unconditionally in ast_bridge_call().  The
bridge code just executed an 'h' extension so the main PBX loop does not
need to execute one as well.

(issue https://issues.asterisk.org/view.php?id=16106)
Reported by: ajohnson

(issue https://issues.asterisk.org/view.php?id=16548)
Reported by: hajekd

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=318282 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-09 14:07 svnbot         Checkin                                      
2011-05-09 14:07 svnbot         Note Added: 0134687                          
======================================================================




More information about the asterisk-bugs mailing list