Thanks for the reply,
I didn't find any suspicious logs in kamailio apart from the log which i shared with you in chain mail.
Within a Pcap trace, we typically process INVITE, 300 Multiple Choice responses, and ACK messages pertaining to a specific server
Note: For these drop requests, How do we acknowledge in kamailio?
-- Is it possible to manage these drop requests in the Kamailio configuration file without actually dropping the request?
Let me know if you need more information.
That looks to me that an ACK was received at kamailio for a response
that it generated (not relayed) to the UAC. It's normal for the SL
module to absorb such an ACK. It's not an error condition.
Your original message was about "core:drop_requests", so I doubt that
it's related.
My same advice applies: take traces and logs, and correlate them.
> Also I have another query, For these drop requests, How do we acknowledge in kamailio?
What do you mean, exactly?
James
On Thu, 26 Oct 2023 at 13:11, satyaprakash ch
<chiramchetty.satyaprakash@gmail.com> wrote:
>
> Hi,
>
> Thanks for the reply,
>
> When I was testing, I found the below log.
>
> Log ==== DEBUG: sl [sl_funcs.c:462]: sl_filter_ACK(): SL local ACK found -> dropping it!
>
> On Wed, Oct 25, 2023 at 12:44 PM Henning Westerholt <hw@gilawa.com> wrote:
>>
>> Hello,
>>
>> the sanity module can be used for request and reply checks, as e.g. visible in the default configuration.
>> It might be a bit too short documented in the module readme.
>>
>> Cheers,
>>
>> Henning Westerholt
>>
>> --
>> Henning Westerholt - https://skalatan.de/blog/
>> Kamailio services - https://gilawa.com
>>
>>
>>
>> > -----Original Message-----
>> > From: James Browne via sr-users <sr-users@lists.kamailio.org>
>> > Sent: Dienstag, 24. Oktober 2023 17:55
>> > To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
>> > Cc: satyaprakash ch <chiramchetty.satyaprakash@gmail.com>; James Browne
>> > <james@frideo.com>
>> > Subject: [SR-Users] Re: Inquiry Regarding Kamailio Behavior and Drop
>> > Requests
>> >
>> > I expect that it's not related, because the documentation is clear that the
>> > function relates to requests, not responses.
>> >
>> > https://kamailio.org/docs/modules/5.5.x/modules/sanity.html#sanity.f.sanit
>> > y_check
>> > - 4.1. sanity_check([msg_checks [, uri_checks]])
>> > - This function makes a row of sanity checks over the given SIP request...
>> >
>> > It seems simple: check the logs from the xlog command and see what you find.
>> > If it's not clear enough, add the Call-ID to the log message, and then also
>> > capture (tshark/tcpdump) traffic for subsequent analysis.
>> >
>> > James
>> >
>> > On Mon, 16 Oct 2023 at 16:52, satyaprakash ch via sr-users <sr-
>> > users@lists.kamailio.org> wrote:
>> > >
>> > > Hi,
>> > >
>> > > We possess a code within Kamailio, which specifically handles malformed SIP
>> > responses. Below is the code snippet:
>> > >
>> > > reply_route
>> > > Copy code
>> > > if(!sanity_check("17604", "6")) {
>> > > xlog("Malformed SIP response from $si:$sp\n"); drop;
>> > >
>> > > Additionally, we have Kamailio drop request statistics as follows:
>> > >
>> > > Command: kamctl stats | grep core:drop_requests Output of the command:
>> > > core:drop_requests = 5
>> > >
>> > > My queries are:
>> > >
>> > > 1. Is the aforementioned "reply_route" related to the drop requests we are
>> > experiencing?
>> > > 2. If it is not related, what could be the cause of the drop requests?
>> > > __________________________________________________________
>> > > Kamailio - Users Mailing List - Non Commercial Discussions To
>> > > unsubscribe send an email to sr-users-leave@lists.kamailio.org
>> > > Important: keep the mailing list in the recipients, do not reply only to the
>> > sender!
>> > > Edit mailing list options or unsubscribe:
>> > __________________________________________________________
>> > Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe
>> > send an email to sr-users-leave@lists.kamailio.org
>> > Important: keep the mailing list in the recipients, do not reply only to the
>> > sender!
>> > Edit mailing list options or unsubscribe: