sr-dev May 2022

sr-dev@lists.kamailio.org

12 participants
285 discussions

[kamailio/kamailio] [stirshaken] add identity header in reply messages or to a separate variable (#2770)

by sergei lavrov

### Description I'm unable to add the generated `Identity` value to reply message when `kamailio` acts as a redirect server and replies with `302 Moved Temporarily` instead of relaying `INVITE`. This code doesn't work, i.e. no `Identity` header in `302 Moved Temporarily` message: ``` if (stirshaken_add_identity($var(x5u), $var(attest), $var(origtn_val), $var(desttn_val), $var(origid)) == 1) { append_branch("sip:$rU@127.0.0.1:6060"); sl_send_reply("302", "Moved Temporarily"); exit; } ``` ### Expected behavior It would be nice if the `stirshaken_add_identity_*` functions would add the generated `Identity` header to the reply messages too, or store the generated `Identity` header in a separate variable, like `$identity`, for the future processing. -- 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/2770

2 years, 4 months

[kamailio/kamailio] secfilter: Wrong format on RPC response data (Issue #2992)

by Olle E. Johansson

secfilter RPC functions to get statistics use a console format to printing data, suitable for **kamcmd** but not for any RPC method. This should be converted to a machine-parsable data structure (much like dispatcher, usrloc and htable data dumps). -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2992 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2992(a)github.com>

2 years, 4 months

[kamailio/kamailio] topos breaking update messages (Issue #3090)

by Simone de Blasiis

### Description This issue has already been reported in the past both on GitHub ( Issue #2659 ) and on the [mailing list](https://lists.kamailio.org/pipermail/sr-users/2022-April/114620.html). We are experiencing some issues with UPDATE messages being sent by the PSTN after an early media announcement. To reproduce the issue we can call a specific number that has an early media announcement, since it's a paid phone number it has to announce how much it would cost before picking up the call. In this initial part the call is being negotiated in g711a. As soon as the announcement ends, the PSTN sends an UPDATE message containing the new desired codec (g729) for the actual call. Kamailio doesn't route the UPDATE message to the destination and it instead replies with a 404 message. If topos is disabled the update message gets routed correctly. #### SIP Traffic I've attached a pcap with anonymized IPs to make it harder for bots. Here is a legend for the IPs: - 12.34.123.123 is Kamailio - 62.23.19.74 is the PSTN - 1.2.130.40 is the client making the call [errorupdate_anon.zip](https://github.com/kamailio/kamailio/files/8522365/er… ### 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 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3090 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3090(a)github.com>

2 years, 5 months

[kamailio/kamailio] topos breaks early-dialog update even on 5.6.0~rc0 (Issue #3112)

by George Diamantopoulos

### Description Topos still seems to break early-dialog UPDATEs in my configuration. This is on 5.6.0~rc0+bpo11.20220506004754.1 from 56-nightly which I believe includes c309122 and ceb688b. I haven't tested rc1 yet (there are no debs at this time) but there doesn't seem to be any topos-related commits since rc0 either. ### Troubleshooting #### SIP Traffic Attaching pcaps from a lab environment to demonstrate the problem. One with topos on (failure), one with off (success). There were no other configuration changes between these tests. ### Possible Solutions Only turning topos off seems to resolve this for me. ### Additional Information ``` version: kamailio 5.6.0-rc0 (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 sbcprov0-stage-tis0-cn1 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 GNU/Linux ``` [pcaps.tar.gz](https://github.com/kamailio/kamailio/files/8704222/pcaps.tar.… -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3112 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3112(a)github.com>

2 years, 6 months

git:master:26ef622f: dialog: Terminate dialogs in Early stage and add functionality to send messages within a dialog

by Carsten Bock

Module: kamailio Branch: master Commit: 26ef622ff3621c8a82c1c3560a32e8d735e30c4e URL: https://github.com/kamailio/kamailio/commit/26ef622ff3621c8a82c1c3560a32e8d… Author: Carsten Bock <carsten(a)ng-voice.com> Committer: Carsten Bock <carsten(a)ng-voice.com> Date: 2022-04-27T11:33:31+02:00 dialog: Terminate dialogs in Early stage and add functionality to send messages within a dialog - This change adds the capability to termiante a dialog in early stage by either sending a SIP response to the A-Party or by sending a CANCEL to the B-Party - This change adds a function to send a request in-dialog from script (e.g. send INFO to a party to provide additional information or for example UPDATE a Media-Session in early stage, when certain conditions are met --- Modified: src/modules/dialog/dialog.c Modified: src/modules/dialog/dlg_handlers.c Modified: src/modules/dialog/dlg_hash.h Modified: src/modules/dialog/dlg_req_within.c Modified: src/modules/dialog/dlg_req_within.h Modified: src/modules/dialog/doc/dialog.xml Modified: src/modules/dialog/doc/dialog_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/26ef622ff3621c8a82c1c3560a32e8d… Patch: https://github.com/kamailio/kamailio/commit/26ef622ff3621c8a82c1c3560a32e8d…

2 years, 6 months

[kamailio/kamailio] kamctl - maintenance for dbtextdb.py tool (#2469)

by Daniel-Constantin Mierla

**kamctl** include a python tool that is parsing SQL statements to do operations over the **db_text** files, for the common db operations (e.g., insert, delete). It is located at: * https://github.com/kamailio/kamailio/tree/master/utils/kamctl/dbtextdb The tool was contributed long time ago and not kept up to date, being known not to work with Python3 (e.g., #2464). This issue is created to see if someone has the interest to pick up the maintenance of this tool, if not it will be removed from kamctl. Note that db_text works with text files, so it is not necessary to have a tool for managing the content of these files, they can be simply updated with any text editor. -- 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/2469

2 years, 6 months

[kamailio/kamailio] [kamctl] Dispatcher operations in a case of db_text are mostly incorrect (#2464)

by Igor Olhovskiy

### Description On creating dispatcher with `kamctl` in the case of `db_text` it fails ### Troubleshooting #### Reproduction Point `kamctlrc` to DB_TEXT. Run `kamctl dispatcher add 1 sip:asterisk_2:5060 1 3` Run 'kamctl dispatcher add 1 sip:asterisk_2:5060 1 3 'prefix=123' 'test1'' Run 'kamctl dispatcher show' Run 'kamctl dispatcher reload' #### Debugging Data ``` # kamctl dispatcher add 1 sip:asterisk_2:5060 1 3 attrs cannot be empty or null -e \E[37;31mERROR: dispatcher - SQL Error ``` ``` # kamctl dispatcher add 1 sip:asterisk_2:5060 1 3 'prefix=123' 'test1' Traceback (most recent call last): File "/usr/lib/x86_64-linux-gnu/kamailio//kamctl/dbtextdb/dbtextdb.py", line 1243, in <module> main(sys.argv) File "/usr/lib/x86_64-linux-gnu/kamailio//kamctl/dbtextdb/dbtextdb.py", line 1230, in main dataset = conn.Execute(' '.join(argv[1:])) File "/usr/lib/x86_64-linux-gnu/kamailio//kamctl/dbtextdb/dbtextdb.py", line 423, in Execute self.WriteTempTable() File "/usr/lib/x86_64-linux-gnu/kamailio//kamctl/dbtextdb/dbtextdb.py", line 1138, in WriteTempTable self.temp_file.write(header.strip() + '\n') File "/usr/lib/python3.7/tempfile.py", line 620, in func_wrapper return func(*args, **kwargs) TypeError: a bytes-like object is required, not 'str' -e \E[37;31mERROR: dispatcher - SQL Error ``` dump is showing active dispatchers, show - is not. ``` # kamctl dispatcher dump { "jsonrpc": "2.0", "result": { "NRSETS": 1, "RECORDS": [{ "SET": { "ID": 1, "TARGETS": [{ "DEST": { "URI": "sip:asterisk_2:5060", "FLAGS": "AP", "PRIORITY": 0 } }] } }] }, "id": 124 } root@e529c8cb4f62:/# kamctl dispatcher show -e dispatcher gateways ``` No result on reload ``` # kamctl dispatcher reload { "jsonrpc": "2.0", "result": { }, "id": 160 } ``` ### Possible Solutions I've tried to add data to the table manually, but here I got another issue. But on Kamailio load, the only first dispatcher is processed. Will add another issue on this. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` /# kamailio -v version: kamailio 5.4.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_BLACKLIST, 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 8.3.0 ``` * **Operating System**: Debian 10/Docker ``` # uname -a Linux 9b7efa852274 5.3.18-lp152.36-default #1 SMP Tue Aug 18 17:09:44 UTC 2020 (885251f) 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/2464

2 years, 6 months

[kamailio/kamailio] The acc modules writes a random string into the sip_reason field for an ACK message (FAKED_REPLY) (Issue #2981)

by Frits Wiersma

### Description While upgrading to kamailio version 5.5.2 I noticed that the sip reason is not always filled in correctly. In our current setup with kamailio version 4.4 the acc module writes the INVITE, ACK end BYE messages to a postgres database. Also the missed calls are logged. With version 5.5.2 but also with version 5.5.3 the sip reason seems to contain a random 2 digits. It gets even worse when a call is missed and kamailio generates a 408 timeout. Then a random string of 15 characters is written to the database. Sometimes this results in a fatal error because the postgres driver can't escape the string. ### Troubleshooting The relevant part in de code is in the function env_set_code_status in file acc_logic.c if (reply==FAKED_REPLY || reply==NULL) { /* code */ acc_env.code_s.s = int2bstr((unsigned long)code, code_buf, &acc_env.code_s.len); /* reason */ if (acc_env.reason.len == 0) { /* already extracted in case of locally generated replies */ acc_env.reason.s = error_text(code); acc_env.reason.len = strlen(acc_env.reason.s); } The sip reason is only filled in when the len is 0, but once the length is set it looks like it's not being reset to 0 again somewhere. I can fix the problem by removing the if statement, but that is probably not the intention of the programmer. #### Reproduction The wrong reason in the ACK can probably be reproduces with any call, but in my test setup an Asterisk system answers the call. After the "OK" an ACK is received which is seen as a FAKED_REPLY. The reason.len however is still 2 and the reason is not set. The new function "env_set_reason" is not being called in this case. The issue with the 408 can be reproduced by calling an endpoint and let kamailio timeout. This has to be done twice to reproduce the error. This time kamailio wants to write the missed INVITE to the database with a random string of 15 characters for the sip reason. To me it looks like the length of 15 comes from the length of the "Request Timeout" string but the pointer reason.s point to a memory part of a previous transaction which is already gone ? #### Debugging Data #### Log Messages #### SIP Traffic ### Possible Solutions ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.2 (x86_64/linux) 55e232 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: 55e232 compiled on 15:45:52 Dec 9 2021 with gcc 8.3.0 ``` * **Operating System**: ``` Linux 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2981 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2981(a)github.com>

2 years, 6 months

[kamailio/kamailio] Database TLS connection through cnf file: TLS error followed by memory corruption messages (Issue #3115)

by liviu-rolo

### 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>

2 years, 6 months

[kamailio/kamailio] Kamailio 5.5.4 siputils doesn't validate long Austrian numbers as valid e164 (Issue #3117)

by Simone de Blasiis

### 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: 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**: ``` No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Linux kamailio-primary 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/3117 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3117(a)github.com>

2 years, 6 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2022