Inquiry Regarding Kamailio Behavior and Drop Requests

List overview All Threads
Download

newer

older

Kamailio 5.4.3 Troubleshooting...

Information about Kamailio...

satyaprakash ch

16 Oct 2023 16 Oct '23

6:40 p.m.

Hi, We possess a code within Kamailio, which specifically handles malformed SIP responses. Below is the code snippet: *reply_routeCopy 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?

Attachments:

attachment.html (text/html — 805 bytes)

Show replies by date

satyaprakash ch

17 Oct 17 Oct

4:06 p.m.

Hi, Any reply would be appreciated. On Mon, Oct 16, 2023 at 10:10 PM satyaprakash ch < chiramchetty.satyaprakash(a)gmail.com> wrote:

...

James Browne

24 Oct 24 Oct

5:54 p.m.

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.sanity… - 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(a)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(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:

Henning Westerholt

25 Oct 25 Oct

9:14 a.m.

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(a)lists.kamailio.org> Sent: Dienstag, 24. Oktober 2023 17:55 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Cc: satyaprakash ch <chiramchetty.satyaprakash(a)gmail.com>om>; James Browne <james(a)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(a)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(a)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(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:

satyaprakash ch

26 Oct 26 Oct

3:10 p.m.

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(a)gilawa.com> wrote:

...

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(a)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(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only

to the

sender!

Edit mailing list options or unsubscribe:

the

sender! Edit mailing list options or unsubscribe:

satyaprakash ch

4:39 p.m.

Hi, Also I have another query, For these drop requests, How do we acknowledge in kamailio? On Thu, Oct 26, 2023 at 6:40 PM satyaprakash ch < chiramchetty.satyaprakash(a)gmail.com> wrote:

...

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

malformed SIP

we are

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(a)lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only

to the

sender! Edit mailing list options or unsubscribe:

James Browne

4:48 p.m.

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(a)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(a)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(a)lists.kamailio.org> > > Sent: Dienstag, 24. Oktober 2023 17:55 > > To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > > Cc: satyaprakash ch <chiramchetty.satyaprakash(a)gmail.com>om>; James Browne > > <james(a)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(a)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(a)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(a)lists.kamailio.org > > Important: keep the mailing list in the recipients, do not reply only to the > > sender! > > Edit mailing list options or unsubscribe:

satyaprakash ch

5:01 p.m.

...

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(a)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(a)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(a)lists.kamailio.org> > > Sent: Dienstag, 24. Oktober 2023 17:55 > > To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > > Cc: satyaprakash ch <chiramchetty.satyaprakash(a)gmail.com>om>; James

Browne

> > <james(a)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(a)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(a)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(a)lists.kamailio.org > > Important: keep the mailing list in the recipients, do not reply only

to the

> > sender! > > Edit mailing list options or unsubscribe:

James Browne

5:31 p.m.

I don't think it's possible. It's definitely not _always_ possible. For example, if a non-SIP message arrives to kamailio, then the request_route is never going to run, because the core will drop the message first. If I was to troubleshoot this further, then I'd get logs with (millisecond) timestamps, take pcap traces at the same time, and then later see what matches. That's how I'll know which SIP messages (or IP packets) are getting dropped (to make the core:drop_requests statistic). I don't know how else to do it, but I expect that this should certainly work. James On Thu, 26 Oct 2023 at 15:01, satyaprakash ch <chiramchetty.satyaprakash(a)gmail.com> wrote:

...

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. On Thu, Oct 26, 2023 at 8:18 PM James Browne <james(a)frideo.com> wrote: > > 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(a)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(a)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(a)lists.kamailio.org> > >> > Sent: Dienstag, 24. Oktober 2023 17:55 > >> > To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > >> > Cc: satyaprakash ch <chiramchetty.satyaprakash(a)gmail.com>om>; James Browne > >> > <james(a)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(a)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(a)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(a)lists.kamailio.org > >> > Important: keep the mailing list in the recipients, do not reply only to the > >> > sender! > >> > Edit mailing list options or unsubscribe:

196

days inactive

206

days old

sr-users@lists.kamailio.org

Manage subscription

8 comments

3 participants

tags (0)

participants (3)

Henning Westerholt
James Browne
satyaprakash ch