sr-users

sr-users@lists.kamailio.org

49 participants
37556 discussions

Kamailio PCSCF route logic
by Weiqi Yao 30 Mar '22

30 Mar '22

Hello community, We made some modifications to Kamailio PCSCF sample cfg file, so when PCSCF receiving an tcp SUBSCRIBE message it add ;transport=tcp to the end of Contact URI. Below is what we added the route block right after if (is_method("INVITE|SUBSCRIBE")) logic if (is_method("SUBSCRIBE") && proto=='tcp') { $var(original_contact_header) = $ct; $var(new_contact_header) = $(var(original_contact_header){re.subst,/(.*:.*)(>);/\1;transport=tcp>/g}); remove_hf("Contact"); append_hf("Contact: $var(new_contact_header)\r\n"); msg_apply_changes(); } We did see the ;transport=tcp been added but we also seeing a bad line ;alias=[...] is added before the To: line [cid:image001.png@01D84375.8D109B20] Does anyone know what function might cause this ;alias been added before To: line? BR, Weiqi

2 2

Parallel forking call drop scenario
by Koray Vatansever 30 Mar '22

30 Mar '22

Hi everyone, I'm facing the following situation. Clients are connected over TLS. Therefore there is no retransmission in Kamailio. How can I prevent this call drop? +---+ +-----------+ +-----+ +-----+ | A | | Kamailio | | B1 | | B2 | +---+ +-----------+ +-----+ +-----+ | | | | | INVITE | | | |------------------------------------>| | | | | -------------------\ | | | |-| Parallel forking | | | | | |------------------| | | | | | | | | INVITE | | | |---------------------->| | | | | | | | INVITE | | | |--------------------------------------------------->| | | | | | | 180 Ringing | | | |<----------------------| | | | | | | | | 180 Ringing | | |<---------------------------------------------------| | | | ------------------------\ | | | |-| User answers the call | | | | | |-----------------------| | | | | | | | 200 OK | | | |<----------------------| | | | | | | 200 OK | | | |<------------------------------------| | | | | | | | ACK | | | |------------------------------------>| | | | | | | | | ACK | | | |---------------------->| | | ------------------------------\ | | | |-| Session established with B1 | | | | | |-----------------------------| | | | | | | | ----------------------------\ | | | |-| Client changes network | | | | | | LTE to Wifi or vice versa | | | | | | Temporary connection lost | | | CANCEL | | |---------------------------| | |----------------------------------------------X | | | | | -------------------------------------------------\ | | | |-| Reconnected with different IP | | | | | | CANCEL is missed and client continues ringing. | | | | | | User answers the call. | | | | 200 OK | |------------------------------------------------| | |<---------------------------------------------------| | | | | | 200 OK | | | |<------------------------------------| | | | | | | | | | BYE | | |<---------------------------------------------------| | | | | | BYE | | | |<------------------------------------| | | | ---------------------------\ | | | |-| Session terminated by B2 | | | | | | Call Drop | | | | | |--------------------------| | | |

2 2

More than TCP 800 concurrent calls, slows Kamailio (LUA FILE API REQUESTS)
by Giovanni Jose 30 Mar '22

30 Mar '22

Hello Guys I am having this issue where kamailio is receiving requests from SIPp (we are currently testing the platform and doing QA) but if we do more than 800 concurrent calls kamailio starts failing and slowing the requests, The scenario is the following: I am sending 5000 calls at 100 CPS on TCP and I am having this route in the configuration file: # Handle the calls to api route[CALL_API] { xlog("L_NOTICE"," Call request $var(call_request) method: $rm \n"); $var(loop_true)=1; while ($var(loop_true)) { if(!lua_run("call_request","$var(call_request)","$sht(token=>new_token)")) { xlog("L_NOTICE", "SCRIPT: failed to execute lua function!\n"); } if ($var(loop_true)){ sleep("1"); } } xlog("L_NOTICE", "SCRIPT: Sucess to execute lua function!\n"); } So I am executing a LUA script for the requests and the API response will tell the destination of the call. At 800 concurrent calls, I can notice SLOWLINESS in the SIPp testing tool, and then I will start receiving 408 timeouts. This sounds like a load issue or something because I believe there's a time that it's been added every time we hit the backend and wait for the response. any help will be appreciated Regards Gio

2 1

dispatcher socket attrs binding
by David Villasmil 29 Mar '22

29 Mar '22

Hello guys, Im starting kamailio with listen=0.0.0.0:5060 and in my dispatcher list i have in the attrs something like: socket=udp:172.17.0.2:5060 That IP address belongs to kamailio's host and it is binging to it. Is it right i can't set a specific IP in the socket attribute if listen is 0.0.0.0? maybe i should be able to? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 4

kamailio - mariadb hosted on remote server - issue
by Youssef Boujraf 29 Mar '22

29 Mar '22

Dear all, I don't belive to connect Kamailio to a remote Mariadb will take too much time. STEP 1 : KAMAILIO : -------------------------------- $ sudo 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 STEP 2 : Set the kamctlrc config ------------------------------------------------ KAMAILIO IP : 192.168.1.41 MARIADB IP : 192.168.1.39 - /etc/kamailio/kamctlrc SIP_DOMAIN=example.be DBENGINE=MYSQL DBHOST=192.168.1.39 // where the mariadb is installed DBNAME=kamailio DBRWUSER="kamailio" DBRWPW="XX" DBROUSER="kamailioro" DBROPW="XX" DBACCESSHOST=192.168.1.41 // where kamctl is launched (here kamailio srv) DBROOTUSER="root" DBROOTPW="kamailio" CHARSET="latin1" STEP 3 : MARIADB : hosted on different srv than kamailio -------------------------------------------------------------------------------------- IP : 192.168.1.39 - /etc/mysql/mariadb.conf.d/50-server.cnf # this is only for the mysqld standalone daemon [mysqld] # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. #bind-address = 127.0.0.1 bind-address = 0.0.0.0 STEP 4 : TEST : Reote connection with the DB ---------------------------------------------------------------------- REMOTE IP : 192.168.1.41 DB IP : 192.168.1.39 $ sudo mysql -u root -h 192.168.1.39 -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 298 Server version: 10.5.15-MariaDB-1:10.5.15+maria~bullseye mariadb.org binary distribution Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]>The connection is established with success. STEP 5 : KAMAILIO DB : creation ---------------------------------------------------- $ sudo kamdbctl create -e \E[37;33mINFO: creating database kamailio ... -e \E[37;33mINFO: granting privileges to database kamailio ... -e \E[37;33mINFO: creating standard tables into kamailio ... -e \E[37;33mINFO: Core Kamailio tables successfully created. Create the presence related tables? (y/n): y -e \E[37;33mINFO: creating presence tables into kamailio ... -e \E[37;33mINFO: Presence tables successfully created. Create the tables for imc cpl siptrace domainpolicy carrierroute drouting userblocklist htable purple uac pipelimit mtree sca mohqueue rtpproxy rtpengine secfilter? (y/n): y -e \E[37;33mINFO: creating extra tables into kamailio ... -e \E[37;33mINFO: Extra tables successfully created. Create the tables for uid_auth_db uid_avp_db uid_domain uid_gflags uid_uri_db? (y/n): y -e \E[37;33mINFO: creating uid tables into kamailio ... -e \E[37;33mINFO: UID tables successfully created. STEP 6 : DB : verify the users creation and rights -------------------------------------------------------------------------- MariaDB [(none)]> select user, host from mysql.user; +-------------+--------------+ | User | Host | +-------------+--------------+ | kamailio | 192.168.1.39 | | kamailioro | 192.168.1.39 | | kamailio | 192.168.1.41 | | kamailioro | 192.168.1.41 | | root | 192.168.1.41 | | kamailio | localhost | | kamailioro | localhost | | mariadb.sys | localhost | | mysql | localhost | | root | localhost | +-------------+--------------+ 10 rows in set (0.001 sec) MariaDB [(none)]> SHOW GRANTS FOR kamailio(a)192.168.1.41; +--------------------------------------------------------------------------------------------------------------------+ | Grants for kamailio(a)192.168.1.41 | +--------------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO `kamailio`(a)`192.168.1.41` IDENTIFIED BY PASSWORD '*157PASSWORD' | | GRANT ALL PRIVILEGES ON `kamailio`.* TO `kamailio`(a)`192.168.1.41` | +--------------------------------------------------------------------------------------------------------------------+ 2 rows in set (0.000 sec) MariaDB [(none)]> SHOW GRANTS FOR kamailio(a)192.168.1.39; +--------------------------------------------------------------------------------------------------------------------+ | Grants for kamailio(a)192.168.1.39 | +--------------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO `kamailio`(a)`192.168.1.39` IDENTIFIED BY PASSWORD '*157PASSWORD' | | GRANT ALL PRIVILEGES ON `kamailio`.* TO `kamailio`(a)`192.168.1.39` | +--------------------------------------------------------------------------------------------------------------------+ 2 rows in set (0.000 sec) MariaDB [(none)]> SHOW GRANTS FOR kamailio@localhost; +-----------------------------------------------------------------------------------------------------------------+ | Grants for kamailio@localhost | +-----------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO `kamailio`@`localhost` IDENTIFIED BY PASSWORD '*157PASSWORD' | | GRANT ALL PRIVILEGES ON `kamailio`.* TO `kamailio`@`localhost` | +-----------------------------------------------------------------------------------------------------------------+ 2 rows in set (0.000 sec)STEP 7 : ADDRESS TABLE : add new ip address$ sudo systemctl restart kamailio sipsecure@kamailio:/etc$ sudo kamctl address add 0 192.168.1.26 32 0 HP -e \E[37;33mINFO: execute '/sbin/kamctl address reload' to synchronize cache and database STEP 8 : DB : verify if the new ip address is created ? Yes MariaDB [(none)]> select * from kamailio.address; +----+-----+--------------+------+------+------+ | id | grp | ip_addr | mask | port | tag | +----+-----+--------------+------+------+------+ | 1 | 0 | 192.168.1.26 | 32 | 0 | HP | +----+-----+--------------+------+------+------+ 1 row in set (0.000 sec) STEP 9 : Reload the content of the DB into kamailio. It failed ---------------------------------------------------------------------------------------- The host: '192.168.1.41' is kamailio (remote client)$ sudo kamctl address reload { "jsonrpc": "2.0", "error": { "code": 500, "message": "Reload failed." }, "id": 12397 } In /var/log/daemon.log Mar 28 17:09:49 db04srv mariadbd[2430]: 2022-03-28 17:09:49 281 [Warning] Aborted connection 281 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Mar 28 17:09:49 db04srv mariadbd[2430]: 2022-03-28 17:09:49 273 [Warning] Aborted connection 273 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Mar 28 17:09:49 db04srv mariadbd[2430]: 2022-03-28 17:09:49 295 [Warning] Aborted connection 295 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Mar 28 17:09:49 db04srv mariadbd[2430]: 2022-03-28 17:09:49 264 [Warning] Aborted connection 264 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Now, if I am trying to restart "kamailio" service, I got an error : Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: DEBUG: <core> [core/sr_module.c:940]: init_mod(): permissions Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: DEBUG: permissions [address.c:179]: reload_address_db_table(): Number of rows in address table: 1 Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: DEBUG: permissions [address.c:191]: reload_address_db_table(): failure during checks of database value 1 (group) in address table Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: ERROR: permissions [address.c:233]: reload_address_db_table(): database problem - invalid record Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: CRITICAL: permissions [address.c:536]: init_addresses(): reload of address table failed Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: ERROR: permissions [permissions.c:657]: mod_init(): failed to initialize the allow_address function Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: ERROR: <core> [core/sr_module.c:942]: init_mod(): Error while initializing module permissions (/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so) Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/cfg.y:1860]: yyparse(): loading module permissions.so Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/sr_module.c:513]: ksr_locate_module(): found module to load </usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so> Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/sr_module.c:563]: load_module(): trying to load </usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so> Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/kemi.c:3090]: sr_kemi_modules_add(): adding module: permissions Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/cfg.lex:1963]: pp_define(): defining id: MOD_permissions Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'permissions' matches module 'permissions' Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/sr_module.c:811]: find_param_export(): found <db_url> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/modparam.c:128]: set_mod_param_regex(): found <db_url> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'permissions' matches module 'permissions' Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/sr_module.c:811]: find_param_export(): found <load_backends> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/modparam.c:128]: set_mod_param_regex(): found <load_backends> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:31 kamailio kamailio: DEBUG: <core> [core/sr_module.c:719]: find_mod_export_record(): found export of <allow_source_address> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:31 kamailio kamailio: DEBUG: <core> [core/sr_module.c:719]: find_mod_export_record(): found export of <allow_source_address_group> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.soIf I remove the record from the database manually, I can restart kamailio but no way to add any address. Thanks if someone could highlight my path. Best Regards, -- Youssef

2 4

avps on regexps?
by David Villasmil 28 Mar '22

28 Mar '22

Hello guys, Is it possible to use apvs on regexps like: $avp(myvar)=$(re{uri.user}{re.subst,/^\+$avp(some_var)/$avp(some_var)/}); doesn't seem possible Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 3

proxy and forward
by jaflong jaflong 28 Mar '22

28 Mar '22

2 1

nathelper OPTIONS ping
by Xuo Guoto 28 Mar '22

28 Mar '22

Hello all, I am trying to periodically send SIP OPTIONS to all connected WebRTC clients from Kamailio. The functionality is similar to qualify=yes of Asterisk. Following are the configuration changes I have made to get this working. #!define FLB_NATSIPPING 7 <snip/> loadmodule "nathelper.so" <snip/> # ----- nathelper params ----- modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") modparam("nathelper", "sipping_bflag", FLB_NATSIPPING) modparam("nathelper", "natping_interval", 20) modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") <snip/> # Handle SIP registrations route[REGISTRAR] { if (is_method("REGISTER")) { xlog("L_INFO", "Processing REGISTER in route[REGISTRAR]\n"); if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); # do SIP NAT pinging xlog("L_INFO", "Setting FLB_NATSIPPING\n"); setbflag(FLB_NATSIPPING); } if (!save("location")) { sl_reply_error(); } xlog("L_INFO", "Successfully processed REGISTER in route[REGISTRAR]\n"); exit; } } When the WebRTC client registers, I can see the log: Setting FLB_NATSIPPING, but SIP OPTIONS packets are not seen. I am checking it using the Chrome console, at client side as well as sipdump module in server side. Do I have to do any additional configuration? I am not posting the full config file here so that its easy to focus on the relevant parts, but can do that if needed. Thanks and regards, X.

2 1

Re: [SR-Users] Kamailio : kamctl address reload with HAProxy
by Henning Westerholt 28 Mar '22

28 Mar '22

Hello, please keep the list in CC – that others can comment as well. Can you actually connect from the kamailio system e.g. with mysql client? If yes, as I said – I would try to debug the issue further with network analysis tools. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Paclinio <thomas.leutscher(a)gmail.com> Sent: Monday, March 28, 2022 1:11 PM To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] Kamailio : kamctl address reload with HAProxy Hello, KAMCTL : I've resolved the problem with kamctl that now can communicate with my remote Cluster by adding this line in kamctlrc. // HAPROXY = 192.168.1.37 DBHOST=192.168.1.37 DBACCESSHOST=192.168.1.37 I can now add and reload new addresses with success. KAMAILIO + HAPROXY: But now, I've this issue when restarting kamailio. Mar 28 10:54:39 kamailio /usr/sbin/kamailio[8416]: ERROR: permissions [address.c:233]: reload_address_db_table(): database problem - invalid record Mar 28 10:54:39 kamailio /usr/sbin/kamailio[8416]: ERROR: permissions [permissions.c:657]: mod_init(): failed to initialize the allow_address function Mar 28 10:54:39 kamailio /usr/sbin/kamailio[8416]: ERROR: <core> [core/sr_module.c:942]: init_mod(): Error while initializing module permissions (/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so) My DBURL is #!substdef "!DB_USER!kamailio!g" #!substdef "!DB_PASS!XXXXX!g" #!substdef "!DB_HOST!192.168.1.37!g" // HA PROXY #!substdef "!DB_PORT!MY_PORT_DB!g" #!substdef "!DB_NAME!kamailio!g" #!define DBURL "mysql://DB_USER:DB_PASS@DB_HOST/DB_NAME" KAMAILIO + REMOTE DB : Even I using a remote database I'm getting the same issue. I've discovered the connection between kamailio and remote database is aborded instantly after restarting kamailio. Mar 28 11:47:30 db03srv mariadbd[874]: 2022-03-28 11:47:30 44076 [Warning] Aborted connection 44076 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Thank you [Das Bild wurde vom Absender entfernt.]<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Le dim. 27 mars 2022 à 22:52, Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> a écrit : Hello, it seems the data that gets delivered to the Kamailio is corrupted. Analyse it further e.g. with a network trace, wireshark etc.. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Paclinio Sent: Friday, March 25, 2022 5:22 PM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] Kamailio : kamctl address reload with HAProxy Dear colleagues, I've installed a Galera cluster with a HAProxy that kamailio interacts with. Kamailio's DBURL is linked to the proxy that will contact the databases. Kamailio works fine except when I need to reload something from the database (Using kamctl). When cache and database are the same I receive sudo kamctl address reload { "jsonrpc": "2.0", "result": "Reload OK", "id": 13111 } Now when I have something using kamctl, it still works and is replaced on all my databases. sipsecure@kamailio:~$ sudo kamctl address add 0 192.168.48.15 32 0 Test -e \E[37;33mINFO: execute '/sbin/kamctl address reload' to synchronize cache and database Then when i try to reload i receive sipsecure@kamailio:~$ sudo kamctl address reload { "jsonrpc": "2.0", "error": { "code": 500, "message": "Reload failed." }, "id": 13504 } And when I'm going to read my logs to see a error, I only see that little sentence Mar 25 17:14:40 kamailio /usr/sbin/kamailio[13343]: ERROR: permissions [address.c:233]: reload_address_db_table(): database problem - invalid record Could I have some explanation ? Thank you. [Das Bild wurde vom Absender entfernt.]<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>

2 2

t_suspend / t_continue & insert_hf
by Fuad Trle 28 Mar '22

28 Mar '22

Hello, I'm inserting some headers after getting value from http_async_query. If a call is relayed, I see them. But If I t_suspend and t_continue call (before time out), I do not see added headers. Here is flow: route(START) t_newtran(); #.. prep for query http_async_query("url","HTTP"); route(HTTP) #.. collect and using data from query insert_hf("$var(key): $var(value)\r\n"); t_store(); if (registered("location") { route(RELAY); } else { t_suspend(); exit; } route(AWAKE) t_continue(); I see that the branch index ($T_branch_idx) is 0 at start. 1 after http query, +1 if there is forking or location. +1 after t_suspend. It looks like t_continue uses a branch with index after t_suspend. I tried with t_save_lumps() to carry over changes. Any idea how to do this?

3 3

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