THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#52 - pv argument support for route() function
User who did this - Andrei Pelinescu-Onciul (andrei)
Reason for closing: Implemented
Additional comments about closing: GIT#d75db62
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=52
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#52 - pv argument support for route() function
User who did this - Andrei Pelinescu-Onciul (andrei)
----------
I've just added support for generic rvalue expressions (see GIT#d75db62).
E.g.: route("foo"+$i) or route((a)received.proto +"_proto_"+$var(route_set)) will work now.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=52#comment50
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#51 - route is not called and no error is produced
User who did this - Andrei Pelinescu-Onciul (andrei)
Reason for closing: Fixed
Additional comments about closing: Fixed in GIT#0a3ab1.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=51
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#51 - route is not called and no error is produced
User who did this - Andrei Pelinescu-Onciul (andrei)
----------
Ok, now it won't start if a route does no exist, e.g.:
ERROR: <core> [route.c:1030]: route "foo" not found at /home/andrei/sr.git/while.cfg:37
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=51#comment49
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#46 - return does not work when called inside while statement
User who did this - Andrei Pelinescu-Onciul (andrei)
Reason for closing: Fixed
Additional comments about closing: Fixed in GIT#0a3ab1.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=46
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#46 - return does not work when called inside while statement
User who did this - Andrei Pelinescu-Onciul (andrei)
----------
Thanks, should be fixed in GIT#0a3ab1.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=46#comment48
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi, this is a common issue reported by other users. Imagine I do
failover between two gateways based on request timeout:
------------------------------
failure_route[FAILURE_ROUTE_OUT] {
# Locally generated 408 due to transaction timeout:
if (t_local_replied("last") && $T_reply_code==408) {
xlog("L_ERROR", "_ERROR_ $T_reply_code local replied => failover\n");
... do failover ...
}
}
------------------------------
The above code runs when the gateway-1 doesn't reply at all so
"fr_timer" expires (let's say 5 seconds).
The problem is that such code also runs when no final response at all
is received from gateway-1 in "fr_inv_timer" (let's say 150 seconds).
This is, 408 is locallly generated even if the proxy has received
provisional responses for such transaction.
Main problem this originates is the fact that the list of gateways
could end without any of them giving a final reply, and when no more
gateways are available it's common to reply 500/503 to the client.
Two workarounds:
a) When no more gateways are available inspect if $T_reply_code==408
and then reply 408 rather than 500/503.
I don't like it as if no one gateways has replied a provisional
response in "fr_timer" then I have a *real* problem and I should reply
500/503.
b) Enable a flag(PROVISIONAL_RECEIVED) when a provisional response is
received and then reply 408/480 when no more gateways are available.
Anyhow, there should be (IMHO) a in-built way to determine if the 408
occurs after "fr_timer" or "fr_inv_timer". Do I miss something? do you
consider this a real need?
Regards.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>