sr-dev February 2014

sr-dev@lists.kamailio.org

38 participants
235 discussions

git:3.3: pkg/kamailio/deb: init script. Get back SHM_MEMORY PKG_MEMORY and CFGFILE

by Victor Seva

Module: sip-router Branch: 3.3 Commit: 6b4db8e5d0a035e690dea80e8623be034895d236 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=6b4db8e… Author: Victor Seva <linuxmaniac(a)torreviejawireless.org> Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org> Date: Fri Feb 21 11:50:16 2014 +0100 pkg/kamailio/deb: init script. Get back SHM_MEMORY PKG_MEMORY and CFGFILE (cherry picked from commit f46beec41b3b5caa3977ddd452b3671bebf69069) --- pkg/kamailio/deb/debian/kamailio.default | 9 +++++++-- pkg/kamailio/deb/debian/kamailio.init | 19 ++++++++++++------- pkg/kamailio/deb/lenny/kamailio.default | 9 +++++++-- pkg/kamailio/deb/lenny/kamailio.init | 19 ++++++++++++------- pkg/kamailio/deb/lucid/kamailio.default | 9 +++++++-- pkg/kamailio/deb/lucid/kamailio.init | 19 ++++++++++++------- pkg/kamailio/deb/precise/kamailio.default | 9 +++++++-- pkg/kamailio/deb/precise/kamailio.init | 19 ++++++++++++------- pkg/kamailio/deb/squeeze/kamailio.default | 9 +++++++-- pkg/kamailio/deb/squeeze/kamailio.init | 19 ++++++++++++------- pkg/kamailio/deb/wheezy/kamailio.default | 9 +++++++-- pkg/kamailio/deb/wheezy/kamailio.init | 19 ++++++++++++------- 12 files changed, 114 insertions(+), 54 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=6b4…

10 years, 10 months

[tracker] Comment added: Kamailio doesn't to handle any SIP message at all after several dialogs... (CPU high usage)

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#397 - Kamailio doesn't to handle any SIP message at all after several dialogs... (CPU high usage) User who did this - Daniel-Constantin Mierla (miconda) ---------- Can you attach with gdb to the pid of each process eating a lot of cpu and get the output for next command? bt full ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=397#comment1299 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.

10 years, 10 months

[tracker] Task opened: Kamailio doesn't to handle any SIP message at all after several dialogs... (CPU high usage)

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Jack Wang (GoGoJack) Attached to Project - sip-router Summary - Kamailio doesn't to handle any SIP message at all after several dialogs... (CPU high usage) Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - Critical Priority - Normal Reported Version - 4.0 Due in Version - Undecided Due Date - Undecided Details - First, thanks for watching my poor English, hope guys can understand what I want to show you :) __issue __ * Objective: test the stability of kamailio with lots of registered users * Work: take 4~9 users registered and do call in\out with an MCU I found it's OK for just doing registration actions , but a trouble always occured when doing call in\out for a time (5 minutes ~ 3hrs , frequently in 1~2hrs) - kamailio doesn't to handle SIP message anymore, this causes that all the registration failed and was changed to "expired" state in user location table of database so that I can't do call in\out for every register user until I restart kamailio. It seems CPU usage of kamailio is too high after checking by typing "top" command: **[normal state]** <code> CPU: 0.2% usr 0.2% sys 0.0% nic 99.5% idle 0.0% io 0.0% irq 0.0% sirq ... PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND 6169 6150 xxxxxxxx S 49476 2.3 3 0.0 ./kamailio -P /var/run/kamailio.pid -f /var/test/kamailio.cfg 6168 6150 xxxxxxxx S 49472 2.3 3 0.0 ./kamailio -P /var/run/kamailio.pid -f /var/test/kamailio.cfg 6171 6150 xxxxxxxx S 49472 2.3 3 0.0 ./kamailio -P /var/run/kamailio.pid -f /var/test/kamailio.cfg 6172 6150 xxxxxxxx S 49472 2.3 0 0.0 ./kamailio -P /var/run/kamailio.pid -f /var/test/kamailio.cfg</code> **[abnormal state]** <code> CPU: 11.4% usr 88.5% sys 0.0% nic 0.0% idle 0.0% io 0.0% irq 0.0% sirq ... PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND 6216 6203 xxxxxxxx R 48308 2.3 0 24.2 ./kamailio -P /var/run/kamailio.pid -f /var/test/kamailio.cfg 6218 6203 xxxxxxxx R 48308 2.3 3 24.1 ./kamailio -P /var/run/kamailio.pid -f /var/test/kamailio.cfg 6217 6203 xxxxxxxx R 48308 2.3 1 23.7 ./kamailio -P /var/run/kamailio.pid -f /var/test/kamailio.cfg 6221 6203 xxxxxxxx R 48308 2.3 2 22.4 ./kamailio -P /var/run/kamailio.pid -f /var/test/kamailio.cfg</code> since the process doesn't crash , I can't do a core dump for this, and I can't find any rules for this bug because it may happen on anywhere, it's better to get suggestions from you. __other environment settings__ kamailio version: 4.0.5 CPU: ARM Cortex A8 Database: SQLite More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=397 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.

10 years, 10 months

[tracker] Task opened: Looping while parsing malformed Supported field

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Savolainen Dmitri (sdi) Attached to Project - sip-router Summary - Looping while parsing malformed Supported field Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - Critical Priority - Normal Reported Version - 4.1 Due in Version - Undecided Due Date - Undecided Details - Error while parsing malformed Supported field. Kamailio go to top of CPU usage and stop handling requests. Loop "while (pos < len)" in parse_option_tag_body function (parse_option_tags.h) is never stop <code> kamcmd> core.info { version: kamailio 4.1.1 id: ab7f96 -dirty compiler: gcc 4.3.4 compiled: 16:51:25 Jan 20 2014 flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES } </code> <code> log# gdb /usr/local/kamailio411/sbin/kamailio 26994 (gdb) bt #0 0x081a8ee5 in parse_option_tag_body (body=0xb3fd3438, tags=0xb3fd5eb0) at parse_option_tags.h:98 #1 0x081a8dce in parse_supported (msg=0xb4005bd4) at parse_supported.c:63 #2 0xaba18a9b in save (_m=0xb4005bd4, _d=0xac091008, _cflags=0, _uri=0x0) at save.c:896 #3 0xaba0f4ab in w_save2 (_m=0xb4005bd4, _d=0xac091008 "\214\017\t�", _cflags=0x0) at reg_mod.c:452 #4 0x0805f7cd in do_action (h=0xbfb86f68, a=0xb3fac5e8, msg=0xb4005bd4) at action.c:1105 #5 0x08067a49 in run_actions (h=0xbfb86f68, a=0xb3fac5e8, msg=0xb4005bd4) at action.c:1599 #6 0x080680ff in run_actions_safe (h=0xbfb88b04, a=0xb3fac5e8, msg=0xb4005bd4) at action.c:1664 #7 0x08103906 in rval_get_int (h=0xbfb88b04, msg=0xb4005bd4, i=0xbfb872c4, rv=0xb3fac75c, cache=0x0) at rvalue.c:924 #8 0x0810507b in rval_expr_eval_int (h=0xbfb88b04, msg=0xb4005bd4, res=0xbfb872c4, rve=0xb3fac758) at rvalue.c:1918 #9 0x08105262 in rval_expr_eval_int (h=0xbfb88b04, msg=0xb4005bd4, res=0xbfb875d0, rve=0xb3facb88) at rvalue.c:1926 #10 0x0805f4cb in do_action (h=0xbfb88b04, a=0xb3fad090, msg=0xb4005bd4) at action.c:1075 #11 0x08067a49 in run_actions (h=0xbfb88b04, a=0xb3fac0c8, msg=0xb4005bd4) at action.c:1599 #12 0x0805daee in do_action (h=0xbfb88b04, a=0xb3e9ad50, msg=0xb4005bd4) at action.c:715 #13 0x08067a49 in run_actions (h=0xbfb88b04, a=0xb3e9a340, msg=0xb4005bd4) at action.c:1599 #14 0x0805f6fd in do_action (h=0xbfb88b04, a=0xb3ec5ac4, msg=0xb4005bd4) at action.c:1090 #15 0x08067a49 in run_actions (h=0xbfb88b04, a=0xb3ec5ac4, msg=0xb4005bd4) at action.c:1599 #16 0x0805f740 in do_action (h=0xbfb88b04, a=0xb3ec5b68, msg=0xb4005bd4) at action.c:1094 #17 0x08067a49 in run_actions (h=0xbfb88b04, a=0xb3ec5b68, msg=0xb4005bd4) at action.c:1599 #18 0x0805f740 in do_action (h=0xbfb88b04, a=0xb3ec5c0c, msg=0xb4005bd4) at action.c:1094 #19 0x08067a49 in run_actions (h=0xbfb88b04, a=0xb3ec5c0c, msg=0xb4005bd4) at action.c:1599 #20 0x0805f740 in do_action (h=0xbfb88b04, a=0xb3ec5cb0, msg=0xb4005bd4) at action.c:1094 #21 0x08067a49 in run_actions (h=0xbfb88b04, a=0xb3e8a2c0, msg=0xb4005bd4) at action.c:1599 #22 0x080681a9 in run_top_route (a=0xb3e8a2c0, msg=0xb4005bd4, c=0x0) at action.c:1685 #23 0x080e458b in receive_msg ( buf=0x82ea2a0 "REGISTER sip:sip.telphin.com:5068 SIP/2.0\r\nVia: SIP/2.0/UDP 213.170.81.130:5600;branch=z9hG4bKt5eurr2030eg3e4id1s0.1\r\nMax-Forwards: 16\r\nContact: <sip:00041943@213.170.81.130:5600;rinstance=cc1a5d7b824"..., len=876, rcv_info=0xbfb88d0c) at receive.c:212 #24 0x08173183 in udp_rcv_loop () at udp_server.c:536 #25 0x080af4fe in main_loop () at main.c:1617 #26 0x080b2450 in main (argc=8, argv=0xbfb88fb4) at main.c:2533 (gdb) p *body $8 = { s = 0x82ea4cd "time�\r\nUser-Agent: Telphin Softphone release 1104a stamp 56747\r\nAuthorization: Digest username=\"XXXXXXXX\",realm=\"sip.telphin.com\",nonce=\"XXXXXXXXXXXXXXXXXXXXX\",uri=\"sip:sip.telphin.com:5068"..., len = 5} (gdb) n 93 while (pos < len) { (gdb) 97 val = LOWER_DWORD(READ(p)); (gdb) 98 switch (val) { (gdb) 121 if ( pos+5 <= len && LOWER_BYTE(*(p+4))=='r' (gdb) 93 while (pos < len) { (gdb) 97 val = LOWER_DWORD(READ(p)); (gdb) 98 switch (val) { (gdb) 121 if ( pos+5 <= len && LOWER_BYTE(*(p+4))=='r' (gdb) 93 while (pos < len) { (gdb) 97 val = LOWER_DWORD(READ(p)); (gdb) </code> More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=396 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.

10 years, 10 months

git:4.0: tm: safety check for uas callid value when callid_matching is 1

by Daniel-Constantin Mierla

Module: sip-router Branch: 4.0 Commit: ce060959dad97a346046b276633bfbc442aaf1e6 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=ce06095… Author: Alex Hermann <alex(a)speakup.nl> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Fri Feb 21 00:10:35 2014 +0100 tm: safety check for uas callid value when callid_matching is 1 - according to the documentation is for UA that cannot match the responses when call-id is changed, but is not the case of self generated requests - closes FS#390 (cherry picked from commit 1787b4239f3494fe7a88b0868a807e86a3b92639) (cherry picked from commit ef478ac0709a9bef99df0818f68b597f39ba7c3b) --- modules/tm/t_lookup.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/modules/tm/t_lookup.c b/modules/tm/t_lookup.c index fec6e8b..db88d0f 100644 --- a/modules/tm/t_lookup.c +++ b/modules/tm/t_lookup.c @@ -1013,6 +1013,7 @@ int t_reply_matching( struct sip_msg *p_msg , int *p_branch ) continue; if (cfg_get(tm, tm_cfg, callid_matching) && + p_cell->uas.request && p_cell->uas.request->callid && (p_msg->callid->body.len != p_cell->uas.request->callid->body.len || memcmp(p_msg->callid->body.s, p_cell->uas.request->callid->body.s, p_msg->callid->body.len) != 0) ) {

10 years, 10 months

git:4.1: tm: safety check for uas callid value when callid_matching is 1

by Daniel-Constantin Mierla

Module: sip-router Branch: 4.1 Commit: ef478ac0709a9bef99df0818f68b597f39ba7c3b URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=ef478ac… Author: Alex Hermann <alex(a)speakup.nl> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Fri Feb 21 00:10:35 2014 +0100 tm: safety check for uas callid value when callid_matching is 1 - according to the documentation is for UA that cannot match the responses when call-id is changed, but is not the case of self generated requests - closes FS#390 (cherry picked from commit 1787b4239f3494fe7a88b0868a807e86a3b92639) --- modules/tm/t_lookup.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/modules/tm/t_lookup.c b/modules/tm/t_lookup.c index fbc624b..6c198a4 100644 --- a/modules/tm/t_lookup.c +++ b/modules/tm/t_lookup.c @@ -984,6 +984,7 @@ int t_reply_matching( struct sip_msg *p_msg , int *p_branch ) continue; if (cfg_get(tm, tm_cfg, callid_matching) && + p_cell->uas.request && p_cell->uas.request->callid && (p_msg->callid->body.len != p_cell->uas.request->callid->body.len || memcmp(p_msg->callid->body.s, p_cell->uas.request->callid->body.s, p_msg->callid->body.len) != 0) ) {

10 years, 10 months

[tracker] Comment added: Bug in tm with topoh modules - segfault on callid comparison.

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#390 - Bug in tm with topoh modules - segfault on callid comparison. User who did this - Daniel-Constantin Mierla (miconda) ---------- I accepted the patch from Alex, solving the issue in tm. After looking at the purpose of callid matching, it is not needed for local generated requests. Topoh might still generate the error messages -- I have to analyse the code a bit, and don't do encoding/decoding for local generated requests and their responses. But other than log messages, the crash should not happen anymore. I let the item open on the tracker until I look at topoh for this case. ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=390#comment1298 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.

10 years, 10 months

git:master: tm: safety check for uas callid value when callid_matching is 1

by Daniel-Constantin Mierla

Module: sip-router Branch: master Commit: 1787b4239f3494fe7a88b0868a807e86a3b92639 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=1787b42… Author: Alex Hermann <alex(a)speakup.nl> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Fri Feb 21 00:10:35 2014 +0100 tm: safety check for uas callid value when callid_matching is 1 - according to the documentation is for UA that cannot match the responses when call-id is changed, but is not the case of self generated requests - closes FS#390 --- modules/tm/t_lookup.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/modules/tm/t_lookup.c b/modules/tm/t_lookup.c index fbc624b..6c198a4 100644 --- a/modules/tm/t_lookup.c +++ b/modules/tm/t_lookup.c @@ -984,6 +984,7 @@ int t_reply_matching( struct sip_msg *p_msg , int *p_branch ) continue; if (cfg_get(tm, tm_cfg, callid_matching) && + p_cell->uas.request && p_cell->uas.request->callid && (p_msg->callid->body.len != p_cell->uas.request->callid->body.len || memcmp(p_msg->callid->body.s, p_cell->uas.request->callid->body.s, p_msg->callid->body.len) != 0) ) {

10 years, 10 months

Performance impact with AVP and VAR's

by Jijo

Hi All, I have around 300 AVP's and quite amount of VAR's are used in the config file? Does that impact performance?, If so how can i improve it? Thanks Jijo

10 years, 10 months

[tracker] Comment added: kamailio crashed time to time in the different places

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#393 - kamailio crashed time to time in the different places User who did this - Daniel-Constantin Mierla (miconda) ---------- Can you give the output in gdb of: p *hdr ? ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=393#comment1297 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.

10 years, 10 months

← Newer
1
...
7
8
9
10
11
12
13
...
24
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev February 2014