sr-users April 2010

sr-users@lists.kamailio.org

65 participants
103 discussions

by dotnetdub

Hello List, I have been running a very stable Kamailio 1.4 install for over a year now with no downtime. From time to time I get a message from the OS telling me that task kamailio:xxxx blocked for more than 120 seconds and a dump into syslog. I recently setup Kamailio 3.01 and it's been running for around 3 weeks now. Purely testing at the moment, there is only 1 SIP registration and almost no activity most of the time. I was checking dmesg and: [269844.208011] INFO: task kamailio:28504 blocked for more than 120 seconds. [269844.208093] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [269844.208178] kamailio D f6d77bf8 0 28504 28484 [269844.208180] f771e140 00000082 00000002 f6d77bf8 f7091390 f771e2cc c4019020 00000000 [269844.208184] 00000000 011615c9 f7091398 00000282 00000000 00000000 00000000 ffffffff [269844.208188] f5cba384 f5cba38c f5cba388 f771e140 c02c91ec f6969d68 f5cba38c f771e140 [269844.208191] Call Trace: [269844.208203] [<c02c91ec>] __mutex_lock_slowpath+0x50/0x7b [269844.208208] [<c02c9082>] mutex_lock+0xa/0xb [269844.208210] [<c02b7d4d>] unix_dgram_recvmsg+0x3e/0x231 [269844.208214] [<c0161beb>] get_page_from_freelist+0xc1/0x3e9 [269844.208218] [<c0161045>] __rmqueue_smallest+0x83/0xe3 [269844.208221] [<c025f771>] sock_recvmsg+0xde/0xf9 [269844.208226] [<c01387b0>] autoremove_wake_function+0x0/0x2d [269844.208231] [<c01620e9>] __alloc_pages_internal+0xb5/0x34e [269844.208236] [<c0260595>] sys_recvfrom+0xb4/0x116 [269844.208239] [<c011af13>] do_page_fault+0x0/0x8f9 [269844.208242] [<c0108540>] do_notify_resume+0x5f8/0x649 [269844.208247] [<c011b3c5>] do_page_fault+0x4b2/0x8f9 [269844.208250] [<c0260a48>] sys_socketcall+0x135/0x19e [269844.208254] [<c0108853>] sysenter_past_esp+0x78/0xb1 [269844.208257] [<c02c0000>] xenfb_probe+0xd1/0x35b [269844.208261] ======================= [269844.208262] INFO: task kamailio:28506 blocked for more than 120 seconds. [269844.208314] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [269844.208395] kamailio D d0e00947 0 28506 28484 [269844.208397] f77f8e60 00000082 00000002 d0e00947 00004292 f77f8fec c4024020 00000001 [269844.208401] 00000000 00000001 00000002 00000000 f7091398 00000001 00000001 c01211f2 [269844.208404] f5cba384 f5cba38c f5cba388 f77f8e60 c02c91ec f5cba38c f60add68 f77f8e60 [269844.208408] Call Trace: [269844.208410] [<c01211f2>] __wake_up_sync+0x2a/0x3e [269844.208413] [<c02c91ec>] __mutex_lock_slowpath+0x50/0x7b [269844.208416] [<c02c9082>] mutex_lock+0xa/0xb [269844.208418] [<c02b7d4d>] unix_dgram_recvmsg+0x3e/0x231 [269844.208421] [<c0161beb>] get_page_from_freelist+0xc1/0x3e9 [269844.208424] [<c0161045>] __rmqueue_smallest+0x83/0xe3 [269844.208427] [<c025f771>] sock_recvmsg+0xde/0xf9 [269844.208431] [<c01387b0>] autoremove_wake_function+0x0/0x2d [269844.208435] [<c01620e9>] __alloc_pages_internal+0xb5/0x34e [269844.208440] [<c0260595>] sys_recvfrom+0xb4/0x116 [269844.208444] [<c0180d0d>] cp_new_stat64+0xfc/0x10e [269844.208449] [<c011b3c5>] do_page_fault+0x4b2/0x8f9 [269844.208452] [<c0260a48>] sys_socketcall+0x135/0x19e [269844.208456] [<c0108853>] sysenter_past_esp+0x78/0xb1 [269844.208459] [<c02c0000>] xenfb_probe+0xd1/0x35b [269844.208462] ======================= [274198.229285] INFO: task kamailio:28504 blocked for more than 120 seconds. [274198.229340] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [274198.229422] kamailio D f6d77bf8 0 28504 28484 [274198.229425] f771e140 00000082 00000002 f6d77bf8 f7091390 f771e2cc c4019020 00000000 [274198.229429] 00000000 011615c9 f7091398 00000282 00000000 00000000 00000000 ffffffff [274198.229432] f5cba384 f5cba38c f5cba388 f771e140 c02c91ec f6969d68 f5cba38c f771e140 [274198.229436] Call Trace: [274198.229447] [<c02c91ec>] __mutex_lock_slowpath+0x50/0x7b [274198.229453] [<c02c9082>] mutex_lock+0xa/0xb [274198.229455] [<c02b7d4d>] unix_dgram_recvmsg+0x3e/0x231 [274198.229459] [<c0161beb>] get_page_from_freelist+0xc1/0x3e9 [274198.229463] [<c0161045>] __rmqueue_smallest+0x83/0xe3 [274198.229466] [<c025f771>] sock_recvmsg+0xde/0xf9 [274198.229471] [<c01387b0>] autoremove_wake_function+0x0/0x2d [274198.229476] [<c01620e9>] __alloc_pages_internal+0xb5/0x34e [274198.229481] [<c0260595>] sys_recvfrom+0xb4/0x116 [274198.229484] [<c011af13>] do_page_fault+0x0/0x8f9 [274198.229487] [<c0108540>] do_notify_resume+0x5f8/0x649 [274198.229492] [<c011b3c5>] do_page_fault+0x4b2/0x8f9 [274198.229495] [<c0260a48>] sys_socketcall+0x135/0x19e [274198.229499] [<c0108853>] sysenter_past_esp+0x78/0xb1 [274198.229502] [<c02c0000>] xenfb_probe+0xd1/0x35b [274198.229506] ======================= [274198.229507] INFO: task kamailio:28506 blocked for more than 120 seconds. [274198.229559] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [274198.229641] kamailio D d0e00947 0 28506 28484 [274198.229643] f77f8e60 00000082 00000002 d0e00947 00004292 f77f8fec c4024020 00000001 [274198.229646] 00000000 00000001 00000002 00000000 f7091398 00000001 00000001 c01211f2 [274198.229650] f5cba384 f5cba38c f5cba388 f77f8e60 c02c91ec f5cba38c f60add68 f77f8e60 [274198.229653] Call Trace: [274198.229656] [<c01211f2>] __wake_up_sync+0x2a/0x3e [274198.229659] [<c02c91ec>] __mutex_lock_slowpath+0x50/0x7b [274198.229662] [<c02c9082>] mutex_lock+0xa/0xb [274198.229664] [<c02b7d4d>] unix_dgram_recvmsg+0x3e/0x231 [274198.229667] [<c0161beb>] get_page_from_freelist+0xc1/0x3e9 [274198.229670] [<c0161045>] __rmqueue_smallest+0x83/0xe3 [274198.229673] [<c025f771>] sock_recvmsg+0xde/0xf9 [274198.229677] [<c01387b0>] autoremove_wake_function+0x0/0x2d [274198.229681] [<c01620e9>] __alloc_pages_internal+0xb5/0x34e [274198.229686] [<c0260595>] sys_recvfrom+0xb4/0x116 [274198.229690] [<c0180d0d>] cp_new_stat64+0xfc/0x10e [274198.229696] [<c011b3c5>] do_page_fault+0x4b2/0x8f9 [274198.229699] [<c0260a48>] sys_socketcall+0x135/0x19e [274198.229703] [<c0108853>] sysenter_past_esp+0x78/0xb1 [274198.229706] [<c02c0000>] xenfb_probe+0xd1/0x35b There was no activity when this happened. ON the 1.4 box there could be about 10 sessions setup when it happens. kamctl ps: Process:: ID=14 PID=28504 Type=MI DATAGRAM Process:: ID=15 PID=28505 Type=MI DATAGRAM Process:: ID=16 PID=28506 Type=MI DATAGRAM Even on the old install this doesn't seem to cause any problem and same here on 3.01 but would like to try and solve it. Any idea? Regards, Stephen

14 years, 7 months

[Kamailio-Users] fr_inv_timer in kam-3.0

by Andreas Granig

Hi, In the docs at http://kamailio.org/docs/modules/3.0.x/modules/tm.html#fr_inv_timer it says that fr_inv_timer_avp should be defined like this, without $ or $avp: modparam("tm", "fr_inv_timer_avp", "my_fr_inv_timer") In kam <= 1.5 I did it like that: modparam("tm", "fr_inv_timer_avp", "$avp(s:callee_fr_inv_timer)") which doesn't give me an error on startup with kam-3.0 either, but the timer doesn't get fired (I use seconds for that as noted in the docs). If I change it to modparam("tm", "fr_inv_timer_avp", "callee_fr_inv_timer") then I get the error "malformed or non AVP callee_fr_inv_timer AVP definition", same with setting it to "s:callee_fr_inv_timer". Anyhow, it seems to be deprecated anyways, so I'm looking to get t_set_fr() working. I'm just curious how I can use a var or AVP loaded from DB to set the value on-the-fly? t_set_fr(...) seems to allow only constants to be set. Couldn't find anything in the docs regarding that one. Thanks, Andreas

14 years, 7 months

[Kamailio-Users] drop in branch/onsend-route in kam-3.0

by Andreas Granig

Hi, Looks like behavior of drop has changed in Kamailio 3.0. Before, I was able to drop() a specific branch in branch_route depending on various checks. http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.0.x#drop still says this is possible, http://kamailio.org/docs/modules/3.0.x/modules/tm.html#t_on_branch says it's not possible. So calling drop() in branch_route has no effect, and I have no idea how to mark a branch in branch_route to be dropped in onsend_route, because checking a bflag doesn't work there, and neither does checking $rU. Any ideas on how to accomplish dropping a specific branch? Andreas

14 years, 7 months

[Kamailio-Users] Understanding memory-leaks by inspecting PKG/SHM memory status at shutdown

by Iñaki Baz Castillo

Hi, according to the wiki page: http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory In order to detect a possible memory leak (in PGK or SHM) a good way is enabling memory debugging and shuting down the server, so: "the memory manager will dump the memory status. Normally most of the memory is cleaned during shutdown. If there is memory leak, it should be visible as not-freed memory." But I would like to know how exactly to detect if there is a memoty leak by inspecting the SHM/PKG status, something like this: ----------------------------------------------------------------------------------------------------------------------------- [32715]: Memory status (pkg): [32715]: fm_status (0x701a40): [32715]: heap size= 16777216 [32715]: used= 189696, used+overhead=247392, free=16529824 [32715]: max used (+overhead)= 247392 [32715]: dumping free list: [32715]: hash = 1 fragments no.: 1, unused: 0#012#011#011 bucket size: 8 - 8 (first 8) [32715]: hash = 2058 fragments no.: 1, unused: 0#012#011#011 bucket size: 8388608 - 16777216 (first 16530136) [32715]: TOTAL: 2 free fragments = 16530144 free bytes [32678]: Memory status (shm): [32678]: fm_status (0x7fa57921c000): [32678]: heap size= 67108864 [32678]: used= 16, used+overhead=35872, free=67072992 [32678]: max used (+overhead)= 2821064 [32678]: dumping free list: [32678]: hash = 1 fragments no.: 45, unused: 0#012#011#011 bucket size: 8 - 8 (first 8) [32678]: hash = 2 fragments no.: 4, unused: 0#012#011#011 bucket size: 16 - 16 (first 16) [32678]: hash = 3 fragments no.: 16, unused: 0#012#011#011 bucket size: 24 - 24 (first 24) [32678]: hash = 4 fragments no.: 2, unused: 0#012#011#011 bucket size: 32 - 32 (first 32) [32678]: hash = 5 fragments no.: 1, unused: 0#012#011#011 bucket size: 40 - 40 (first 40) [32678]: hash = 6 fragments no.: 1, unused: 0#012#011#011 bucket size: 48 - 48 (first 48) [32678]: hash = 7 fragments no.: 39, unused: 0#012#011#011 bucket size: 56 - 56 (first 56) [32678]: hash = 8 fragments no.: 1, unused: 0#012#011#011 bucket size: 64 - 64 (first 64) [32678]: hash = 9 fragments no.: 1, unused: 0#012#011#011 bucket size: 72 - 72 (first 72) [32678]: hash = 10 fragments no.: 2, unused: 0#012#011#011 bucket size: 80 - 80 (first 80) [32678]: hash = 15 fragments no.: 1, unused: 0#012#011#011 bucket size: 120 - 120 (first 120) [32678]: hash = 25 fragments no.: 1, unused: 0#012#011#011 bucket size: 200 - 200 (first 200) [32678]: hash = 40 fragments no.: 5, unused: 0#012#011#011 bucket size: 320 - 320 (first 320) [32678]: hash = 112 fragments no.: 1, unused: 0#012#011#011 bucket size: 896 - 896 (first 896) [32678]: hash = 128 fragments no.: 4, unused: 0#012#011#011 bucket size: 1024 - 1024 (first 1024) [32678]: hash = 129 fragments no.: 2, unused: 0#012#011#011 bucket size: 1032 - 1032 (first 1032) [32678]: hash = 224 fragments no.: 1, unused: 0#012#011#011 bucket size: 1792 - 1792 (first 1792) [32678]: hash = 258 fragments no.: 3, unused: 0#012#011#011 bucket size: 2064 - 2064 (first 2064) [32678]: hash = 473 fragments no.: 1, unused: 0#012#011#011 bucket size: 3784 - 3784 (first 3784) [32678]: hash = 1026 fragments no.: 1, unused: 0#012#011#011 bucket size: 8208 - 8208 (first 8208) [32678]: hash = 2049 fragments no.: 2, unused: 0#012#011#011 bucket size: 16384 - 32768 (first 16512) [32678]: hash = 2051 fragments no.: 1, unused: 0#012#011#011 bucket size: 65536 - 131072 (first 98336) [32678]: hash = 2056 fragments no.: 1, unused: 0#012#011#011 bucket size: 2097152 - 4194304 (first 2621440) [32678]: hash = 2060 fragments no.: 1, unused: 0#012#011#011 bucket size: 33554432 - 67108864 (first 64287800) [32678]: TOTAL: 137 free fragments = 67072992 free bytes ----------------------------------------------------------------------------------------------------------------------------- This is, how should look this SHM/PKG status example (after shutdown) in case there is a memory leak? how to detect not-freed memory? Thanks a lot. -- Iñaki Baz Castillo <ibc(a)aliax.net>

14 years, 7 months

[Kamailio-Users] irc devel meeting

by Daniel-Constantin Mierla

Hello, I know some of devels are still in Easter vacation, but I hope we can get together soon on irc to sketch the plan for 3.1 release. I propose next week, Wednesday, April 14, 15:00UTC, on #sip-router channel hosted by irc.freenode.net If you are a developer and want to participate, please announce. If it is not possible to attend for major contributors, we can look for another date (eventually start a pool to see the day were most of us are available). Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla

14 years, 7 months

[Serusers] ReTransmission of CANCELs on 0.9.7

by rupert.organ＠bt.com

Hi All, Has anyone come up against an issue on 0.9.6 / 0.9.7 whereby a SIP App Server, delivers a CANCEL to the SER. The SER proxies the CANCELs to all the forked endpoints. At the same time it sends "200 Cancelling" back to the SIP App server...(this suppresses CANCEL retransmission from the SIP App server). If one of the CANCELs from the SER to the SIP UA gets lost....the phone keeps ringing. There is no CANCEL retransmission on the SER !!! There is CANCEL retransmission on the SIP App, but when it sends SER replies "no pending branches" Ideally want the SER do CANCEL retransmissions. I understand the timers were rewritten in 0.10.x but this is not hardened version like 0.9.6....any suggestions? Thanks in advance Rupert

14 years, 7 months

[Kamailio-Users] merging users mailing lists

by Daniel-Constantin Mierla

Hello, I propose to merge the users mailing lists, most of the traffic these days is about 3.0 and even there are 2 stables branches now, they are sync'ed, so same code more or less. For 3.1 will be one stable branch, falvor selection will be only a matter of make command. Lately common useful topics are discussed on those different mailing lists, notifications and knowledge base building require cross-posting, lot of overhead imo. Any other opinion? Like with devel mailing lists, existing email addresses for users ML can still be used, just that end on same ML. Natural choice will be to have users@kamailio and serusers@iptel to be directed to sr-users(a)lists.sip-router.org Cheers, Daniel -- Daniel-Constantin Mierla * http://www.asipto.com/

14 years, 7 months

[Kamailio-Users] mc (Midnight Commander) syntax highlighting scheme

by Константин

Hi all! For easy editing kamailio configuration files I developed a syntax highlighting scheme for mc. Preview The scheme includes basic syntactic structures of Kamailio 1.5, all constants, variables, operators and standart core functions. To install it, download the file kamailio.syntax from attachment and copy it to /usr/share/mc/syntax (for Debian Etch) Next, add to the file /usr/share/mc/syntax/Syntax including: file ..\*\\.cfg$ Kamailio\sconfig include kamailio.syntax Thats all, I hope its helps someone ;) -- Shpinev Konstantin mailto:kks_mail@inbox.ru

14 years, 7 months

[Kamailio-Users] Version 3

by dotnetdub

Hi List, Anybody using this in production yet? If so what kind of volume and how is reliability? Looking to move to this platform, looks very good, interested to hear some experiences. Thanks, Stephen

14 years, 7 months

Re: [Kamailio-Users] Odd Behaviour with Kamailio + TLS

by Hemanshu Patel

Yes, i had installed self signed certificates via IE. Bria shows it and validates them during registration process, its the call initiation where it creates problem. Kamailio starts without fix_nated_register. With this function it gives configuration file error. and i had load nathelper.so and that is been confirmed via logs -- Regards, Hemanshu Patel SIS,Ahmedabad. M: 09601295238 > Just checking... > > Some time ago, I made some tests with Bria and self signed certs... It was a little tricky to find that I had to install the cert through IE. Did you install them this way? Can you check Bria's log to ensure that the cert is accepted? > > Edson. > > Henning Westerholt escreveu: >> On Thursday 01 April 2010, Hemanshu Patel wrote: >>> yes i did, and log shows that nathelper.so load without any problem. kamailio loads and work perfectly with grandstream devices with TLS and >>> SRTp. it gives problem with Bria softphones only. >>> I am using self signed certificates which works perfectly with grandstream, can there be any chances that due to self sign ness of the >>> certificates, it doesnt work well with bria devices. >> Hi Hemanshu, >> ok, so the error you reported in your previous message is solved. It could be >> possible that the Bria softphone implement a more strict policy with regards >> to the check of the certificates. But you should be able to find something in >> the UA documentation about this, you could ask the vendor or other users. As >> the last resort just test with certificates that are not self signed. ;-) >> Cheers, >> Henning >> _______________________________________________ >> Kamailio (OpenSER) - Users mailing list >> Users(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >

14 years, 7 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users April 2010