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

[noreply at bugs.digium.com]

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 15:12 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?
====================================================================== 

---------------------------------------------------------------------- 
 xrg - 07-20-07 15:12  
---------------------------------------------------------------------- 
What you are saying in fact is that there is no way that a script could
replace the dialplan logic. For example, the a2billing script would redial
(using a different trunk) if the first dial failed.
Being able to write advanced dialplan scripts on procedural languages was
such a nice feature. I recognize that dialplan is sometimes not a
procedural matter that other langs could handle, but this barrier (of no
script effectively crossing the live/dead channel transition) will limit
things. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-20-07 15:12  xrg            Note Added: 0067656                          
======================================================================