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 th
The response code corresponds directly to the control frame types in
frame.h. The code will be different depending on the technology used to
dial. The 0 code is some sort of failure not involving any other
control frames. Usually timeout is 3 (RINGING). I have provided a list
taken from frame.h
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 o
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 Origina
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 availa
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 t
