Hi 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;
};
}
On Fri, Apr 8, 2011 at 11:08 AM, marius zbihlei <marius.zbih...@1and1.ro> wrote:
> On 04/07/2011 10:02 PM, Morten Isaksen wrote:
>>
>> Hi!
>>
>> Kamailio 3.0.3.
>>
>> I have a strange problem with one of our Kamailio servers. This one is
>> used for routing (with carrierroute) and to send presence information
>> (with pua module)
>>
>> Once every 10 day or so I get this error and then Kamailio stops
>> responding to any SIP packets.
>>
>> Apr 6 08:05:48 sip-core-1 /usr/local/sbin/kamailio[9186]: WARNING:
>> <script>: Failure route - M=INVITE RURI=sip:8615x...@178.xx.xx.xx
>> F=sip:861XXXXX@188.120.93.114:1025 T=sip:86155x...@sip1.uni-tel.dk
>> IP=178.XX.XX.XX ID=6de881ec07f9c6494ee589cf208da358@10.11.87.206
>> Apr 6 08:05:48 sip-core-1 /usr/local/sbin/kamailio[9186]: ERROR:
>> carrierroute [cr_func.c:95]: cannot find AVP 'carrier'
>> Apr 6 08:05:48 sip-core-1 /usr/local/sbin/kamailio[9186]: ERROR:
>> carrierroute [cr_func.c:805]: invalid carrier id -1
>> Apr 6 08:05:48 sip-core-1 /usr/local/sbin/kamailio[9186]: ERROR:
>> <script>: cr_next_domain failed
>>
>>
>
> Hello Morten,
>
> Do you have the carrier avp set in the failure route (it is ok if it's set
> in normal route it should be visible from there)? Also can you paste the
> lines from failure_route that are around the cr_next_domain . My suspicion
> is that you have some calls that reach failure route, but because of some
> particular cfg lines, they are not correctly routed and the daemon just
> sleeps in some lines of code on each worker.
>
> For replicating the bug and retrieve the line of code where the workers
> block(as Daniel suggested), it would be better if you decrease the number of
> worker and keep the same shm memory config value.
>
> Marius
>
>> Shared memory size is 128M and over halv is free just before the
>> error. The server is in production and does handle debug>1 well, so I
>> do not have much information in the log files. Private memory is the
>> default size.
>>
>> Any ideas what it could be, or how to investegate further?
>>
>> I think my next steps would be to increase the private memory og to
>> increase children=4 to children=8
>>
>>
>
>
> _______________________________________________
> 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
>
--
Morten Isaksen
_______________________________________________
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
