[asterisk-bugs] [Asterisk 0014811]: DeadAGI at h extension

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14811 
====================================================================== 
Reported By:                hoaianh
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14811
Category:                   Resources/res_agi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.24 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-02 07:54 CDT
Last Modified:              2009-04-08 10:31 CDT
====================================================================== 
Summary:                    DeadAGI at h extension
Description: 
I make outgoing call with the context

[out]
exten => s,1,Anser()
exten => s,n,Playback(tt-weasels)
exten => s,n,Dial(ss7/out/123456789)
exten => s,n,Hangup()

exten => h,1,DeadAgi(agi://agi-server/script)

The problem is when leg A is hang up it works fine but if leg B is hang up
I get 
--> deadagi_exec: Running DeadAGI on a live channel will cause problems,
please use AGI

This one seems to be very close to issue 0014624 but the major difference
is that always happens.

On another box with 1.4.19.2 it works just fine.


====================================================================== 

---------------------------------------------------------------------- 
 (0102907) juggie (manager) - 2009-04-08 10:31
 http://bugs.digium.com/view.php?id=14811#c102907 
---------------------------------------------------------------------- 
hoaianh,

I dont think the behaviour of the call should of changed, only the warning
in the older release of 1.4.19 (before it was added) should not show up.

If you can confirm that the actual behaviour has changed then we may have
an issue, but if you are just seeing the warning in one version and not in
he other that is just cosmetic, let us know. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-08 10:31 juggie         Note Added: 0102907                          
======================================================================