Guys,
I'm getting this error on the logs for failure route but just for some of the calls I pass. If I call afterwards to that number it rings OK, so it is a random event:
ERROR:carrierroute:cr_load_next_domain: during set_next_domain_recursor, prefix '1054111547533610', carrier 2, domain 1
I'm filling carrierfailureroute with an empty string when I want taht route to be the final one; is it OK to do that?
Thanks in advance, Uriel
One more piece of info, I found out that cr_next_domain is failing when i reach the last carrier failure route.
I'm loading this on carrierroute and carrierfailureroute: CR 5544 2 0 105411609187 0 0 120 4 192.168.200.23 900210540 J10 5545 2 1 105411609187 0 0 30 4 192.168.200.14 900210540 J10 CFR 9240 2 0 105411609187 192.168.200.23 ... 0 0 1 J10 9241 2 1 105411609187 192.168.200.14 ... 0 0 J10
This is what I get on syslog:
Mar 26 10:16:23 cc1pri /usr/local/sbin/kamailio[25163]: Carrier encontrado; ruteando sip:9002105401160918752@192.168.200.23sip%3A9002105401160918752@192.168.200.23 Mar 26 10:16:23 cc1pri /usr/local/sbin/kamailio[25163]: Carrier fallo ruteando sip:9002105401160918752@192.168.200.23sip%3A9002105401160918752@192.168.200.23 Mar 26 10:16:23 cc1pri /usr/local/sbin/kamailio[25163]: Se encontre otro carrier para rutear 9002105401160918752 Mar 26 10:16:23 cc1pri /usr/local/sbin/kamailio[25163]: Carrier fallo ruteando sip:9002105401160918752@192.168.200.14sip%3A9002105401160918752@192.168.200.14 Mar 26 10:16:23 cc1pri /usr/local/sbin/kamailio[25163]: ERROR:carrierroute:cr_load_next_domain: during set_next_domain_recursor, prefix '10541160918752', carrier 2, domain 1
Using this peace of code:
route[2] {
t_on_failure("2"); t_relay(); exit; }
route[20] {
# ----- Rutear menasje con CR -----
$avp(s:rutaindice) := 0; if(!cr_route("$avp(s:routeTree)", "$avp(s:rutaindice)", "$oU", "$oU", "call_id", "$avp(s:cr_host)")) { sl_send_reply("480", "Temporarily unavailable"); } else { xlog("L_ERR", "Carrier encontrado; ruteando $ru\n"); route(2); }; }
failure_route[2] {
# ----- Re-Rutear menasje con CR -----
xlog("L_ERR", "Carrier fallo ruteando $ru\n"); if (t_check_status("408|404|5[0-9][0-9]|6[0-9][0-9]")) { if (!cr_next_domain("$avp(s:routeTree)", "$avp(s:rutaindice)", "$oU", "$avp(s:cr_host)", "$T_reply_code", "$avp(s:cfr_domain)")) { t_reply("404", "Not found"); exit; };
$avp(s:rutaindice) = $avp(s:cfr_domain);
if(!cr_route("$avp(s:routeTree)", "$avp(s:rutaindice)", "$oU", "$oU", "call_id")){ xlog("L_ERR", "No se encontraron mas carrier para rutear $rU\n"); t_reply("404", "Not found"); } else { xlog("L_ERR", "Se encontre otro carrier para rutear $rU\n"); append_branch(); route(2); }; }; }
On Wed, Mar 25, 2009 at 10:53 AM, Uriel Rozenbaum <uriel.rozenbaum@gmail.com
wrote:
Guys,
I'm getting this error on the logs for failure route but just for some of the calls I pass. If I call afterwards to that number it rings OK, so it is a random event:
ERROR:carrierroute:cr_load_next_domain: during set_next_domain_recursor, prefix '1054111547533610', carrier 2, domain 1
I'm filling carrierfailureroute with an empty string when I want taht route to be the final one; is it OK to do that?
Thanks in advance, Uriel
On Thursday 26 March 2009, Uriel Rozenbaum wrote:
One more piece of info, I found out that cr_next_domain is failing when i reach the last carrier failure route.
Hi Uriel,
may i ask you for a bit more details? Does it fail to read the last failure_route, even if its present? Or it does print this error message when it reaches the last failure_route, and there are no more routes to load?
Cheers,
Henning
Hi Henning,
Kamailio is printing this error when it reaches the last failure_route. I've left next_domain empty on all last routes.
Let me know if you need some piece of the cfg or something (I sent some on a later mail).
Thanks! Uriel
On Mon, Mar 30, 2009 at 6:43 AM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Thursday 26 March 2009, Uriel Rozenbaum wrote:
One more piece of info, I found out that cr_next_domain is failing when i reach the last carrier failure route.
Hi Uriel,
may i ask you for a bit more details? Does it fail to read the last failure_route, even if its present? Or it does print this error message when it reaches the last failure_route, and there are no more routes to load?
Cheers,
Henning
On Monday 30 March 2009, Uriel Rozenbaum wrote:
Kamailio is printing this error when it reaches the last failure_route. I've left next_domain empty on all last routes.
Let me know if you need some piece of the cfg or something (I sent some on a later mail).
Hi Uriel,
the ERROR message you've reported is not a real problem. Its severity was changed to INFO in the 1.4.4 release, i also rephrased it a bit (r5426). Now its behaves exactly like the "normal" routing.
This message is reported when cr fails to lookup a route, i.e. no more (failure) routes are available, or can be matched against the message content/ flags.
Cheers,
Henning
Henning,
The issue I'm facing is that, when this happens I get no record on the missed_calls table, but only for this attempt; all other attempts are recorded.
This will impact on teh ASR calculation script we developed and the routing logic that uses those values.
Do you think it was fixed on 1.5? Uriel
On Mon, Mar 30, 2009 at 9:38 AM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Monday 30 March 2009, Uriel Rozenbaum wrote:
Kamailio is printing this error when it reaches the last failure_route. I've left next_domain empty on all last routes.
Let me know if you need some piece of the cfg or something (I sent some
on
a later mail).
Hi Uriel,
the ERROR message you've reported is not a real problem. Its severity was changed to INFO in the 1.4.4 release, i also rephrased it a bit (r5426). Now its behaves exactly like the "normal" routing.
This message is reported when cr fails to lookup a route, i.e. no more (failure) routes are available, or can be matched against the message content/ flags.
Cheers,
Henning
On Monday 30 March 2009, Uriel Rozenbaum wrote:
The issue I'm facing is that, when this happens I get no record on the missed_calls table, but only for this attempt; all other attempts are recorded.
This will impact on teh ASR calculation script we developed and the routing logic that uses those values.
Do you think it was fixed on 1.5?
Hi Uriel,
you should get an error in your script in this case, cr_next_domain return -1. So in your cfg kamailio will return 404 and exit the script. So i don't think its an error in cr, its probably related to the usage of the acc module in your cfg.
Cheers,
Henning
I'm using this piece of code as failure route:
failure_route[2] {
# ----- Re-Rutear menasje con CR -----
xlog("L_ERR", "Carrier fallo ruteando $ru\n"); if (t_check_status("408|404|5[0-9][0-9]|6[0-9][0-9]")) { if (!cr_next_domain("$avp(s:routeTree)", "$avp(s:rutaindice)", "$oU", "$avp(s:cr_host)", "$T_reply_code", "$avp(s:cfr_domain)")) { t_reply("404", "Not found"); exit; };
$avp(s:rutaindice) = $avp(s:cfr_domain);
if(!cr_route("$avp(s:routeTree)", "$avp(s:rutaindice)", "$oU", "$oU", "call_id")){ xlog("L_ERR", "No se encontraron mas carrier para rutear $rU\n"); t_reply("404", "Not found"); } else { xlog("L_ERR", "Se encontre otro carrier para rutear $rU\n"); append_branch(); route(2); }; } else { t_reply("404", "Not found"); exit; }; }
And right in the main route i have:
if (is_method("INVITE|BYE|CANCEL")) { setflag(1); setflag(2); }
In order to bill all messages.
Is there any error in the failure logic?
On Mon, Mar 30, 2009 at 1:02 PM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Monday 30 March 2009, Uriel Rozenbaum wrote:
The issue I'm facing is that, when this happens I get no record on the missed_calls table, but only for this attempt; all other attempts are recorded.
This will impact on teh ASR calculation script we developed and the
routing
logic that uses those values.
Do you think it was fixed on 1.5?
Hi Uriel,
you should get an error in your script in this case, cr_next_domain return -1. So in your cfg kamailio will return 404 and exit the script. So i don't think its an error in cr, its probably related to the usage of the acc module in your cfg.
Cheers,
Henning
On Monday 30 March 2009, Uriel Rozenbaum wrote:
I'm using this piece of code as failure route:
append_branch();
Hi Uriel,
do you do a "revert_uri()" somewhere before entering the failure_route? And can you check if you perhaps reset the failed flag somewhere later in your cfg?
[..] And right in the main route i have:
if (is_method("INVITE|BYE|CANCEL")) { setflag(1); setflag(2); }
In order to bill all messages.
Is there any error in the failure logic?
Flag 1 is the successful, and 2 the failed flag?
Cheers,
Henning
Henning,
Let me attach the full cfg for clarity.
The flags are as you said; how can I do revert_uri before failure route? you mean within failure_route[20] do a revert_uri first thing before any further processing?
Thanks, Uriel
On Mon, Mar 30, 2009 at 2:44 PM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Monday 30 March 2009, Uriel Rozenbaum wrote:
I'm using this piece of code as failure route:
append_branch();Hi Uriel,
do you do a "revert_uri()" somewhere before entering the failure_route? And can you check if you perhaps reset the failed flag somewhere later in your cfg?
[..] And right in the main route i have:
if (is_method("INVITE|BYE|CANCEL")) { setflag(1); setflag(2); }
In order to bill all messages.
Is there any error in the failure logic?
Flag 1 is the successful, and 2 the failed flag?
Cheers,
Henning
-
Henning Westerholt -
Uriel Rozenbaum