On Wed, Feb 2, 2011 at 3:51 PM, Bogdan-Andrei Iancu wrote:
> Hi Brett,
>
> The error log you get is triggered when the internal function
> "next_branches" returns false (a negative code). This is when:
> - function called from wrong route type (like for a reply)
> - there are no more branches
On Feb 2, 2011, at 4:51 PM, Bogdan-Andrei Iancu wrote:
> Hi Brett,
>
> The error log you get is triggered when the internal function "next_branches"
> returns false (a negative code). This is when:
> - function called from wrong route type (like for a reply)
> - there are no more branches l
On Feb 2, 2011, at 4:54 PM, Bogdan-Andrei Iancu wrote:
>> next_branches actually never returns false (0) as a result of SVN trunk
>> commit 7248, so you'll never hit your t_reply call.
>>
>
> Actually next_branches() do return false (which is -1, not 0) - see my
> previous email.
So it does
Hi Andrew,
Andrew Mortensen wrote:
On Jan 29, 2011, at 11:53 AM, Brett Nemeroff wrote:
All,
I'm routing calls using 3XX redirects. I serialize the branches. I immediately
call a next_branches() and arm a failure_route. In the failure route I do
something like:
if (!next_branche
Hi Brett,
The error log you get is triggered when the internal function
"next_branches" returns false (a negative code). This is when:
- function called from wrong route type (like for a reply)
- there are no more branches left
- internal error
I guess in your case, the second case (w
On Jan 29, 2011, at 11:53 AM, Brett Nemeroff wrote:
> All,
>
> I'm routing calls using 3XX redirects. I serialize the branches. I
> immediately call a next_branches() and arm a failure_route. In the failure
> route I do something like:
>
>
> if (!next_branches()) {
>
All,
I'm routing calls using 3XX redirects. I serialize the branches. I
immediately call a next_branches() and arm a failure_route. In the failure
route I do something like:
if (!next_branches()) {
t_reply("503","Service Unavailable ");
exit;
}
To
