sr-dev September 2019

sr-dev@lists.kamailio.org

24 participants
369 discussions

[kamailio/kamailio] Modules: db_redisusrloc for usrloc module (#1446)
by Surendra Tiwari 06 Nov '19

06 Nov '19

#### Pre-Submission Checklist    - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1446 -- Commit Summary -- * kamailio db_redisusrloc -- File Changes -- A src/modules/db_redisusrloc/Makefile (36) A src/modules/db_redisusrloc/README (88) A src/modules/db_redisusrloc/db_redisusrloc.c (100) A src/modules/db_redisusrloc/doc/Makefile (4) A src/modules/db_redisusrloc/doc/db_redisusrloc.xml (45) A src/modules/db_redisusrloc/doc/db_redisusrloc_admin.xml (86) A src/modules/db_redisusrloc/redisdb_base.c (1189) A src/modules/db_redisusrloc/redisdb_connection.c (100) A src/modules/db_redisusrloc/redisdb_connection.h (43) A src/modules/db_redisusrloc/redisdb_dbase.h (96) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1446.patch https://github.com/kamailio/kamailio/pull/1446.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/1446

4 15

[kamailio/kamailio] Add optional parameter to ds_is_from_list() to check only active GW (#1908)
by pwakano 31 Oct '19

31 Oct '19

### Description Currently ds_is_from_list() matches all GWs in the dispatcher list, not considering if the GW is disabled or not. It might have situation where a GW is permanently disabled but can't be removed (because of CDR references for instance). In this case it is not desired to match a disabled GW in the test. The function should accept a new parameter which will tell if it should or not match disabled GWs. For backward compatibility, it should not be a mandatory parameter and its default value should be to match disabled GW (as it is today). ### Expected behavior ds_is_from_list() should return false in case it matches a disabled GW and the new parameter tells not to match disabled GWs. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1908

3 4

[kamailio/kamailio] Malformed INVITE message crashes Kamailio (#2044)
by santoshsridhar 28 Oct '19

28 Oct '19

### Description I have sent malformed data to kamailio server and its getting crashed.  ### Troubleshooting #### Reproduction This can be easily reproducable by remove .(eol) from each line of invite packet  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` 32(78) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 13 0(46) ALERT: <core> [main.c:745]: handle_sigs(): child process 47 exited by a signal 11 0(46) ALERT: <core> [main.c:748]: handle_sigs(): core was generated 0(46) INFO: <core> [main.c:771]: handle_sigs(): terminating due to SIGCHLD 2(48) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 6(52) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 8(54) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 12(58) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 13(59) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 15(61) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 17(63) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 18(64) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 20(66) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 22(68) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 24(70) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 26(72) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 28(74) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 32(78) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 25(71) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 21(67) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 23(69) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 14(60) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 3(49) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 29(75) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 19(65) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 30(76) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 11(57) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 7(53) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 31(77) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 16(62) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 9(55) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 27(73) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 10(56) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 4(50) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 5(51) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 0(46) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized 2019/08/26 06:14:51.186871 [ERR] (cli) child process died with exit code 1 ``` #### SIP Traffic  ``` INVITE sip:9631793333@10.130.72.178:5060 SIP/2.0 Max-Forwards: 66 From: "9631791999" <sip:9631791999@test.santhos.com>;tag=8BpeDNKX9g7ZN To: <sip:12254431343@52.77.251.154> Call-ID: 0e61d723-400b-1238-5ea2-029e611e72cc CSeq: 8715558 INVITE Supported: timer, path, replaces Allow-Events: talk, hold, conference, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 248 Remote-Party-ID: "9631791999" <sip:9631791999@test.santhos.com>;party=calling;screen=yes;privacy=off Contact: <sip:btpsh-5d5dab4f-36-1@3.82.91.199;alias=10.130.74.48~5060~1> User-Agent: NewServer Accept: application/sdp Allow: INVITE,ACK,CANCEL,BYE,UPDATE v=0 o=- 1566538700029766 7092256907260767331 IN IP4 3.220.58.181 s=X-Lite release 5.6.1 stamp 99140 c=IN IP4 3.220.58.181 t=0 0 m=audio 10030 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` root@test-server:/# kamailio -v version: kamailio 5.1.4 (x86_64/linux) cc647d 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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: cc647d compiled on 10:09:16 Jul 29 2019 with gcc 5.4.0 ``` * **Operating System**:  ``` root@test-server:/# cat /etc/debian_version stretch/sid root@test-server:/# uname -a Linux test-server 4.14.77-69.57.amzn1.x86_64 #1 SMP Tue Nov 6 21:32:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2044

3 7

[kamailio/kamailio] http_async_client: memory mismanagement (#1407)
by Dragos Oancea 25 Oct '19

25 Oct '19

#### Pre-Submission Checklist    - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ X] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #1208 #### Description p->headers.t is dynamically allocated header_list_add() in and should be freed with free_async_query(). You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1407 -- Commit Summary -- * http_async_client: memory mismanagement -- File Changes -- M src/modules/http_async_client/async_http.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1407.patch https://github.com/kamailio/kamailio/pull/1407.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/1407

5 11

Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
by Daniel-Constantin Mierla 25 Oct '19

25 Oct '19

Hello, after couple of months waiting for feedback about the workaround with the preloaded shared library to set the PTHREAD_PROCESS_SHARED attribute for pthread mutex/rwlock in order to avoid deadlocks and as it seems to be the solution, I just pushed a few commits to move that code in the core of kamailio. It this way the initialization with the PTHREAD_PROCESS_SHARED attribute is done by default when libssl v1.1 is detected at compile time, without the need of using the approach with a preloaded library. The shared library is still kept in the tls module: * https://github.com/kamailio/kamailio/tree/master/src/modules/tls/utils/open… Probably is going to be removed in the near future. I am asking the community members that use Kamailio on systems with libssl v1.1+ to test the master branch and give feedback. The master branch is anyhow in testing phase for preparing the next major release v5.3.0, so it will help for that as well. If no issue is going to be reported soon, the commits will be backported to stable branches, to re-enable smooth use of Kamailio with libssl v1.1+. When libssl v1.1+ is detected, the core links with pthread, but that was already present in the Makefiles.defs for different compile options. The pthread more or less a default library on linuxes/unixes, so this should not introduce any major dependency to the Kamailio core. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

6 17

[kamailio/kamailio] Cannot package on CentOS 8 (#2078)
by sergey-safarov 24 Oct '19

24 Oct '19

Several packages not exist in CentOS 8 repos. Will wait until docker centos:8 image available and i will try fix **Not existed deps** ``` nothing provides hiredis-devel nothing provides GeoIP-devel nothing provides mysql-devel nothing provides python nothing provides python-devel nothing provides radiusclient-ng-devel nothing provides squirrel-devel nothing provides python2-rpm-macros ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2078

2 5

[kamailio/kamailio] Unit update (#1889)
by sergey-safarov 18 Oct '19

18 Oct '19

#### Pre-Submission Checklist - [ ] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [x] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist: - [x] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #1827 #### Description 1) tmpfiles creation is implemented via systemd 2) owner of kamailio process implemented via systemd drop-in 3) kamailio started as simple process, that allow systemd check kamailio process without PID file. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1889 -- Commit Summary -- * Init scripts always create kamailio user and group. * Added kamailio.tmpfiles. Directory /run/kamailio is created by command * Starting kamailio as forground process allow systemd not check kamailio PID. -- File Changes -- M pkg/kamailio/deb/buster/kamailio.default (11) M pkg/kamailio/deb/buster/kamailio.service (10) A pkg/kamailio/deb/buster/kamailio.tmpfiles (1) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1889.patch https://github.com/kamailio/kamailio/pull/1889.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/1889

6 20

[kamailio/kamailio] Segfault in t_reply of Kamailio v5.2.2 rev. 9bc44f (#2055)
by Muhammad Shahzad Shafi 09 Oct '19

09 Oct '19

### Description Kamailio v5.2.2 rev. 9bc44f randomly crashes once a week. The problem seems to be related to TM and ASYNC modules as seen in back-trace of dump core below.  ### Troubleshooting None. We have dump core file available for analysis. #### Reproduction Randomly, roughly once every 5 to 7 days.  #### Debugging Data  ``` Program terminated with signal 11, Segmentation fault. #0 0xb4ecdb33 in faked_env (t=0x7ad779f8, msg=0x0, is_async_env=1) at t_reply.c:813 813 t_reply.c: No such file or directory. (gdb) info locals __FUNCTION__ = "faked_env" (gdb) list 808 in t_reply.c (gdb) bt full #0 0xb4ecdb33 in faked_env (t=0x7ad779f8, msg=0x0, is_async_env=1) at t_reply.c:813 __FUNCTION__ = "faked_env" #1 0xb4eedba2 in t_continue_helper (hash_index=48512, label=393930873, rtact=0xb5ba6184, cbname=0x0, cbparam=0x0) at t_suspend.c:337 t = 0x7ad779f8 backup_T = 0xffffffff backup_T_branch = -1 faked_req = 0x7afdf1bc brpl = 0x0 erpl = 0x8055fd2 faked_req_len = 3176 cancel_data = {cancel_bitmap = 3076137104, reason = {cause = 26896, u = {text = {s = 0xb51cc7e0 "\254\026\003", len = 134606304}, e2e_cancel = 0xb51cc7e0, packed_hdrs = {s = 0xb51cc7e0 "\254\026\003", len = 134606304}}}} branch = 0 uac = 0x7ad77b64 ret = 0 cb_type = 2 msg_status = -1256442488 last_uac_status = -1245318100 reply_status = 137942287 do_put_on_wait = 134606304 hdr = 0xb55987d8 prev = 0x0 tmp = 0x0 route_type_bk = 1 keng = 0x0 evname = {s = 0xb4f31305 "tm:continue", len = 11} __FUNCTION__ = "t_continue_helper" #2 0xb4ef0a2d in t_continue (hash_index=48512, label=393930873, route=0xb5ba6184) at t_suspend.c:583 No locals. #3 0xb43ceac3 in async_exec_task (param=0x7a94bf54) at async_sleep.c:233 atp = 0x7a94bf54 keng = 0x0 cbname = {s = 0x0, len = 0} evname = {s = 0xb43d1a94 "async:task-exec", len = 15} __FUNCTION__ = "async_exec_task" #4 0x080894c6 in async_task_run (idx=4) at core/async_task.c:282 ptask = 0x7a94bf4c received = 4 __FUNCTION__ = "async_task_run" #5 0x08087ca1 in async_task_child_init (rank=0) at core/async_task.c:185 pid = 0 i = 3 __FUNCTION__ = "async_task_child_init" #6 0x08201d26 in init_child (rank=0) at core/sr_module.c:871 ret = 62 #7 0x0806b3d9 in main_loop () at main.c:1737 i = 4 pid = 5982 si = 0x0 si_desc = "udp receiver child=3 sock=85.118.42.43:5080\000\000\002a\267гn\267p\037\000\000\240\263n\267\364\237n\267\240\263n\267`\025\316\b\220W\371\277\315\002a\267\220\000\000\000`\025\316\b\364\237n\267\025\000\000\000\060X\371\277\355\ng\267\060/\316\b0/\316\b@q\245\265\000@\000\000@\220n\267\000\000\000" nrprocs = 4 woneinit = 1 __FUNCTION__ = "main_loop" #8 0x08071e84 in main (argc=13, argv=0xbff95be4) at main.c:2696 cfg_stream = 0x8bd3008 c = -1 r = 0 tmp = 0xbff96822 "" tmp_len = -1218858976 port = 2209 proto = 1 options = 0x83779a8 ":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 = 1217010649 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbff95be4 p = 0x805e474 "[\201\303\060\037@" st = {st_dev = 14, __pad1 = 0, st_ino = 10873, st_mode = 16832, st_nlink = 2, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, st_size = 120, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1559687937, tv_nsec = 2808493}, st_mtim = {tv_sec = 1566372756, tv_nsec = 587274417}, st_ctim = { tv_sec = 1567450779, tv_nsec = 139516276}, __unused4 = 0, __unused5 = 0} __FUNCTION__ = "main" ``` #### Log Messages  ``` Sep 3 03:02:03 webrtc-as1 kernel: [7785063.653846] kamailio[5987]: segfault at 318 ip b4ecdb33 sp bff94f90 error 6 in tm.so[b4e15000+12a000] ``` #### SIP Traffic Not available ### Possible Solutions N/A ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.2.2 (i386/linux) 9bc44f 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 9bc44f -dirty compiled on 11:33:22 Apr 29 2019 with gcc 4.7.2 ``` * **Operating System**:  ``` Linux webrtc-as1 3.16.0-0.bpo.4-686-pae #1 SMP Debian 3.16.36-1+deb8u2~bpo70+1 (2016-10-19) i686 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2055

2 9

[kamailio/kamailio] Kamailio stops responding to SIP requests when it cannot resolve DNS from siptrace (#2081)
by ramontelnyx 09 Oct '19

09 Oct '19

#### Reproduction ``` You can reproduce the issue by: 1) Enabling siptrace 2) Populating the duplicate_uri field with a non-existing domain 3) Sending test calls ``` #### Log Messages ``` 1(1164) CRITICAL: <core> [core/proxy.c:264]: mk_proxy(): could not resolve hostname: "homer7-hep.query.consul" 1(1164) ERROR: siptrace [siptrace_hep.c:177]: trace_send_hep3_duplicate(): bad host name in uri ``` ### Additional Information ``` # /usr/local/sbin/kamailio -version version: kamailio 5.2.4 (x86_64/linux) a57138 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: a57138 compiled on 14:41:20 Aug 21 2019 with gcc 6.3.0 ``` * **Operating System**: ``` LInux Debian Stretch Linux 4.4.0-109-generic #132-Ubuntu SMP Tue Jan 9 19:52:39 UTC 2018 x86_64 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2081

2 4

Kamailio Developers Meeting, Nov 14-15, 2019, in Dusseldorf
by Daniel-Constantin Mierla 09 Oct '19

09 Oct '19

Hello, Kamailio SIP Server project is organizing another meeting of its developers during November 14-15, 2019, hosted again by sipgate.de in Dusseldorf, Germany. The event is intended to facilitate the interaction between Kamailio developers and to offer a convenient environment for working together on several topics of high interest for the project, including writing code for Kamailio and its tools, improving documentation, or discuss about future development. Everyone from the community is welcome to join. Please note we have a limited capacity of 20 seats in the meeting room. Also, very important to be aware that this is not an event to learn how to use Kamailio. More details about the event, the venue, how to register, are available at: * https://www.kamailio.org/w/developers-meeting/ Looking forward to those two intensive hacking Kamailio days in Dusseldorf! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

1 1

← Newer
1
...
6
7
8
9
10
11
12
...
37
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev September 2019