On 04/09/2011 11:09 AM, Morten Isaksen wrote:
Hi Marius,
Hello,
Thanks for the update, but unfortunately I can't spot anything wrong. As
Daniel noted, please send a trace of the worker process (you can also
select the worker's pid from the log file)Attack with GDB for several
times and issue a bt (or bt full) command. If the traces are different,
this will help. Also do a ngrep to see that indeed you have traffic and
K is not responding at all.
Marius
The carrier avp is always set in route[0].
My failure_route looks like this.
xlog("L_WARN", "Failure route - M=$rm RURI=$ru F=$fu T=$tu
IP=$si ID=$ci\n");
if (t_check_status("408|404|5[0-9][0-9]|6[0-9][0-9]")&&
!t_check_status("503")) {
revert_uri();
if (!cr_next_domain("$avp(s:carrier)", "$avp(s:domain)", "$rU",
"$avp(s:host)",
"$T_reply_code", "$avp(s:domain)")) {
xlog("L_ERR", "cr_next_domain failed\n");
exit;
}
if (!cr_route("$avp(s:carrier)", "$avp(s:domain)", "$rU",
"$rU",
"call_id")) {
xlog("L_ERR", "cr_route failed\n");
exit;
}
$avp(s:host)= $rd;
t_on_failure("COREROUTE");
append_branch();
xlog("L_WARN", "Outgoing M=$rm RURI=$ru F=$fu T=$tu
IP=$si ID=$ci\n");
xlog("$si -> $rd");
if (!t_relay()) {
xlog("L_ERR", "t_relay failed\n");
exit;
};
}
_______________________________________________
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
