sr-users September 2022

sr-users@lists.kamailio.org

41 participants
52 discussions

by Joseph Goettgens

I am not sure what I have to look for and I didn't change the initial config files (except for the 666 mode for kamailio_rpc.sock). As far as Kamailio is concerned the socket files files do exist: root@deb11srv1-kamailio:/var/www/siremis-5.3.x# ls -l /run/kamailio/ insgesamt 4 srw------- 1 kamailio kamailio 0 7. Jun 11:37 kamailio_ctl -rw-r--r-- 1 kamailio kamailio 5 7. Jun 11:37 kamailio.pid prw-rw---- 1 kamailio kamailio 0 7. Jun 11:37 kamailio_rpc.fifo srw-rw-rw- 1 kamailio kamailio 0 7. Jun 11:37 kamailio_rpc.sock When I look at siremis/log/ERR.log I repeatedly get: '06/07/2022','09:43:29','ERR','ErrorHandler','socket_bind(): unable to bind address [2]: No such file or directory','' This disappears when I put the local file socket in /tmp: <UnixSockLocal name="unixsocklocal" address="/tmp/siremis_rpc.sock" timeout="3.0"/> which was probably done this way in previous versions of Siremis (before systemd private tmp config). In this case I get no error messages, but still no answers (as expected). The next step seems to get UnixSockLocal right.

2 years, 2 months

MANAGE_REPLY: do_action(): bad uri: How to mirror username changes from the invite to all replies?

by Benoît Panizzon

Hey there! Kamailio is being used between CPE (customer) and IC. Towards IC we use e164 numbers Towards customers we use 'localized' numbers and also ensure that Privacy is enforced by setting usernames to 'Anonymous' if Privacy is set to id, remove unwanted header etc. I realized, that I have to apply the same translations to replies and re-invites to make sure, they do not leak unwanted information towards the customer. But when I try to set: onreply_route[MANAGE_REPLY] $fU,$rU,$tU within MANAGE_REPLY I get: do_action(): bad uri Just removing unwanted header works fine it looks as it's only changing the usernames that causes this issue. What would be the proper was to change usernames in replies? Is there any module which would apply the same user translations as done with the invite to all replies and re-invites? -- 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, 2 months

tls_wolfssl talk at KWO: traffic generation scripts are online

by Richard Chan

Hi sr-users, The TLS traffic generation scripts are online here: * SIP library - fork of sippy/b2bua - use main-async branch https://github.com/space88man/b2bua This branch is an async refactoring of sippy; the master branch of the repo is the regular sync+elperiodic version. * runtime UA generation scripts: https://github.com/space88man/multiuac-tester This repo contains the TLS-client transport (sippy out-of-the-box supports UDP); also gratuitously uses the match/case syntax for fun (so needs Python 3.10) * no documentation: the scripts/t_register.py and scripts/t_phone.py should give you an idea how to create UACs. The script in the talk is scripts/t_register.py - creates SIP UACs that sit in an infinite loop and do REGISTER and keepalive ('\r\n\r\n'). Disclaimer: this is not a SIP-scenario framework like SIPp; SIP messages are programmatically created using sippy; e.g., the test scenario does not need to handle RTP media so the SDP body is a hardcoded string. Regards S-P

2 years, 2 months

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

2 years, 2 months

Re: [SR-Users] SSL Offloading with AWS ELB or Google GSLB and Kamailio

by Mohammed Alarayshi

Hi Joel Did you manage to offload TLS SSL on the load balancer side ? I tested it before on AWS and the calls were working well. Wondering if this makes any issues like you said with headers ?

2 years, 2 months

slow timer too slow: overflow

by Denys Pozniak

Hello! After some time, Kamailio stops processing incoming messages. slow timer too slow: overflow messages appear in the log (I suspect that the problem is related to the rtimer module) Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 2b45547f33f5203f-4091(a)10.10.10.10} <core> [core/mem/q_malloc.c:430]: qm_malloc(): qm_malloc(0x7f163b9f9010, 960) called from core: core/rvalue.c: rval_new_empty(246), module: core; Free fragment> Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 2b45547f33f5203f-4091(a)10.10.10.10} <core> [core/rvalue.c:253]: rval_new_empty(): could not allocate private memory from pkg pool Aug 29 14:19:17 kamailio[11330]: 12(11330) WARNING: <core> [core/timer.c:936]: timer_handler(): slow timer too slow: overflow (62671 - 61648 = 1023) Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 34618af41c3866bc-16408(a)10.10.10.20} <core> [core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f163b9f9010, 960); Free fragment not found! Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 34618af41c3866bc-16408(a)10.10.10.20} <core> [core/mem/q_malloc.c:430]: qm_malloc(): qm_malloc(0x7f163b9f9010, 960) called from core: core/rvalue.c: rval_new_empty(246), module: core; Free fragment no> Aug 29 14:19:17 kamailio[11320]: 2(11320) ERROR: {1 10 OPTIONS 34618af41c3866bc-16408(a)10.10.10.20} <core> [core/rvalue.c:253]: rval_new_empty(): could not allocate private memory from pkg pool Aug 29 14:19:17 kamailio[11330]: 12(11330) WARNING: <core> [core/timer.c:936]: timer_handler(): slow timer too slow: overflow (62671 - 61648 = 1023) Aug 29 14:19:18 kamailio[11320]: 2(11320) ERROR: {1 10 KDMQ 1c18959d07113951-203309(a)10.10.10.30} <core> [core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f163b9f9010, 960); Free fragment not found! Aug 29 14:19:18 kamailio[11320]: 2(11320) ERROR: {1 10 KDMQ 1c18959d07113951-203309(a)10.10.10.30} <core> [core/mem/q_malloc.c:430]: qm_malloc(): qm_malloc(0x7f163b9f9010, 960) called from core: core/rvalue.c: rval_new_empty(246), module: core; Free fragment no> Please point me out where the source of the problem could be. version: kamailio 5.6.1 (x86_64/linux) -- BR, Denys Pozniak

2 years, 2 months

Dynamic rtimer interval, transaction to replace in-memory dispatcher list

by Anton Yabchinskiy

Hello, I have two slightly related questions, and would appreciate any advice on the matter. The first one is about dynamic `rtimer` (or `timer`) intervals. In the route, called by the timer process there is a request to a neighbor service. In the response there's a set of new destinations for in-memory dispatcher list and some TTL value. And I need to adjust the timer interval based on this TTL (e.g., timer interval may be 10 min, but TTL may suggest to request destinations every 5 min since now). Also, the first call to the timer route should be at T+0, not at T+interval. As far as I can tell from `rtimer` module implementation, that's unfeasible. But maybe I'm missing something? Any suggestion on how one should implement something like this? The second one is about updating in-memory dispatcher list. After receiving and parsing new destinations in the timer route, the previous in-memory destinations must be replaced by these new destinations. The naive way of doing so would look something like: `dispatcher.reload` to clear previous list, then a series of `dispatcher.add` calls to add new destinations. But a failed `add` call may lead to wrong in-memory destinations set. As far as I understand I should start using some transaction-aware database for dispatcher destinations, and literally write a transaction. Are there any other ways to solve this?

2 years, 2 months

Kamailio 5.6 rpm availability

by Riccardo Villa

Hello, I can’t find rpm packages of kamailio 5.6.x on rpm.kamailio.org, do you know if it’s planned to build them in the future? I’m available if some help/testing is needed. Thanks, Riccardo Villa -- -- NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.

2 years, 2 months

How to hide Via and Record-Route header to external network and restore them to internal network?

by Anthony Blandin

Hi Community, I have set up a SBC with Kamailio. I am testing voice call from external network to my network and voice call from my network to external network. When I send SIP messages to external network, I want to hide Via and Record-Route headers but when I receive replies from the external network I want to restore these Via and Record-Route headers to my network. How to store and restore these headers in Kamailio configuration ? Could you help on this? Thanks Anthony Blandin

2 years, 2 months

remove user param from RURI

by Maarten Ureel

Hello I have a SIP INVITE with a RURI like this: sip:31427;phone-context=stripped@IP How can I remove the phone-context parameter here? In reality it's a very long string and the next hop (an SBC) is complaining about it, but I don't need it anyway. Regards Maarten

2 years, 2 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 September 2022