[asterisk-bugs] [Asterisk 0015104]: Asterisk Manager API Action Originate / OriginateResponse

[Asterisk Bug Tracker]

The following issue has been SUBMITTED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15104 
====================================================================== 
Reported By:                nblasgen
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15104
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
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-05-13 22:16 CDT
Last Modified:              2009-05-13 22:16 CDT
====================================================================== 
Summary:                    Asterisk Manager API Action Originate /
OriginateResponse
Description: 
I have the following issue.  When placing an outbound call with Asterisk
Manager's Originate command, if the call times out, I get an
OriginateResponse reason of `0` and `Failure` as the response.  I should be
getting a "No Answer" response instead (code `4`) (at least in my mind a
timeout should not be a failure).

I've tested on the following platforms:

Asterusj 1.4.20
Asterisk 1.4.23
Asterisk 1.4.24.1
Asterisk 1.4 r191778
Asterisk 1.4 r193870

My test method was to initiate a Originate call to myself (Asterisk -> SIP
-> PSTN) with a short 4 second timeout and look at the OriginateResponse
that came back 4 seconds after starting that call.  ASYNC is set to True.

Can someone tell me if this is really the expected outcome of a timeout? 
I expect a Failure to mean the call was rejected by the remote side.  And
since someone will end up looking into this, can we maybe get an update to
the different "reason" codes?
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-13 22:16 nblasgen       New Issue                                    
2009-05-13 22:16 nblasgen       Asterisk Version          => 1.4.24          
2009-05-13 22:16 nblasgen       Regression                => No              
2009-05-13 22:16 nblasgen       SVN Branch (only for SVN checkouts, not tarball
releases) => N/A             
======================================================================