THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#427 - kamailio sometimes crash when handling failure events
User who did this - Pawel Sternal (Sternik)
----------
I attach a pcap and bt full from gdb (core) from today's crash.
I found in logs when processing ACK this:
<code>
May 14 11:59:50 node02 /usr/sbin/kamailio[31576]: CRITICAL: dialog [dlg_hash.c:841]: log_next_state_dlg(): bogus event 6 in state 1 for dlg 0xa5223ba0 [2649:5896] with clid '039f972664562d09788758b36f12fc1b(a)sip.vanbergsystems.pl' and tags 'as79a6475b' ''
</code>
And about 30 seconds later:
<code>
May 14 12:00:18 node02 /usr/sbin/kamailio[31560]: ALERT: <core> [main.c:775]: handle_sigs(): child process 31582 exited by a signal 11
May 14 12:00:18 node02 /usr/sbin/kamailio[31560]: ALERT: <core> [main.c:778]: handle_sigs(): core was generated
</code>
This child processing failure route:
<code>
if (t_is_canceled()) {
xlog("L_NOTICE","LOG:$ci (failure route 1) transaction was cancelled by UAC");
avp_db_query("select icid_var from dialog_data where callid='$ci'","$avp(icid_next)");
#acc
setflag(30);
drop;
exit;
}
</code>
----------
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=427#comment1446
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 All,
I want to handle a special case in the Kamailio 4.1.3. When I receive
INVITE from some UAC I wanto reply it with 403 message. I am using the
Kamailio in Proxy mode when the INVITE comes I want to reply it with 403
and do not want to send this INVITE to SIP Server.
I expored the Kamailio source code and found that fucntion receive_msg() in
file receive.c receives all the SIP messages. I am able to parse the SIP
INVITE from such UACs but how to reply them with 403 SIP Code. I am unable
to use the t_reply("403","Forbidden") here in this function/file. Also in
this function finally the forward_reply(msg); is called which sends the
INVITE to the Sip Server. But I dont want to send anything to SIP Server in
this case but want to reply the UAC with 403. Can you please guide me how
to do and where to do this.
I am new to kamailio. Please help.
Regards
Varun
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#427 - kamailio sometimes crash when handling failure events
User who did this - Pawel Sternal (Sternik)
----------
yes, i've seen this patch. I was trying delete with avp_delete, pv_unset, assigning $null... but... I had refactoring to use $var variables ;-) Next day I saw that you put a patch for this. $var is enough for me.
siptrace attached.
from last backtrace (gdb_20140511.txt):
<code>
(gdb) frame 4
#4 0xb48dcea3 in dlg_onreply (t=0xa4ffb894, type=1048576, param=0xbff24c9c) at dlg_handlers.c:563
563 dlg_handlers.c: No such file or directory.
in dlg_handlers.c
(gdb) p *dlg
$1 = {ref = 0, next = 0x0, prev = 0x0, h_id = 6149, h_entry = 363, state = 5, lifetime = 21600, init_ts = 1399816405, start_ts = 0, dflags = 512, iflags = 0, sflags = 0, toroute = 0, toroute_name = {s = 0x0,
len = 0}, from_rr_nb = 1, tl = {next = 0x0, prev = 0x0, timeout = 0}, callid = {
s = 0xa4d5a708 "775e6d942c0649244f355f936211892f@sip.freeconet.plsip:+48512911332@sip.freeconet.plsip:+48632186066@sip.freeconet.plsip:hultaj1000@sip.freeconet.pl1166\r\n\n\n\r\n??????miotek@5`\001",
len = 49}, from_uri = {s = 0xa4d5a739 "sip:+48512911332@sip.freeconet.plsip:+48632186066@sip.freeconet.plsip:hultaj1000@sip.freeconet.pl1166\r\n\n\n\r\n??????miotek@5`\001", len = 33}, to_uri = {
s = 0xa4d5a75a "sip:+48632186066@sip.freeconet.plsip:hultaj1000@sip.freeconet.pl1166\r\n\n\n\r\n??????miotek@5`\001", len = 33}, req_uri = {
s = 0xa4d5a77b "sip:hultaj1000@sip.freeconet.pl1166\r\n\n\n\r\n??????miotek@5`\001", len = 31}, tag = {{s = 0xa4fc8bf0 "w", len = 10}, {s = 0x0, len = 0}}, cseq = {{s = 0xa4d76230 "\005\001", len = 3},
{s = 0x0, len = 0}}, route_set = {{s = 0xa4fc8c1e "447-OEM-0041153-42872-C07C6E47-05060213.218.116.66", len = 44}, {s = 0x0, len = 0}}, contact = {{s = 0xa4fc8bfa "?\f\214?\003", len = 36}, {s = 0x0,
len = 0}}, bind_addr = {0xb56824fc, 0x0}, cbs = {first = 0xa500db80, types = 8684}, profile_links = 0x0, vars = 0x0}
(gdb) frame 3
#3 0xb48e90f5 in dlg_release (dlg=0xa4d5a644) at dlg_hash.c:826
826 dlg_hash.c: No such file or directory.
in dlg_hash.c
(gdb) p *dlg
$2 = {ref = 0, next = 0x0, prev = 0x0, h_id = 6149, h_entry = 363, state = 5, lifetime = 21600, init_ts = 1399816405, start_ts = 0, dflags = 512, iflags = 0, sflags = 0, toroute = 0, toroute_name = {s = 0x0,
len = 0}, from_rr_nb = 1, tl = {next = 0x0, prev = 0x0, timeout = 0}, callid = {
s = 0xa4d5a708 "775e6d942c0649244f355f936211892f@sip.freeconet.plsip:+48512911332@sip.freeconet.plsip:+48632186066@sip.freeconet.plsip:hultaj1000@sip.freeconet.pl1166\r\n\n\n\r\n??????miotek@5`\001",
len = 49}, from_uri = {s = 0xa4d5a739 "sip:+48512911332@sip.freeconet.plsip:+48632186066@sip.freeconet.plsip:hultaj1000@sip.freeconet.pl1166\r\n\n\n\r\n??????miotek@5`\001", len = 33}, to_uri = {
s = 0xa4d5a75a "sip:+48632186066@sip.freeconet.plsip:hultaj1000@sip.freeconet.pl1166\r\n\n\n\r\n??????miotek@5`\001", len = 33}, req_uri = {
s = 0xa4d5a77b "sip:hultaj1000@sip.freeconet.pl1166\r\n\n\n\r\n??????miotek@5`\001", len = 31}, tag = {{s = 0xa4fc8bf0 "w", len = 10}, {s = 0x0, len = 0}}, cseq = {{s = 0xa4d76230 "\005\001", len = 3},
{s = 0x0, len = 0}}, route_set = {{s = 0xa4fc8c1e "447-OEM-0041153-42872-C07C6E47-05060213.218.116.66", len = 44}, {s = 0x0, len = 0}}, contact = {{s = 0xa4fc8bfa "?\f\214?\003", len = 36}, {s = 0x0,
len = 0}}, bind_addr = {0xb56824fc, 0x0}, cbs = {first = 0xa500db80, types = 8684}, profile_links = 0x0, vars = 0x0}
</code>
In event_route[tm:local-request] i'm doing something with PUBLISH - changing body. And also using avp_db_query
----------
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=427#comment1445
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#427 - kamailio sometimes crash when handling failure events
User who did this - Daniel-Constantin Mierla (miconda)
----------
>From the core of last backtrace ( gdb_20140511.txt ), can you get with gdb the output of next commands:
frame 4
p *dlg
frame 3
p *dlg
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=427#comment1444
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#427 - kamailio sometimes crash when handling failure events
User who did this - Daniel-Constantin Mierla (miconda)
----------
The master branch has a patch for rtimer and avp/xavp --- otherwise, yes, in older versions you should not use them.
Any other event_route block, or just the one from cnxcc?
Can you get the sip packets for the first backtrace you attached here, respectively the file gdb_20140509.txt?
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=427#comment1443
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#427 - kamailio sometimes crash when handling failure events
User who did this - Pawel Sternal (Sternik)
----------
Yes, but i'm not using avp or xapv variables in rtimer. I had notice that using this variables causes memmory leak...
Hmmm... but in event_route[cnxcc:call-shutdown] I've do avp_db_query... maybe this is the problem?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=427#comment1442
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.