From dteurlings@signet.nl Tue May 12 10:03:16 2015 From: "Dirk Teurlings - SIGNET B.V." To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] Keep-Alive in dialog "freeing a free fragment" Date: Tue, 12 May 2015 10:03:10 +0200 Message-ID: <5551B3BE.4050009@signet.nl> In-Reply-To: <5550C9D8.7010707@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1112517332==" --===============1112517332== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Daniel, This fixes the problem, thanks very much, Will this fix be included in the next (4.2 and/or 4.3) stable release? Cheers, Dirk Teurlings On 11-05-15 17:25, Daniel-Constantin Mierla wrote: > Following quickly up, I pushed another patch that will remove the dialog > from keepalive list as soon as 'deleted' state is discovered and also > sends keepalive options only if dialog is in state 'confirmed'. > > Can you test the patch and see how it works? > > - > https://github.com/kamailio/kamailio/commit/0e22abe2b89be8936df4b8230955fba= f43ad40e7 > > Cheers, > Daniel > > On 11/05/15 16:55, Daniel-Constantin Mierla wrote: >> Hello, >> >> the message "freeing a free fragment ..." is from Dialog KA Timer and >> that process doesn't handle any SIP reply or the transmission timeout >> callback. I will look at the code and see if I can spot where the double >> free happens. >> >> But now I understand that the dialog is actually not ended, right? >> >> Cheers, >> Daniel >> >> >> On 07/05/15 17:05, Dirk Teurlings - SIGNET B.V. wrote: >>> Hi Daniel, >>> >>> Good to see you found an improvement, not sure yet if it'll help us. >>> >>> Here is the non-debug log first. Just now I noticed that the initial >>> dialog doesn't get ended as well now, 5fa4dc3670596fb626269f083b0c9480 >>> in the log. >>> >>> The setup is like this >>> >>> Leg 1 Kamailio -> Asterisk >>> Leg 2 (initialized by Asterisk) -> Kamailio -> Gateway >>> >>> First the output of ps >>> >>> Process:: ID=3D0 PID=3D21528 Type=3Dattendant >>> Process:: ID=3D1 PID=3D21530 Type=3Dudp receiver child=3D0 sock=3D127.0.= 0.1:5060 >>> Process:: ID=3D2 PID=3D21531 Type=3Dudp receiver child=3D0 >>> sock=3D192.168.10.246:5060 >>> Process:: ID=3D3 PID=3D21532 Type=3Dudp receiver child=3D0 >>> sock=3D31.223.168.246:5060 >>> Process:: ID=3D4 PID=3D21533 Type=3Dudp receiver child=3D0 sock=3D[::1]:= 5060 >>> Process:: ID=3D5 PID=3D21534 Type=3Dudp receiver child=3D0 >>> sock=3D[2001:4cb8:34a:10::246]:5060 >>> Process:: ID=3D6 PID=3D21535 Type=3Dslow timer >>> Process:: ID=3D7 PID=3D21536 Type=3Dtimer >>> Process:: ID=3D8 PID=3D21537 Type=3DMI FIFO >>> Process:: ID=3D9 PID=3D21538 Type=3Dctl handler >>> Process:: ID=3D10 PID=3D21539 Type=3DTIMER NH >>> Process:: ID=3D11 PID=3D21540 Type=3DDialog KA Timer >>> Process:: ID=3D12 PID=3D21541 Type=3DDialog Clean Timer >>> Process:: ID=3D13 PID=3D21542 Type=3DWLCC TB TIMER >>> Process:: ID=3D14 PID=3D21543 Type=3DLLCC TB TIMER >>> Process:: ID=3D15 PID=3D21544 Type=3Dtcp receiver (generic) child=3D0 >>> Process:: ID=3D16 PID=3D21545 Type=3Dtcp main process >>> >>> And the log >>> >>> May 7 18:54:43 vps-host /usr/sbin/kamailio[21532]: INFO: