Not sure if it is documented, but iirc, failed transactions accounting
reports each stage of a failed forwarding (i.e., each final negative
reply received for a transactions is reported).
Try:
modparam("acc", "failed_transaction_flag", 4)
And in failure route before t_reply(480...) do
setflag(4);
See if this way is reported only once.
Be sure flag 4 is not used for something else, of if it used then use an
unused one.
Cheers,
Daniel
On 1/18/11 11:41 AM, Mino Haluz wrote:
These are my modparams.
modparam("acc", "failed_transaction_flag", 1)
modparam("acc", "report_cancels", 1)
modparam("acc", "report_ack", 0)
modparam("acc", "early_media", 0)
modparam("acc", "log_level", 5)
modparam("acc", "log_flag", 1)
modparam("acc", "log_missed_flag", 1)
modparam("acc", "radius_config",
"/etc/radiusclient-ng/radiusclient.conf") # This is the
location of the configuration file of radius client
modparam("acc", "radius_flag", 1)
modparam("acc", "radius_missed_flag", 1)
Packet 408 is not sent to the caller, ony my 480.
And this is my failroute once more:
failure_route[FAIL_ONE] {
if (t_is_canceled()) {
exit;
}
if (t_check_status("408|480")) {
t_reply("480","Temporarily unavailable");
exit;
}
}
On Tue, Jan 18, 2011 at 11:27 AM, Daniel-Constantin Mierla
<mico...@gmail.com> wrote:
Do you have failed transaction accounting enabled?
Can you watch the sip traffic (ngrep, wireshark), is the 408 sent to caller
as well?
Cheers,
Daniel
On 1/18/11 10:54 AM, Mino Haluz wrote:
So
failure_route[FAIL_ONE] {
...
if (t_check_status("408")) {
t_reply("480","Temporarily Unavailable");
exit;
}
}
Thank you, but I am encountering particular problem, that there are 2
messages stored in the radius, the original 408 and my 480 Temporarily
unavailabe. Can I force to do not write that original 408 to radius?
On Fri, Jan 14, 2011 at 10:39 AM, Klaus Darilion
<klaus.mailingli...@pernau.at> wrote:
Am 14.01.2011 10:28, schrieb Mino Haluz:
Hi,
I would like to force kamailio to send another code as Request timeout
when fr invite timeout is hit. Is there some nice way how to achieve it,
or I have to edit the code ? :(
activate a failure route: t_on_failure("foo")
then in failure route check for the status (e.g. 408):
failure_route[foo] {
...
if (t_check_status("487")) {
t_reply("499","or what ever you want");
exit;
}
...
}
regards
klaus
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA
http://www.asipto.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA
http://www.asipto.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
