asterisk users - May 2009 - Asterisk Manager API Action Originate

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

Now in Asterisk 1.4.23 I get some error code 5's but since they're so
few I
tend not to worry.  But what is concerning is the number of Error 0's I
get.  Error 0 is "No Such Extension" (ie, Failure I assume) but my
Provider's CDR log shows "No Answer."  (I would show you my CDR
but it seems
Originate doesn't log in the CDR like every other call for some reason).

Any ideas to correct this issue?  Or is there a better updated version of
that list that would fix my understanding of what the error codes were?

Nicholas Blasgen
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20090511/5fb05feb/attachment.htm

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
Are you referring to the originateresponse event?

Which version of Asterisk?

-- 
Kind Regards,

Matt Riddell
Director
_______________________________________________

http://www.venturevoip.com (Great new VoIP end to end solution)
http://www.venturevoip.com/news.php (Daily Asterisk News - html)
http://www.venturevoip.com/newrssfeed.php (Daily Asterisk News - rss)

On Mon, 2009-05-11 at 20:44 -0700, Nicholas Blasgen
wrote:
> (I would show you my CDR but it seems Originate doesn't log in the CDR
> like every other call for some reason).
Try testing with "unanswered=yes" in your CDR.  If that still does not
fix the problem, this is probably a bug. Test with the latest SVN (a
similar bug was recently fixed), and if you still see the problem, open
a new issue.
-- 
Matthew Nicholson
Digium, Inc. | Software Developer