sr-users March 2020

sr-users@lists.kamailio.org

64 participants
80 discussions

by Henning Westerholt

Hi Virgilio, there is a page in the old wiki: https://www.kamailio.org/dokuwiki/doku.php/development:release-policy about it. Basically, the last two stable version are supported. We release roughly every 10-12 month a new major release, the next one probably this summer (e.g. 5.4.0). I estimate the 5.3 branch will be maintained until roughly second/third quarter of 2021, so there is still plenty of time. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Virgílio Cunha Sent: Wednesday, March 18, 2020 7:23 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] Segmentation fault in DMQ module Hi, Sorry for using this topic for this question, but where can I find Kamailio's release policy? I needed to know how long the kamailio 5.3.x branch will maintain its support. Best Regards, Virgílio Cunha Em ter., 17 de mar. de 2020 às 11:03, Daniel-Constantin Mierla <miconda(a)gmail.com<mailto:miconda@gmail.com>> escreveu: Hello, if it is a runtime issue, then it is better to upgrade to a supported release series and try to reproduce it. Looking at startup/shutdown code is easier than the rest used during runtime by a module, but it is not the case here. So we may waste a lot of time to dig into it and discover it was fixed or the code in an older release was refactored not matching any longer what is now in stable releases. Cheers, Daniel On 17.03.20 11:35, Virgílio Cunha wrote: Hi, The problem does not just occur when kamailio is restarted. The restart was the way I found to reproduce the problem, because when a proxy is restarted, there is more traffic from DMQ messages, so the problem is more likely to occur. The full backtrace is following: GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /opt/ptin/kamailio-ksipadp/bin/ksipadp-proxy...Reading symbols from /usr/lib/debug/usr/sbin/kamailio.debug...done. done. [New Thread 506] Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /usr/lib64/kamailio/modules/db_postgres.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/db_postgres.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/db_postgres.so Reading symbols from /usr/lib64/libpq.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libpq.so.5 Reading symbols from /usr/lib64/kamailio/libsrdb2.so.1...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/libsrdb2.so.1.0.debug...done. done. Loaded symbols for /usr/lib64/kamailio/libsrdb2.so.1 Reading symbols from /usr/lib64/kamailio/libsrdb1.so.1...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/libsrdb1.so.1.0.debug...done. done. Loaded symbols for /usr/lib64/kamailio/libsrdb1.so.1 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libldap_r-2.4.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libldap_r-2.4.so.2 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/liblber-2.4.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/liblber-2.4.so.2 Reading symbols from /usr/lib64/libsasl2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libsasl2.so.2 Reading symbols from /usr/lib64/libssl3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl3.so Reading symbols from /usr/lib64/libsmime3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libsmime3.so Reading symbols from /usr/lib64/libnss3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libnss3.so Reading symbols from /usr/lib64/libnssutil3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libnssutil3.so Reading symbols from /lib64/libplds4.so...(no debugging symbols found)...done. Loaded symbols for /lib64/libplds4.so Reading symbols from /lib64/libplc4.so...(no debugging symbols found)...done. Loaded symbols for /lib64/libplc4.so Reading symbols from /lib64/libnspr4.so...(no debugging symbols found)...done. Loaded symbols for /lib64/libnspr4.so Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libcrypt.so.1 Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libfreebl3.so...(no debugging symbols found)...done. Loaded symbols for /lib64/libfreebl3.so Reading symbols from /usr/lib64/kamailio/modules/ctl.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/ctl.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/ctl.so Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Reading symbols from /usr/lib64/kamailio/modules/kex.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/kex.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/kex.so Reading symbols from /usr/lib64/kamailio/libsrutils.so.1...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/libsrutils.so.1.0.debug...done. done. Loaded symbols for /usr/lib64/kamailio/libsrutils.so.1 Reading symbols from /lib64/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libm.so.6 Reading symbols from /usr/lib64/kamailio/modules/tm.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/tm.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/tm.so Reading symbols from /usr/lib64/kamailio/modules/tmx.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/tmx.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/tmx.so Reading symbols from /usr/lib64/kamailio/modules/corex.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/corex.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/corex.so Reading symbols from /usr/lib64/kamailio/modules/cfg_rpc.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/cfg_rpc.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/cfg_rpc.so Reading symbols from /usr/lib64/kamailio/modules/sl.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/sl.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/sl.so Reading symbols from /usr/lib64/kamailio/modules/rr.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/rr.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/rr.so Reading symbols from /usr/lib64/kamailio/modules/maxfwd.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/maxfwd.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/maxfwd.so Reading symbols from /usr/lib64/kamailio/modules/siputils.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/siputils.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/siputils.so Reading symbols from /usr/lib64/kamailio/modules/sanity.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/sanity.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/sanity.so Reading symbols from /usr/lib64/kamailio/modules/textops.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/textops.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/textops.so Reading symbols from /usr/lib64/kamailio/modules/textopsx.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/textopsx.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/textopsx.so Reading symbols from /usr/lib64/kamailio/modules/dmq.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/dmq.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/dmq.so Reading symbols from /usr/lib64/kamailio/modules/htable.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/htable.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/htable.so Reading symbols from /usr/lib64/kamailio/modules/pv.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/pv.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/pv.so Reading symbols from /usr/lib64/kamailio/modules/xlog.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/xlog.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/xlog.so Reading symbols from /usr/lib64/kamailio/modules/jsonrpcs.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/jsonrpcs.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/jsonrpcs.so Reading symbols from /usr/lib64/kamailio/modules/uac.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/uac.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/uac.so Reading symbols from /usr/lib64/kamailio/modules/uac_redirect.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/uac_redirect.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/uac_redirect.so Reading symbols from /usr/lib64/kamailio/modules/db_text.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/db_text.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/db_text.so Reading symbols from /usr/lib64/kamailio/modules/dispatcher.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/dispatcher.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/dispatcher.so Reading symbols from /usr/lib64/kamailio/modules/sqlops.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/sqlops.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/sqlops.so Reading symbols from /usr/lib64/kamailio/modules/regex.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/regex.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/regex.so Reading symbols from /lib64/libpcre.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libpcre.so.0 Reading symbols from /usr/lib64/kamailio/modules/permissions.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/permissions.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/permissions.so Reading symbols from /usr/lib64/kamailio/modules/dialplan.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/dialplan.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/dialplan.so Reading symbols from /usr/lib64/kamailio/modules/mtree.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/mtree.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/mtree.so Reading symbols from /usr/lib64/kamailio/modules/cfgutils.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/cfgutils.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/cfgutils.so Reading symbols from /usr/lib64/kamailio/modules/statsd.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/statsd.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/statsd.so Reading symbols from /usr/lib64/kamailio/modules/app_lua.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/app_lua.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/app_lua.so Reading symbols from /usr/lib64/liblua-5.1.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/liblua-5.1.so<http://liblua-5.1.so> Reading symbols from /usr/lib64/kamailio/modules/rtimer.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/rtimer.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/rtimer.so Reading symbols from /usr/lib64/kamailio/modules/mqueue.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/mqueue.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/mqueue.so Reading symbols from /usr/lib64/kamailio/modules/auth.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/auth.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/auth.so Reading symbols from /usr/lib64/kamailio/modules/usrloc.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/usrloc.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/usrloc.so Reading symbols from /usr/lib64/kamailio/modules/registrar.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/registrar.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/registrar.so Reading symbols from /usr/lib64/kamailio/modules/dmq_usrloc.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/dmq_usrloc.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/dmq_usrloc.so Reading symbols from /usr/lib64/kamailio/modules/xhttp.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/xhttp.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/xhttp.so Reading symbols from /usr/lib64/kamailio/modules/exec.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/exec.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/exec.so Reading symbols from /usr/lib64/kamailio/modules/http_client.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/http_client.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/http_client.so Reading symbols from /usr/lib64/libxml2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libxml2.so.2 Reading symbols from /usr/lib64/libcurl.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcurl.so.4 Reading symbols from /lib64/libidn.so.11...(no debugging symbols found)...done. Loaded symbols for /lib64/libidn.so.11 Reading symbols from /lib64/libldap-2.4.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libldap-2.4.so.2 Reading symbols from /usr/lib64/libssh2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssh2.so.1 Reading symbols from /usr/lib64/kamailio/modules/json.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/json.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/json.so Reading symbols from /lib64/libjson-c.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libjson-c.so.2 Reading symbols from /usr/lib64/kamailio/modules/ipops.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/ipops.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/ipops.so Reading symbols from /lib64/libnss_dns.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_dns.so.2 Core was generated by `/opt/ptin/kamailio-ksipadp/bin/ksipadp-proxy -f /opt/ptin/kamailio-ksipadp/prox'. Program terminated with signal 11, Segmentation fault. #0 0x00007fefe58ea7c4 in atomic_get (v=0x0) at ../../core/atomic/atomic_common.h:66 66 return atomic_get_int(&(v->val)); Missing separate debuginfos, use: debuginfo-install kamailio-ksipadp-2.8.0-1.ptin.el6.x86_64 (gdb) bt full #0 0x00007fefe58ea7c4 in atomic_get (v=0x0) at ../../core/atomic/atomic_common.h:66 No locals. #1 0x00007fefe58ee246 in job_queue_size (queue=0x0) at worker.c:254 No locals. #2 0x00007fefe58ed920 in add_dmq_job (msg=0x7ff028b453f8, peer=0x7fefebcc4df8) at worker.c:184 i = 1 found_available = 0 new_job = {f = 0x7fefe2613797 <usrloc_dmq_handle_msg>, msg = 0x7fefebce67c8, orig_peer = 0x7fefebcc4df8, next = 0x0, prev = 0x0} worker = 0x7fefe7a1d890 cloned_msg = 0x7fefebce67c8 cloned_msg_len = 3888 __FUNCTION__ = "add_dmq_job" #3 0x00007fefe58dfec1 in dmq_handle_message (msg=0x7ff028b453f8, str1=0x0, str2=0x0) at message.c:66 peer = 0x7fefebcc4df8 __FUNCTION__ = "dmq_handle_message" #4 0x0000000000433729 in do_action (h=0x7ffc89e35670, a=0x7ff0285a9340, msg=0x7ff028b453f8) at core/action.c:1054 ret = -5 v = 1 dst = {send_sock = 0x7ff0285a8810, to = {s = {sa_family = 21376, sa_data = "\343\211\374\177\000\000\370S\264(\360\177\000"}, sin = { sin_family = 21376, sin_port = 35299, sin_addr = {s_addr = 32764}, sin_zero = "\370S\264(\360\177\000"}, sin6 = {sin6_family = 21376, sin6_port = 35299, sin6_flowinfo = 32764, sin6_addr = {__in6_u = {__u6_addr8 = "\370S\264(\360\177\000\000pV\343\211\374\177\000", __u6_addr16 = {21496, 10420, 32752, 0, 22128, 35299, 32764, 0}, __u6_addr32 = {682906616, 32752, 2313377392, 32764}}}, sin6_scope_id = 1}}, id = 32764, proto = 0 '\000', send_flags = {f = 0, blst_imask = 0}} tmp = 0x389c422190 "" new_uri = 0x7c00000000 <Address 0x7c00000000 out of bounds> end = 0x6e00000077 <Address 0x6e00000077 out of bounds> crt = 0x389c98e120 "" cmd = 0x7ff0283219b0 len = 0 user = 0 uri = {user = {s = 0x7ffc89e34a10 "@K\343\211\374\177", len = 4459394}, passwd = {s = 0x7ffc89e34e80 "\356Q\343\211\374\177", len = 682906616}, host = {s = 0x7ff0285a9020 "\177\001", len = -1981589904}, port = {s = 0x0, len = 1}, params = { s = 0x7ff028b453f8 "\017", len = 295169284}, sip_params = {s = 0x32 <Address 0x32 out of bounds>, len = 1073741824}, headers = { s = 0x2000000 <Address 0x2000000 out of bounds>, len = 4289104}, port_no = 60676, proto = 5047, type = 2312043322, flags = 2168712452, transport = {s = 0x0, len = -1675583518}, ttl = {s = 0x89e34e90 <Address 0x89e34e90 out of bounds>, len = 35715777}, user_param = { s = 0xffffffff0000003c <Address 0xffffffff0000003c out of bounds>, len = -1671419584}, maddr = {s = 0x0, len = -1981592704}, method = { s = 0x389c603c48 "", len = -1671391960}, lr = {s = 0x0, len = -1981592544}, r2 = {s = 0x1dde9a0 " 9\336\001", len = 0}, gr = { s = 0x4 <Address 0x4 out of bounds>, len = 2479}, transport_val = {s = 0x389c422190 "", len = 1}, ttl_val = { s = 0x7ffc89e34b40 "pM\343\211\374\177", len = 5683491}, user_param_val = {s = 0x40e7e8 "\370\377\377\377\377\377\377\377@ݘ\234\070", len = -1671362728}, maddr_val = {s = 0x404130 "", len = 0}, method_val = {s = 0x1000003b4 <Address 0x1000003b4 out of bounds>, len = 0}, lr_val = {s = 0x7fefe7374b9a "%x%c%x%c", len = -1673386776}, r2_val = {s = 0x7ffc89e34bd0 "", len = -1981592584}, gr_val = { ---Type <return> to continue, or q <return> to quit--- s = 0x389c422190 "", len = 0}} next_hop = {user = {s = 0x1 <Address 0x1 out of bounds>, len = 40}, passwd = {s = 0x0, len = -1407107317}, host = { s = 0x2000000 <Address 0x2000000 out of bounds>, len = 31398688}, port = {s = 0x1dde9a0 " 9\336\001", len = 31320480}, params = { s = 0x7ffc89e34c20 "", len = -1981593152}, sip_params = {s = 0x7ffc89e34910 "\200N\343\211\374\177", len = 682906616}, headers = { s = 0x32 <Address 0x32 out of bounds>, len = 1073741824}, port_no = 0, proto = 512, type = ERROR_URI_T, flags = 4289104, transport = { s = 0x7ffc89e34900 "\020J\343\211\374\177", len = 4457737}, ttl = {s = 0x7ffc89e348f0 "", len = -1981593520}, user_param = { s = 0x7ffc89e34858 "\r", len = -1981593264}, maddr = {s = 0x7ffc89e34870 "", len = -1981593456}, method = {s = 0x7ffc89e348b0 "\r", len = -1981593392}, lr = {s = 0x8cd2d0 <Address 0x8cd2d0 out of bounds>, len = 13}, r2 = { s = 0x10100000002 <Address 0x10100000002 out of bounds>, len = -1}, gr = {s = 0x0, len = 0}, transport_val = {s = 0x0, len = 682906616}, ttl_val = {s = 0x7ff0285a9020 "\177\001", len = -1981593296}, user_param_val = {s = 0x7ffc89e34fa0 "\001\200\255\373\374\177", len = 0}, maddr_val = {s = 0x10000000d <Address 0x10000000d out of bounds>, len = -1981591296}, method_val = { s = 0x7fef00000000 <Address 0x7fef00000000 out of bounds>, len = -1671151657}, lr_val = {s = 0x7fefe7374ba2 "", len = 682906616}, r2_val = {s = 0x32 <Address 0x32 out of bounds>, len = 1073741824}, gr_val = {s = 0x2000000 <Address 0x2000000 out of bounds>, len = 4289104}} u = 0x389c4224e8 port = 0 dst_host = 0x89e34bd0 i = 32764 flags = 52 avp = 0x189e35040 st = {flags = 2313374752, id = 32764, name = {n = -1981593512, s = {s = 0x7ffc89e34858 "\r", len = -1981593152}, re = 0x7ffc89e34858}, avp = 0x7ffc89e347a0} sct = 0x0 sjt = 0x7ff028b453f8 rve = 0x32 mct = 0x40000000 rv = 0x7ffc89e34c20 rv1 = 0x2000000 c1 = {cache_type = 2313374144, val_type = 32764, c = {avp_val = {n = 1, s = {s = 0x1 <Address 0x1 out of bounds>, len = 1}, re = 0x1}, pval = { rs = {s = 0x1 <Address 0x1 out of bounds>, len = 1}, ri = -1407115050, flags = 52}}, i2s = "\000\000\000\000\000\000\000\000\274\224 \254\064\000\000\000\240G\343\211\374\177"} s = {s = 0x1 <Address 0x1 out of bounds>, len = -1981593512} srevp = {0x7ffc89e34960, 0x34ac208a97} mod_f_params = {{type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, { type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = { number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = { s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}} ---Type <return> to continue, or q <return> to quit--- __FUNCTION__ = "do_action" #5 0x00000000004404b8 in run_actions (h=0x7ffc89e35670, a=0x7ff0285a9340, msg=0x7ff028b453f8) at core/action.c:1552 t = 0x7ff0285a9340 ret = -1 mod = 0x1dde9a0 ms = 176570657 __FUNCTION__ = "run_actions" #6 0x0000000000433692 in do_action (h=0x7ffc89e35670, a=0x7ff0285a9668, msg=0x7ff028b453f8) at core/action.c:1045 ret = 1 v = 1 dst = {send_sock = 0x7ffc89e35380, to = {s = {sa_family = 61042, sa_data = "I", '\000' <repeats 12 times>}, sin = {sin_family = 61042, sin_port = 73, sin_addr = {s_addr = 0}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 61042, sin6_port = 73, sin6_flowinfo = 0, sin6_addr = {__in6_u = {__u6_addr8 = "\000\000\000\000\000\000\000\000\020\000\000\000\005\000\000", __u6_addr16 = { 0, 0, 0, 0, 16, 0, 5, 0}, __u6_addr32 = {0, 0, 16, 5}}}, sin6_scope_id = 673678288}}, id = 32752, proto = 0 '\000', send_flags = { f = 0, blst_imask = 32752}} tmp = 0x66307b "H\213E\270H\203\300\070\351O\003" new_uri = 0x7ff028a93048 "" end = 0x7ff028a93038 "\303l\256" crt = 0x2000000 <Address 0x2000000 out of bounds> cmd = 0x1773508 len = 6791248 user = 0 uri = {user = {s = 0xae6ecd "", len = 11430897}, passwd = {s = 0x7c95f8 "core: core/parser/msg_parser.c", len = 682507016}, host = { s = 0xae6c43 "To: <sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080>>\r\nFrom: <sip:usrloc@10.112.101.128:5060<http://sip:usrloc@10.112.101.128:5060>>;tag=8a3534eb92149bbe647f599d354f2511-090e\r\nCSeq: 10 KDMQ\r\nCall-ID: 409f4ac5788a8cc4-24333(a)10.112.101.128<mailto:409f4ac5788a8cc4-24333@10.112.101.128>\r\nContent-Length: 39"..., len = 11430924}, port = {s = 0x0, len = 682507072}, params = { s = 0x7ff028ae3c90 <incomplete sequence \350>, len = 0}, sip_params = {s = 0x7ffc89e35330 "\246", len = 6697083}, headers = { s = 0x7c9170 "core", len = -1981590832}, port_no = 8, proto = 0, type = ERROR_URI_T, flags = 30415600, transport = { s = 0xa8428197 <Address 0xa8428197 out of bounds>, len = -1675583518}, ttl = {s = 0x3000000030 <Address 0x3000000030 out of bounds>, len = 44108294}, user_param = {s = 0x400000017 <Address 0x400000017 out of bounds>, len = 8176032}, maddr = {s = 0x0, len = -1981590448}, method = {s = 0x389c603c48 "", len = 11431629}, lr = {s = 0x7ffc89e35450 "\220T\343\211\374\177", len = 6869803}, r2 = { s = 0x7cc190 "get_hdr_field", len = 6730416}, gr = {s = 0x7ffc89e35300 "", len = 673677328}, transport_val = {s = 0x389c422190 "", len = 673677328}, ttl_val = {s = 0x7ffc89e35350 "\200S\343\211\374\177", len = -413652166}, user_param_val = {s = 0x40e7f9 "", len = 0}, maddr_val = {s = 0x2000000 <Address 0x2000000 out of bounds>, len = 24588552}, method_val = { s = 0x67a450 "\030A\211\321A)\301D\211ȉ\302H\213\205(\377\377\377\211P \276\004", len = 8965880}, lr_val = { s = 0x8cd2d0 <Address 0x8cd2d0 out of bounds>, len = 8}, r2_val = {s = 0xa6 <Address 0xa6 out of bounds>, len = 8136007}, gr_val = { s = 0x7c95f8 "core: core/parser/msg_parser.c", len = 682176488}} next_hop = {user = {s = 0x1e7374b9a <Address 0x1e7374b9a out of bounds>, len = 674472240}, passwd = { s = 0xffffffff <Address 0xffffffff out of bounds>, len = 4289104}, host = {s = 0x4e2cb1825 <Address 0x4e2cb1825 out of bounds>, len = -1667705792}, port = {s = 0x0, len = 1073741824}, params = {s = 0x2000000 <Address 0x2000000 out of bounds>, len = 4289104}, sip_params = {s = 0x7ffc89e35180 "\360Q\343\211\374\177", len = 6031673}, headers = {s = 0x7fefe2cb183f "", len = -1981591296}, port_no = 23013, proto = 58022, type = 32751, flags = 2313376240, transport = {s = 0x7fefe7374b9a "%x%c%x%c", len = -1981590944}, ttl = { ---Type <return> to continue, or q <return> to quit--- s = 0x1a <Address 0x1a out of bounds>, len = 4289104}, user_param = {s = 0x7fefe2a659e5 "5e6a5a14-1fa-", len = -1670974014}, maddr = { s = 0x30fbad8001 <Address 0x30fbad8001 out of bounds>, len = -492414491}, method = {s = 0x7fefe2a659e5 "5e6a5a14-1fa-", len = -492414491}, lr = {s = 0x7fefe2a659e5 "5e6a5a14-1fa-", len = -492414478}, r2 = {s = 0x7fefe2a659ff "", len = -492414491}, gr = {s = 0x7fefe2a659ff "", len = 0}, transport_val = {s = 0x0, len = 6730416}, ttl_val = {s = 0x7ffc89e351a0 "", len = 673677328}, user_param_val = { s = 0x2000000 <Address 0x2000000 out of bounds>, len = 673677328}, maddr_val = {s = 0x7ffc89e351f0 "Cl\256", len = -413652166}, method_val = {s = 0x7ff028278010 "\001", len = 0}, lr_val = {s = 0x2000000 <Address 0x2000000 out of bounds>, len = 24589344}, r2_val = { s = 0x67a138 "", len = 8965088}, gr_val = {s = 0x8cd2d0 <Address 0x8cd2d0 out of bounds>, len = 682507072}} u = 0x66273d port = 0 dst_host = 0x40000000 i = 28 flags = 0 avp = 0xae6cc7 st = {flags = 31129600, id = 0, name = {n = 0, s = {s = 0x0, len = 93}, re = 0x0}, avp = 0x7ffc89e35080} sct = 0x7ffc89e35490 sjt = 0x6943d3 rve = 0x7ff0285a8808 mct = 0x6a283b rv = 0x0 rv1 = 0x7c9170 c1 = {cache_type = 24, val_type = 48, c = {avp_val = {n = -1981590720, s = {s = 0x7ffc89e35340 "\370\225|", len = -1981590912}, re = 0x7ffc89e35340}, pval = {rs = {s = 0x7ffc89e35340 "\370\225|", len = -1981590912}, ri = 0, flags = 0}}, i2s = '\000' <repeats 21 times>} s = {s = 0x7fefe2cb183f "", len = -490006491} srevp = {0x7fefe2cb1825, 0x7fefe2cb1832} mod_f_params = {{type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, { type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = { number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = { s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}} __FUNCTION__ = "do_action" #7 0x00000000004404b8 in run_actions (h=0x7ffc89e35670, a=0x7ff0285a85d0, msg=0x7ff028b453f8) at core/action.c:1552 t = 0x7ff0285a9668 ret = 1 mod = 0x417250 ms = 176570657 __FUNCTION__ = "run_actions" #8 0x0000000000440c4a in run_top_route (a=0x7ff0285a85d0, msg=0x7ff028b453f8, c=0x0) at core/action.c:1641 ---Type <return> to continue, or q <return> to quit--- ctx = {rec_lev = 2, run_flags = 0, last_retcode = 1, jmp_env = {{__jmpbuf = {140669451785720, -8516593617994257148, 50, 1073741824, 33554432, 4289104, -8516593618092823292, 8518532807277145348}, __mask_was_saved = 0, __saved_mask = {__val = {140668355198191, 4302791168, 48, 48, 18446744073709551615, 140722621863712, 140668355198919, 50, 0, 4611686022755909632, 140669451785208, 140722621863776, 5814046, 6608344928, 140669451785208, 0}}}}} p = 0x7ffc89e35670 ret = 682907128 sfbk = 0 #9 0x000000000052e6b9 in receive_msg ( buf=0xae6bc0 "KDMQ sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080> SIP/2.0\r\nVia: SIP/2.0/UDP 10.112.101.128;branch=z9hG4bK8791.0c350dd3", '0' <repeats 24 times>, ".0\r\nTo: <sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080>>\r\nFrom: <sip:usrloc@10.112.101.128<mailto:sip%3Ausrloc@10.112.101.128>"..., len=781, rcv_info=0x7ffc89e35a70) at core/receive.c:264 msg = 0x7ff028b453f8 ctx = {rec_lev = -1981589208, run_flags = 32764, last_retcode = 8, jmp_env = {{__jmpbuf = {163, 4253893, 8100093, 140669451683568, 140722621864176, 4845170, 0, 21474836480}, __mask_was_saved = 673677840, __saved_mask = {__val = {140668768878592, 140722621864448, 6697083, 8094080, 5501958, 243141751568, 140669476122624, 140722621864896, 4294967295, 88212724672, 1, 140668357584160, 0, 33554432, 1024, 6608345520}}}}} bctx = 0x7ffc89e359b0 ret = 0 stats_on = 0 tvb = {tv_sec = 140722621864208, tv_usec = 8961768} tve = {tv_sec = 0, tv_usec = 243139749096} tz = {tz_minuteswest = 50, tz_dsttime = 0} diff = 0 inb = { s = 0xae6bc0 "KDMQ sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080> SIP/2.0\r\nVia: SIP/2.0/UDP 10.112.101.128;branch=z9hG4bK8791.0c350dd3", '0' <repeats 24 times>, ".0\r\nTo: <sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080>>\r\nFrom: <sip:usrloc@10.112.101.128<mailto:sip%3Ausrloc@10.112.101.128>"..., len = 781} netinfo = {data = {s = 0x7ffc00000001 <Address 0x7ffc00000001 out of bounds>, len = 0}, dst = 0x1, rcv = 0x389c422190} keng = 0x0 __FUNCTION__ = "receive_msg" #10 0x00000000006456a3 in udp_rcv_loop () at core/udp_server.c:515 len = 781 buf = "KDMQ sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080> SIP/2.0\r\nVia: SIP/2.0/UDP 10.112.101.128;branch=z9hG4bK8791.0c350dd3", '0' <repeats 24 times>, ".0\r\nTo: <sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080>>\r\nFrom: <sip:usrloc@10.112.101.128:5060<http://sip:usrloc@10.112.101.128:5060>>;tag=8a3"... tmp = 0x100000000 <Address 0x100000000 out of bounds> from = 0x7ff028b2c728 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {140722462617610, 140722621864592}, addr32 = {2154131466, 32764, 2313378448, 32764}, addr16 = { 28682, 32869, 32764, 0, 23184, 35299, 32764, 0}, addr = "\npe\200\374\177\000\000\220Z\343\211\374\177\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {1080520714, 0}, addr32 = {1080520714, 0, 0, 0}, addr16 = {28682, 16487, 0, 0, 0, 0, 0, 0}, addr = "\npg@", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5080, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = { sa_family = 2, sa_data = "\023\304\npe\200\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = { s_addr = 2154131466}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, ---Type <return> to continue, or q <return> to quit--- sin6_flowinfo = 2154131466, sin6_addr = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7ff02830fff0, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #11 0x0000000000423c7d in main_loop () at main.c:1623 i = 0 pid = 0 si = 0x7ff02830fff0 si_desc = "udp receiver child=0 sock=10.112.103.64:5080<http://10.112.103.64:5080>\000\000\000\000 _\343\211\374\177\000\000\062\000\000\000\000\000\000\000\000\000\000@\000\000\000\000\000\000\000\002\000\000\000\000PrA\000\000\000\000\000PSn\234\070\000\000\000\060\000\000\000\060\000\000\000\020]\343\211\374\177\000\000@\\\343\211\374\177\000\000\000px\347\357\177\000" nrprocs = 4 woneinit = 0 __FUNCTION__ = "main_loop" #12 0x000000000042b0ce in main (argc=13, argv=0x7ffc89e36008) at main.c:2646 cfg_stream = 0x1bb5010 c = -1 r = 0 tmp = 0x7ffc89e36ef7 "" tmp_len = 32764 port = -1981587768 proto = 56 options = 0x7434f8 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 4012862799 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7ffc89e35f08 p = 0x100000000 <Address 0x100000000 out of bounds> st = {st_dev = 64769, st_ino = 148592, st_nlink = 2, st_mode = 16877, st_uid = 498, st_gid = 498, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1576522467, tv_nsec = 972000117}, st_mtim = {tv_sec = 1519927576, tv_nsec = 668342155}, st_ctim = {tv_sec = 1584026268, tv_nsec = 165523404}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) Em ter., 17 de mar. de 2020 às 09:52, Daniel-Constantin Mierla <miconda(a)gmail.com<mailto:miconda@gmail.com>> escreveu: Hello, does it happen only when doing restart of kamailio? Can you send the full backtrace from gdb? Also, 5.0.x is no longer a supported release for quite some time, try to upgrade to 5.2.x or even better to the latest one 5.3.x and see if you can reproduce it with one of the supported releases, maybe it is something that was already fixed. Cheers, Daniel On 17.03.20 10:32, Virgílio Cunha wrote: Hello, I have in production environment with 4 proxies using DMQ to sync terminal registers and the DMQ configuration parameters is following: loadmodule "dmq.so" #modparam("dmq", "server_address", "sip:MY_IP_ADDRESS:MY_PORT_ADDRESS") modparam("dmq", "notification_address", "DMQ_HOSTS") modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 4) In the lab environment with the same configuration that in prod, I can simulate this problem with 12000 terminal REGISTERS and, when doing several restarts on a proxy, one of them is generated a coredump. Analyzing the core, I can see that the problem is concurrency in the dmq synchronization. Job_queue_size (...) is called with a valid queue and, but inside this function, the queue is null. (gdb) up #1 0x00007fefe58ee246 in job_queue_size (queue=0x0) at worker.c:254 254 return atomic_get(&queue->count); (gdb) print queue $1 = (job_queue_t *) 0x0 (gdb) up #2 0x00007fefe58ed920 in add_dmq_job (msg=0x7ff028b453f8, peer=0x7fefebcc4df8) at worker.c:184 184 if(job_queue_size(workers[i].queue) == 0) { (gdb) print i $2 = 1 (gdb) print workers[i].queue $3 = (job_queue_t *) 0x7fefebce49b0 If I configure DMQ with num_workers=1 I can't reproduce this problem. I'm using the kamailio 5.0.8 release. Is this problem known to you? What is the right way to solve it? Best Regards, Virgílio Cunha _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com> www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda> -- Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com> www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

4 years, 8 months

tls: ssl bug #1491 workaround

by Javier Valencia

Hi there I have a Kamailio with TLS/Websocket solution. I'm getting some errors on log and some users can't connect. My log: Mar 18 09:49:15 webrtc /usr/sbin/kamailio[11915]: ERROR: tls [tls_server.c:192]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: shm=8212904 threshold1=8388608 Mar 18 09:49:15 webrtc /usr/sbin/kamailio[11915]: ERROR: <core> [core/tcp_read.c:1485]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f6297bd62c0 r: 0x7f6297bd6340 Kamailio is running like: /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 16 -u kamailio -g kamailio Kind regards, Javier Valencia. -- Logo <http://www.voiper.es/> Javier Valencia | CTO Centro de Negocios Martín Buendía Camino de las Cañadas, nº 1C, Portal 1, 2ºG 29649 Mijas (Málaga) # 951562080 (T) <tel:951562080> | 687486759 (M) <tel:687486759> # www.voiper.es <http://www.voiper.es/> ------------------------------------------------------------------------ AVISO LEGAL ----------- Este mensaje contiene información confidencial destinada para ser leída exclusivamente por el destinatario. Queda prohibida la reproducción, publicación, divulgación, total o parcial del mensaje así como el uso no autorizados por el emisor. En caso de recibir el mensaje por error, se ruega su comunicación al remitente lo antes posible. Por favor, indique inmediatamente si usted o su empresa no aceptan comunicaciones de este tipo por Internet. Las opiniones, conclusiones y demás información incluida en este mensaje que no esté relacionada con asuntos profesionales de SMART RECARGAS, S.L, se entenderá que nunca se ha dado, ni está respaldado por el mismo. Responsable del Tratamiento de Datos ------------------------------------ SMART RECARGAS , SL Camino de las Cañadas, 1C PORTAL 1 2º G 29651 MIJAS COSTA (MALAGA)

4 years, 8 months

Re: [SR-Users] I need to configure apns push notification in kamailio

by master1024

Hello Team, I need to configure apns sip push in kamailio, I have read it many sites but I don't get proper understanding I read it is done with the help of tsilo module kindly support in it. Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, February 27, 2020 11:10 AM, master1024 <master1024(a)protonmail.com> wrote: > Hello, > > I need to configure apns push notification in kamailio kindly help. I have a file push.php It is capable to push notification on ios device know i want to implement in kamailio when the user is offline then push notification fire kindly help in this. > > Think Out of the Box > > Sent with [ProtonMail](https://protonmail.com) Secure Email.

4 years, 8 months

systemd - properly starting up rtpengine with kernel forwarding

by Daniel-Constantin Mierla

Hello, do people here have (implemented) special ways to properly start rtpengine with kernel forwarding after system reboot? >From rtpengine readme: """ A typical start-up sequence including in-kernel forwarding might look like this: # this only needs to be one once after system (re-) boot modprobe xt_RTPENGINE iptables -I INPUT -p udp -j RTPENGINE --id 0 ip6tables -I INPUT -p udp -j RTPENGINE --id 0 # ensure that the table we want to use doesn't exist - usually needed after a daemon # restart, otherwise will error echo 'del 0' > /proc/rtpengine/control # start daemon /usr/sbin/rtpengine --table=0 --interface=10.64.73.31 --interface=2001:db8::4f3:3d \ --listen-ng=127.0.0.1:2223 --tos=184 --pidfile=/run/rtpengine.pid --no-fallback """ I was relying on shell scripts executed on boot time, but now that systemd is more common, I am looking to see what are "standard"/"recommended" ways for running additional scripts besides the start/stop daemon, which makes it also easier to build packages not worrying about the type of OS and how it can run scripts at startup. Systemd seems to have the "ExecStartPre" option, is it what people use to ensure the rtpengine kernel module is loaded and iptables rule exists? Any systemd-specific wayt to run a script only once after system boot? I have seen workarounds on the net for creating like a rc.local service, but they didn't look to be systemd-native, ... Not strictly related, but if someone is aware or had some experiences with, I am curious if "echo 'del 0' > /proc/rtpengine/control" is really needed because on a system where I forgot to have it in the scripts (well, was commented), I haven't noticed any issues after rtpengine restarts. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com

4 years, 8 months

I need to configure apns push notification in kamailio

by master1024

Hello Team, I want to configure ios push notification in kamailio, if it is possible kindly support me in deep, because I am new in kamailio. Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, March 16, 2020 1:24 PM, master1024 <master1024(a)protonmail.com> wrote: > Hello Team, > > I want to implement apns push notification on messages and calling in kamailio kindly support me. I am Beginner in kamailio. > > Sent with [ProtonMail](https://protonmail.com) Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Thursday, March 5, 2020 10:18 AM, master1024 <master1024(a)protonmail.com> wrote: > >> Hello Team, >> Kindly support in the same. >> >> Sent with [ProtonMail](https://protonmail.com) Secure Email. >> >> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >> On Wednesday, March 4, 2020 11:18 AM, master1024 <master1024(a)protonmail.com> wrote: >> >>> Hello Team, >>> >>> I need to configure apns Push Notification in kamailio kindly support in it. I read from the site https://medium.com/@denys.pozniak/apple-push-notification-with-kamailio-eec… but I don't understand properly because here is missing push.php, I have another push.php and it is able to push notification on ios device but I need to understand how to integrate that push.php with kamailio, I need that when user is offline during call or message then push notification will fire from php script and application will wake up via push notification. >>> >>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>> >>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>> On Tuesday, March 3, 2020 12:06 PM, master1024 <master1024(a)protonmail.com> wrote: >>> >>>> Hello Team, >>>> I already read this and attempt to implement that but $sht is creating problem for me. and it is not working for me. >>>> >>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>> >>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>> On Monday, March 2, 2020 11:14 PM, M S <shaheryarkh(a)gmail.com> wrote: >>>> >>>>> Here is a good starting point for you. Adapt and extend as needed in your setup. >>>>> >>>>> https://medium.com/@denys.pozniak/apple-push-notification-with-kamailio-eec… >>>>> >>>>> Hope this helps. >>>>> >>>>> On Mon, 2 Mar 2020, 12:39 master1024, <master1024(a)protonmail.com> wrote: >>>>> >>>>>> Hello Team, >>>>>> Kindly explain your 1st step, The IOS app must what what kind of parameters and how many parameters we needed ??? >>>>>> >>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>>>> >>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>>>> On Thursday, February 27, 2020 6:38 PM, M S <shaheryarkh(a)gmail.com> wrote: >>>>>> >>>>>>> Push notification setup is long and complex but generally has following process. Don't forget to read documentation of relevant kamailio modules for proper use. >>>>>>> >>>>>>> 1. The iOS app must send push notification parameters in SIP request e.g. SIP Register. In kamailio, when this request is received, you must extract them and save them in some db backend, e.g. MySQL, Redis etc. >>>>>>> >>>>>>> 2. For each income call, check if destination is offline and push parameters stored in db. If so, then you suspend the INVITE transaction using ASYNC or TSILO module and store transaction information in db. >>>>>>> >>>>>>> 3. Then using the push parameters stored in db, you send the push notification to device using CURL or HTTP client modules etc. >>>>>>> >>>>>>> 4. When device receives push notification, it must come online and send SIP register with push parameters. Kamailio again stores push parameters and checks if an INVITE transaction is waiting for the device. Retrieve the transaction, restore it and forward call to the device. >>>>>>> >>>>>>> 5. If device does not comes online upon receiving push notification and call times out or caller hangs up the call then you need to clean up transaction data stored in db. Similarly, you need to setup mechanism to purge push notification data after some time e.g. 7 or 10 days to ensure device push parameters remain up to date etc. >>>>>>> >>>>>>> The iOS apps now need to implement CallKit for push notification capable calls, that adds some serious difficultly in processing such calls since they show fake call screen before the actual call is received by app and if callee is too quick to respond to call (answer or reject) then kamailio will never know and still send the real call (step 4 above) later on, so you will need to manage that too. >>>>>>> >>>>>>> Hope this helps. >>>>>>> >>>>>>> On Thu, 27 Feb 2020, 13:25 master1024, <master1024(a)protonmail.com> wrote: >>>>>>> >>>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>>>>>> >>>>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>>>>>> On Thursday, February 27, 2020 5:52 PM, master1024 <master1024(a)protonmail.com> wrote: >>>>>>>> >>>>>>>>> Hello Team, >>>>>>>>> >>>>>>>>> I need to configure apns sip push notification in kamailio, I have read it many sites but I don't get proper understanding I read it is done with the help of tsilo module kindly support in it. >>>>>>>>> >>>>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>>>>>>> >>>>>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>>>>>>> On Thursday, February 27, 2020 11:10 AM, master1024 <master1024(a)protonmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> I need to configure apns push notification in kamailio kindly help. I have a file push.php It is capable to push notification on ios device know i want to implement in kamailio when the user is offline then push notification fire kindly help in this. >>>>>>>>>> >>>>>>>>>> Think Out of the Box >>>>>>>>>> >>>>>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

4 years, 8 months

tls.options RPC reporting default settings

by Sergiu Pojoga

Hi there, Having custom TLS config in tls.cfg, RPC `tls.options` seems to report default settings. Bug or intended? root@kam:/# kamcmd version kamailio 5.3.2 (x86_64/linux) 0bed10 root@kam:/# kamcmd tls.options { force_run: 0 method: TLSv1 verify_certificate: 0 verify_depth: 9 require_certificate: 0 private_key: /usr/local/etc/kamailio/cert.pem ca_list: certificate: /usr/local/etc/kamailio/cert.pem cipher_list: session_cache: 0 session_id: kamailio-tls-5.x.y config: /usr/local/etc/kamailio/tls.cfg ... } modparam("tls", "config", "/usr/local/etc/kamailio/tls.cfg") root@kam:/usr/local/etc/kamailio# cat tls.cfg [server:default] method = TLSv1.2+ verify_certificate = yes require_certificate = yes private_key = /tmp/privkey.pem certificate = /tmp/fullchain.pem ca_list = /etc/ssl/certs/ca-certificates.crt [client:default] method = TLSv1.2+ verify_certificate = yes require_certificate = yes private_key = /tmp/privkey.pem certificate = /tmp/fullchain.pem ca_list = /etc/ssl/certs/ca-certificates.crt Cheers.

4 years, 8 months

Kamailio v5.3.3 Released

by Daniel-Constantin Mierla

Hello, Kamailio SIP Server v5.3.3 stable release is out. This is a maintenance release of the latest stable branch, 5.3, that includes fixes since the release of v5.3.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.3.x. Deployments running previous v5.3.x versions are strongly recommended to be upgraded to v5.3.3. For more details about version 5.3.3 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2020/03/kamailio-v5-3-3-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Special circumstances are now everywhere word wide, impacting all of us, therefore we wish a smooth time during this crisis and to stay healthy to all our developers, supporters and community members along with their beloved ones! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

4 years, 8 months

Info: Kamailio World 2020 – Event Cancelled For April 27-29, 2020

by Daniel-Constantin Mierla

Source: https://www.kamailioworld.com/k08/2020/03/kamailio-world-2020-event-cancell… It is probably no much of a surprise that the next Kamailio World Conference and the NG-Emergency track cannot be organized any more during April 27-29, 2020. We are trying to find out the best alternatives for later in the year, when we hope the situation will be back to normal and people will be again in mood for social interaction. Being one of proposed alternatives, because we discussed a lot during the last several days with the people involved in organizing the event as well as its active community, we want to make it clear right now that we do not plan to switch to an online version (i.e., video conferencing) at the same dates. With the current situation out there, it is very likely that the level of stress everywhere will be high during the next 6 weeks till the initial planned dates, so putting together the infrastructure for video conferencing, synchronizing with the speakers and participants will just add to it, therefore it is better that everyone is focusing on taking care of the beloved ones and how to deal the best with the daily constraints during this interval. All the payments received for participating at or supporting Kamailio World 2020 will be refunded. If you are among them, thank you once more! We will contact you very soon with the relevant details. Keep also an eye on the event website for updates related to what is going to be next related to the conference! We hope the evolution will turn into a positive perspective very soon and the crisis is going to end rapidly, so everyone can return to the usual activities! Moreover, we wish you and the beloved ones a smooth time during this exceptional situation and to stay healthy! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

4 years, 8 months

Releasing Kamailio v5.3.3

by Daniel-Constantin Mierla

Hello, I am considering to release Kamailio v5.3.3 next week, either on Monday (March 16) or Tuesday (March 17). As usual, if any of you are aware of issues not reported on the tracker yet or knows fixes not backported to branch 5.3, reported them as soon as possible to take care of them. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com

4 years, 8 months

out of shm without any visible reason

by Juha Heinanen

K reported during about 90 sec period that it is out of shared memory: Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm [t_hooks.c:136]: insert_tmcb(): out of shm. mem Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: acc [acc_logic.c:394]: acc_onreq(): cannot register additional callbacks Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core> [core/sip_msg_clone.c:499]: sip_msg_shm_clone(): could not allocate shared memory from shm pool Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm [t_lookup.c:1293]: new_t(): out of mem: Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm [t_lookup.c:1439]: t_newtran(): new_t failed ... Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core> [core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f1f2a506000, 1232); Free fragment not found! Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core> [core/mem/q_malloc.c:434]: qm_malloc(): qm_malloc(0x7f1f2a506000, 1232); Free fragment not found! Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm [t_reply.c:1957]: relay_reply(): cannot alloc reply shmem Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core> [core/sip_msg_clone.c:499]: sip_msg_shm_clone(): could not allocate shared memory from shm pool Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: acc [acc_logic.c:562]: acc_onreply(): failed to clone the request - acc aborted ... Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: <core> [core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f1f2a506000, 5728); Free fragment not found! Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: <core> [core/mem/q_malloc.c:434]: qm_malloc(): qm_malloc(0x7f1f2a506000, 5728); Free fragment not found! Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: tm [t_lookup.c:1293]: new_t(): out of mem: Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: tm [t_lookup.c:1439]: t_newtran(): new_t failed And after that period it started working normally again and core.shmmem showed: { total: 134217728 free: 124173808 used: 9530960 real_used: 10043920 max_used: 134217728 fragments: 349 } As can be seen, shm had been full, but normally only about 10% of it is in use. Syslog does not show any traffic spikes or other unusual activity before the memory got full. Any ideas what could cause such a high memory usage or could there be a bug in shm management? -- Juha

4 years, 8 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 March 2020