sr-users March 2020

sr-users@lists.kamailio.org

64 participants
83 discussions

Segmentation fault in DMQ module
by Virgílio Cunha 27 Mar '20

27 Mar '20

Hello, I have in production environment with 4 proxies using DMQ to sync terminal registers and the DMQ configuration parameters is following: loadmodule "dmq.so" #modparam("dmq", "server_address", "sip:MY_IP_ADDRESS:MY_PORT_ADDRESS") modparam("dmq", "notification_address", "DMQ_HOSTS") modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 4) In the lab environment with the same configuration that in prod, I can simulate this problem with 12000 terminal REGISTERS and, when doing several restarts on a proxy, one of them is generated a coredump. Analyzing the core, I can see that the problem is concurrency in the dmq synchronization. Job_queue_size (...) is called with a valid *queue *and, but inside this function, the *queue *is null. (gdb) up #1 0x00007fefe58ee246 in job_queue_size (queue=0x0) at worker.c:254 254 return atomic_get(&queue->count); (gdb) print queue $1 = (job_queue_t *) 0x0 (gdb) up #2 0x00007fefe58ed920 in add_dmq_job (msg=0x7ff028b453f8, peer=0x7fefebcc4df8) at worker.c:184 184 if(job_queue_size(workers[i].queue) == 0) { (gdb) print i $2 = 1 (gdb) print workers[i].queue $3 = (job_queue_t *) 0x7fefebce49b0 If I configure DMQ with num_workers=1 I can't reproduce this problem. I'm using the kamailio 5.0.8 release. Is this problem known to you? What is the right way to solve it? Best Regards, Virgílio Cunha

3 7

Multiple advertise addresses per socket
by Sergiu Pojoga 25 Mar '20

25 Mar '20

Hi there, Question: how can I advertise and later match multiple FQDNs per socket? Example: auto_aliases=no alias="mydomain.net":5060 alias="mydomain.net":5061 alias="client1.mydomain.net":5060 alias="client1.mydomain.net":5061 # looks like I can advertise only one address per socket? listen=udp:65.65.65.65:5060 advertise "mydomain.net":5060 listen=tls:65.65.65.65:5061 advertise "mydomain.net":5061 Adding RR before relaying downstream like so: record_route_preset("client1.mydomain.net:5061;transport=tls;r2=on", "client1.mydomain.net:5060;r2=on"); This is the warning (just warning, works fine otherwise) after receiving for example the ACK from upstream following the 200 OK: *WARNING*: {1 19082 ACK } rr [loose.c:768]: rr_do_force_send_socket(): no socket found to match second RR (sip:client1.mydomain.net:5061 ;transport=tls;lr;r2=on) Figured warning itself can be turned off with modparam "enable_socket_mismatch_warning" of RR, still I'd like to know if I'm doing something wrong or there's a better way. Much obliged, --Sergiu

2 3

Kamailio 5.3.2 - Signal 11 on startup
by José Seabra 25 Mar '20

25 Mar '20

Hello there, I'm facing an issue with kamailio 5.3.2 when it is starting up, it breaks with signal 11 and generates a coredump file: - https://pastebin.com/FSqyGFp8 This seems to be something related to dmq module, kamailio exits with signal 11 when it receives a DMQ notification_peer message. I did a few more tests and I noticed that problem disappears if I configure DMQ with one worker only, which takes me to think that it's something related to concurrency. Best regards -- Cumprimentos José Seabra

2 7

about kamailio.cfg NAT test
by Juha Heinanen 24 Mar '20

24 Mar '20

In kamailio/etc/kamailio.cfg NAT test is based on nat_uac_test("19"). 19 includes test 16: 16 - Test if the source port is different from the port in the “Via” header. If the “Via” header contains no port, it uses the default SIP port 5060 Based on a couple of tests using baresip, looks like that results in false positive when UA connects to SIP proxy via TCP. An example: T 2020/03/24 13:57:12.685441 192.26.134.10:38940 -> 192.26.134.1:5060 [AP] #127 REGISTER sip:test.tutpro.com SIP/2.0. Via: SIP/2.0/TCP 192.26.134.10:44717;branch=z9hG4bK5b6aa423104ef942;rport. Does someone know why test 16 is included? -- Juha

3 5

Transformations - urlencode
by João Vitor Arruda 24 Mar '20

24 Mar '20

Hello, I was looking in the transformation documentation ( https://www.kamailio.org/wiki/cookbooks/devel/transformations) something to URL encode a pv or var for use in a HTTP query but was not able to find it. Digging a bit in the source code I found that "s.urlencode.param" actually exists and from my initial tests it works just fine. I'm wondering if there is any reason why this is not mentioned in the documentation of if it should not be used at all. Thanks, Joao Arruda

3 3

Manipulating contacts header results in a malformed SIP packet
by Andrew White 23 Mar '20

23 Mar '20

Hi all, Hope everyone is well, and looking forward to seeing you all whenever Kamailio World ends up being! I’m currently dealing with an issue which I’m unsure if it’s due to my own implementation, or a bug. When attempting to manipulate the Contact header via app_ruby, the SIP message I send ends up being malformed. Here’s the code I’m using: def replace_contact_header(uri) #KSR::HDR.remove("Contact") if KSR::HDR.is_present('Contact') > 0 #KSR::HDR.append("Contact: #{uri}\r\n") KSR::HDR.rmappend("Contact", "Contact: #{uri}\r\n") end Note that I have tried both rmappend and the commented out functions too. I call this with a custom built URI, such as <61400123123(a)kamailio.test.uconnected.com.au <mailto:61400123123@kamailio.test.uconnected.com.au>>. This function is called just before a KSR::TM.t_relay(). Here’s the result I get watching from tshark (some info scrubbed for privacy): Record-Route: <sip:1.2.3.4;lr;ftag=e3p42efd3635HH;vst=AAAAAAAAAAAAAAAAAAAAAAoUXVFHDQAAs83AEGwAAFgwCQA8QY3RlZC5jb20uYXU-;did=927.f0f2> … Call-ID: 3de29646-e423-1238-e712-023563fb337c CSeq: 17736747 INVITE sip:4.5.6.7:5060;alias=10.100.1.1~5060~1Content-Type: application/sdp Content-Length: 483 Contact: <sip:61400123123@kamailio.test.uconnected.com.au> In this case, 4.5.6.7 is the PBX I made the call from (and the value of the original Contact header), and 1.2.3.4 is what kamailio.test.uconnected.com.au <http://kamailio.test.uconnected.com.au/> resolves to, and is this Kamailio instance. Here’s a copy of the same thing when I don’t call my replace_contact_header function and t_relay: Record-Route: <sip:1.2.3.4;lr;ftag=j6jebCSa5Qap6c;vst=AAAAAAAAAAAAAAAAAAAAAAoUXVND38dTgwEGEAEGwAAFgwCQA8Fdn83lZC5jb20uYXU-;did=827.40b> ... Call-ID: 249571c5-e91a-ae91-6d8e-023563fb337c CSeq: 17735867 INVITE Contact: <sip:4.5.6.7:5060;alias=10.100.1.1~5060~1> Content-Type: application/sdp Content-Length: 483 Given the relative simplicity of the function, I have to assume this is an error with how the function is manipulating the existing Contact header? It seems that the “Contact: <“ part of the header is being removed as well as the “>\r\n", but the rest being left. I’m currently using commit 283e468401d809ca9b71368c32badf3a70d48b8b <https://github.com/kamailio/kamailio/commit/283e46> on Amazon Linux 2, which is CentOS/RHEL based. Thanks! Andrew

5 7

Pike Module Clarification
by JR Richardson 23 Mar '20

23 Mar '20

Hi All, Please clarify the pike settings for SIP message count, the module Doc reports: ---- modparam("pike", "sampling_time_unit", 10) modparam("pike", "reqs_density_per_unit", 30) How many requests should be allowed per sampling_time_unit before blocking all the incoming request from that IP. Practically, the blocking limit is between ( let's have x=reqs_density_per_unit) x and 3*x for IPv4 addresses and between x and 8*x for IPv6 addresses. ----- So the example above the SIP message rate is 30 messages within 10 seconds triggers an pike alert? The description I'm confused on is "Practically, the blocking 'limit is between' (let's have x=reqs_density_per_unit) x and 3*x for IPv4" The way this reads to me is the Pike alert could be triggered anywhere between 30 and 90 (3*30) messages within 10 second period. Am I reading this correctly? What determines when the pike trigger actually happens, could the trigger happen at say 56 messages within 10 seconds? Thanks. JR Richardson Engineering for the Masses Chasing the Azeotrope JRx DistillCo 1'st Place Brisket 1'st Place Chili

4 7

set_advertised_address not accepting vars
by Sergiu Pojoga 22 Mar '20

22 Mar '20

Hi there, The function doesn't appear to accept vars. For example, set_advertised_address("$var(someaddress)") results in a VIA of string $var(someaddress), instead of var's value. https://www.kamailio.org/wiki/cookbooks/5.3.x/core#set_advertised_address kamailio 5.3.2 (x86_64/linux) 0bed10 Cheers. --Sergiu

3 3

pipelimit: inexistent pipe error logs
by Nuno Ferreira 20 Mar '20

20 Mar '20

Hi all, I'm using pipelimit with the "clean_unused" option to get rid of pipes that are not used for quite some time. At the same time we are monitoring pipelimit with a jsonrpc call similar to: # curl --header 'Content-Type: application/json' --data-binary '{"id": 1, "jsonrpc": "2.0", "method": "pl.list", "params": ["pipe_INVITE"]' http://127.0.0.1:8000/RPC Reply: { "jsonrpc": "2.0", "error": { "code": 400, "message": "Unknown pipe id pipe_INVITE" }, "id": 1 } The above reply is valid because the pipe_INVITE was not loaded yet, but the request makes kamailio to log the following log messages: Jan 20 11:21:48 proxy1 kamailio[24474]: ERROR: pipelimit [pl_ht.c:519]: rpc_pl_list(): no pipe: pipe_INVITE Jan 20 11:21:48 proxy1 kamailio[24474]: ERROR: <core> [core/parser/parse_fline.c:262]: parse_first_line(): parse_first_line: bad message (offset: 20) Jan 20 11:21:48 proxy1 kamailio[24474]: [466B blob data] Since the monitoring system does periodic requests, those log lines get a bit annoying and fill the log with ERROR messages that aren't really errors. IMHO the first log line should be converted to DEBUG instead of ERROR, but I have some doubts about the one from parse_fline.c:262. parse_first_line() is used to process both SIP and HTTP. It makes sense to log ERROR if SIP but not in the case of HTTP... Regarding the "[466B blob data]" I really don't know from where it's coming from. I can submit a PR, but I would like to have first some feedback from you. Thank you, Nuno -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

3 10

is_gflag Always Returns FALSE
by Yufei Tao 20 Mar '20

20 Mar '20

Hi, I got some problems with is_gflags: 1. Set the gflag: # kamcmd cfgutils.set_gflag 1024 2. Check the gflags - fine: # kamcmd cfgutils.get_gflags 0x400 (1024) 3. Check using is_gflag - problem: # kamcmd cfgutils.is_gflag 1024 FALSE Seems is_gflag always returns FALSE somehow. Calling function is_gflag() from the cfg file seems to always return FALSE too. I tried this on Kamailio 5.3.2 and 5.3.3 and the behaviour is the same. Best regards, Yufei

2 5

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

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 March 2020