[asterisk-bugs] [Asterisk 0014624]: 1.4.23.1 DeadAGI() in "h" extension

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14624 
====================================================================== 
Reported By:                acunningham
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14624
Category:                   General
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     feedback
Target Version:             1.4.25
Asterisk Version:           1.4.23 
Regression:                 Yes 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-08 19:22 CDT
Last Modified:              2009-03-09 23:44 CDT
====================================================================== 
Summary:                    1.4.23.1 DeadAGI() in "h" extension
Description: 
The following worked correctly on 1.4.21.1 and older:

exten => h, 1, DeadAGI(agi://127.0.0.1/end)

but on 1.4.23.1 sometimes gives:

    -- Executing [h at from-external:1] DeadAGI("SIP/1.2.3.4-406c3838",
"agi://127.0.0.1/end") in new stack
[Mar  8 20:17:20] WARNING[19208]: res_agi.c:2158 deadagi_exec: Running
DeadAGI on a live channel will cause problems, please use AGI

Changing to:

exten => h, 1, AGI(agi://127.0.0.1/end)

sometimes gives the converse warning about running AGI on a dead channel.
Is Asterisk sometimes calling the DeadAGI before really hanging up the
call?
====================================================================== 

---------------------------------------------------------------------- 
 (0101444) acunningham (reporter) - 2009-03-09 23:44
 http://bugs.digium.com/view.php?id=14624#c101444 
---------------------------------------------------------------------- 
Looking deeper in the logs on a 1.4.21.1 machine, you're right - it's
happening there too.

Is it possible to have the update done that was done for 1.6 back-ported
to 1.4? We are not able to guarantee that the call will have been hung up
by other means before reaching the "h" extension as this is not always in
our control. At present we're damned if we do use DeadAGI and damned if we
don't. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-09 23:44 acunningham    Note Added: 0101444                          
======================================================================