[SR-Users] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > is it the latest stable point version 5.6.2, or the latest version from > branch 5.6? Latest from 5.6. I just built new Debian package like this: MEMDBG=1 $(MAKE) FLAVOUR=kamailio cfg prefix=/usr cfg_prefix=$(BASEDIR) ... -I does not show DBG_QM_MALLOC.

[SR-Users] Re: [sr-dev] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Daniel-Constantin Mierla
Not the original developer of the memory managers, but, iirc, one of the reasons for private memory manager was to avoid a multi-threading related lock/mutex that is done by system malloc()/free(), which is not necessary for pure multi-process application. I did not analyzed myself, but I guess

[SR-Users] Re: Call drop when reinvite is proceed

2023-01-05 Thread Alex Balashov
Nathan, It is only valid to add a Record-Route header to an initial INVITE (NOT within a dialog), because it tells both parties to the dialog where to send in-dialog requests (e.g. re-invites, BYE, e2e ACK) -- the kind handled in route[WITHINDLG}. So, this is quite radiantly wrong, though it

[SR-Users] Re: Too many 200:OK sip responses

2023-01-05 Thread Henning Westerholt
Hello, from which database you want to delete the calls? Usually this is not needed. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com From: Waqar 40 Sent: Thursday, January 5, 2023 10:51 AM To: Kamailio (SER) -

[SR-Users] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Alex Balashov
Thanks, that's educational. I assumed the original argument was performance-related. I just wasn't sure if that was still (sufficiently to be important) true. After all, lots of SER/OpenSER design decisions in the early 2000s made the most sense then, like inventing own imperative scripting

[SR-Users] Re: Call drop when reinvite is proceed

2023-01-05 Thread Nathan C
Hello Daniel, Thank you for the information. It works well. If it can help someone, I added in route[WITHINDLG]: if (is_method("INVITE")) { record_route(); } Thank you all for your help. Regards, Nathan __ Kamailio

[SR-Users] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Henning Westerholt
Just to add, this paper gives a lot of benchmark results for different allocators and two glibc versions: https://adms-conf.org/2019-camera-ready/durner_adms19.pdf It seems that even in 2019 using a special allocator can have some benefits for certain workloads. Cheers, Henning -- Henning

[SR-Users] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Henning Westerholt
(adding sr-dev) Hi Alex, the memory allocator of glibc was not really efficient regarding the particular needs of a SIP server (allocation of many small string objects). That has probably improved in the last years, also system performance just got much faster. Other programs/tools also use

[SR-Users] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Alex Balashov
> On Jan 5, 2023, at 9:40 AM, Henning Westerholt wrote: > > Hello Alex, > > there might be some performance implications by switching to system malloc. > There is also easier debugging by internal Kamailio memory manager support. > > In this particular example with the leak, Kamailio would

[SR-Users] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Henning Westerholt
Hello Alex, there might be some performance implications by switching to system malloc. There is also easier debugging by internal Kamailio memory manager support. In this particular example with the leak, Kamailio would use in the end all of the system memory, and the machine out of memory

[SR-Users] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Alex Balashov
This prompts a question that isn't really related to the problem, but I have wondered for some time: What are the downsides of removing PKG_MALLOC and using the libc allocator? It seems like it would provide unlimited package memory and remove the need to manage it, but I assume there is a

[SR-Users] Re: Too many 200:OK sip responses

2023-01-05 Thread David Villasmil
So you’re saying you do see the 200 from the b-leg? Shouldn’t you try to see why kamailio is not detecting it and forwarding it to the a-leg so the a-leg can send an ACK and finish the transaction properly? On Thu, 5 Jan 2023 at 11:21, Waqar 40 wrote: > Yes. The ACK is missing. Kamailio does

[SR-Users] Re: Call drop when reinvite is proceed

2023-01-05 Thread Daniel-Constantin Mierla
Hello, On 05.01.23 10:16, Nathan C wrote: > Hello all, > > Thank you for your all your answers > > I checked the headers and I 've seen several things: > > 1/ In the Invite I see : > sip:test@KAMAILIO_SERVER_IP > > In the reinvite i see: > sip:remote_endpoint > via Kamailio IP address > > 2/

[SR-Users] Re: Too many 200:OK sip responses

2023-01-05 Thread Waqar 40
Yes. The ACK is missing. Kamailio does not receive 200:OK from calling points for these calls. How can I identify these calls which are in session and was in a ringing state? I want to delete their data from the database. On Thu, Jan 5, 2023 at 1:03 PM Olle E. Johansson wrote: > > > > On 5 Jan

[SR-Users] Re: Call drop when reinvite is proceed

2023-01-05 Thread Nathan C
Hello all, Thank you for your all your answers I checked the headers and I 've seen several things: 1/ In the Invite I see : sip:test@KAMAILIO_SERVER_IP In the reinvite i see: sip:remote_endpoint via Kamailio IP address 2/ In the call flow everything is going well until the ack. At the

[SR-Users] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Daniel-Constantin Mierla
Hello, is it the latest stable point version 5.6.2, or the latest version from branch 5.6? Is it accounting done to database, syslog or radius? Cheers, Daniel On 05.01.23 00:13, Juha Heinanen wrote: > In latest stable K release, we noticed pkg memory leak (pgk memory usage > increases by each

[SR-Users] Re: pkg memory leak when acc module cdr_enabled

2023-01-05 Thread Henning Westerholt
Hi Juha, there have been some changes related to that modules indeed for the latest release. Using memory debugging (http://www.kamailio.org/wiki/tutorials/troubleshooting/memory), in particular the statistics and/or memory dump will probably show the place where its allocated. Then we could