sr-dev August 2022

sr-dev@lists.kamailio.org

16 participants
204 discussions

[kamailio/kamailio] Regression on app_lua after ASLR enable (Issue #3202)

by Boris Korzun

### Description There's a regression after enabling Address Space Layout Randomization (ASLR). Kamailio causes SIGSEGV while loading `app_lua` (or other KEMI Interpreters probably). ### Troubleshooting #### Reproduction The regression has appeared after update FreeBSD kernel to https://github.com/freebsd/freebsd-src/commit/10192e77cfacd1f27601882af6188… Kamailio falls after `loadmodule "app_lua.so"` in `kamailio.cfg`. #### Debugging Data ``` root@server:/usr/jails/containers/kamailio/var/coredump/986# jexec kamailio lldb -c /var/coredump/986/kamailio.13521.core -- /usr/local/sbin/kamailio (lldb) target create "/usr/local/sbin/kamailio" --core "/var/coredump/986/kamailio.13521.core" Core file '/var/coredump/986/kamailio.13521.core' (x86_64) was loaded. (lldb) bt all * thread #1, name = 'kamailio', stop reason = signal SIGSEGV * frame #0: 0x0000000825b61350 libc.so.7`strncmp(s1=<unavailable>, s2=<unavailable>, n=<unavailable>) at strncmp.c:47:7 frame #1: 0x00000000003fc394 kamailio`sr_kemi_modules_add(klist=0x0000000861afb410) at kemi.c:3392:8 frame #2: 0x0000000861ae6154 app_lua.so`mod_register(path="/usr/local/lib/kamailio/modules/app_lua.so", dlflags=0x0000000821805b48, p1=0x0000000000000000, p2=0x0000000000000000) at app_lua_mod.c:605:2 frame #3: 0x00000000005e4b30 kamailio`load_module(mod_path="app_lua.so") at sr_module.c:592:7 frame #4: 0x0000000000885936 kamailio`yyparse at cfg.y:1965:8 frame #5: 0x00000000002ff384 kamailio`main(argc=7, argv=0x000000082180a848) at main.c:2506:6 frame #6: 0x00000000002ddd90 kamailio`_start(ap=<unavailable>, cleanup=<unavailable>) at crt1_c.c:75:7 ``` `_sr_kemi_modules[].mname.s` for `app_lua` points to incorrect data after second call `mod_register()(a)app_lua_mod.c` from `load_module()(a)sr_module.c` (reloading the module for setting correct `dlflags`). #### Log Messages ``` 08:35:53.689647 DEBUG: <core> [core/cfg.y:1964]: yyparse(): loading module kemix.so 08:35:53.689684 DEBUG: <core> [core/sr_module.c:516]: ksr_locate_module(): found module to load </usr/local/lib/kamailio/modules/kemix.so> 08:35:53.689698 DEBUG: <core> [core/sr_module.c:566]: load_module(): trying to load </usr/local/lib/kamailio/modules/kemix.so> 08:35:53.689796 DEBUG: <core> [core/kemi.c:3398]: sr_kemi_modules_add(): adding module: kx 08:35:53.689847 DEBUG: <core> [core/cfg.lex:2039]: pp_define(): defining id: MOD_kemix 08:35:53.689895 DEBUG: <core> [core/cfg.y:1964]: yyparse(): loading module app_lua.so 08:35:53.689931 DEBUG: <core> [core/sr_module.c:516]: ksr_locate_module(): found module to load </usr/local/lib/kamailio/modules/app_lua.so> 08:35:53.689948 DEBUG: <core> [core/sr_module.c:566]: load_module(): trying to load </usr/local/lib/kamailio/modules/app_lua.so> 08:35:53.690418 DEBUG: <core> [core/kemi.c:3494]: sr_kemi_eng_register(): registered config routing enginge [lua] 08:35:53.690444 DEBUG: <core> [core/kemi.c:3398]: sr_kemi_modules_add(): adding module: app_lua ``` ### Possible Solutions Temporary solution is disabling ASLR, ex. FreeBSD: ``` # sysctl kern.elf64.aslr.enable=0 # sysctl kern.elf64.aslr.pie_enable=0 ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.6.1 (x86_64/freebsd) b36a13 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_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, select, kqueue. id: b36a13 compiled on 08:12:34 Jul 27 2022 with cc FreeBSD clang version 14.0.5 (https://github.com/llvm/llvm-project.git llvmorg-14.0.5-0-gc12386ae247c) ``` 5.5.4 is affected too * **Operating System**: ``` FreeBSD 13/stable ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3202 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3202(a)github.com>

8 months, 1 week

[kamailio/kamailio] RPC command dlg.profile_get_size with per_value response (Issue #2976)

by dvillaume

Hello, I would like to suggest you an implementation of the rpc command dlg.profile_get_size (on a valued profile) that would return a list of values and the number of current dialogs for any of them . This could be usefull if you want to get stats per customer_id/trunks/ips or whatever and don't want to get the whole table but only the size. Regards, David -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2976 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2976(a)github.com>

8 months, 3 weeks

[kamailio/kamailio] Socket name ignored when sending to HEP server (Issue #3174)

by manticode

When **trace_mode** is set to 1, then **send_sock_name** is not used (it uses the unexpected socket listen socket). However, when **trace_mode** is set to 4, then **send_sock_name** works correctly. Also, in both cases, **send_sock_addr** works correctly. ``` listen=udp:SIP_IPADDRESS:SIP_PORT listen=udp:SIPCAPTURE_IPADDRESS:SIP_PORT name "siptrace_socket" modparam("siptrace", "duplicate_uri", "sip:10.218.31.205:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "hep_version", 3) modparam("siptrace", "hep_capture_id", 110) modparam("siptrace", "send_sock_name", "siptrace_socket") modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_mode", 1) modparam("siptrace", "trace_to_database", 0) ``` This is tested on Kamailio 5.5.1 and 5.5.3. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3174 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3174(a)github.com>

8 months, 3 weeks

[kamailio/kamailio] Segfault in Kamailio 5.6.0 (Issue #3134)

by David Cunningham

We have installed Kamailio 5.6.0 from http://deb.kamailio.org/kamailio56, but it is intermittently crashing with a segfault like this: May 29 04:46:53 ss2 kernel: [26920.901572] kamailio[1416]: segfault at 43a ip 00007f78d1396ab5 sp 00007ffd2487ca10 error 4 in app_perl.so[7f78d1392000+21000] May 29 04:46:53 ss2 kernel: [26920.901575] Code: 8b 05 8f 34 02 00 48 8b 00 48 89 c7 e8 7b ff ff ff e8 3f e5 ff ff 48 8b 15 78 34 02 00 48 89 02 48 8b 05 6e 34 02 00 48 8b 00 <0f> b6 90 3a 04 00 00 48 8b 05 5d 34 02 00 48 8b 00 83 ca 02 88 90 May 29 04:46:56 ss2 kernel: [26923.737834] kamailio[1409]: segfault at 43a ip 00007f78d1396ab5 sp 00007ffd2487ca10 error 4 in app_perl.so[7f78d1392000+21000] May 29 04:46:56 ss2 kernel: [26923.737838] Code: 8b 05 8f 34 02 00 48 8b 00 48 89 c7 e8 7b ff ff ff e8 3f e5 ff ff 48 8b 15 78 34 02 00 48 89 02 48 8b 05 6e 34 02 00 48 8b 00 <0f> b6 90 3a 04 00 00 48 8b 05 5d 34 02 00 48 8b 00 83 ca 02 88 90 Perl is version 5.30.0, and the system is running Ubuntu 20.04. A Perl library is loaded using: modparam( "app_perl", "filename", "/path/to/our/Kamailio.pm" ) We have not found a core file anywhere on the server. Please let us know what other information you need, thanks. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3134 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3134(a)github.com>

8 months, 3 weeks

Info: Kamailio World Conference Online 2022 - The Schedule

by Daniel-Constantin Mierla

The schedule for Kamailio World Conference Online 2022 has been published on the event website: - https://www.kamailioworld.com The event spans over two days, September 7-8, 2022, with presentations and open discussion sessions during 12:50-17:00UTC. With the main target to share the knowledge and connect the community, the conference has presentations covering use of Kamailio for 5G services, NAT traversal and integration with RTPEngine, TLS with WolfSSL, end to end testing testing, controlling SIP message content from KEMI and resources management for scalability. It is a good balance between established and new speakers at this edition of Kamailio World Conference. There is no registration required to join the event, the sessions will be presented in a live video conferencing room streamed to YouTube KamailioWorld Channel. A text chat room will be made available for posting questions and background discussions. Book the dates in your agenda and prepare for another amazing Kamailio World Conference! Keep the eye on the event website for updates! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

8 months, 4 weeks

[kamailio/kamailio] [presence] `active_watchers` entries not removed on timeout or expiration. (Issue #3074)

by Mike Moore

### Description  When handling a `PUBLISH` we call [handle_publish()](https://kamailio.org/docs/modules/5.5.x/modules/presence.… and `NOTIFY`s are sent to all of the corresponding `active_watchers` (as expected). However, when `NOTIFY`s timeout (`408`), we're seeing that the corresponding entries in the `active_watchers` table are _not_ being deleted as expected. Furthermore, we've noticed that `NOTIFY`s are being sent to `active_watchers` which are expired (i.e. `expires < UNIX_TIMESTAMP()`) and when we run `kamcmd presence.cleanup`, no expired entries are removed from the `active_watchers` table. We suspect that all of these things might be related--the common theme being that records aren't deleted when expected. ### Troubleshooting #### Reproduction  In our setup, we're using Kamailio as a "presence server" (via the [presence](https://kamailio.org/docs/modules/5.5.x/modules/presence.html), [presence_dialoginfo](https://kamailio.org/docs/modules/5.5.x/modules/presen…, and [presence_xml](https://kamailio.org/docs/modules/5.5.x/modules/presence_xml.… modules). We're using [`subs_db_mode`](https://kamailio.org/docs/modules/5.5.x/modules/presence.html#presence.p.subs_db_mode) `3` (DB-only scheme) and we have multiple Kamailio instances connected to a shared database (MySQL `8.0.27`). Everything seems to be working as expected. However, as we accumulated stale entries in the `active_watchers` table we're finding that we're wasting more and more time on sending `NOTIFY`s to black holes. We're generating a _lot_ of traffic and waiting for the timeouts to hit is causing memory issues and backups. Here are the relevant portions of our `kamailio.cfg` file: ``` # ----- presence params ----- modparam("presence", "db_table_lock_type", 0) # Disable locking; MySQL has issues with this is enabled. modparam("presence", "db_update_period", -1) # Disable synchronization. modparam("presence", "db_url", PRESENCE_DB_URL) modparam("presence", "expires_offset", 60) # Force the client to send an UPDATE before the old PUBLISH expires. modparam("presence", "max_expires", 1800) modparam("presence", "min_expires", 1700) modparam("presence", "publ_cache", 0) # Disable the PUBLISH cache since the database is shared. modparam("presence", "server_address", "sip:$CLUSTER_DOMAIN_NAME:5060") # This becomes the value of the Contact header. modparam("presence", "sip_uri_match", 1) # Use case insensitive URI matching. modparam("presence", "subs_db_mode", 3) # Database-only scheme; everything is stored in the database. modparam("presence", "notifier_processes", 0) # Caution! Under load a race condition can cause CSeq's to be reused. modparam("presence", "timeout_rm_subs", 1) # ----- presence_dialoginfo params ----- modparam("presence_dialoginfo", "force_single_dialog", 1) # Maybe not all phones support multiple "dialog" elements? modparam("presence_dialoginfo", "force_dummy_dialog", 1) # Maybe not all phones support a null body? # ----- presence_xml params ----- modparam("presence_xml", "db_url", PRESENCE_DB_URL) modparam("presence_xml", "force_active", 1) # Skip permission/XCAP checks. modparam("presence_xml", "force_dummy_presence", 1) # Default to a simple "open" status when presentity info is unavailable. # ... route[PRESENCE] { if (!is_method("PUBLISH|SUBSCRIBE")) { return; } if (!t_newtran()) { sl_reply_error(); exit; } if (is_method("PUBLISH")) { handle_publish(); t_release(); } else if (is_method("SUBSCRIBE")) { handle_subscribe(); t_release(); } exit; } ``` #### SIP Traffic  Here's a somewhat sanitized example (the message seems OK to us; however, the `Subscription-State: terminated; reason=timeout` does make us wonder--do we as the sender _know_ that the client is terminated/timed-out?): ``` 2022/04/05 21:09:55.209846 10.21.3.12:5060 -> 10.31.0.226:6060 NOTIFY sip:SomeUser@192.168.86.24:54639;alias=123.21.125.232~54639~1 SIP/2.0 Via: SIP/2.0/UDP presence-w.staging.internal:5060;branch=z9hG4bK43ea.648a1952000000000000000000000000.0 To: <sip:SomeOtherUser@9bfadf66-a77b-6a69-25f3-02d96d4aa946>;tag=2607596073 From: <sip:SomeUser@9bfadf66-a77b-6a69-25f3-02d96d4aa946>;tag=69309ea83adcd977af8788878e9f31b3-42e32342 CSeq: 66 NOTIFY Call-ID: 0_2607659559(a)192.168.86.24 Route: <sip:10.31.0.226:6060;r2=on;lr;ftag=2607596073>, <sip:55.8.122.110;r2=on;lr;ftag=2607596073> Content-Length: 710 Max-Forwards: 70 Event: dialog Contact: <sip:presence-w.staging.internal:5060> Subscription-State: terminated;reason=timeout Content-Type: application/dialog-info+xml <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="66" state="full" entity="sip:SomeUser@9bfadf66-a77b-6a69-25f3-02d96d4aa946"> <dialog id="0_1364146118(a)192.168.1.244" call-id="0_1364146118(a)192.168.1.244" direction="initiator"> <state>confirmed</state> <remote> <identity>sip:4355558565@9bfadf66-a77b-6a69-25f3-02d96d4aa945:5060</identity> <target uri="sip:4355558565@9bfadf66-a77b-6a69-25f3-02d96d4aa946:5060"/> </remote> <local> <identity>sip:SomeUser@9bfadf66-a77b-6a69-25f3-02d96d4aa946:5060</identity> <target uri="sip:SomeUser@123.130.50.202:58872"/> </local> </dialog> </dialog-info> ``` ### Possible Solutions  We didn't see any functions in the `presence` module that we could call directly to clean things up. One thought we had was to manually run some database commands from `event_route[presence:notify-reply]` (or in a `reply_route`). We've noticed that once the problematic entries are manually removed from the database that we no longer attempt to send `NOTIFY`s to the defunct destinations. ### 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**:  ``` $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye $ uname -a Linux ip-10-21-3-12 5.10.0-13-cloud-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/3074 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3074(a)github.com>

9 months

[kamailio/kamailio] 5.5.1 crash processing INVITE and CANCEL at almost the same time (Issue #3156)

by Victor Seva

### Description While a INVITE is been processed the CANCEL of that transaction is been processed in other process almost at the same time ### Troubleshooting #### Reproduction Quite difficult to reproduce I would say #### Debugging Data ``` Reading symbols from /usr/sbin/kamailio... Reading symbols from /usr/lib/debug/.build-id/e3/9bd8ad0900c980149b00579cce26035c9cb118.debug... warning: Can't open file /dev/zero (deleted) during file-backed mapping note processing [New LWP 4136750] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio -P /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/k'. Program terminated with signal SIGSEGV, Segmentation fault. #0 atomic_dec_and_test_int (var=0x20) at ../../core/parser/../mem/../atomic/atomic_x86.h:222 222 ../../core/parser/../mem/../atomic/atomic_x86.h: No such file or directory. (gdb) backtrace #0 atomic_dec_and_test_int (var=0x20) at ../../core/parser/../mem/../atomic/atomic_x86.h:222 0000001 t_unref (p_msg=<optimized out>) at t_lookup.c:1514 #2 0x000055eee962d69b in exec_post_script_cb (msg=msg@entry=0x7f7e265822c8, type=type@entry=REQUEST_CB_TYPE) at core/script_cb.c:182 0000003 0x000055eee95dfcbe in receive_msg ( buf=buf@entry=0x55eee9a00740 <buf> "INVITE sip:...@fake.dom:5060;transport=udp SIP/2.0\r\nRecord- Route: <sip:X.X.X.X;r2=on;lr=on;ftag=1E7F0816-6299BCF10003883E-7FFFF700;ngcplb=yes;socket=udp:Y.Y.Y.Y:5060>\r \nRe"..., len=<optimized out>, rcv_info=rcv_info@entry=0x7ffc96d12af0) at core/receive.c:520 #4 0x000055eee96d4c40 in udp_rcv_loop () at core/udp_server.c:543 #5 0x000055eee94db634 in main_loop () at main.c:1730 #6 0x000055eee94d2d2c in main (argc=<optimized out>, argv=<optimized out>) at main.c:3053 ``` #### Log Messages Notice that both messages came in the same second ( IPs and numbers have been changed ) ``` Jun 3 09:49:05 sipwise2-prx03a proxy[4136750]: NOTICE: DEFAULT_ROUTE <script>: New request on proxy - M=INVITE R=«sip:+49......@X.X.X.X :5060;transport=udp» F=«sip:+49...@fake.dom» T=«sip:+49...@Y.Y.Y.Z» IP=«Y.Y.Y.Z»:«5060» («Y.Y.Y.Y»:«5060») ID=«31668-TN-030322e6-0904f8ba1(a)fake.xn--dom_b2b-1-era UA='Cirpack/v4.88 (gw_sip)' DESTIP=«Y.Y.Y.G»:«5062» ``` ``` Jun 3 09:49:05 sipwise2-prx03a proxy[4136755]: NOTICE: DEFAULT_ROUTE <script>: New request on proxy - M=CANCEL R=«sip:+49...@X.X.X.X :5060;transport=udp» F=«sip:+49...@fake.dom» T=«sip:+49...@Y.Y.Y.Z» IP=«Y.Y.Y.Y»:«5060» («Y.Y.Y.Y»:«5060 ») ID=«31668-TN-030322e6-0904f8ba1(a)fake.xn--dom_b2b-1-era UA='<null>' DESTIP=«Z.Z.Z.Z»:«5062» Jun 3 09:49:05 sipwise2-prx03a proxy[4136755]: NOTICE: DEFAULT_ROUTE <script>: Sending reply S=100 Trying M=CANCEL fs='«Z.Z.Z.Z»:«5062»' du ='«Y.Y.Y.Y»:«5060»' - R=«sip:+49...@X.X.X.X:5060;transport=udp» ID=«31668-TN-030322e6-0904f8ba1(a)fake.xn--dom_b2b-1-era UA='<n ull>' ``` ### Additional Information This is the Sipwise flavor 5.5.1-1+0~mr9.5.3.2 -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3156 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3156(a)github.com>

9 months

[kamailio/kamailio] [presence] [dialog events] BLF problem: "early" state persisting after "terminated" (Issue #3192)

by liviu-rolo

### Description Relevant modules and parameters in configuration: ``` loadmodule "presence.so" loadmodule "dialog.so" loadmodule "presence_xml.so" loadmodule "pua.so" loadmodule "presence_dialoginfo.so" loadmodule "pua_dialoginfo.so" modparam("dialog", "db_mode", 1) modparam("presence", "subs_db_mode", 2) modparam("presence", "db_table_lock_type", 0) modparam("pua", "db_mode", 2) modparam("pua", "db_table_lock_write", 0) ``` Using 2 UDP receiver processes. User1 is watching (has` SUBSCRIBE`d to) User2, which is called by User3 (call1). User2 doesn't answer, phone is ringing. User1 now also calls User2 (call2), but we don't support receiving a second call so, for this `INVITE`, after 183, almost immediately, a 486 "Busy Here" message is sent and the call is cancelled (call2 finished). The 183 reply generates an "**early**" state on the UDP1 process, while 486 goes to "**terminated**" on the UDP2 process. The `PUBLISH` messages are processed almost concomitantly. The problem is that "**early**" state arrives to the subscriber (User1) after the "**terminated**" one (seen with `sngrep`) so the phone button keeps blinking for a while (... and the state cannot be changed by other call while the "**early**" event is still in the `presentity` table of the database). I suspect a concurrency problem since I didn't reproduce it with only one UDP receiver process. Even if the "**terminated**" lifetime is much smaller (11s vs minutes), I strongly believe it is still there when the "**early**" state is written. Does the "**early**" event checks the database/memory for a "**terminated**" event for the same call ID? Is it because of the missing locks maybe (`db_table_lock_type`, `db_table_lock_write`) ? ### Troubleshooting #### Reproduction Using 2 UDP receiver processes. User1 is watching (has `SUBSCRIBE`d to) User2, which is called by User3 (call1). User2 doesn't answer, phone is ringing. User1 now also calls User2 (call2), but we don't support receiving a second call so, for this `INVITE`, after 183, almost immediately, a 486 "Busy Here" message is sent and the call is cancelled (call2 finished). I would not say that it is systematic, but easy enough to reproduce. #### Debugging Data  #### Log Messages  #### 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: , EXTRA_DEBUGUSE_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 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**: Docker image around ``` $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3192 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3192(a)github.com>

9 months

[kamailio/kamailio] Function sql_xquery returns 1 for empty query result. (Issue #3163)

by admin-toneca

### Description Function sql_xquery returns 1 for empty query result. #### Reproduction Table sbc_uacreg is empty modparam("sqlops", "sqlcon", "con=>mysql://kamailio:pass@172.31.1.237/fs") if (sql_xquery("con", "SELECT * FROM sbc_uacreg WHERE l_uuid = '$hdr(X-Gateway)'", "ra") == 1) { xlog("(PSTN) SELECT * FROM sbc_uacreg WHERE l_uuid = '$hdr(X-Gateway)' =============================================================================\n"); $var(register) = "1"; } #### Log Messages ``` Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_query.c:72]: db_do_submit_query(): submitted query: SELECT * FROM sbc_uacreg WHERE l_uuid = 'GwProdIpAuth', result 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:119]: db_new_result(): allocate 56 bytes for result set at 0x7fa7c2c91170 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:67]: db_mysql_get_columns(): 16 columns returned from the query Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:156]: db_allocate_columns(): allocate 128 bytes for result names at 0x7fa7c2c91288 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:167]: db_allocate_columns(): allocate 64 bytes for result types at 0x7fa7c2c91370 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7fa7c2c91418 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c91418)[0]=[id] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:105]: db_mysql_get_columns(): use DB1_INT result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[1] at 0x7fa7c2c91490 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c91490)[1]=[l_uuid] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[2] at 0x7fa7c2c91508 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c91508)[2]=[l_username] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[3] at 0x7fa7c2c91580 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c91580)[3]=[l_domain] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[4] at 0x7fa7c2c915f8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c915f8)[4]=[r_username] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[5] at 0x7fa7c2c91670 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c91670)[5]=[r_domain] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[6] at 0x7fa7c2c916e8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c916e8)[6]=[realm] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[7] at 0x7fa7c2c91760 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c91760)[7]=[auth_username] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[8] at 0x7fa7c2c917d8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c917d8)[8]=[auth_password] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[9] at 0x7fa7c2c91850 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2c91850)[9]=[auth_ha1] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[10] at 0x7fa7c2cbe3c8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2cbe3c8)[10]=[auth_proxy] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[11] at 0x7fa7c2cbe440 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2cbe440)[11]=[expires] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:105]: db_mysql_get_columns(): use DB1_INT result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[12] at 0x7fa7c2cbe4b8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2cbe4b8)[12]=[flags] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:105]: db_mysql_get_columns(): use DB1_INT result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[13] at 0x7fa7c2cbe530 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2cbe530)[13]=[reg_delay] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:105]: db_mysql_get_columns(): use DB1_INT result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[14] at 0x7fa7c2cbe5a8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2cbe5a8)[14]=[contact_addr] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:84]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[15] at 0x7fa7c2cbe620 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:91]: db_mysql_get_columns(): RES_NAMES(0x7fa7c2cbe620)[15]=[socket] Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:148]: db_mysql_get_columns(): use DB1_STRING result type Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} db_mysql [km_res.c:181]: db_mysql_convert_rows(): no rows returned from the query Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} sqlops [sql_api.c:494]: sql_exec_xquery(): no result after query Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:79]: db_free_columns(): freeing 16 columns Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[0] at 0x7fa7c2c91418 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[1] at 0x7fa7c2c91490 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[2] at 0x7fa7c2c91508 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[3] at 0x7fa7c2c91580 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[4] at 0x7fa7c2c915f8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[5] at 0x7fa7c2c91670 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[6] at 0x7fa7c2c916e8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[7] at 0x7fa7c2c91760 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[8] at 0x7fa7c2c917d8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[9] at 0x7fa7c2c91850 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[10] at 0x7fa7c2cbe3c8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[11] at 0x7fa7c2cbe440 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[12] at 0x7fa7c2cbe4b8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[13] at 0x7fa7c2cbe530 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[14] at 0x7fa7c2cbe5a8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[15] at 0x7fa7c2cbe620 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:96]: db_free_columns(): freeing result names at 0x7fa7c2c91288 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:101]: db_free_columns(): freeing result types at 0x7fa7c2c91370 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [db_res.c:138]: db_free_result(): freeing result set at 0x7fa7c2c91170 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: exec: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} *** cfgtrace:dbg_cfg_trace(): request_route=[PSTN] c=[/usr/local/etc/kamailio/kamailio.cfg] l=1155 a=25 n=xlog Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Via] type 1 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Max-Forwards] type 8 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [From] type 4 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [To] type 3 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Call-ID] type 6 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [CSeq] type 5 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Contact] type 7 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [User-Agent] type 28 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Allow] type 21 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Supported] type 17 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Allow-Events] type 39 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Content-Type] type 11 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Content-Disposition] type 30 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Content-Length] type 12 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: DEBUG: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [X-Gateway] type 0 Jun 24 17:14:52 ip-172-31-3-158 /usr/local/sbin/kamailio[49325]: ERROR: {1 53491654 INVITE 00a98cb1-6e84-123b-fca2-069c0e3bf50e} <script>: (PSTN) SELECT * FROM sbc_uacreg WHERE l_uuid = 'GwProdIpAuth' ============================================================================= ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.7.0-dev0 (x86_64/linux) 0d9380 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: 0d9380 compiled on 14:06:32 May 26 2022 with gcc 11.2.0 ``` * **Operating System**:  ``` Distributor ID: Ubuntu Description: Ubuntu 22.04 LTS Release: 22.04 Codename: jammy Linux ip-172-31-3-158 5.15.0-1011-aws #14-Ubuntu SMP Wed Jun 1 20:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3163 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3163(a)github.com>

9 months

The SIP TLS/ALPN identifier is now registred

by Olle E. Johansson

I’ve finally got confirmation that the SIP ALPN identifier is registered. https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype… For Kamailio, this could assist when we multiplex multiple protocols on the same port, like we do for HTTPs and SIP/TLS many times. ALPN Is part of the TLS handshake, indicating what protocol comes after TLS is done. For it to help, both phones and servers needs to support it. I do think it would be helpful. Cheers, /O

9 months

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev August 2022