sr-users

sr-users@lists.kamailio.org

25 participants
37379 discussions

Start a nNew thread

Software bill of materials (SBOM)
by Ivan Ribakov 30 Sep '23

30 Sep '23

Any recommendations for a tool that can generate SBOM for a Kamailio instance based on configured modules? Thanks, Ivan

6 10

periodic could not resolve hostname
by Sergiu Pojoga 28 Sep '23

28 Sep '23

Aloha, I'm experiencing this internal DNS problem with Kamailio, can't seem to figure out what's causing it. Maybe someone can help. Essentially, from time to time (one or two times a day) this situation happens, starting with logs: linux kamailio[773]: ERROR: uac [uac_reg.c:1163]: uac_reg_send(): failed to send request for [some-uuid] linux kamailio[773]: ERROR: <core> [core/resolve.c:1730]: sip_hostport2su(): could not resolve hostname: "my.domain.net" linux kamailio[773]: ERROR: tm [ut.h:309]: uri2dst2(): failed to resolve " my.domain.net" linux kamailio[773]: ERROR: tm [uac.c:480]: t_uac_prepare(): no socket found # Do a Kamailio internal DNS lookup, no results found??? root@linux:~# kamcmd dns.lookup a my.domain.net error: 400 - Not found # Do a system DNS lookup. All good. root@linux:~# dig my.domain.net ;; QUESTION SECTION: ;my.domain.net. IN A ;; ANSWER SECTION: my.domain.net. 18000 IN A 192.168.0.1 # Delete internal Kamailio DNS record root@linux:~# kamcmd dns.delete_a my.domain.net # Lookup again right away. It's there, problem fixed. Why?? root@linux:~# kamcmd dns.lookup a my.domain.net { name: my.domain.net type: A size_bytes: 120 reference_counter: 2 permanent: no expires: 7674 last_used: 0 negative_entry: no records: { { rr_idx: 0 rr_ip: 192.168.0.1 rr_permanent: no rr_expires: 7674 } } }

2 2

What is the expected behavior for dispatcher's ds_next_dst?
by geoff.goas＠interoptechnologies.com 28 Sep '23

28 Sep '23

Hello, I have some questions about dispatcher's behavior. I noticed that when I first ds_select_dst() a specific dispatcher group ID, ds_next_dst() will cycle through the active destinations in that group. When it reaches the end of the destinations in the group, it does not return "false", instead it starts to return destinations that are not a part of that group, ie. those destinations which are listed prior to the selected group in the dispatcher.list file. Is this the expected behavior? I've observed it on kamailio 5.3 and 5.5 releases. My dispatcher.list: # Group 1 1 sip:127.0.0.1:5071;transport=udp 8 0 # Group 2 2 sip:127.0.0.1:5072;transport=udp 8 0 # Group 3 3 sip:127.0.0.1:7010;transport=udp 8 0 3 sip:127.0.0.1:7011;transport=udp 8 0 3 sip:127.0.0.1:7012;transport=udp 8 0 # Group 4 4 sip:127.0.0.1:5071;transport=udp 8 0 4 sip:127.0.0.1:5072;transport=udp 8 0 I have the following in failure_route (excerpt): $var(dsFoundDestination) = 0; if (t_any_replied()) { xavp_params_implode("_dsdst_", "$var(dsDestinations)"); xlog("L_INFO", "FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [$var(dsDestinations)]"); if (ds_next_dst()) { xavp_params_implode("_dsdst_", "$var(dsDestinations)"); xlog("L_INFO", "FAILURE ROUTE: Next destination selected: [$du] from [$var(dsDestinations)]"); $var(dsFoundDestination) = 1; } } else if (ds_select_dst("3", "8")) // Dispatcher Group 3 { xlog("L_INFO", "FAILURE ROUTE: Did not find any replies on this transaction. Selected destination: [$du]"); $var(dsFoundDestination) = 1; } if ($var(dsFoundDestination)) { $var(logString) = "FAILURE ROUTE: Relayed to [" + $du + "]"; if (t_relay()) { xlog("L_INFO", "$var(logString)"); } } Produces the following logs: FAILURE ROUTE: Did not find any replies on this transaction. Selected destination: [sip:127.0.0.1:7012;transport=udp] FAILURE ROUTE: Relayed to [sip:127.0.0.1:7012;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=3;uri=sip:127.0.0.1:7012;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:7011;transport=udp] from [grp=3;uri=sip:127.0.0.1:7011;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:7011;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=3;uri=sip:127.0.0.1:7011;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:7010;transport=udp] from [grp=3;uri=sip:127.0.0.1:7010;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:7010;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=3;uri=sip:127.0.0.1:7010;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:5072;transport=udp] from [grp=2;uri=sip:127.0.0.1:5072;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:5072;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=2;uri=sip:127.0.0.1:5072;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:5072;transport=udp] from [grp=2;uri=sip:127.0.0.1:5072;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:5072;transport=udp] FAILURE ROUTE: Already have replies on this transaction. Selecting next destination from: [grp=2;uri=sip:127.0.0.1:5072;transport=udp;] FAILURE ROUTE: Next destination selected: [sip:127.0.0.1:5071;transport=udp] from [grp=1;uri=sip:127.0.0.1:5071;transport=udp;] FAILURE ROUTE: Relayed to [sip:127.0.0.1:5071;transport=udp] I want to stop the loop once there are no more active destinations in group 3. Is the solution simply to check that the selected destination is part of the desired group and stop processing if it is not? Thanks for your time.

5 8

Kamailio v5.7.2 Released
by Daniel-Constantin Mierla 27 Sep '23

27 Sep '23

Hello, Kamailio SIP Server v5.7.2 stable release is out. This is a maintenance release of the latest stable branch, 5.7, that includes fixes since the release of v5.7.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.7.x. Deployments running previous v5.7.x versions are strongly recommended to be upgraded to v5.7.2. For more details about version 5.7.2 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/09/kamailio-v5-7-2-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 0

Releasing v5.7.2
by Daniel-Constantin Mierla 27 Sep '23

27 Sep '23

Hello, I am considering to release Kamailio v5.7.2 (out of branch 5.7) this week (likely on Wednesday or Thursday, Sep 27/28, 2023). 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 World Conference - www.kamailioworld.com

1 1

failure_route, change_reply_status, and append_hf: Not Working as Expected
by sadik.oualla.mohamed＠gmail.com 26 Sep '23

26 Sep '23

Hello Kamailio Community, I'm currently working on a project that involves complex SIP routing and handling. I've encountered some difficulties while using change_reply_status, and append_hf functions in failure_route route in Kamailio. Although the documentation does provide guidance, the behaviors I am experiencing aren't aligning with the expected outcomes. Issue 1: failure_route I've set up a failure_route to handle specific SIP response codes (>4xx). However, I've observed that it get trigered and lunched, but I can't use change_reply_status or append_hf, I was using this first in onreply_route. Issue 2: change_reply_status I tried to use the change_reply_status function to modify the status of SIP replies, but it raises an error that this command cannot be executed here. Issue 3: append_hf I've also attempted to use append_hf in my failure_route block to add headers to replies, but the headers are not being added as expected. As a workaround, I've been using send_reply and append_to_reply for adding custom headers, and they seem to be working as expected. However, I found some old messages in kamailio mailing list, I can summerize what I learned like this ``` #Functions and Context - append_hf(): Adds a header to the currently processed SIP message. If you are in a route {...} block, then this adds the header to the request. If you are in an onreply_route, it adds the header to the reply. This function always acts on the message currently under scrutiny. - append_to_reply(): This function is used to add a header to a reply that will be generated by Kamailio at a later time. This function only affects replies generated by Kamailio itself and is not applicable for messages that are simply being forwarded. #Contexts - route {...}: This is typically where the incoming SIP request gets processed. Here, append_hf() will add headers to that request, and append_to_reply() will add headers to any replies that Kamailio might generate for this request. - onreply_route: This is where incoming SIP replies are processed. Here, append_hf() will act on the reply, not the request. ``` I'd like to know if there is a way to handle sip replies in failure_route, because send_reply make a new reply from kamailio, instead I want to keep some important headers from the original reply. I'd appreciate any insights or guidance the community can offer. Best regards,

2 1

RTPengine use single port for all calls
by Mahmood Alkhalil 26 Sep '23

26 Sep '23

Hello Kamailio, Is it possible to use RTPengine with a single UDP port for all calls instead of a range of ports? For example, when an invite is received or sent, the offered SDP for RTPengine is to receive RTP packets on a single port that is the same for all other calls, so that on firewalls only one port is to be opened.

2 2

Re: Choose RTP port in routing script
by Duarte Rocha 26 Sep '23

26 Sep '23

2 1

cdr_json_pre_encoded_prefix
by Oleg Podguyko 26 Sep '23

26 Sep '23

I try to use cdr_json_pre_encoded_prefix (string) parameters from acc_json module modparam("acc_json", "cdr_extra", "spx_resp=$avp(spx_resp)") modparam("acc_json", "cdr_json_pre_encoded_prefix", "spx_resp") do restart and get next mistakes: sep 22 14:17:15 vms-vms-spx-1 kamailio[581922]: ERROR: <core> [core/modparam.c:169]: set_mod_param_regex(): parameter <cdr_json_pre_encoded_prefix> of type <1:string> not found in module <acc_json> сен 22 14:17:15 vms-vms-spx-1 kamailio[581922]: CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio_vmsspx/modules.cfg, line 125, column 63: Can't set module parameter sep 22 14:17:15 vms-vms-spx-1 kamailio[581922]: ERROR: bad config file (1 errors) (parsing code: 0) sep 22 14:17:15 vms-vms-spx-1 systemd[1]: kamailio_vmsspx.service: Control process exited, code=exited status=255 sep 22 14:17:15 vms-vms-spx-1 systemd[1]: kamailio_vmsspx.service: Failed with result 'exit-code'. What’s wrong? I used: [opodguyko@vms-vms-spx-1 ~]$ kamailio -version version: kamailio 5.5.3 (x86_64/linux) b02728-dirty 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: b02728 -dirty compiled on 15:35:46 Dec 15 2021 with gcc 8.3.1 [opodguyko@vms-vms-spx-1 ~]$ This parameter was added at release 5.5.0 Oleg Podguyko

3 3

Choose RTP port in routing script
by Duarte Rocha 26 Sep '23

26 Sep '23

Hello all, I have my rtpengine configured to use ports 20000 - 50000 for RTP in rtpengine.conf. Now i want to able to select the port or the port range in a call by call basis. Is that possible? I've tried to use "media-address" flag on rtpengine_manage but i wasn't successful. Thanks in advance, Cheers, Duarte Rocha

2 1

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