sr-users October 2015

sr-users@lists.kamailio.org

77 participants
125 discussions

segmentation fault when mongodb & tls enabled. ( kamailio 4.3.2)

by Jijo

I'm observing a segmentation fault when mongodb & tls enabled. It doesn't happen when one of the module is disabled. OS: centos 6.7 kamailio 4.3.2 mongo-c-driver version 1.1.10. It happens immediately after i register a subscriber. The location table is updated with the new data and in parallel core is generated as well. Loaded symbols for /lib64/libnss_dns-2.12.so Core was generated by `/usr/local/kamailio_proxy/sbin/kamailio -f /usr/local/kamailio_proxy/etc/kamail'. Program terminated with signal 11, Segmentation fault. #0 0x00007fd3adf65e69 in atomic_cmpxchg_int (var=0x56444e3055445030, old=0, new_v=1) at ../../atomic/atomic_x86.h:233 233 ATOMIC_FUNC_CMPXCHG(cmpxchg, "cmpxchgl %2, %1", int , int) Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-15.el6_6.2.x86_64 cyrus-sasl-plain-2.1.23-15.el6_6.2.x86_64 db4-4.7.25-19.el6_6.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-42.el6.x86_64 libcom_err-1.41.12-22.el6.x86_64 libcurl-7.19.7-46.el6.x86_64 libidn-1.18-2.el6.x86_64 libselinux-2.0.94-5.8.el6.x86_64 libssh2-1.4.2-1.el6_6.1.x86_64 libunistring-0.9.3-5.el6.x86_64 libxml2-2.7.6-20.el6.x86_64 mysql-libs-5.1.73-5.el6_6.x86_64 nspr-4.10.8-1.el6_6.x86_64 nss-3.18.0-5.3.el6_6.x86_64 nss-util-3.18.0-1.el6_6.x86_64 openldap-2.4.40-5.el6.x86_64 openssl-1.0.1e-42.el6.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt #0 0x00007fd3adf65e69 in atomic_cmpxchg_int (var=0x56444e3055445030, old=0, new_v=1) at ../../atomic/atomic_x86.h:233 #1 0x00007fd3adf65eb6 in futex_get (lock=0x56444e3055445030) at ../../futexlock.h:99 #2 0x00007fd3adf66468 in prv_lock_tree_branch (b=192 '\300') at ip_tree.c:47 #3 0x00007fd3adf664e5 in lock_tree_branch (b=192 '\300') at ip_tree.c:66 #4 0x00007fd3adf6dda6 in swap_routine (ticks=123206032, param=0x0) at pike_funcs.c:293 #5 0x00000000005fef8e in compat_old_handler (ti=1971296512, tl=0x7fd32ccea430, data=0x7fd32ccea430) at timer.c:996 #6 0x00000000005ff94c in slow_timer_main () at timer.c:1130 #7 0x00000000004a8676 in main_loop () at main.c:1628 #8 0x00000000004ae38e in main (argc=11, argv=0x7fff1d97ec28) at main.c:2533 (gdb) On Clean up after the core, mongo db does segmentation fault as well Loaded symbols for /lib64/libnss_files-2.12.so Reading symbols from /lib64/libnss_dns-2.12.so...Reading symbols from /usr/lib/debug/lib64/libnss_dns-2.12.so.debug...done. done. Loaded symbols for /lib64/libnss_dns-2.12.so Core was generated by `/usr/local/kamailio_proxy/sbin/kamailio -f /usr/local/kamailio_proxy/etc/kamail'. Program terminated with signal 11, Segmentation fault. #0 __pthread_mutex_destroy (mutex=0x7fd32cce7be8) at pthread_mutex_destroy.c:28 28 if ((mutex->__data.__kind & PTHREAD_MUTEX_ROBUST_NORMAL_NP) == 0 Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-15.el6_6.2.x86_64 cyrus-sasl-plain-2.1.23-15.el6_6.2.x86_64 db4-4.7.25-19.el6_6.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-42.el6.x86_64 libcom_err-1.41.12-22.el6.x86_64 libcurl-7.19.7-46.el6.x86_64 libidn-1.18-2.el6.x86_64 libselinux-2.0.94-5.8.el6.x86_64 libssh2-1.4.2-1.el6_6.1.x86_64 libunistring-0.9.3-5.el6.x86_64 libxml2-2.7.6-20.el6.x86_64 mysql-libs-5.1.73-5.el6_6.x86_64 nspr-4.10.8-1.el6_6.x86_64 nss-3.18.0-5.3.el6_6.x86_64 nss-util-3.18.0-1.el6_6.x86_64 openldap-2.4.40-5.el6.x86_64 openssl-1.0.1e-42.el6.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt #0 __pthread_mutex_destroy (mutex=0x7fd32cce7be8) at pthread_mutex_destroy.c:28 #1 0x00007fd32c86f9e6 in _mongoc_ssl_thread_cleanup () at src/mongoc/mongoc-ssl.c:555 #2 _mongoc_ssl_cleanup () at src/mongoc/mongoc-ssl.c:106 #3 0x00007fd32c8606a9 in _mongoc_do_cleanup () at src/mongoc/mongoc-init.c:127 #4 0x000000344480cdb3 in pthread_once () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_once.S:104 #5 0x00007fd32c8523df in __do_global_dtors_aux () from /usr/lib64/libmongoc-1.0.so.0.0.0 #6 0x0000000000000000 in ?? () (gdb) mongo-c-driver version 1.1.10 version: kamailio 4.3.2 (x86_64/linux) b5980b-dirty flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_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 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: b5980b -dirty compiled on 13:35:24 Sep 28 2015 with gcc 4.

9 years

pv_printf buffer for spec value

by Sven Neuhaus

Hello, I'm getting these errors since the last couple of changes I made to the Kamailio 4.3.x configuration: ERROR: <core> [pvapi.c:1361]: pv_printf(): no more space for spec value ERROR: <core> [pvapi.c:1370]: pv_printf(): buffer overflow -- increase the buffer size... I'm not even using pv_printf() so this error is a bit surprising. The first thing I tried was increasing the buffer from its default size of 1024 to 4096 (pv_buffer_size=4096) but the error messages persist. What other functions use this buffer? Regards, -Sven Neuhaus

9 years

listening on multiple port

by Thibault Gueslin

I would like to set up kamailio in order to listen to multiple port. I have set : port=5060 port=5228 But it always listen on the port indicated on last line: Listening on udp: 127.0.0.1:5228 udp: x.x.x.x:5228 tcp: 127.0.0.1:5228 tcp: x.x.x.x:5228 Aliases: I don't have any "listen" in my config file. Is it supposed to work like that ?

9 years

[CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded

by Daniel Pocock

FOSDEM is one of the world's premier meetings of free software developers, with over five thousand people attending each year. FOSDEM 2016 takes place 30-31 January 2016 in Brussels, Belgium. http://fosdem.org This email contains information about: - Real-Time communications dev-room and lounge, - speaking opportunities, - volunteering in the dev-room and lounge, - related events around FOSDEM, including the XMPP summit, - social events (including the Saturday night dinner), - the Planet aggregation sites for RTC blogs Call for participation - Real Time Communications (RTC) ======================================================= The Real-Time dev-room and Real-Time lounge is about all things involving real-time communication, including: XMPP, SIP, WebRTC, telephony, mobile VoIP, codecs, privacy and encryption. The dev-room is a successor to the previous XMPP and telephony dev-rooms. We are looking for speakers for the dev-room and volunteers and participants for the tables in the Real-Time lounge. The dev-room is only on Saturday, 30 January 2016. The lounge will be present for both days. To discuss the dev-room and lounge, please join the FSFE-sponsored Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc Speaking opportunities ---------------------- Note: if you used Pentabarf before, please use the same account/username Main track: the deadline for main track presentations is midnight today, 30 October. Leading developers in the Real-Time Communications field are encouraged to consider submitting a presentation to the main track at https://fosdem.org/submit Real-Time Communications dev-room: deadline 27 November Please also use the Pentabarf system to submit a talk proposal for the dev-room. On the "General" tab, please look for the "Track" option and choose "Real-Time devroom". https://penta.fosdem.org/submission/FOSDEM16/ Other dev-rooms: some speakers may find their topic is in the scope of more than one dev-room. It is permitted to apply to more than one dev-room but please be kind enough to tell us if you do this. You can find the full list of dev-rooms at https://www.fosdem.org/2016/schedule/tracks/ Lightning talks: deadline 27 November The lightning talks are an excellent opportunity to introduce a wider audience to your project. Given that dev-rooms are becoming increasingly busy, all speakers are encouraged to consider applying for a lightning talk as well as a slot in the dev-room. On the "General" tab, please look for the "Track" option and choose "Lightning Talks". https://fosdem.org/submit First-time speaking? -------------------- FOSDEM dev-rooms are a welcoming environment for people who have never given a talk before. Please feel free to contact the dev-room administrators personally if you would like to ask any questions about it. Submission guidelines --------------------- The Pentabarf system will ask for many of the essential details. Please remember to re-use your account from previous years if you have one. In the "Submission notes", please tell us about: - the purpose of your talk - any other talk applications (dev-rooms, lightning talks, main track) - availability constraints and special needs You can use HTML in your bio, abstract and description. If you maintain a blog, please consider providing us with the URL of a feed with posts tagged for your RTC-related work. We will be looking for relevance to the conference and dev-room themes, presentations aimed at developers of free and open source software about RTC-related topics. Please feel free to suggest a duration between 20 minutes and 55 minutes but note that the final decision on talk durations will be made by the dev-room administrators. As the two previous dev-rooms have been combined into one, we may decide to give shorter slots than in previous years so that more speakers can participate. Please note FOSDEM aims to record and live-stream all talks. The CC-BY license is used. For any questions, please join the FSFE-sponsored Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc Volunteers needed ================= To make the dev-room and lounge run successfully, we are looking for volunteers: - FOSDEM provides video recording equipment and live streaming, volunteers are needed to assist in this - organizing one or more restaurant bookings (dependending upon number of participants) for the evening of Saturday, 30 January - participation in the Real-Time lounge - helping attract sponsorship funds for the dev-room to pay for the Saturday night dinner and any other expenses - circulating this Call for Participation to other mailing lists FOSDEM is made possible by volunteers and if you have time to contribute, please feel free to get involved through https://volunteers.fosdem.org/ Related events - XMPP and RTC summits ===================================== The XMPP Standards Foundation (XSF) has traditionally held a summit in the days before FOSDEM. There is discussion about a similar summit taking place on 28 and 29 January 2016 http://wiki.xmpp.org/web/Summit_19 - please join the mailing list for details: http://mail.jabber.org/mailman/listinfo/summit We are also considering a more general RTC or telephony summit, potentially on 29 January. Please join the Free-RTC mailing list and send an email if you would be interested in participating, sponsoring or hosting such an event. Social events and dinners ========================= The traditional FOSDEM beer night occurs on Friday, 29 January On Saturday night, there are usually dinners associated with each of the dev-rooms. Most restaurants in Brussels are not so large so these dinners have space constraints. Please subscribe to the Free-RTC mailing list for further details about the Saturday night dinner options and how you can register for a seat: https://lists.fsfe.org/mailman/listinfo/free-rtc Spread the word and discuss =========================== If you know of any mailing lists where this CfP would be relevant, please forward this email. If this dev-room excites you, please blog or microblog about it, especially if you are submitting a talk. If you regularly blog about RTC topics, please send details about your blog to the planet site administrators: http://planet.jabber.org ralphm(a)ik.nu http://planet.sip5060.net daniel(a)pocock.pro http://planet.opentelecoms.org daniel(a)pocock.pro Please also link to the Planet sites from your own blog or web site. Contact ======= For discussion and queries, please join the free-rtc mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc The dev-room administration team: Daniel Pocock <daniel(a)pocock.pro> Ralph Meijer <ralphm(a)ik.nu> Saúl Ibarra Corretgé <saul(a)ag-projects.com> Iain R. Learmonth <irl(a)debian.org>

9 years

Huge TLS performance regression migrating from 3.3.7 to 4.2.6

by Tristan Mahé

Hi List, I've been reaching a strange thing lately, trying to upgrade to kamailio 4.2.6 ( identical config ): - 35% loss of performance on TLS connections ( Sipp REGISTER scenario, easily reproduced ). - more TCP workers needed to ease the TCP queues ( 32 workers on 3.3.7, at least 64 are needed on 4.2.6 to avoid "queue full" messages in logs ). - kamailio 4.2.6 intermittent processing of requests ( Kamailio stops accepting new tcp connections, then resume a bit later, then stops again,... ) => starts happening when Kamailio is treating more than 20k tcp connections, with between 500-1k req/s. During those periods, trying to connect to kamailio with an openssl s_client -connect will end up in a timeout or with a long delay before the certificate is received ( 03 CONNECTED ). - kamailio 4.2.6 dropping connections, kamailio 3.3.7 keeping those connections: after a while, the number of active connections starts to decrease on kam4, on kam3 it stays constant. I was wondering if I was alone in this situation or if someone else is impacted, has some advices ? It does not seem to be a config issue, as it is the same that was deployed with both versions.

9 years

DB Problems after upgrade

by Nahum Nir

Hi All, I had a working Kamailio with Siremis. I upgraded wanted a new cfg file (big mistake, I know). I defined the DBURL at kamailio.cfg and the server start without errors, users can register but I can not make calls and Siremis missed calls table is not updated. What files and where should I update? Should I run kamdbctl? Thanks, Nir

9 years

Kamailio configuration file rtpproxy_manage not found when starting

by amar Smart Telecom

Dear All, I was trying to make such that rtpproxy is used for all calls in kamailio, Part of Kamailio.cfg looks like following: ============================= loadmodule "rtpproxy.so" # ----- rtpproxy params ----- modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { if(!t_is_set("branch_route")) t_on_branch("MANAGE_BRANCH"); } if (is_method("INVITE|SUBSCRIBE|UPDATE")) { if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY"); rtpproxy_manage("co") ; # added amar 20151015 } if (is_method("INVITE")) { if(!t_is_set("failure_route")) t_on_failure("MANAGE_FAILURE"); } if (!t_relay()) { sl_reply_error(); } exit; } But when I run Kamailio start it gives error: Error looks like following: =================== Oct 15 16:13:42 smart kamailio[18472]: * Not starting Kamailio SIP server: invalid configuration file! Oct 15 16:13:42 smart kamailio[18472]: * Oct 15 16:13:42 smart kamailio[18472]: * 0(18480) ERROR: <core> [cfg.y:3299]: yyparse(): cfg. parser: failed to find command rtpproxy_manage (params 1) What could be the problem?

9 years

kamctl fifo t_uac_dlg TLS

by Ahmed Salem

Hi, I have a kamailio tls configuration which is working fine for calls & messages In the tls configuration i set these parameters to yes for the server and client verify_certificate = yes require_certificate = yes But when I use "kamctl fifo t_uac_dlg MESSAGE" to send a message I get the following errors, when verify_certificate & require_certificate are set to no the message is sent correctly. Can somebody please help me resolve this issue. tls [tls_server.c:1193]: tls_read_f(): TLS write:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading tls [tls_server.c:1193]: tls_read_f(): TLS accept:error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading Thanks Ahmed

9 years

dmq_usrloc for writing to DB on one machine

by Sebastian Damm

Hi, I evaluated the dmq_usrloc module, and it works pretty good if there are two identical machines which replicate their location with each other. But what I actually want to do is to send registrations to an extra machine which is just there for writing the location into a central DB (in one table for all the registrars), from where it can be accessed (by a web page for example). So for example, I have three machines, registrar 1 and registrar 2, and receiver. receiver will never interact with customers. It is just there for writing the location into the database. I configured both registrars to send their packets to receiver, and I configured the receiver to send its packets (which it actually never does) to a dns name containing both registrars. But after reading the content of some PING messages and reading something about "autodiscovery" of dmq on the mailing list, I'm not sure whether my scenario will work the way I want it to. Can somebody explain whether I can use dmq_usrloc for this purpose? Or is it only intended to be used for bidirectional replication? Best Regards, Sebastian

9 years

100% CPU usage after NTP date update

by Stefan Kohlhauser

Hello everyone! Setup: I am currently using a Kamailio 4.2.3 on an embedded device (low CPU and RAM). The device is not able to store the current date, so after a reboot its 1. Jan 1970 until NTP updates the date. Problem: If the date is updated after the Kamailio has started (a leap of 45 years) the Kamailio uses up all the CPU and renders the device useless for a very long time. Notes: There are no incomming requests at the time. (But the Kamailio is not responsive during that time anyway.) Adjusting the internal Kamailio-time seems to take longer when the date update leap is bigger. My questions: 1) Can I prevent the Kamailio from using up the entire CPU after a date update? Or maybe do the internal ticks-update more gracefully? 2) For my better understanding: What happens within the Kamailio after adjust_ticks has updated the internal date? Thanks in advance for your help! Best regards, Stefan

9 years

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 October 2015