[asterisk-bugs] [Asterisk 0016239]: AMD() incorrectly sets AMDCAUSE channel variable

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16239 
====================================================================== 
Reported By:                CGMChris
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16239
Category:                   Applications/app_amd
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.26.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-12 17:10 CST
Last Modified:              2009-11-13 07:52 CST
====================================================================== 
Summary:                    AMD() incorrectly sets AMDCAUSE channel variable
Description: 
If, as SOON as the phone rings (you have to be really quick!) you pickup
and hangup as fast as you can (preferably using a button instead of a
handset), the AMDCAUSE channel variable is first set to HANGUP and then
immediately changed to TOOLONG.

I am calling AMD() from an AGI() script...and my AGI script continues to
execute to completion as if the channel was still active (rather than
immediately exiting on hangup), if and only if the hangup occurs extremely
quickly.  There may be a more severe underlying channel problem that 
supersedes AMD().

My "dialpan" is as follows:
$engine->agi->exec('Answer','');
$engine->agi->exec('Background','silence/0');
$engine->agi->exec('AMD','');

The AGI script is launched using AMI and the Originate command.  It may
also be note worthy that I am using SIP on both end-points.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-13 07:52 lmadsen        version                  1.4.26 =>           
2009-11-13 07:52 lmadsen        Description Updated                          
2009-11-13 07:52 lmadsen        Additional Information Updated                  
 
======================================================================