[asterisk-bugs] [Asterisk 0010315]: res_agi behaviour change in 1.2 & 1.4

noreply at bugs.digium.com noreply at bugs.digium.com
Thu Jul 26 23:07:52 CDT 2007


The following issue has been set as RELATED TO issue 0010035. 
====================================================================== 
http://bugs.digium.com/view.php?id=10315 
====================================================================== 
Reported By:                juggie
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   10315
Category:                   Resources/res_agi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.9  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-26-2007 23:05 CDT
Last Modified:              07-26-2007 23:07 CDT
====================================================================== 
Summary:                    res_agi behaviour change in 1.2 & 1.4
Description: 
This effects i believe 1.2.20+ and 1.4.8+

While this is not the 'accepted behavior' deadagi has been used alot to
run agi's on a live channel when a user does not want the script to exit
when a hangup has been detected.  This was used with the popular package
a2billing 
(http://trac.asterisk2billing.org) and as a result i've seen alot of
complaints in #asterisk about it.

When i finally had time to follow up on the problem it turns out to be a
change in handle_exec within res_agi which was due to bug
http://bugs.digium.com/view.php?id=10035.

http://svn.digium.com/view/asterisk/branches/1.2/res/res_agi.c?r1=71065&r2=71656

This issue has already been solved in trunk as res_agi will no longer
close the control connection when it sends a sighup.  Should we backport
that fix? or just revert the original behavior of returning whatever the
application returns.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0010035 Agi exits without any possibility to ca...
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-26-07 23:07  juggie         Relationship added       related to 0010035  
======================================================================




More information about the asterisk-bugs mailing list