I realize I haven't exhausted my attempt for clarification on the Asterisk Users group, but the more I trouble shoot this the more clear it is to be that this is either a bug or a "feature" and that the Users group would be of no help. Before I report this on the Asterisk Issue Tracker, I thought I would check with the Developers mailing list first.<br>
<br>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 code of ZERO and Failure as the reason. I should be getting a "No Answer" response instead (at least in my mind a timeout should not be a failure).<br>
<br>I've tested on the following platforms:<br><br>Asterisk 1.4.23<br>Asterisk 1.4.24.1<br>Asterisk 1.4 r191778<br>
Asterisk 1.4 r193870<br><br>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.<br>
<br clear="all">Nicholas Blasgen<br>Partner / Network Operations<br>Refractive Dialer LLC<br>415.692-5277 (w)<br>408.497.9796 (c)<br>
<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Nicholas Blasgen</b> <span dir="ltr"><<a href="mailto:nicholas@refractivedialer.com">nicholas@refractivedialer.com</a>></span><br>
Date: Tue, May 12, 2009 at 11:48 AM<br>Subject: Re: [asterisk-users] Asterisk Manager API Action Originate<br>To: Asterisk Users Mailing List - Non-Commercial Discussion <<a href="mailto:asterisk-users@lists.digium.com">asterisk-users@lists.digium.com</a>><br>
<br><br>Matt & Others,<br><br>So to continue the issue, here's what I've learned.<br><br>Tested on Asterisk:<br><br>1.4.24.1<br>SVN 193870<br>SVN 191778<br><br>So I think that covers most everything. What I've learned is that any Timeout sends back a response code of ZERO instead of what I would have expected, ONE. Anyone offer any other suggestions to try?<br>
<br>My way to test this was to make a simple script to perform an AMI Originate call with a 4 second timeout. I then have a standard tool to display all AMI Events. On every system I tried I would get Response of "Failure" and Error Code of ZERO.<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Tue, May 12, 2009 at 10:13 AM, Nicholas Blasgen <span dir="ltr"><<a href="mailto:nicholas@refractivedialer.com" target="_blank">nicholas@refractivedialer.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Matt,<br><br>Oh, I thought it was Asterisk 1.4.23 like I wrote in my first email, but turns out to be Asterisk SVN-branch-1.4-r191778.<br>
<br>But yes, I am talking about originateresponse. I'm going to do some more debugging today to see if I can get the more information about the issue. When I either Originate from the CLI or from AMI, I don't get anything on the console for either the errors or the initial connection. I've had a lot of issues trying to debug Originate as a result. And no CDR logs are being recorded.<div>
<div></div><div><br>
<br><div class="gmail_quote">On Tue, May 12, 2009 at 5:36 AM, Matt Riddell <span dir="ltr"><<a href="mailto:lists@venturevoip.com" target="_blank">lists@venturevoip.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On 12/05/2009 3:44 p.m., Nicholas Blasgen wrote:<br>
> Has anyone else had issues with Originate returning the wrong error<br>
> code? According to the docs, the following errors are supposed to be<br>
> returned:<br>
><br>
> 0 = no such extension or number<br>
> 1 = no answer<br>
> 4 = answered<br>
> 8 = congested or not available<br>
<br>
</div>Are you referring to the originateresponse event?<br>
<br>
Which version of Asterisk?<br></blockquote></div><br>
</div></div></blockquote></div><br>
</div></div></div><br>