sr-dev May 2022

sr-dev@lists.kamailio.org

12 participants
287 discussions

[kamailio/kamailio] Database TLS connection through cnf file: TLS error followed by memory corruption messages (Issue #3115)
by liviu-rolo 16 Jun '22

16 Jun '22

### Description Using kamailio 5.5.4 from the official Docker image (created like `create_dockerfile.sh bullseye 5.5.4`, but with no ENTRYPOINT). Doing TLS listening like: ``` socket_workers=2 tls_max_connections=20000 listen=tls:192.168.0.11:5061 enable_tls=yes dns_tls_pref=50 tls_port_no=5061 loadmodule "tls.so" ``` It is the second loaded module after tcpops. Have to connect to the database through cnf files for the SSL support: `modparam("sqlops","sqlcon","euler=>mysql://[euler]/euclid")` Relevant section in the cnf file: ``` [euler] port = 3306 host = 127.0.0.1 protocol = tcp user = gauss password = fermat default-character-set = utf8 ssl-ca = /SSL/riemann/ca-cert.pem ssl-cert = /SSL/riemann/client-cert.pem ssl-key = /SSL/riemann/client-key.pem #ssl-verify-server-cert ``` When starting kamailio: ``` 8(18) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: SSL connection error: PEM lib 8(18) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool 8(18) ERROR: sqlops [sql_api.c:165]: sql_connect(): failed to connect to the database [euclid] 8(18) ERROR: <core> [core/sr_module.c:874]: init_mod_child(): error while initializing module sqlops (/home/euler/lib64/euler/modules/sqlops.so) (idx: 8 rank: -2 desc: [Async Task Worker - default]) 8(18) ERROR: <core> [core/pt.c:338]: fork_process(): init_child failed for process 8, pid 18, "Async Task Worker - default" 8(18) ERROR: <core> [main.c:1850]: main_loop(): error in init_child 12(22) CRITICAL: <core> [core/mem/q_malloc.c:501]: qm_free(): BUG: bad pointer 0x7fafa23e6270 (out of memory block!) called from tls: tls_init.c: ser_free(323) - ignoring ``` Then kamailio just hangs on in an incomplete state: ``` / # ps auxww --forest USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 29 0.6 0.0 4092 3244 pts/1 Ss 08:59 0:00 bash root 36 0.0 0.0 6692 2964 pts/1 R+ 08:59 0:00 \_ ps auxww --forest root 1 0.0 0.0 4092 3252 pts/0 Ss 08:58 0:00 bash root 8 0.4 0.0 110868 23764 pts/0 S+ 08:58 0:00 kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 9 0.0 0.0 0 0 ? Zs 08:58 0:00 \_ [kamailio] <defunct> root 10 0.5 0.0 111080 31148 ? S 08:58 0:00 kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 11 0.0 0.0 111080 13412 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 12 99.9 0.0 111080 13240 ? R 08:58 0:43 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 13 0.0 0.0 111080 14252 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 14 0.0 0.0 111080 13432 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 15 0.0 0.0 111080 13296 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 16 0.0 0.0 111080 13348 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 17 0.0 0.0 111080 13220 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 18 0.0 0.0 111072 14196 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 19 99.7 0.0 111080 10748 ? R 08:58 0:43 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 20 0.2 0.0 0 0 ? Z 08:58 0:00 \_ [kamailio] <defunct> root 21 0.0 0.0 111080 13068 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 22 0.0 0.0 111080 13156 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 23 0.0 0.0 111080 10684 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 24 0.0 0.0 111080 10684 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 25 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 26 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 27 0.0 0.0 111080 13344 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 28 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg ```  ### Troubleshooting #### Reproduction  It is always happening, but not when either `listen=tls` or the SSL options in the cnf file are dropped. #### Debugging Data  ``` / # ps auxww --forest USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 29 0.6 0.0 4092 3244 pts/1 Ss 08:59 0:00 bash root 36 0.0 0.0 6692 2964 pts/1 R+ 08:59 0:00 \_ ps auxww --forest root 1 0.0 0.0 4092 3252 pts/0 Ss 08:58 0:00 bash root 8 0.4 0.0 110868 23764 pts/0 S+ 08:58 0:00 kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 9 0.0 0.0 0 0 ? Zs 08:58 0:00 \_ [kamailio] <defunct> root 10 0.5 0.0 111080 31148 ? S 08:58 0:00 kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 11 0.0 0.0 111080 13412 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 12 99.9 0.0 111080 13240 ? R 08:58 0:43 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 13 0.0 0.0 111080 14252 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 14 0.0 0.0 111080 13432 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 15 0.0 0.0 111080 13296 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 16 0.0 0.0 111080 13348 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 17 0.0 0.0 111080 13220 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 18 0.0 0.0 111072 14196 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 19 99.7 0.0 111080 10748 ? R 08:58 0:43 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 20 0.2 0.0 0 0 ? Z 08:58 0:00 \_ [kamailio] <defunct> root 21 0.0 0.0 111080 13068 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 22 0.0 0.0 111080 13156 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 23 0.0 0.0 111080 10684 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 24 0.0 0.0 111080 10684 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 25 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 26 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 27 0.0 0.0 111080 13344 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg root 28 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg ``` #### Log Messages  ``` 8(18) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: SSL connection error: PEM lib 8(18) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool 8(18) ERROR: sqlops [sql_api.c:165]: sql_connect(): failed to connect to the database [euclid] 8(18) ERROR: <core> [core/sr_module.c:874]: init_mod_child(): error while initializing module sqlops (/home/euler/lib64/euler/modules/sqlops.so) (idx: 8 rank: -2 desc: [Async Task Worker - default]) 8(18) ERROR: <core> [core/pt.c:338]: fork_process(): init_child failed for process 8, pid 18, "Async Task Worker - default" 8(18) ERROR: <core> [main.c:1850]: main_loop(): error in init_child 12(22) CRITICAL: <core> [core/mem/q_malloc.c:501]: qm_free(): BUG: bad pointer 0x7fafa23e6270 (out of memory block!) called from tls: tls_init.c: ser_free(323) - ignoring ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.4 (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 10.2.1 ``` * **Operating System**:  ``` Linux euler01 5.4.44-2-pve #1 SMP PVE 5.4.44-2 (Wed, 01 Jul 2020 16:37:57 +0200) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3115 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3115(a)github.com> [View Less]

2 9

[kamailio/kamailio] Kamailio 5.5.4 siputils doesn't validate long Austrian numbers as valid e164 (Issue #3117)
by Simone de Blasiis 15 Jun '22

15 Jun '22

### Description When using the [is_e164 function](https://kamailio.org/docs/modules/5.5.x/modules/siputils.html#sip… on a long Austrian number it doesn't seem to return true even if it's in e164 format. #### Reproduction The number in question, with some digits obfuscated for privacy, is +4322367108xxxxxx. I can confirm that the number exists and is a valid one. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.4 (x86_64/linux) flags: … [View More]

3 4

[kamailio/kamailio] crash related to functions in cfg file parser for invalid cfg (#2239)
by Henning Westerholt 14 Jun '22

14 Jun '22

Against current git master. ``` henning@static:~/repositories/kamailio$ cat etc/crash-4.cfg #!KAMAILIO loadmodule "sl.so" request_route { switch (1) { case -1: send_reply("404", "Not Found"); case -2: send_reply("405",("Method Not Allowed"); exit; } ``` > $ ./src/kamailio -f etc/crash-4.cfg -L src/modules/ -Y /tmp -E -d > 0(2278) CRITICAL: <core> [core/cfg.y:3549]: yyerror_at(): … [View More]

2 2

[kamailio/kamailio] KEMI Fatal Python error: failed releasing import lock after fork (Issue #3125)
by Nigel Daniels 10 Jun '22

10 Jun '22

### Description using kamailio 5.6.0 python: 3.8.10 OS : ubuntu 20.0.4 When trying to use kemi with the default configuration I get on startup. ` Fatal Python error: failed releasing import lock after fork ` #### Reproduction Using The configuration described here : https://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/kemi/#bas… #### Debugging Data ``` 0(1) INFO: <core> [core/kemi.c:106]: sr_kemi_core_info(): ===== kamailio.child_init(1) kamailio | 0(1) … [View More]DEBUG: <core> [core/sr_module.c:923]: init_child(): initializing PROC_POSTCHILDINIT with rank -126 kamailio | 0(1) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 0 rank -126: app_python3 [stand-alone receiver @ 10.10.0.4:5060] kamailio | Fatal Python error: failed releasing import lock after fork kamailio | Python runtime state: initialized kamailio | kamailio | Current thread 0x00007f3faa857180 (most recent call first): kamailio | <no Python frame> kamailio | 7(14) DEBUG: <core> [core/pt.c:308]: fork_process(): seeding PRNG with 1232772928 kamailio | 7(14) DEBUG: <core> [core/rand/cryptorand.c:36]: cryptorand_seed(): seeding cryptorand generator with 1232772928 kamailio | 7(14) DEBUG: <core> [core/rand/fortuna/random.c:175]: sr_add_entropy(): additional 4 bytes entropy added to cryptographic PRNG kamailio | 7(14) DEBUG: <core> [core/pt.c:313]: fork_process(): test random numbers 987270226 561754816 1532392054 1162699744 kamailio | 7(14) DEBUG: <core> [core/sr_module.c:923]: init_child(): initializing PROC_RPC with rank -2 kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: corex [ctl handler] kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: usrloc [ctl handler] kamailio | 7(14) DEBUG: <core> [core/utils/sruid.c:121]: sruid_init(): root for sruid is [ulcx-62931156-e-] (0 / 16) kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: registrar [ctl handler] kamailio | 7(14) DEBUG: <core> [core/utils/sruid.c:121]: sruid_init(): root for sruid is [uloc-62931156-e-] (0 / 16) kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: jsonrpcs [ctl handler] kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: kex [ctl handler] kamailio | 7(14) DEBUG: kex [kex_mod.c:155]: child_init(): rank is (-2) kamailio | 7(14) DEBUG: <core> [core/utils/sruid.c:121]: sruid_init(): root for sruid is [srid-62931156-e-] (0 / 16) kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: tm [ctl handler] kamailio | 7(14) DEBUG: tm [callid.c:136]: child_init_callid(): callid: '2ef035de7699493f-14(a)10.10.0.4' kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: tmx [ctl handler] kamailio | 7(14) DEBUG: tmx [tmx_mod.c:262]: child_init(): rank is (-2) kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: sl [ctl handler] kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: ctl [ctl handler] kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: debugger [ctl handler] kamailio | 7(14) DEBUG: debugger [debugger_mod.c:224]: child_init(): rank is (-2) kamailio | 7(14) DEBUG: <core> [core/sr_module.c:875]: init_mod_child(): idx 7 rank -2: app_python3 [ctl handler] kamailio | 7(14) DEBUG: app_python3 [apy_kemi.c:234]: sr_apy_kemi_exec_func_ex(): execution of method: .info kamailio | 7(14) DEBUG: app_python3 [apy_kemi.c:266]: sr_apy_kemi_exec_func_ex(): param[1] for: info is str: ===== kamailio.child_init(-2) kamailio | kamailio | 7(14) INFO: <core> [core/kemi.c:106]: sr_kemi_core_info(): ===== kamailio.child_init(-2) kamailio | 7(14) DEBUG: ctl [ctl.c:329]: mod_child(): ctl: mod_child(0), fork_process=0, csl=0x56186255e180 kamailio | 7(14) DEBUG: ctl [ctl.c:336]: mod_child(): ctl: 0 io_listen_loop(1, 0x56186255e180) kamailio | 7(14) INFO: ctl [io_listener.c:213]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) kamailio | 7(14) DEBUG: ctl [io_listener.c:245]: io_listen_loop(): io_listen_loop: adding socket 8, type 2, transport 3 (/var/run/kamailio//kamailio_ctl) kamailio | 7(14) DEBUG: ctl [../../core/io_wait.h:374]: io_watch_add(): processing io_watch_add(0x7f3fa8aa2380, 8, 2, 0x56186255e180) - fd_no=0 kamailio exited with code 139 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3125 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3125(a)github.com> [View Less]

3 9

[kamailio/kamailio] auth: Add pv_auth_check overload with second passwd parameter (PR #3126)
by Jon Bergli Heier 03 Jun '22

03 Jun '22

#### 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 - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] 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 - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  This change modifies the `pv_auth_check` function to take an optional second password argument `passwd2`. The motivation for this change is to allow authenticating against two passwords, which is useful if you want to eg. rotate passwords periodically and still allow using the previous password during a transition period. You can technically do this with two calls to `pv_auth_check`, but with `nonce_count` enabled the first call will invalidate nc which will always cause the second call to fail. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3126 -- Commit Summary -- * auth: Add pv_auth_check overload with second passwd parameter -- File Changes -- M src/modules/auth/auth_mod.c (143) M src/modules/auth/doc/auth_functions.xml (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3126.patch https://github.com/kamailio/kamailio/pull/3126.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3126 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3126(a)github.com> [View Less]

2 4

[kamailio/kamailio] tm: try next ip on receiving code other than 503 if dns failover (PR #3129)
by Mvondo Eric 03 Jun '22

03 Jun '22

#### Pre-Submission Checklist    - [ ] 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 - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] 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  By default when doing dns failover the tm module will try next ips only when receiving 503 code or no response. the new failover_reply_codes provides a way to try next ip when receiving specific codes or class code. for example try next ip even if the previous one returned 408 You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3129 -- Commit Summary -- * Enable tm dns failover to try next ip on receiving code other than 503 -- File Changes -- M src/modules/tm/doc/params.xml (25) M src/modules/tm/t_funcs.c (11) M src/modules/tm/t_reply.c (12) M src/modules/tm/t_reply.h (4) M src/modules/tm/tm.c (139) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3129.patch https://github.com/kamailio/kamailio/pull/3129.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3129 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3129(a)github.com> [View Less]

3 5

[kamailio/kamailio] ims_qos: fix compilation warning (PR #3127)
by Atanas Bakalov 02 Jun '22

02 Jun '22

You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3127 -- Commit Summary -- * ims_qos: fix compilation warning -- File Changes -- M src/modules/ims_qos/rx_aar.c (1) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3127.patch https://github.com/kamailio/kamailio/pull/3127.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3127 You are receiving this because you … [View More]

2 2

[kamailio/kamailio] DNS Failover try next destinations on receiving code other than 503 (Issue #3122)
by patrickarton 02 Jun '22

02 Jun '22

### Description All ips destination of DNS Failover are tried only if either no response or 503 response. I woud like to try others ips when receiving code other than 503 response (example when receiving 408 from a previous one).  ### Expected behavior #### Actual observed behavior #### Debugging Data ``` None ``` #### Log Messages  ``` None ``` #### SIP Traffic  ``` obvious ``` ### Possible Solutions A possible solution will be to modify the reply_received function of tm's t_reply.c file. ``` int reply_received( struct sip_msg *p_msg ) { } ```  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3122 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3122(a)github.com> [View Less]

1 1

[kamailio/kamailio] 'kamcmd ul.dump' error on 5.6 (Issue #3123)
by MayamaTakeshi 02 Jun '22

02 Jun '22

### Description If there are no usrloc registrations, all is good: ``` [root@lab002194-flip-server install]$ kamcmd ul.dump { Domains: { Domain: { Domain: devflip_location Size: 1024 AoRs: { } Stats: { Records: 0 Max-Slots: 0 } } } } ```` But … [View More]if there are registered SIP endpoints, we get: ``` [root@lab002194-flip-server install]$ kamcmd ul.dump { Domains: { Domain: { Domain: devflip_location Size: 1024 AoRs: { Info: { AoR: oweruaodsiflwosdfjoe(a)lsjfoasjdfosaodfsdfafolekodc.com HashID: -2013386516 Contacts: { Contact: { Address: sip:oweruaodsiflwosdfjoe@10.255.255.195:6060 Expires: 96 Q: 0 ERROR:: while parsing the record 14, @140: ff : bad record ``` #### Reproduction Just register some SIP endpoints against kamailio and issue 'kamcmd ul.dump' ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.6.0 (x86_64/linux) 61e86a 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: 61e86a compiled on 06:54:55 May 26 2022 with gcc 10.2.1 ``` * **Operating System**:  ``` [root@lab002194-flip-server kamailio-5.6]$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye [root@lab002194-flip-server kamailio-5.6]$ uname -a Linux lab002194-flip-server 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3123 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3123(a)github.com> [View Less]

2 4

[kamailio/kamailio] Fix Makefile.groups and SLACK for build on FreeBSD (PR #3130)
by Boris Korzun 31 May '22

31 May '22

#### 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) - [ ] 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 … [View More]

2 2

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2022