[Asterisk-bugs] [Asterisk 0010245]: Agi in live & dead channels? Don't drop DeadAGI from live.

noreply at bugs.digium.com noreply at bugs.digium.com
Fri Jul 20 08:37:37 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10245 
====================================================================== 
Reported By:                xrg
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10245
Category:                   Resources/res_agi
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.8  
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-20-2007 03:14 CDT
Last Modified:              07-20-2007 08:37 CDT
====================================================================== 
Summary:                    Agi in live & dead channels? Don't drop DeadAGI from
live.
Description: 
According to http://bugs.digium.com/view.php?id=10210, the DeadAGI will be
phased out from working on live
channels. In the a2billing project (www.asterisk2billing.org), DeadAGI is
the core element which calculates destination, dials and after the call
records the call charges, all in one AGI call.

Is there some other AGI method that can manipulate a call both at Dial and
after that?
If no, could you reconsider banning DeadAGI on live channels?
====================================================================== 

---------------------------------------------------------------------- 
 juggie - 07-20-07 08:37  
---------------------------------------------------------------------- 
I'm working on a seriously large update of res_agi (which it badly needs),
however, it will not change the fact that a call to DeadAGI should not keep
running after the channel dies.  What was actually happening was DeadAGI
would never exit on a live channel until the script terminated.  Hence,
your AGI had the ability to block asterisk from entering the h extension to
handle a hangup, clearly this is not the behavior we want.

As Corydon76 stated, AGI() will still tell you about the hangup, it wont
terminate until it does, and then you can either ignore the SIGHUP and not
exit and clean up, or rerun your script again in DeadAGI on the h
extension.  Obviously all the channel variables will still be available, so
it is only a matter of launching your script again. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-20-07 08:37  juggie         Note Added: 0067625                          
======================================================================




More information about the asterisk-bugs mailing list