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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15104 
====================================================================== 
Reported By:                nblasgen
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   15104
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.24 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-05-13 22:16 CDT
Last Modified:              2009-10-09 13:39 CDT
====================================================================== 
Summary:                    [patch] 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?
====================================================================== 

---------------------------------------------------------------------- 
 (0112143) svnbot (reporter) - 2009-10-09 13:39
 https://issues.asterisk.org/view.php?id=15104#c112143 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 223276

_U  branches/1.6.0/
U   branches/1.6.0/main/channel.c

------------------------------------------------------------------------
r223276 | mnicholson | 2009-10-09 13:39:41 -0500 (Fri, 09 Oct 2009) | 21
lines

Merged revisions 223273 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

................
  r223273 | mnicholson | 2009-10-09 13:34:08 -0500 (Fri, 09 Oct 2009) | 14
lines
  
  Merged revisions 223225 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r223225 | mnicholson | 2009-10-09 13:20:11 -0500 (Fri, 09 Oct 2009) |
8 lines
    
    Signal timeouts by returning AST_CONTROL_RINGING when originating
calls.
    (closes issue https://issues.asterisk.org/view.php?id=15104)
    Reported by: nblasgen
    Patches:
          manager-timeout1.diff uploaded by mnicholson (license 96)
    Tested by: nblasgen, mnicholson
  ........
................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=223276 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-09 13:39 svnbot         Note Added: 0112143                          
======================================================================