sr-dev November 2023

sr-dev@lists.kamailio.org

15 participants
385 discussions

[kamailio/kamailio] [pua] reginfo_increase_version does nothing (Issue #3234)

by Matteo

### Description The reginfo notifications sent via pua_reginfo + presence_reginfo contains the version fixed to `0`. The pua docs report the param `reginfo_increase_version` which should increase the version if enabled, but currently does nothing. Looking into the code seems to confirm that, param is read from `pua` module but is not used anywhere. While the param `dlginfo_increase_version` seems to be used for the intended scope. #### Reproduction Setup pua + pua_reginfo to publish registration informations and observe that version param of reginfo is always 0, not respecting pua `reginfo_increase_version` setting. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.6.1 (x86_64/linux) 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, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: unknown compiled with gcc 9.4.0 ``` * **Operating System**: ``` Linux Debian bullseye/sid ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3234 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3234(a)github.com>

2 months, 4 weeks

[kamailio/kamailio] topos: add compatiblity for early in-dialog NOTIFY (PR #3627)

by Maurits de Ruiter

#### 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:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description After enabling the Topos module, we ran into a bit of trouble with early in-dialog notifies. We use the `event: talk` package from Cisco Broadsoft to be able to do call control, as described in chapter 6 here: https://pubhub.devnetcloud.com/media/broadsoft-docs/docs/pdf/BW-SIPAccessSi… This will send a NOTIFY with a header `Event: talk` before the first `200 OK`. Currently this doesn't work with the topos module, since the NOTIFY method without a B-side contact will not check the INVITE record. When added to those methods in `tps_msg.c`, it tries to check the SUBSCRIBE for all NOTIFY's in `tps_storage.c`. The NOTIFY with `Event: talk` will follow on an INVITE, so there was a small change needed there. I've limited it to just the NOTIFY's with the `Event: talk` header, to minimize any impact. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3627 -- Commit Summary -- * topos: add compatiblity for early in-dialog NOTIFY -- File Changes -- M src/modules/topos/tps_msg.c (5) M src/modules/topos/tps_storage.c (3) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3627.patch https://github.com/kamailio/kamailio/pull/3627.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3627 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3627(a)github.com>

3 months

[kamailio/kamailio] callout from event_route [tm:local-response] only occurs once (Issue #3064)

by dpaape

version: kamailio 5.5.2 (arm6/linux) 55e232 raspberry pi 3b I initially stated that I was running on 5.5.3 but I was mistaken. However I checked the 5.5.3 source and it appears to be the same. I think that there is a bug in the tm module with respect to the "tm:local-response" event route. In the "t_reply.c" file, there is a static variable called '_tm_local_response_set_lookup'. This variable is initialized at load time to zero. It is checked in the '_reply_light()' routine and will initiate a local callback from the config script if "armed". The problem as I see it is that if the callback is readied, the variable is set to one. But it is never reset. So the observed behavior is as follows. A REGISTER is received and the request_route arms the callback. The REGISTER requires an authorization (local database sqlite). After the 401 is sent back, the callback via the event route is called as expected. All good except that the event route script fragment is never executed again after the first call... ever, even if it's a new REGISTER request. I would think that somewhere in the tm module, the variable should be reset to zero so that subsequent transactions can initiate the event route again. Or maybe the variable ought to live somewhere in the transaction cell??? . . . t_on_reply ("MY_FRAG"); t_on_failure ("MY_FRAG"); . . . event_route [tm:local-response] { xlog ("L_NOTICE", IN tm:local-response\n"); my_function(); } . . . So 'my_function()' is only called once. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3064 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3064(a)github.com>

3 months

[kamailio/kamailio] Silence “make: --libs: No such file or directory” warnings (PR #3475)

by Дилян Палаузов

With GNU make 4.4 building Kamailio prints many “make: --libs: No such file or directory” and similar warnings. This changeset utilizes immediate variables and silences the warnings on my systems. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3475 -- Commit Summary -- * lib/ims: Aviod “make: --libs: No such file or directory” warnings * auth_identity: Aviod “make: --libs: No such file or directory” warnings * auth_ephemeral: Aviod “make: --libs: No such file or directory” warnings * app_python3: Avoid “/bin/sh: line 1: --ldflags: command not found” warnings * app_python3s: Avoid “/bin/sh: line 1: --ldflags: command not found” warnings * cdp: Aviod “make: --libs: No such file or directory” warnings * cnxcc: Avoid “make: --libs-only-L: No such file or directory” warnings * cplc: Avoid “make: --libs-only-L: No such file or directory” warnings * crypto: Aviod “make: --libs: No such file or directory” warnings * db_postgres: Avoid “make: --libs-only-L: No such file or directory” warnings * db_redis: Avoid “make: --libs-only-L: No such file or directory” warning * dialplan: Avoid “make: --libs-only-L: No such file or directory” warning * gzcompress: Aviod “make: --libs: No such file or directory” warnings * http_async_client: Aviod “make: --libs: No such file or directory” warnings * http_client: Aviod “make: --libs: No such file or directory” warning * ims_auth: Avoid “make: --libs-only-L: No such file or directory” warning * ims_icscf: Aviod “make: --libs: No such file or directory” warning * ims_registrar_scscf: Avoid “make: --libs-only-L: No such file or directory” warnings * ims_registrar_pcscf: Aviod “make: --libs: No such file or directory” warning * ims_isc: Avoid “make: --libs-only-L: No such file or directory” warnings * jansson: Aviod “make: --libs: No such file or directory” warning * kazoo: Avoid “make: --libs: No such file or directory’ warning * lcr: Aviod “make: --libs: No such file or directory” warning * log_systemd: Aviod “make: --libs: No such file or directory” warning * lost: Aviod “make: --libs: No such file or directory” warnings * lwsc: Aviod “make: --libs: No such file or directory” warning * ndb_redis: Aviod “make: --libs: No such file or directory” warning * osp: Avoid “make: --libs: No such file or directory’ warning * outbound: Aviod “make: --libs: No such file or directory” warnings * presence: Avoid “make: --libs-only-L: No such file or directory” warnings * presence_conference: Aviod “make: --libs: No such file or directory” warning * presence_dialog: Aviod “make: --libs: No such file or directory” warning * presence_reginfo: Aviod “make: --libs: No such file or directory” warning * presence_xml: Avoid “make: --libs-only-L: No such file or directory” warnings * pua: Avoid “make: --libs-only-L: No such file or directory” warnings * pua_bla: Aviod “make: --libs: No such file or directory” warning * pua_dialoginfo: Aviod “make: --libs: No such file or directory” warning * pua_reginfo: Aviod “make: --libs: No such file or directory” warning * pua_usrloc: Aviod “make: --libs: No such file or directory” warning * pua_xmpp: Aviod “make: --libs: No such file or directory” warning * regex: Aviod “make: --libs: No such file or directory” warning * rls: Avoid “make: --libs-only-L: No such file or directory” warnings * slack: Aviod “make: --libs: No such file or directory” warning * systemdops: Avoid “make: --libs-only-L: No such file or directory” warning * tls: Aviod “make: --libs: No such file or directory” warnings * tlsa: Avoid “make: --libs-only-L: No such file or directory” warning * topos_redis: Aviod “make: --libs: No such file or directory” warning * utils: Avoid “make: --libs-only-L: No such file or directory” warnings * uuid: Aviod “make: --libs: No such file or directory” warning * websocket: Aviod “make: --libs: No such file or directory” warnings * xcap_server: Avoid “make: --libs-only-L: No such file or directory” warnings * xhttp_pi: Avoid “make: --libs-only-L: No such file or directory” warnings * xmlops: Aviod “make: --libs: No such file or directory” warning * xmlrpc: Aviod “make: --libs: No such file or directory” warning -- File Changes -- M src/lib/ims/Makefile (4) M src/modules/app_python3/Makefile (6) M src/modules/app_python3s/Makefile (6) M src/modules/auth_ephemeral/Makefile (2) M src/modules/auth_identity/Makefile (4) M src/modules/cdp/Makefile (4) M src/modules/cnxcc/Makefile (4) M src/modules/cplc/Makefile (4) M src/modules/crypto/Makefile (2) M src/modules/db_postgres/Makefile (2) M src/modules/db_redis/Makefile (2) M src/modules/dialplan/Makefile (2) M src/modules/gzcompress/Makefile (2) M src/modules/http_async_client/Makefile (6) M src/modules/http_client/Makefile (2) M src/modules/ims_auth/Makefile (4) M src/modules/ims_icscf/Makefile (4) M src/modules/ims_isc/Makefile (4) M src/modules/ims_registrar_pcscf/Makefile (4) M src/modules/ims_registrar_scscf/Makefile (4) M src/modules/jansson/Makefile (2) M src/modules/kazoo/Makefile (2) M src/modules/lcr/Makefile (2) M src/modules/log_systemd/Makefile (2) M src/modules/lost/Makefile (6) M src/modules/lwsc/Makefile (2) M src/modules/ndb_redis/Makefile (2) M src/modules/osp/Makefile (2) M src/modules/outbound/Makefile (7) M src/modules/presence/Makefile (4) M src/modules/presence_conference/Makefile (4) M src/modules/presence_dialoginfo/Makefile (4) M src/modules/presence_reginfo/Makefile (4) M src/modules/presence_xml/Makefile (4) M src/modules/pua/Makefile (4) M src/modules/pua_bla/Makefile (4) M src/modules/pua_dialoginfo/Makefile (4) M src/modules/pua_reginfo/Makefile (4) M src/modules/pua_usrloc/Makefile (4) M src/modules/pua_xmpp/Makefile (4) M src/modules/regex/Makefile (2) M src/modules/rls/Makefile (4) M src/modules/slack/Makefile (2) M src/modules/systemdops/Makefile (2) M src/modules/tls/Makefile (4) M src/modules/tlsa/Makefile (4) M src/modules/topos_redis/Makefile (2) M src/modules/utils/Makefile (4) M src/modules/uuid/Makefile (2) M src/modules/websocket/Makefile (2) M src/modules/xcap_server/Makefile (4) M src/modules/xhttp_pi/Makefile (4) M src/modules/xmlops/Makefile (4) M src/modules/xmlrpc/Makefile (4) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3475.patch https://github.com/kamailio/kamailio/pull/3475.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3475 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3475(a)github.com>

3 months, 2 weeks

[kamailio/kamailio] cfgt: doesn't support tm_suspend() tm_continue() (#684)

by Victor Seva

Actual implementation doesn't work with async. Need to investigate how to support it --- 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/684

3 months, 2 weeks

[kamailio/kamailio] TLS related crash in Kamailio 5.7.2 (double free) (Issue #3635)

by Sebastian Damm

### Description We have updated one system from a Ubuntu Focal 5.6.x container to a Ubuntu Jammy 5.7.2 container. In the last 24 hours, we saw three crashes. The logs of the last crash say: ``` Nov 09 20:39:34 sipproxy /usr/sbin/kamailio[4332]: CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f[4434056180](tel:4434056180)), called from tls: tls_init.c: ser_free> Nov 09 20:39:34 sipproxy /usr/sbin/kamailio[4331]: CRITICAL: <core> [core/mem/q_malloc.c:123]: qm_debug_check_frag(): BUG: qm: fragm. 0x7f[44340561](tel:44340561)d0 (address 0x7f[4434056208](tel:4434056208)) beginning overwritten > Nov 09 20:39:43 sipproxy /usr/sbin/kamailio[4273]: ALERT: <core> [main.c:776]: handle_sigs(): child process 4331 exited by a signal 6 Nov 09 20:39:43 sipproxy /usr/sbin/kamailio[4273]: ALERT: <core> [main.c:779]: handle_sigs(): core was generated ``` #### Debugging Data Backtraces of the three crashes are attached. [kamailio-crash1.log](https://github.com/kamailio/kamailio/files/13313115/ka… [kamailio-crash2.log](https://github.com/kamailio/kamailio/files/13313116/ka… [kamailio-crash3.log](https://github.com/kamailio/kamailio/files/13313117/ka… ### Additional Information We are using the official Kamailio debian packages. * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.7.2 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: unknown compiled with gcc 11.4.0 ``` * **Operating System**:  ``` root@sipproxy:/WORKSPACE/sipproxy-container# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy root@sipproxy:/WORKSPACE/sipproxy-container# uname -a Linux sipproxy 5.15.0-87-generic #97-Ubuntu SMP Mon Oct 2 21:09:21 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3635 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3635(a)github.com>

3 months, 2 weeks

[kamailio/kamailio] dialog: failover database loading behaviour in shared DB scenario, expiration of dialogs (#2080)

by Henning Westerholt

The dialog module will expire dialogs that don't actually belong to the particular proxy. Scenario: 2 proxies on 5.2.4 with a loadbalancer in front. Call was routed over proxy1, dialog timeout on proxy2 was shorter (to make it easier to reproduce it). The results: * Dialog synchronized with DMQ: proxy 2 would timeout the dialog * Dialog entry synchronized to proxy2 DB and proxy2 restarted: Proxy2 would timeout the dialog * Dialog entry synchronized to proxy2 DB and proxy2 not restarted: Proxy2 would _not_ timeout the dialog (I’ve tried both db_mode 1 and 2) So the proxy2 would load the dialog into memory and then later expire it. So timeout routes, send_bye on timeout would not work correctly. One idea to solve this would be to check e.g. over the existing socket data if the dialog belongs to this proxy and skip loading it in this case. This could be also made configurable e.g. with a module parameter. Any comments? Better ideas how to solve it? -- 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/2080

3 months, 2 weeks

[kamailio/kamailio] ndb_redis doesn't use AUTH on a slave server in redis cluster. (Issue #3654)

by Dries De Gendt

### Description & troubleshooting I have defined a redis cluster as followed. The cluster consists of 3 masters (port 6379) and 3 slaves (port 6380). The password is identical on all nodes through redis option 'requirepass'. ``` modparam("ndb_redis", "server", "name=sbcredis;addr=SBCMASTERREDISIP;port=6379;db=0;pass=REDACTED") modparam("ndb_redis", "server", "name=sbcredis;addr=PRIVATEIP;port=6380;db=0;pass=REDACTED") modparam("ndb_redis", "server", "name=sbcredis;addr=ASTP5IP;port=6380;db=0;pass=REDACTED") modparam("ndb_redis", "server", "name=sbcredis;addr=ASTP6IP;port=6379;db=0;pass=REDACTED") modparam("ndb_redis", "server", "name=sbcredis;addr=ASTP3IP;port=6380;db=0;pass=REDACTED") modparam("ndb_redis", "server", "name=sbcredis;addr=ASTP4IP;port=6379;db=0;pass=REDACTED") modparam("ndb_redis", "cluster", 1) modparam("ndb_redis", "allow_dynamic_nodes", 1) modparam("ndb_redis", "debug", 3) ``` When executing the redis_cmd command, most of the times an expected warning is shown due to another server providing the requested slot: `"(error) MOVED ... 192.168.136.241:6380"` Notice that I've enabled "allow_dynamic_nodes" to make sure there is an automated connection attempt to the indicated server. However, it appears that sometimes a "NOAUTH Authentication required." error is thrown when there is a redirection to a slave server serving that slot. I can authenticate succesfull on the redis-cli when using the identical password though. Also note that when a redis master is queried, the redis_cmd is successful. #### Reproduction Each simple redis command that needs authentication (GET, SET, ...) `redis_cmd("sbcredis", "SET TESTKEY TESTVALUE", "r");` #### Log Messages ``` ndb_redis [redis_client.c:1089]: redisc_exec(): Redis error:NOAUTH Authentication required. ``` ### Possible Solutions None for now except disabling the password on all nodes. ### Additional Information ``` kamailio 5.7.2 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3654 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3654(a)github.com>

3 months, 2 weeks

[kamailio/kamailio] kazoo: SIGSEGV on module unload (Issue #3648)

by sergey-safarov

On core load ``` Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio --atexit=no -DD -P /run/kamailio/kamailio.pid -f /etc/kamail'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000ffff94f36350 in strlen () from /lib64/libc.so.6 Missing separate debuginfos, use: yum debuginfo-install glibc-2.28-236.el8.aarch64 jansson-2.14-1.el8.aarch64 json-c-0.13.1-3.el8.aarch64 keyutils-libs-1.5.10-9.el8.aarch64 krb5-libs-1.18.2-25.el8.aarch64 libblkid-2.32.1-43.el8.aarch64 libcom_err-1.45.6-5.el8.aarch64 libcurl-minimal-7.61.1-33.el8.aarch64 libevent-2.1.8-5.el8.aarch64 libgcc-8.5.0-20.el8.aarch64 libmount-2.32.1-43.el8.aarch64 libnghttp2-1.33.0-3.el8_2.1.aarch64 librabbitmq-0.9.0-4.el8.aarch64 libselinux-2.9-8.el8.aarch64 libunistring-0.9.9-3.el8.aarch64 libuuid-2.32.1-43.el8.aarch64 libxml2-2.9.7-16.el8.aarch64 mariadb-connector-c-3.1.11-2.el8_3.aarch64 openssl-libs-1.1.1k-9.el8.aarch64 pcre-8.42-6.el8.aarch64 pcre2-10.32-3.el8.aarch64 systemd-libs-239-78.el8.aarch64 xz-libs-5.2.4-4.el8.aarch64 zlib-1.2.11-25.el8.aarch64 ``` **bt full** ``` #0 0x0000ffff94f36350 in strlen () from /lib64/libc.so.6 No symbol table info available. #1 0x0000ffff94f60c7c in vfprintf () from /lib64/libc.so.6 No symbol table info available. #2 0x0000ffff94fe500c in __vsyslog_chk () from /lib64/libc.so.6 No symbol table info available. #3 0x0000ffff94fe5110 in syslog () from /lib64/libc.so.6 No symbol table info available. #4 0x000000000077ebb8 in qm_status (qmp=0xffff8acee000) at core/mem/q_malloc.c:877 __llevel = -4 qm = 0xffff8acee000 f = 0xffff8c0e0c08 i = 5961 j = 9650680 h = 0 unused = 0 memlog = -4 mem_summary = 0 __func__ = "qm_status" __llevel = <optimized out> __kld = <optimized out> #5 0x0000000000772e30 in qm_debug_check_frag (qm=0xffff8acee000, f=0xffff8c0e0c08, file=0xffff8a2a47f0 "kazoo: kz_amqp.c", line=633, efile=0x934218 "core/mem/q_malloc.c", eline=511) at core/mem/q_malloc.c:139 p = 0xffffd0ed96e0 __func__ = "qm_debug_check_frag" #6 0x00000000007775c8 in qm_free (qmp=0xffff8acee000, p=0xffff8c0e0c40, file=0xffff8a2a47f0 "kazoo: kz_amqp.c", func=0xffff8a2abcb0 <__func__.18644> "kz_amqp_destroy_channels", line=633, mname=0xffff8a2a4350 "kazoo") at core/mem/q_malloc.c:511 qm = 0xffff8acee000 f = 0xffff8c0e0c08 size = 281472999768912 next = 0xd0ed9740 prev = 0x1 __func__ = "qm_free" #7 0x0000000000784058 in qm_shm_free (qmp=0xffff8acee000, p=0xffff8c0e0c40, file=0xffff8a2a47f0 "kazoo: kz_amqp.c", func=0xffff8a2abcb0 <__func__.18644> "kz_amqp_destroy_channels", line=633, mname=0xffff8a2a4350 "kazoo") at core/mem/q_malloc.c:1350 No locals. #8 0x0000ffff8a248270 in kz_amqp_destroy_channels (server_ptr=0xffff8ad28880) at kz_amqp.c:633 i = 25 __func__ = "kz_amqp_destroy_channels" #9 0x0000ffff8a2482b4 in kz_amqp_destroy_server (server_ptr=0xffff8ad28880) at kz_amqp.c:641 next = 0x0 __func__ = "kz_amqp_destroy_server" #10 0x0000ffff8a248388 in kz_amqp_destroy_zone (zone_ptr=0xffff8ad28410) at kz_amqp.c:652 next = 0xffff8ad28918 server_ptr = 0xffff8ad28880 __func__ = "kz_amqp_destroy_zone" #11 0x0000ffff8a248488 in kz_amqp_destroy_zones () at kz_amqp.c:664 g = 0xffff8ad28410 __func__ = "kz_amqp_destroy_zones" #12 0x0000ffff8a248510 in kz_amqp_destroy () at kz_amqp.c:672 __func__ = "kz_amqp_destroy" #13 0x0000ffff8a2402a0 in mod_destroy () at kazoo.c:541 __func__ = "mod_destroy" #14 0x00000000005e1670 in destroy_modules () at core/sr_module.c:842 t = 0xffff9379c750 foo = 0xffff9379b798 __func__ = "destroy_modules" #15 0x000000000041e81c in cleanup (show_status=1) at main.c:561 memlog = -767102331 __func__ = "cleanup" #16 0x00000000004208b4 in shutdown_children (sig=15, show_status=1) at main.c:704 __func__ = "shutdown_children" #17 0x00000000004217d0 in handle_sigs () at main.c:735 chld = 65535 chld_status = 0 any_chld_stopped = 0 memlog = 4407388 __func__ = "handle_sigs" #18 0x0000000000434058 in main_loop () at main.c:1900 i = 8 pid = 1350059 si = 0x0 si_desc = "udp receiver child=7 sock=[2605:84c0:51:1f04::6]:5080\000\000\000\360\234\355\320\377\377\000\000صx\223\377\377\000\000\300\234\355\320\377\377\000\000\250\303Փ\377\377\000\000\340\234\355\320\377\377\000\000\360\234\355\320\377\377\000\000\360\234\355\320\377\377\000\000\300\234\355\320\377\377\000\000\320\377\377\377\200\377\377\377" nrprocs = 8 woneinit = 1 __func__ = "main_loop" #19 0x000000000043f094 in main (argc=11, argv=0xffffd0eda278) at main.c:3078 cfg_stream = 0xec522a0 c = -1 r = 0 tmp = 0xffffd0edae66 "" tmp_len = 0 port = 0 proto = 65535 ahost = 0x0 aport = 0 options = 0x8c99d0 ":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 = 1225301378 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 2 n_lst = 0xffffffff p = 0xffff94f39348 <__libc_start_main+160> "" st = {st_dev = 22, st_ino = 18918, st_mode = 16832, st_nlink = 2, st_uid = 992, st_gid = 987, st_rdev = 0, __pad1 = 0, st_size = 60, st_blksize = 4096, __pad2 = 0, st_blocks = 0, st_atim = {tv_sec = 1695127265, tv_nsec = 210164976}, st_mtim = {tv_sec = 1695742685, tv_nsec = 688032700}, st_ctim = {tv_sec = 1695742685, tv_nsec = 688032700}, __glibc_reserved = {0, 0}} tbuf = '\000' <repeats 56 times>, "xN!\225\377\377\000\000hN!\225\377\377\000\000\bN!\225\377\377\000\000(N!\225\377\377\000\000\070N!\225\377\377\000\000\250N!\225\377\377\000\000\270N!\225\377\377\000\000\310N!\225\377\377\000\000HN!\225\377\377\000\000XN!\225\377\377", '\000' <repeats 18 times>, "\330M!\225\377\377", '\000' <repeats 42 times>... option_index = 12 long_options = {{name = 0x8cbda8 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x8c6c10 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x8cbdb0 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x8cbdb8 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x8cbdc0 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x8cbdd0 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x8cbde0 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x8cbdf0 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x8cbe00 "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x8cbe10 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x8cbe20 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x8cbe28 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x8cbe38 "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" ``` Some more info ``` (gdb) f 8 #8 0x0000ffff8a248270 in kz_amqp_destroy_channels (server_ptr=0xffff8ad28880) at kz_amqp.c:633 633 shm_free(server_ptr->channels); (gdb) list 628 for(i=0; i < dbk_channels; i++) { 629 if(server_ptr->channels[i].targeted != NULL) { 630 kz_amqp_free_bind(server_ptr->channels[i].targeted); 631 } 632 } 633 shm_free(server_ptr->channels); 634 server_ptr->channels = NULL; 635 } 636 637 kz_amqp_server_ptr kz_amqp_destroy_server(kz_amqp_server_ptr server_ptr) (gdb) p server_ptr $1 = (kz_amqp_server_ptr) 0xffff8ad28880 (gdb) p *server_ptr $2 = {id = 1, channel_index = 20, zone = 0xffff8ad28410, connection = 0xffff8ad28578, producer = 0xffff8c754700, channels = 0xffff8c0e0c40, next = 0x0} (gdb) p server_ptr->channels $3 = (kz_amqp_channel_ptr) 0xffff8c0e0c40 (gdb) p *server_ptr->channels $4 = {cmd = 0x0, targeted = 0xffff8c0e1220, consumer = 0x0, channel = 1, state = KZ_AMQP_CHANNEL_FREE, timer = {tv_sec = 1700266610, tv_usec = 250929}, lock = 0} (gdb) f 7 #7 0x0000000000784058 in qm_shm_free (qmp=0xffff8acee000, p=0xffff8c0e0c40, file=0xffff8a2a47f0 "kazoo: kz_amqp.c", func=0xffff8a2abcb0 <__func__.18644> "kz_amqp_destroy_channels", line=633, mname=0xffff8a2a4350 "kazoo") at core/mem/q_malloc.c:1350 1350 qm_free(qmp, p, file, func, line, mname); (gdb) list 1345 } 1346 void qm_shm_free(void* qmp, void* p, const char* file, const char* func, 1347 unsigned int line, const char* mname) 1348 { 1349 qm_shm_lock(); 1350 qm_free(qmp, p, file, func, line, mname); 1351 qm_shm_unlock(); 1352 } 1353 #else 1354 void* qm_shm_malloc(void* qmp, size_t size) ``` This happened on customized Kamailio 5.6.4 where reverted some commits. If it does not make sense for you please close. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3648 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3648(a)github.com>

3 months, 3 weeks

[kamailio/kamailio] Kamailio 5.6 do not execute "event_route[websocket:closed]" when tcp reset (Issue #3389)

by ReznikovAlexei

### Description I have faced with an issue in Kamailio 5.6 when tcp closed reset by peer on remote side but Kamailio dont executing route block "event_route[websocket:closed]". ### Kamailio minimal config file ####### Global Parameters ######### listen=udp:192.168.31.81:5060 listen=tcp:192.168.31.81:5060 listen=tcp:192.168.31.81:7000 tcp_accept_no_cl=yes ######## Kamailio control connector module ######## loadmodule "tm.so" loadmodule "ctl.so" modparam("ctl", "binrpc_buffer_size", 4096) loadmodule "pv.so" loadmodule "sl.so" loadmodule "xlog.so" loadmodule "nathelper.so" loadmodule "xhttp.so" loadmodule "websocket.so" loadmodule "ipops.so" loadmodule "siputils.so" loadmodule "rr.so" loadmodule "usrloc.so" loadmodule "registrar.so" request_route { if(method=="REGISTER"){ save("location"); exit; } } event_route[xhttp:request] { set_reply_close(); set_reply_no_connect(); xlog("L_WARN", "websocket|log|connection from $si received!\n"); if ($hdr(Upgrade)=~"websocket" && $hdr(Connection)=~"Upgrade" && $rm=~"GET") { if (ws_handle_handshake()) { exit; } } xhttp_reply("404", "Not found", "", ""); } event_route[websocket:closed] { xlog("L_WARN", "websocket|log|connection from $si closed!\n"); } #### Reproduction ###Kamailio started and client sipml5 connected [root@centos8 kamailio]# sh /root/run_kamailio.sh Listening on udp: 192.168.31.81:5060 tcp: 192.168.31.81:5060 tcp: 192.168.31.81:7000 Aliases: tcp: centos8.local.tst:7000 tcp: centos8.local.tst:5060 udp: centos8.local.tst:5060 15(29286) WARNING: <script>: websocket|log|connection from 192.168.31.100 received! ### closing tcp connection by remote side C:\Users\Alex>netstat -ano | findstr :7000 TCP 192.168.31.100:51688 192.168.31.81:7000 ESTABLISHED 9624 C:\Users\Alex>taskkill /pid 9624 /F SUCCESS: The process with PID 9624 has been terminated. ### issue reproduced 17(29288) ERROR: <core> [core/tcp_read.c:272]: tcp_read_data(): error reading: Connection reset by peer (104) ([192.168.31.100]:51688 ->17(29288) ERROR: <core> [core/tcp_read.c:274]: tcp_read_data(): -> [192.168.31.81]:7000) 17(29288) ERROR: <core> [core/tcp_read.c:1478]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f47d5134ad0 r: 0x7f47d5134bf8 (-1) And nothing else but I am expecting something like that: this is output from Kamailio 5.5 where the issue not reproduced. 13(39207) WARNING: websocket [ws_frame.c:227]: encode_and_send_ws_frame(): TCP/TLS connection get failed 13(39207) ERROR: websocket [ws_frame.c:761]: ping_pong(): sending keepalive 14(39208) WARNING: <script>: websocket|log|connection from 192.168.31.100 closed! Also additional output ws.dump [root@centos8 kamailio]# kamcmd ws.dump { connections: { } info: { wscounter: 0 truncated: no } } ### Possible Solutions I found a commit which called this behavior https://github.com/kamailio/kamailio/commit/3033b7681b4240fd64c9f1ff446b529… If I was built Kamailo without this commit, the issue not reproduced, also the issue not reproduced in Kamailio 5.5 or older. ### Additional Information ``` [root@centos8 kamailio-5.6]# kamailio -v version: kamailio 5.6.4 (x86_64/linux) a004cf 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, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: a004cf compiled on 11:09:28 Mar 6 2023 with gcc 8.5.0 ``` * **Operating System**: ``` [root@centos8 kamailio-5.6]# cat /etc/centos-release CentOS Stream release 8 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3389 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3389(a)github.com>

3 months, 3 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev November 2023