sr-dev April 2020

sr-dev@lists.kamailio.org

33 participants
421 discussions

ICMP port-unreachable for UDP INVITEs
by James Browne 06 May '20

06 May '20

I've searched, but I cannot find anything recent about this. My kamailio 5.0.8 proxy sends an INVITE downstream over UDP and gets an ICMP port-unreachable response from the UAS. Apparently ignoring this, it re-transmits the INVITEs and eventually times out and sends to the next host (from the SRV lookup). According to RFC 3261 (https://tools.ietf.org/html/rfc3261#section-8.1.3.1), If a fatal transport error is reported by the transport layer (generally, due to fatal ICMP errors in UDP or connection failures in TCP), the condition MUST be treated as a 503 (Service Unavailable) status code. Does kamailio support handling ICMP responses to INVITEs (and therefore either failing over immediately, or sending 503 upstream immediately)? I don't know for sure the "correct" behavior because the RFC3261 is so old and because ICMP responses are limited in size and therefore can't guarantee to uniquely identify the transactions that caused them.

2 2

Releasing Kamailio v5.3.4
by Daniel-Constantin Mierla 06 May '20

06 May '20

Hello, based on the discussions from yesterday's online devel meeting, I am planning to release next week (likely on Wednesday, May 6) the next minor version out of branch 5.3, respectively 5.3.4. Should anyone be aware of issues not reported to the bug tracker or commits for fixes in master not backported to 5.3 branch, let us know. For new issues, the best is to report them on the tracker. For commits, you can provide links/hashids or make pull requests. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 1

[kamailio/kamailio] Continued OpenSSL 1.1 crashes with 5.3.0 (#2121)
by Nathan Whitehorn 05 May '20

05 May '20

### Description After upgrading to 5.3.0 from 5.2.2 (standard packages on FreeBSD 12.0), I am experiencing intermittent crashes related to handling of BYE messages. ### Troubleshooting #### Reproduction This happens ~ weekly and I have not found a good way to reproduce it. #### Debugging Data An example backtrace is below from the last dumped core (the SIGSEGV one); unfortunately it overwrote the earlier one: ``` * thread #1, name = 'kamailio', stop reason = signal SIGSEGV * frame #0: 0x00000008009c5b79 libc.so.7`___lldb_unnamed_symbol403$$libc.so.7 + 41 frame #1: 0x00000008009ed63e libc.so.7`__free + 990 frame #2: 0x000000080271562b libthr.so.3`pthread_rwlock_destroy + 59 frame #3: 0x0000000802bedbf6 libcrypto.so.111`CRYPTO_THREAD_lock_free + 22 frame #4: 0x0000000802aef3c4 libcrypto.so.111`RSA_free + 100 frame #5: 0x0000000802b10c32 libcrypto.so.111`EVP_PKEY_free + 66 frame #6: 0x000000080296ed86 libssl.so.111`___lldb_unnamed_symbol646$$libssl.so.111 + 134 frame #7: 0x000000080295f93c libssl.so.111`SSL_CTX_free + 236 frame #8: 0x00000008028aee42 tls.so`tls_free_domain + 114 frame #9: 0x00000008028af1d7 tls.so`tls_free_cfg + 199 frame #10: 0x00000008028af2df tls.so`tls_destroy_cfg + 191 frame #11: 0x00000008028ad1f1 tls.so`destroy_tls_h + 1185 frame #12: 0x000000000041adea kamailio`destroy_tls + 26 frame #13: 0x00000000002e36fd kamailio`cleanup + 269 frame #14: 0x00000000002eb5b7 kamailio`___lldb_unnamed_symbol5$$kamailio + 1351 frame #15: 0x00000000002ea5e5 kamailio`handle_sigs + 21669 frame #16: 0x00000000002fb83e kamailio`main_loop + 40014 frame #17: 0x0000000000307d2b kamailio`main + 50267 frame #18: 0x00000000002e311b kamailio`_start + 283 ``` This is with OpenSSL 1.1 With the LD_PRELOAD hack to 5.2.2, things were completely stable; I am trying to use kamailio without the LD_PRELOAD'ed mutex wrapper now, which I believe is no longer required. It looks like the SSL-related stuff in the TLS crash (which was 5 minutes later!) is unrelated to the initial problem and may just be an artifact of one of the kamailio processes crashing earlier. #### Log Messages ``` Nov 2 08:11:31 home /usr/local/sbin/kamailio[94702]: CRITICAL: {1 527440 BYE 973470944-5061-16392(a)BA.A.B.I} <core> [core/mem/q_malloc.c:149]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(c0c0c000, abcdefed)[0x801544c58:0x801544c90]! Memory allocator was called from core: core/action.c:754. Fragment marked by core: core/dset.c:733. Exec from core/mem/q_malloc.c:504. Nov 2 08:13:41 home /usr/local/sbin/kamailio[94703]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 22 Nov 2 08:13:41 home kernel: pid 94702 (kamailio), uid 0: exited on signal 6 (core dumped) Nov 2 08:13:41 home /usr/local/sbin/kamailio[94692]: ALERT: <core> [main.c:767]: handle_sigs(): child process 94702 exited by a signal 6 Nov 2 08:13:41 home /usr/local/sbin/kamailio[94692]: ALERT: <core> [main.c:770]: handle_sigs(): core was generated Nov 2 08:14:56 home login[8284]: ROOT LOGIN (root) ON ttyu0 Nov 2 08:16:26 home kernel: pid 94692 (kamailio), uid 0: exited on signal 11 (core dumped) ``` I had an identical problem a week ago, also with a crash on a BYE for an active call: ``` Oct 27 13:00:02 home /usr/local/sbin/kamailio[79819]: CRITICAL: {1 598425 BYE 649761149-5061-291(a)BA.A.B.I} <core> [core/mem/q_malloc.c:149]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(c0c0c000, abcdefed)[0x801551808:0x801551840]! Memory allocator was called from core: core/action.c:754. Fragment marked by core: core/dset.c:733. Exec from core/mem/q_malloc.c:504. Oct 27 13:02:09 home /usr/local/sbin/kamailio[79820]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 22 Oct 27 13:02:09 home kernel: pid 79819 (kamailio), uid 0: exited on signal 6 (core dumped) Oct 27 13:02:09 home /usr/local/sbin/kamailio[79809]: ALERT: <core> [main.c:767]: handle_sigs(): child process 79819 exited by a signal 6 Oct 27 13:02:09 home /usr/local/sbin/kamailio[79809]: ALERT: <core> [main.c:770]: handle_sigs(): core was generated Oct 27 13:04:55 home kernel: pid 79809 (kamailio), uid 0: exited on signal 11 (core dumped) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.3.0 (x86_64/freebsd) 4cc67a flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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, select, kqueue. id: 4cc67a compiled on 18:51:34 Oct 25 2019 with cc 6.0 ``` * **Operating System**: FreeBSD 12.0 ``` FreeBSD home.XXX 12.0-RELEASE-p10 FreeBSD 12.0-RELEASE-p10 GENERIC amd64 ``` -- 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/2121

2 16

[kamailio/kamailio] [Feature Request] Python3 compatibility for dbtextdb (#1747)
by Anthony Messina 04 May '20

04 May '20

kamctl's dbtextdb.py fails to build in a Python3-only environment. Update dbtextdb to Python3. -- 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/1747

4 12

[kamailio/kamailio] Kamailio service is failed (#2309)
by rombojack 04 May '20

04 May '20

I recently installed kamailio and it was enabled & started--> Service is active & running But once I added users I see kamailio service is failed [root@rlab111053 kamailio]# systemctl status kamailio ● kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/etc/systemd/system/kamailio.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Wed 2020-04-29 18:47:26 IST; 860ms ago Process: 16759 ExecStart=/usr/sbin/kamailio -DD -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY (code=exited, status=255) Main PID: 16759 (code=exited, status=255) Apr 29 18:47:25 rlab111053 systemd[1]: kamailio.service: main process exited, code=exited, status=255/n/a Apr 29 18:47:25 rlab111053 systemd[1]: Unit kamailio.service entered failed state. Apr 29 18:47:25 rlab111053 systemd[1]: kamailio.service failed. Apr 29 18:47:26 rlab111053 systemd[1]: kamailio.service holdoff time over, scheduling restart. Apr 29 18:47:26 rlab111053 systemd[1]: Stopped Kamailio (OpenSER) - the Open Source SIP Server. Apr 29 18:47:26 rlab111053 systemd[1]: start request repeated too quickly for kamailio.service Apr 29 18:47:26 rlab111053 systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Apr 29 18:47:26 rlab111053 systemd[1]: Unit kamailio.service entered failed state. Apr 29 18:47:26 rlab111053 systemd[1]: kamailio.service failed. **I am using below version** [root@rlab111053 kamailio]# kamailio -version version: kamailio 5.1.10 (x86_64/linux) cfcfd5 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: cfcfd5 compiled on 15:40:49 Mar 6 2020 with gcc 4.8.5 [root@rlab111053 kamailio]# Can some help to fix it  ### Description  ### Troubleshooting #### Reproduction  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- 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/2309

3 3

[kamailio/kamailio] Add iteration by all DNS NAPTR records (#2290)
by Semen Darienko 03 May '20

03 May '20

Current stable release support using only one (first by ordering) NAPTR DNS record. I didn't find any ideas how to configure possibility for use all supported NAPTR / SRV records. This pull request resolve this issue. General issue: PreConditions: # host -t naptr voip.somehost.com voip.somehost.com has NAPTR record 1 0 "S" "SIPS+D2T" "" _sips._tcp.voip.somehost.com. voip.somehost.com has NAPTR record 2 0 "S" "SIP+D2U" "" _sip._udp.voip.somehost.com. # host -t srv _sips._tcp.voip.somehost.com _sips._tcp.voip.somehost.com has SRV record 1 1 443 voip.somehost.com. _sips._tcp.voip.somehost.com has SRV record 2 1 5061 192.168.1.50. _sips._tcp.voip.somehost.com has SRV record 3 1 5061 10.100.1.20. # host -t srv _sip._udp.voip.somehost.com _sip._udp.voip.somehost.com has SRV record 1 1 5060 voip.somehost.com. _sip._udp.voip.somehost.com has SRV record 2 1 5060 192.168.1.50. _sip._udp.voip.somehost.com has SRV record 3 1 5060 10.100.1.20. In my configuration of kamailio I don't see trying to use second by priority NAPTR record: voip.somehost.com has NAPTR record 2 0 "S" "SIP+D2U" "" _sip._udp.voip.somehost.com. Kindly ask to share your ideas regarding faced issue and my pull request. Thank you. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2290 -- Commit Summary -- * Add using all NAPTR records -- File Changes -- M src/core/dns_cache.c (86) M src/core/resolve.c (1) M src/core/resolve.h (1) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2290.patch https://github.com/kamailio/kamailio/pull/2290.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/2290

2 3

[kamailio/kamailio] presence module with in-memory presentity records (#2294)
by Daniel-Constantin Mierla 02 May '20

02 May '20

Track the issues discovered by different developers while implementing in-memory only presentity records for presence module. -- 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/2294

2 10

[kamailio/kamailio] usrloc: change "-" for "_" in stats name to be prometheus compliant (#2304)
by Federico Cabiddu 02 May '20

02 May '20

#### Pre-Submission Checklist    - [X] Commit message has the format required by CONTRIBUTING guide - [X] Commits are split per component (core, individual modules, libs, utils, ...) - [X] 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 - [X] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  usrloc generated statistics (contacts, expires, users) contain "-" in their names (usrloc-contacs and so on), which is not valid according to prometheus naming convention. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2304 -- Commit Summary -- * usrloc: change "-" for "_" in stats name to be prometheus compliant -- File Changes -- M src/modules/usrloc/udomain.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2304.patch https://github.com/kamailio/kamailio/pull/2304.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/2304

3 16

git:master:4d49df44: textops: use safer macros for temporarily making zero-ending strings
by Daniel-Constantin Mierla 30 Apr '20

30 Apr '20

Module: kamailio Branch: master Commit: 4d49df443577dab22f6d4dae154468d855cf0463 URL: https://github.com/kamailio/kamailio/commit/4d49df443577dab22f6d4dae154468d… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2020-04-30T15:52:04+02:00 textops: use safer macros for temporarily making zero-ending strings --- Modified: src/modules/textops/textops.c --- Diff: https://github.com/kamailio/kamailio/commit/4d49df443577dab22f6d4dae154468d… Patch: https://github.com/kamailio/kamailio/commit/4d49df443577dab22f6d4dae154468d…

1 0

git:5.1:327548cb: pkg/kamailio/deb: version set to 5.1.10.1
by Victor Seva 30 Apr '20

30 Apr '20

Module: kamailio Branch: 5.1 Commit: 327548cbfdc2c5331d9a9264aa6a1571c35ff02e URL: https://github.com/kamailio/kamailio/commit/327548cbfdc2c5331d9a9264aa6a157… Author: Victor Seva <linuxmaniac(a)torreviejawireless.org> Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org> Date: 2020-04-30T14:01:27+02:00 pkg/kamailio/deb: version set to 5.1.10.1 No code changes, just bump version so we get new builds with the new schema. See for details: https://github.com/kamailio/kamailio/issues/2160 --- Modified: pkg/kamailio/deb/buster/changelog Modified: pkg/kamailio/deb/debian/changelog Modified: pkg/kamailio/deb/jessie/changelog Modified: pkg/kamailio/deb/precise/changelog Modified: pkg/kamailio/deb/sid/changelog Modified: pkg/kamailio/deb/stretch/changelog Modified: pkg/kamailio/deb/trusty/changelog Modified: pkg/kamailio/deb/wheezy/changelog Modified: pkg/kamailio/deb/xenial/changelog --- Diff: https://github.com/kamailio/kamailio/commit/327548cbfdc2c5331d9a9264aa6a157… Patch: https://github.com/kamailio/kamailio/commit/327548cbfdc2c5331d9a9264aa6a157…

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
43
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev April 2020