sr-users June 2022

sr-users@lists.kamailio.org

53 participants
58 discussions

by Daniel-Constantin Mierla

Hello, I am considering to release Kamailio v5.6.1 (out of branch 5.6) on Wednesday, July 6, 2022 -- in about 1 week and a half from now. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online: June 20-23, 2022 * https://www.asipto.com/sw/kamailio-advanced-training-online/

2 years, 4 months

(Off-topic) Vienna, meeting

by Henning Westerholt

(Off-topic) Hello, In about two weeks I will be a few days in Vienna (12h - 14th July). If you want to meet for a drink to chat about Kamailio and other topics, just contact me off-list. Thanks, and regards, Henning

2 years, 4 months

Kamailio 5.5 STIR SHAKEN private key buffer size error

by Maharaja Azhagiah

Hi, I am trying STIR/SHAKEN using libstirshaken in Kamailio 5.5. I used a self signed certificate as this is just a test in the local docker environment. However, when I try to add identity with private key (stirshaken_add_identity_with_key), I get "[error_code: 447] Buffer for key from file /tmp/cert/private.pem too short (2000 <= 3247)" I have tried using 2048 and 4096 size root@5907e44bd056:/tmp/cert# openssl rsa -in private.pem -text -noout | grep "Private-Key" RSA Private-Key: (4096 bit, 2 primes) Could you tell me what is wrong with the certificate? Kamailio version: root@5907e44bd056:/usr/local/kamailio/etc/kamailio# kamailio -v version: kamailio 5.5.4 (x86_64/linux) 469465 Error: 0(404) ERROR: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken [stirshaken_mod.c:761]: ki_stirshaken_add_identity_with_key(): Failed to load private key 0(404) DEBUG: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken [stirshaken_mod.c:117]: stirshaken_print_error_details(): failure details: 0(404) DEBUG: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken [stirshaken_mod.c:118]: stirshaken_print_error_details(): failure reason is: src/stir_shaken_ssl.c:2112: [error_code: 447] Buffer for key from file /tmp/cert/private.pem too short (2000 <= 3247) 0(404) DEBUG: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken [stirshaken_mod.c:119]: stirshaken_print_error_details(): failure error code is: 447 0(404) ERROR: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} <script>: Failed Regards *Maharaja Azhagiah*

2 years, 4 months

Run PCSCF without IPSec

by Weiqi Yao

Hello Community, We are running Kamailio with 3 instances as PCSCF/ICSCF/SCSCF, and we don't want IPsec to be used in between PCSCF and UE and we confirmed the initial Register UE send do not have the Security-Client header. However, seems the IPsec is enabled by default in current PCSCF cfg, we tried to comment WITH_IPSEC as well as couple ipsec_forward function out in the cfg, but when the 401 Challenging message send to PCSCF and PCSCF failed to forward it to UE due to (Create ipsec failed) reason. So I want to reach out and see if anyone have experience not using IPsec with currently Kamailio PCSCF? Any clue or comment will be appreciated! BR, Weiqi

2 years, 4 months

Makefile.rules:191: recipe for target 'tlsa.so' failed

by Abdoul Osséni

Hello, Cannot compile tlsa module. I get the following error message: LD (gcc) [M tlsa.so] tlsa.so /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libssl.a(ssl_lib.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libssl.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status ../../Makefile.rules:191: recipe for target 'tlsa.so' failed make[2]: *** [tlsa.so] Error 1 Makefile:511: recipe for target 'modules' failed make[1]: *** [modules] Error 1 make[1]: Leaving directory '/usr/local/src/kamailio-5.6/kamailio/src' Makefile:34: recipe for target 'all' failed make: *** [all] Error 2 Please find below some information about my environment system: root@sbc:/usr/local/src/kamailio-5.6/kamailio# cat /etc/debian_version 8.6 root@sbc:/usr/local/src/kamailio-5.6/kamailio# openssl version OpenSSL 3.0.4 21 Jun 2022 (Library: OpenSSL 3.0.4 21 Jun 2022) Regards Abdoul

2 years, 4 months

Install Kamailio in captive network

by Rahul mm

Hello guys, Ab initio, I'm loving Kamailio and the endless horizons it opens-up. Is there any document somewhere to get Kamailio installed in a captive network that runs w/o internet? I know this seems bizarre but in the mining industry most of the locations do not have internet facilities but they still want to use VoIP. I do not have the privilege to pull a blade system and put it on the internet to install Kamailio, FS etc. Any suggestions? -- Warm Regds. MathuRahul

2 years, 4 months

Forward reply in onreply_route

by Carsten Bock

Hi, Question: Is there a way to forward a reply from the reply route and do other stuff afterward? We are currently doing operations on a 183 reply and it would be useful if we could forward the reply before continuing to process other stuff. High-Level example: *route { t_on_reply("REPLY"); t_relay();}onreply_route[REPLY] { // Forward the reply to the Caller t_relay(); // Does not work, as t_relay is only allowed in request and failure-routes // Do other fancy stuff, e.g. a DB Update or anything else}* Any ideas? Thanks, Carsten -- Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock

2 years, 4 months

SIP Proxy Challange

by Mihai

Hello ! I have this issue with the telco provider they give the sip trunk on a private connection with private ips, the problem is that i am trying to relocate the sip trunk in remote server and I've tried though basic networking/tunnels/vpn and no go; their sbc is dropping requests and rejects if they are more via headers, they force me to use that connection and the ip allocated. The challenge is how to do this in kamailio, basically I just want to transport the trunk (similar to a reverse proxy for web) to its new destination and from there handle everything. Any hints on how to achieve this?

2 years, 4 months

Phones are not getting registered. Is my setup correct?

by Farhan Sahariar (CSSD)

Hi, I have just installed Goautodial v4. I have followed all the guide to register a phone but this does not work. Is kamailio the reason. I am new to linux need help. [root@vaglxc01 ~]# systemctl status kamailio ● kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/usr/lib/systemd/system/kamailio.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Sun 2022-06-26 16:11:41 +06; 10min ago Process: 1545 ExecStart=/usr/sbin/kamailio -DD -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY (code=exited, status=255) Main PID: 1545 (code=exited, status=255) Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: Unit kamailio.service entered failed state. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: kamailio.service failed. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: kamailio.service holdoff time over, scheduling restart. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: start request repeated too quickly for kamailio.service Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: Unit kamailio.service entered failed state. Jun 26 16:11:41 vaglxc01.goautodial.com systemd[1]: kamailio.service failed. Jun 26 16:11:47 vaglxc01.goautodial.com systemd[1]: start request repeated too quickly for kamailio.service Jun 26 16:11:47 vaglxc01.goautodial.com systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Jun 26 16:11:47 vaglxc01.goautodial.com systemd[1]: kamailio.service failed. [root@vaglxc01 ~]# kamailio -version version: kamailio 5.0.7 (x86_64/linux) 743c2d flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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 ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 743c2d compiled on 03:02:32 Aug 26 2018 with gcc 4.8.5 Best regards, Farhan Sahariar Assistant Manager Customer Support Services Division LEADS Corporation Limited [Description: Description: Green Living Slogan_Email]

2 years, 4 months

How to handle a 301 redirect request from a client?

by Benoît Panizzon

Hi Gang We want to allow customers to send a 301 to forward calls to mimik ISDN PARE. The new destination is in the contact user HF. So I guess I could handle this on the t_on_failure route to catch that error, extract the contact user HF, craft an appropriate Diversion header and send the call on. But I wonder, is there maybe a module which handles all of this out of the box? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 years, 4 months

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 June 2022