Posted: Tue May 12, 2009 7:16 pm Post subject: [asterisk-dev] Asterisk Manager API Action Originate
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.
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).
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.
Nicholas Blasgen
Partner / Network Operations
Refractive Dialer LLC
415.692-5277 (w)
408.497.9796 (c)
---------- Forwarded message ----------
From: Nicholas Blasgen <nicholas@refractivedialer.com (nicholas@refractivedialer.com)>
Date: Tue, May 12, 2009 at 11:48 AM
Subject: Re: [asterisk-users] Asterisk Manager API Action Originate
To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users@lists.digium.com (asterisk-users@lists.digium.com)>
Matt & Others,
So to continue the issue, here's what I've learned.
Tested on Asterisk:
1.4.24.1
SVN 193870
SVN 191778
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?
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.
On Tue, May 12, 2009 at 10:13 AM, Nicholas Blasgen <nicholas@refractivedialer.com (nicholas@refractivedialer.com)> wrote:
Quote:
Matt,
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.
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.
On Tue, May 12, 2009 at 5:36 AM, Matt Riddell <lists@venturevoip.com (lists@venturevoip.com)> wrote:
Quote:
On 12/05/2009 3:44 p.m., Nicholas Blasgen wrote:
> Has anyone else had issues with Originate returning the wrong error
> code? According to the docs, the following errors are supposed to be
> returned:
>
> 0 = no such extension or number
> 1 = no answer
> 4 = answered
> 8 = congested or not available
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum