sr-users June 2013

sr-users@lists.kamailio.org

94 participants
171 discussions

EOF Error in pass_fd
by Ricardo Martinez 20 Nov '13

20 Nov '13

Hello List. The last weekend our kamailio process crashed with this error : Jun 24 06:55:08 pxh /usr/local/sbin/kamailio[10661]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 29 Jun 24 06:55:08 pxh /usr/local/sbin/kamailio[10542]: ALERT: <core> [main.c:751]: child process 10601 exited by a signal 11 Jun 24 06:55:08 pxh /usr/local/sbin/kamailio[10542]: ALERT: <core> [main.c:754]: core was generated Jun 24 06:55:08 pxh /usr/local/sbin/kamailio[10542]: INFO: <core> [main.c:766]: INFO: terminating due to SIGCHLD Can someone tell me what seems to be the problem here? We’re using : version: kamailio 3.2.2 (x86_64/linux) 98ba92-dirty flags: STATS: Off, USE_IPV6, 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 ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 98ba92 -dirty compiled on 12:45:36 Feb 2 2012 with gcc 4.4.6 And this is the bt full from gdb Core was generated by `/usr/local/sbin/kamailio -m 1024'. Program terminated with signal 11, Segmentation fault. #0 mi_profile_list (cmd_tree=<value optimized out>, param=<value optimized out>) at dlg_profile.c:789 789 if ( mi_print_dlg( rpl, ph->dlg, 0)!=0 ) Missing separate debuginfos, use: debuginfo-install filesystem-2.4.30-2.1.el6.x86_64 glibc-2.12-1.25.el6_1.3.x86_64 keyutils-libs-1.4-1.el6.x86_64 krb5-libs-1.9-9.el6_1.2.x86_64 libcom_err-1.41.12-7.el6.x86_64 libselinux-2.0.94-5.el6.x86_64 mysql-libs-5.1.52-1.el6_0.1.x86_64 nss-softokn-freebl-3.12.7-1.1.el6.x86_64 openssl-1.0.0-20.el6_2.1.x86_64 pcre-7.8-3.1.el6.x86_64 zlib-1.2.3-26.el6.x86_64 (gdb) bt full #0 mi_profile_list (cmd_tree=<value optimized out>, param=<value optimized out>) at dlg_profile.c:789 node = <value optimized out> rpl_tree = 0x20a6790 rpl = 0x20a67b0 profile = 0x7fe99a2dda00 ph = 0x0 profile_name = <value optimized out> value = <value optimized out> i = <value optimized out> #1 0x00007fe9dce287b1 in run_mi_cmd (fifo_stream=<value optimized out>) at ../../lib/kmi/mi.h:77 No locals. #2 mi_fifo_server (fifo_stream=<value optimized out>) at fifo_fnc.c:509 mi_cmd = 0x208f8f0 mi_rpl = <value optimized out> hdl = 0x0 line_len = 41 file_sep = 0x2039017 "" command = 0x7fe9dfdbdef9 "profile_list_dlgs" file = 0x7fe9dfd98d78 "/tmp/openser_receiver_27809" f = 0x2039018 reply_stream = 0x20b0980 #3 0x00007fe9dce2a640 in fifo_process (rank=<value optimized out>) at mi_fifo.c:247 fifo_stream = 0x209a0b0 #4 0x00007fe9dce2a9de in mi_child_init (rank=0) at mi_fifo.c:211 pid = <value optimized out> #5 0x00000000004dba41 in init_mod_child (m=0x7fe9dfc6ba10, rank=0) at sr_module.c:886 No locals. #6 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6bd08, rank=0) at sr_module.c:883 No locals. #7 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6c248, rank=0) at sr_module.c:883 No locals. #8 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6c748, rank=0) at sr_module.c:883 No locals. #9 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6d288, rank=0) at sr_module.c:883 No locals. #10 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6d928, rank=0) at sr_module.c:883 No locals. #11 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6dee0, rank=0) at sr_module.c:883 No locals. #12 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6e1f0, rank=0) at sr_module.c:883 No locals. #13 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6e5d0, rank=0) at sr_module.c:883 No locals. #14 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6e830, rank=0) at sr_module.c:883 No locals. #15 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6ebd0, rank=0) at sr_module.c:883 No locals. #16 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6f220, rank=0) at sr_module.c:883 No locals. #17 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6f648, rank=0) at sr_module.c:883 No locals. #18 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6fa60, rank=0) at sr_module.c:883 No locals. #19 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc6fe40, rank=0) at sr_module.c:883 No locals. #20 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc702c0, rank=0) at sr_module.c:883 No locals. #21 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc70ae8, rank=0) at sr_module.c:883 No locals. ---Type <return> to continue, or q <return> to quit--- #22 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc70e18, rank=0) at sr_module.c:883 No locals. #23 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc71100, rank=0) at sr_module.c:883 No locals. #24 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc716c0, rank=0) at sr_module.c:883 No locals. #25 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc71df0, rank=0) at sr_module.c:883 No locals. #26 0x00000000004db9c4 in init_mod_child (m=0x7fe9dfc723c0, rank=0) at sr_module.c:883 No locals. #27 0x000000000046077d in main_loop () at main.c:1661 i = <value optimized out> pid = <value optimized out> si = 0x0 si_desc = "udp receiver child=15 sock=64.76.154.35:5060", '\000' <repeats 20 times>, "\003", '\000' <repeats 15 times>, "\030\325\a\232\351\177\000\000\001\000\000\000\002", '\000' <repeats 11 times>, "\001\000\000\000\000\000\000\000\003\000\000\000\000\000\000\000)\000\000\000\000\000\000" #28 0x0000000000461f13 in main (argc=<value optimized out>, argv=0x7fff2f2b2848) at main.c:2475 cfg_stream = <value optimized out> c = <value optimized out> r = <value optimized out> tmp = 0x7fff2f2b3f76 "" tmp_len = 0 options = 0x5a3178 ":f:cm:M:dVhEb:l:L:n:vrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 1850310455 rfd = <value optimized out> debug_save = <value optimized out> debug_flag = <value optimized out> dont_fork_cnt = <value optimized out> n_lst = <value optimized out> p = <value optimized out> (gdb) Regards, Ricardo.-

4 7

TLS questions
by Fabian Borot 20 Nov '13

20 Nov '13

Hi, please help me out with these questions: Is it possible to configure kamailio to use different certificates, one per peer? Do we just add them to the same "calist.pem" file? Is is possible to configure kamailio to accept a certificate from another device? I mean instead of Kamailio creating the certificate/key and give it to customer/provider. If that is the case, do we also add it to the "calist.pem" file as well? If all the above is true, what happens when the certificates have different expiration dates? thank you very much

3 7

Variables in event_route[sl:local-response]
by Sergey Okhapkin 14 Nov '13

14 Nov '13

Which variables I can use in event_route[sl:local-response] route to xlog proto:ip:port to which the response will be sent? event_route[sl:local-response] { xlog("L_INFO","Local response to *$??*\n$mb\n"); }

3 2

BUG? - Dialog module timeout BYE is not ok.
by Uri Shacked 11 Nov '13

11 Nov '13

Hi, Following this issue, and the issue "BYE dialog timeout bad syntax" from Julia. I have 2 kamailio servers. srv1 creates a dlg_timeout BYE and sends it to srv2 that forwards the BYE to the next sip server (some other server...). I can definitely see that the BYE that is being forward is malformed. The TO header info is not complete (the port section for example). When a "normal" bye is received from srv1 (not dlg_timeout) all works fine. One thing that i do in this scenario, on srv2 i use uac_replace() on the TO header. So, it is OK that the final destination is different (i do translations). I attached the BYE from both servers. Any ideas? Thanks, Uri You probably meant the To and From headers, I'm guessing. Yeah, as long as there is no display name component, URIs in headers like that don't have to go in <>s. The way Kamailio sends it is grammatically valid, per RFC 3261. The user agents are at fault for not understanding it correctly. Alex Balashov <abalashov at evaristesys.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>> wrote: >*"BYE headers"? Which headers? *>* *>*Uri Shacked <ushacked at gmail.com <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>> wrote: *>* *>>*Hi, *>>* *>>*I think there is a bug with the BYE that is sent to the caller and *>>*callee *>>*when dialog timeout happends. *>>* *>> *The BYE headers are sent with no "<" or ">". *>>*So, some sip singaling points decline the BYE. *>>* *>>*BR, *>>*Uri *>>* *>>* *>>*------------------------------------------------------------------------ *>>* *>>*_______________________________________________ *>>*SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing *>*list *>>*sr-users at lists.sip-router.org<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> *>>*http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users *>* *>*-- *>*Sent from my mobile, and thus lacking in the refinement one might *>*expect from a fully-fledged keyboard. *>* *>*Alex Balashov - Principal *>*Evariste Systems LLC *>*235 E Ponce de Leon Ave *>*Suite 106 *>*Decatur, GA 30030 *>*United States *>*Tel: +1-678-954-0670 *>*Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ *>* *>*_______________________________________________ *>*SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list * >*sr-users at lists.sip-router.org<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> *>*http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users * -- Sent from my Nexus 10, with all the figments of autocorrect that might imply. Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.sip-router.org/pipermail/sr-users/attachments/20130422/0c75272…>

4 11

rfc: accounting records time details
by Daniel-Constantin Mierla 05 Sep '13

05 Sep '13

Hello, there were old and recent discussions about the representation of time in accounting records. At this moment the acc module stores the unix timestamp as datetime value. In some countries is required to store more accuracy, beyond the seconds. Also, the datetime gives some troubles with converting back to unix timestamp, specifically with time zones and daylight saving times. I want to open a discussion that is visible for all users and devs, being something affecting probably everyone, input from anyone that is interested being relevant to select the right approach. Here are some suggestions presented so far. 1) store seconds.miliseconds as double - there is a patch (which probably needs some tunings itself) on tracker. The precision is shifted from seconds to milliseconds. Internally computed from microseconds from timeval structure. The other modules might need updates (iirc dbtext has only 2 decimals precisions for double, while miliseconds will require at least three -- could be the case for flatstore or other modules). Advantage is the computing of duration directly by subtraction of two values. 2) store seconds and microseconds as two separate values. Should be no issues with existing modules. Even more accuracy than above, no issues with other modules, but will require to use two columns (thus four values to compute the duration) Any other suggestions? Personally, at this moment, I will go with 2), but that might not meet everyone's needs. So a solution can be to make it configurable, as a bitmask of what time representation to store. Say, there will be a new parameter timestamp_mode for acc module: - bit one set - store seconds timestamp as for now (default) - bit two set - store seconds and microseconds in separate integer columns - bit three set - store seconds.miliseconds as double value in one column I could add the parameter and tune acc for bit one and two. For bit three a deeper review is needed for other modules, probably the developer that submitted to the tracker can do it. More suggestions? Pro or cons opinions? Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, San Francisco, USA - June 24016, 2013 * http://asipto.com/u/katu *

4 9

[Kamailio-Users] Error in Running kamailio !!
by Dinesh gautam 25 Jul '13

25 Jul '13

Dear Sir, I am using kamailio 1.5.0, having installed and configured as given on the kamailio site <http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-1.5.x-from-svn> on my PC having Centos operating system. I have configured the config files kamailio.cfg, kamctlrc accordingly as given on site. when I start the kamailio using kamctl start command. it gives the error message like *[root@localhost ~]# kamctl start database engine 'MYSQL' loaded Control engine 'FIFO' loaded INFO: Starting Kamailio : ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed *please* *help me out to solve this problem and suggest me where I am wrong. * *I have configured kamalio so many times it gives me the same kind of error message. * * - With Regards, Dinesh Kumar Gautam Noida, +919911838275

6 15

How to tie Registration with Client TCP connection
by Krishna Kurapati 24 Jul '13

24 Jul '13

Hi, With TCP, there is no way Server can establish a TCP connection through client's Firewall/NAT. So, when Client connection is disconnected from the server due to Network issues, the Registration should be removed. I tried to handle this with a Event Route in tcp_read.c. However, There is not an easy way to find the Registration with TCP socket info (IP and Port of the Client). Could anyone suggest a solution? Thanks Krish Kura

3 2

Kamailio 4.0.1 presence support
by Rupayan Dutta 24 Jul '13

24 Jul '13

Hello, I've been trying to make the Presence thing work with kamailio 4.0.1 and SipML5 browser client .I have loaded only the modules which are already in the Kamailio.cfg file loadmodule "presence.so" loadmodule "presence_xml.so" Is it necessary to load other modules as well?At the same time I request you to suggest which Sip client I should use in order to make presence work. Rupayan Dutta

2 4

rtimer forking error while starting Kamailio
by Krishna Kurapati 22 Jul '13

22 Jul '13

Hi, After few crashes of the Kamailio during prcessing of the messages, Kamailio fails to start I see rtimer is failing. Here is the log 0(20082) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (0): sqlops 0(20082) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (0): app_lua 0(20082) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (0): rtimer 0(20082) ERROR: rtimer [rtimer_mod.c:162]: failed to start timer routine as process 0(20082) ERROR: <core> [sr_module.c:896]: init_mod_child(): Error while initializing module rtimer (/usr/local/lib64/imckamailio/modules/rtimer.so) 0(20082) ERROR: <core> [main.c:1716]: ERROR: main: error in init_child 6(20091) INFO: <core> [main.c:854]: INFO: signal 15 received What can I do to fix this issue? Thanks Krish

2 1

Kamailio config syntax check leads to memory error
by Fred 09 Jul '13

09 Jul '13

Hi everyone, I'm using Kamailio 3.2.1 with a quite big config file. After adding some new config lines I did a syntax check of the configuration file with "kamailio -c -f <file>" and got the following error output: loading modules under /opt/kamailio/lib/kamailio/modules_k/:/opt/kamailio/lib/kamailio/modules/ 0(28755) : <core> [cfg.lex:1426]: ERROR:lex:addstr: memory allocation error 0(28755) : <core> [cfg.lex:1428]: ERROR:lex:addstr: try to increase pkg size with -M parameter increasing the pkg memory (-M) or shared memory (-m) has no effect. I played around with the size of the configuration file with xlog lines and the cause really seems to be the size of the config file. Restart of Kamailio is possible without problems, it is only the syntax check that leads to the memory error output Is there any possibility to increase the memory for the syntax check? Regards Fred

2 2

Jump to page:

2025

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 June 2013