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.<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">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 class="im">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>