sr-users

sr-users@lists.kamailio.org

47 participants
37554 discussions

set empty custom global variable
by Sergey Safarov 14 Jun '21

14 Jun '21

In Kamailio config I use empty global string variable local.trace_troubleshooting_net = "" descr "trace all SIP messages from given network" When I check variable value I get blank string kamcmd cfg.get local trace_troubleshooting_net I can set new value [root@host]# kamcmd cfg.sets local trace_troubleshooting_net "2600::/48" [root@host]# kamcmd cfg.get local trace_troubleshooting_net 2600::/48 Now I want to set the empty custom global variable using a command kamcmd cfg.sets group trace_troubleshooting_net "" But get error error: 400 - error at parameter 2: expected string type but record doesn't match type How to properly set empty values?

3 4

Kamailio 5.5.0 | CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 26
by Laurent Schweizer 11 Jun '21

11 Jun '21

Dear all, I setup a Kamailio 5.5.0 (from GIT) on a ubuntu Ubuntu 18.04.5 LTS and I have some error with the libssl/ libmysql, seems not happening every time. Regarding the config file, it's a config running correctly on a Kamailio 5.3.x on a centos 7 I have attached the returned error and the result of the core file. Any idea ? BR Laurent version: kamailio 5.5.0 (x86_64/linux) 66370c 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: 66370c compiled on 07:23:15 Jun 11 2021 with gcc 7.5.0 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: loading modules under config path: /usr/local/lib64/kamailio/modules/ Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Listening on Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: 80.132.9.112:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Aliases: Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: zrh02-srv03:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: *: sipbkp.demo.ch:* Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: WARNING: tls [tls_init.c:793]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 13107200 and 6553600 bytes Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: NOTICE: tls [tls_domain.c:1136]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='<default>' ... Jun 11 21:35:46 zrh02-srv03 kernel: [304361.950608] traps: kamailio[7147] general protection ip:7f5d209a344b sp:7ffe6ae5adb8 error:0 in libcrypto.so.1.1[7f5d207b5000+29b000] Jun 11 21:35:46 zrh02-srv03 systemd[1]: Started Kamailio SIP Server. Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7161]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 26 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: <core> [main.c:788]: handle_sigs(): child process 7147 exited by a signal 11 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: <core> [main.c:791]: handle_sigs(): core was generated Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Main process exited, code=exited, status=1/FAILURE Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Failed with result 'exit-code'. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/kamailio...done. [New LWP 7147] [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/local/sbin/kamailio -m 5000 -M 128 -P /run/kamailio/kamailio.pid -f /confi'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (gdb) bt #0 0x00007f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #1 0x00007f5d209a3a5b in X509_STORE_CTX_get_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #2 0x00007f5d209a418d in X509_STORE_CTX_get1_issuer () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #3 0x00007f5d209a9207 in ?? () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #4 0x00007f5d209a9f96 in X509_verify_cert () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #5 0x00007f5d20caf337 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #6 0x00007f5d20cd037b in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #7 0x00007f5d20cd2995 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #8 0x00007f5d20ccc48c in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #9 0x00007f5d20cb84e4 in SSL_do_handshake () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #10 0x00007f5d215cbdb1 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #11 0x00007f5d2159f4de in mysql_real_connect () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #12 0x00007f5d21b410b1 in db_mysql_new_connection (id=0x7f5d21ee2b30) at km_my_con.c:157 #13 0x00007f5d211456dc in db_do_init2 (url=0x7f5d1e9dd4e0 <ul_db_url>, new_connection=0x7f5d21b3f6a4 <db_mysql_new_connection>, pooling=DB_POOLING_PERMITTED) at db.c:317 #14 0x00007f5d211443f9 in db_do_init (url=0x7f5d1e9dd4e0 <ul_db_url>, new_connection=0x7f5d21b3f6a4 <db_mysql_new_connection>) at db.c:270 #15 0x00007f5d21b3459e in db_mysql_init (_url=0x7f5d1e9dd4e0 <ul_db_url>) at km_dbase.c:202 #16 0x00007f5d1e7a1987 in child_init (_rank=-1) at usrloc_mod.c:471 #17 0x000055ddd6c45602 in init_mod_child (m=0x7f5d21e03818, rank=-1) at core/sr_module.c:864 #18 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e03bb8, rank=-1) at core/sr_module.c:860 #19 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e04498, rank=-1) at core/sr_module.c:860 #20 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e056a8, rank=-1) at core/sr_module.c:860 #21 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e06390, rank=-1) at core/sr_module.c:860 #22 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e06b38, rank=-1) at core/sr_module.c:860 #23 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e06fb8, rank=-1) at core/sr_module.c:860 #24 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e075f0, rank=-1) at core/sr_module.c:860 #25 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e090c0, rank=-1) at core/sr_module.c:860 #26 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e09500, rank=-1) at core/sr_module.c:860 #27 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0a400, rank=-1) at core/sr_module.c:860 #28 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0aa70, rank=-1) at core/sr_module.c:860 #29 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0b0b0, rank=-1) at core/sr_module.c:860 #30 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0b5d8, rank=-1) at core/sr_module.c:860 #31 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0bdd0, rank=-1) at core/sr_module.c:860 #32 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0c968, rank=-1) at core/sr_module.c:860 #33 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0f7f8, rank=-1) at core/sr_module.c:860 #34 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e105d8, rank=-1) at core/sr_module.c:860 #35 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e109b0, rank=-1) at core/sr_module.c:860 #36 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e10ea0, rank=-1) at core/sr_module.c:860 #37 0x000055ddd6c45ef9 in init_child (rank=-1) at core/sr_module.c:909 #38 0x000055ddd6b9eebe in fork_process (child_id=-1, desc=0x55ddd6ee7847 "slow timer", make_sock=1) at core/pt.c:337 #39 0x000055ddd6abaa62 in main_loop () at main.c:1814 #40 0x000055ddd6ac6095 in main (argc=9, argv=0x7ffe6ae5d298) at main.c:3053

1 0

Kamailio SBC+ Freeswitch as media server
by John Tuxies 09 Jun '21

09 Jun '21

in a Debian system i am running Kamailio 5.5 installed from repo and with the basic setup i have 2 users 101 & 102 to be able to call each other. So far so good. i added Freeswitch in the same system and tried to follow this guide http://kb.asipto.com/freeswitch:kamailio-3.1.x-freeswitch-1.0.6d-sbc even though it is old and there are many changes. Freeswitch is installed from deb repo as well. after following the guide i tried to adapt to newer versions of kamailio and freeswitch, but i am getting errors. The problem is that the users now are able to register to Kamailio, but unable to call each other. I can see users being registered in Kamailio: *root@kamfs: ~ $ kamctl online101102root@kamfs: ~ $* while when 101 calls 102 i am getting: *2021-06-08 10:35:19.015670 [NOTICE] switch_channel.c:1118 New Channel sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> [f3b8f5a0-652a-4640-b2d3-9b7cc21d7f91]2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_NEW (Cur 1 Tot 5)2021-06-08 10:35:19.015670 [INFO] sofia.c:10362 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> receiving invite from 192.168.1.15:5060 <http://192.168.1.15:5060> version: 1.10.6 -release-18-1ff9d0a60e 64bit call-id: ZDFiZWFkZmVmYjgxZDEwOTgyYTYxZjkxNzkwMzlmYmQ.2021-06-08 10:35:19.015670 [DEBUG] sofia.c:10456 verifying acl "domains" for ip/port 192.168.1.15:0 <http://192.168.1.15:0>.2021-06-08 10:35:19.015670 [WARNING] sofia.c:10569 IP 192.168.1.15 Rejected by acl "domains"2021-06-08 10:35:19.015670 [NOTICE] sofia.c:2445 Hangup sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> [CS_NEW] [CALL_REJECTED]2021-06-08 10:35:19.015670 [DEBUG] sofia.c:1549 Channel is already hungup.2021-06-08 10:35:19.015670 [DEBUG] sofia.c:1549 Channel is already hungup.2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:604 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State NEW2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_HANGUP (Cur 1 Tot 5)2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:848 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Callstate Change DOWN -> HANGUP2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:850 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State HANGUP2021-06-08 10:35:19.015670 [DEBUG] mod_sofia.c:453 Channel sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> hanging up, cause: CALL_REJECTED2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:60 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> Standard HANGUP, cause: CALL_REJECTED2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:850 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State HANGUP going to sleep2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:620 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State Change CS_HANGUP -> CS_REPORTING2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_REPORTING (Cur 1 Tot 5)2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:936 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State REPORTING2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:174 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> Standard REPORTING, cause: CALL_REJECTED2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:936 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State REPORTING going to sleep2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:611 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State Change CS_REPORTING -> CS_DESTROY2021-06-08 10:35:19.015670 [DEBUG] switch_core_session.c:1736 Session 5 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Locked, Waiting on external entities2021-06-08 10:35:19.015670 [NOTICE] switch_core_session.c:1754 Session 5 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Ended2021-06-08 10:35:19.015670 [NOTICE] switch_core_session.c:1758 Close Channel sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> [CS_DESTROY]2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:739 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_DESTROY (Cur 0 Tot 5)2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:749 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State DESTROY2021-06-08 10:35:19.015670 [DEBUG] mod_sofia.c:364 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> SOFIA DESTROY2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:181 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> Standard DESTROY2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:749 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State DESTROY going to sleepfreeswitch@kamfs>* i am attaching the kamailio.cfg file and the whole /etc/freeswitch folder, if someone could help me to solve this issue, please. Kind regards, John

3 2

Any way to force socket used to reach databases ?
by David VILLAUME 08 Jun '21

08 Jun '21

Hello, I’m trying to initiate a redis connection in ndb_redis for topos_redis on a keepalived slave host, but host tries to use the VIP instead of the second socket I defined. Is there a way to influence the ‘database source socket’ so the server can connect with a secondary address even if it does not own the keepalived VIP (tried mhomed options without improvment) ? Regards, David

2 1

List of Header Names
by Evan Verma 07 Jun '21

07 Jun '21

hello! new to working with sip/kamailio. I am currently trying to get a list of all of the header names on the invite the SBC receives. I am having trouble finding a way to do this. Does anyone know of a good solution?

5 4

Problem NOTIFY in Presence module
by hamed r 07 Jun '21

07 Jun '21

hello dears ,i am using presence module and NOTIFY message are working properly. but when i put the database on another server , NOTIFY message will not be sent to subscribers. what is problem?

2 2

List of Header Names
by Evan Verma 05 Jun '21

05 Jun '21

2 1

STIR/SHAKEN
by David Villasmil 04 Jun '21

04 Jun '21

Hello guys, So I'm testing secsipid with made up certificates, basically: [image: Untitled.png] The verification _always_ comes back OK, event if I create the Identity with different From numbers, should that fail? Thanks all, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Info: ClueCon Weekly about Kamailio 5.5 series - Jun 4, 2021, 10:00am CT
by Daniel-Constantin Mierla 04 Jun '21

04 Jun '21

Hello, short announcement to let everyone know that next Friday, Jun 4, 2021, at 10:00am CT (17:00 Berlin), I will join ClueCon Weekly to discuss about latest Kamailio 5.5 series. If you have questions about or just want to be part of the discussions, consider to join the live video conference session, more details at: * https://www.cluecon.com/cclive-6-4/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 1

About Kamailio ass authentication service
by Nael Silega 04 Jun '21

04 Jun '21

hi, i have a question, can i use Kamailio as a authentication service? i´m traing to set up STIR/SHAKEN framework and im looking for a server that work as authentication service

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users