[SR-Users] Re: Kamailio hangs on get_profile_size method.
HI,
Could someone please respond? It would be greatly appreciated.
On Sat, Aug 10, 2024 at 9:06 AM satyaprakash ch <
chiramchetty.satyaprak...@gmail.com> wrote:
> HI,
>
> We are facing a hang issue with Kamailio for the get_profile_size method.
> Randomly, the Kamailio got hangs, and the CPU went 100%.
> During the hanging time, we generated the TRAP and we could see that the
> hang happened on the get_profile_size method. We are getting this hang
> randomly in dlg_profile.c of the following lines:
>
> The hang occurs, causing the CPU to spike to 100% at one of the following
> lines randomly:
>
> 1. if(value->len == ph->value.len && memcmp(value->s, ph->value.s,
> value->len) == 0) {
> 2. ph = ph->next;
> 3. while(ph != profile->entries[i].first);
>
> During our analysis, we found that PROCESS ID 7608 gets a spike of 100%
> utilization.
>
> We suspect there may be an issue with the processing of the 'ph' variable,
> but we couldn't identify the root cause. I've attached the Kamailio TRAP
> for further details. Could you please suggest what might be causing this
> problem and how we can resolve it?
>
> Thank you.
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Kamailio hangs on get_profile_size method.
HI,
We are facing a hang issue with Kamailio for the get_profile_size method.
Randomly, the Kamailio got hangs, and the CPU went 100%.
During the hanging time, we generated the TRAP and we could see that the
hang happened on the get_profile_size method. We are getting this hang
randomly in dlg_profile.c of the following lines:
The hang occurs, causing the CPU to spike to 100% at one of the following
lines randomly:
1. if(value->len == ph->value.len && memcmp(value->s, ph->value.s,
value->len) == 0) {
2. ph = ph->next;
3. while(ph != profile->entries[i].first);
During our analysis, we found that PROCESS ID 7608 gets a spike of 100%
utilization.
We suspect there may be an issue with the processing of the 'ph' variable,
but we couldn't identify the root cause. I've attached the Kamailio TRAP
for further details. Could you please suggest what might be causing this
problem and how we can resolve it?
Thank you.
<>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: Kamailio hang Issue
Hi,
Thank you for the update.
We encountered a core dump, and the hang occurred at the following code
point. According to the core dump, value->len is 7, while ph->value.len is
null.
*if (value->len == ph->value.len && memcmp(value->s, ph->value.s,
value->len) == 0) {*Link:
https://github.com/kamailio/kamailio/blob/5.5/src/modules/dialog/dlg_profile.c#L854C1-L855C1
Could you please provide your suggestions?
On Mon, Aug 5, 2024 at 3:22 PM Henning Westerholt wrote:
> Hello,
>
>
>
> there is a command to get a backtrace from the hanging processes, refer
> e.g. to:
>
> https://lists.kamailio.org/pipermail/sr-users/2015-September/090121.html
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
>
>
> *From:* satyaprakash ch via sr-users
> *Sent:* Sonntag, 4. August 2024 14:43
> *To:* Kamailio (SER) - Users Mailing List
> *Cc:* satyaprakash ch
> *Subject:* [SR-Users] Kamailio hang Issue
>
>
>
> Hi,
>
>
>
> We are encountering a hang issue after deploying the following code:
>
>
> *route(DLG_MANAGE);*
>
>
>
>
>
>
>
>
>
>
> * if ($dlg_var(voip_id) == $null) { $dlg_var(voip_id) =
> $hdr(X-Voip-ID); } route[DLG_MANAGE] { if (is_method("INVITE")) {
> dlg_manage(); } }*
>
> This code includes the set_dialog_profile. We have this setup with 2
> proxy servers with DMQ enabled, but the issue only occurs on one proxy.
>
> When the Kamailio proxy hangs, no logs are written.
>
> If you have any suggestions to resolve this issue, please help.
>
> Thanks.
>
>
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Kamailio hang Issue
Hi,
We are encountering a hang issue after deploying the following code:
*route(DLG_MANAGE);*
*if ($dlg_var(voip_id) == $null) {$dlg_var(voip_id) =
$hdr(X-Voip-ID);}route[DLG_MANAGE] {if (is_method("INVITE")) {
dlg_manage();}}*
This code includes the set_dialog_profile. We have this setup with 2 proxy
servers with DMQ enabled, but the issue only occurs on one proxy.
When the Kamailio proxy hangs, no logs are written.
If you have any suggestions to resolve this issue, please help.
Thanks.
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Assistance Needed to Resolve Duplicate Contact Headers in 200 OK Response
Hi We are receiving 2 to 3 contact headers in the 200 OK response of the registration request. It appears that the `user_location` is updating multiple contact headers for the same extension due to network disconnections. Please suggest a solution to avoid duplicates in the `user_location` module, or how to ensure that only the latest single contact header is included in the 200 OK response. Your suggestion would be appreciated. Thanks and regards, Satyaprakash. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] How to set "set_dialog_profile" value for Leg-a and leg-b.
Hi, We are using kamailio and freeswitch, So when we make a call from A to B the call is going via "kamailio -> freeswitch" and "freeswitch -> kamailio". Please suggest me how i can set "set_dialog_profile" for both legs with unique value in kamailio config file. Thanks. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: Compatibility issue between proxy and registrar
Thanks for the update, Q: You are using DMQ to replicate usrloc between registrars ? A: Yes. On Thu, Apr 25, 2024 at 8:42 PM Julien Chavanton wrote: > You are using DMQ to replicate usrloc between registrars ? > This should not affect the "proxy servers", although their exact role is > not mentioned. > If this is the case, you could do some kamcmd ul.dump on both registrars. > Also the DMQ traffic can be traced by tcpdump etc. > > You may also want to validate the DMQ bus, "the way each node learns about > the other ones." > > On Thu, Apr 25, 2024 at 10:46 AM satyaprakash ch via sr-users < > sr-users@lists.kamailio.org> wrote: > >> Hi, >> >> There are two proxy servers and two registrar servers with DMQ enabled, >> and we have upgraded the proxy servers to 5.7.4 and the registrar servers >> to 5.5.5. >> >> Kamailio proxy version 5.7.4 >> Kamailio registrar version: 5.5.5 >> >> Following the upgrade of the proxy server to 5.7.4, calls are not working >> and no response is received. >> Once again, we have reverted the proxy server to 5.5.5, so that the proxy >> server and the registrar server version are now the same.The calls are now >> working as expected. >> >> We suspect it could be an DMQ issue. >> >> I would appreciate your suggestions on this matter of compatibility >> between proxy and registry servers. >> >> Thanks. >> __ >> Kamailio - Users Mailing List - Non Commercial Discussions >> To unsubscribe send an email to sr-users-le...@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-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Compatibility issue between proxy and registrar
Hi, There are two proxy servers and two registrar servers with DMQ enabled, and we have upgraded the proxy servers to 5.7.4 and the registrar servers to 5.5.5. Kamailio proxy version 5.7.4 Kamailio registrar version: 5.5.5 Following the upgrade of the proxy server to 5.7.4, calls are not working and no response is received. Once again, we have reverted the proxy server to 5.5.5, so that the proxy server and the registrar server version are now the same.The calls are now working as expected. We suspect it could be an DMQ issue. I would appreciate your suggestions on this matter of compatibility between proxy and registry servers. Thanks. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: Kamailio crash due to UDP receiver child (kamailio 5.5.5)
Thank you for the update, Will you suggest which version do we upgrade to?, Does this crash can fix in supported version. Please advise. On Tue, Apr 16, 2024 at 11:22 PM Who AmI wrote: > Hi There, > > I have had similar issues and this was found to be the child processes > being stalled - either by network or timeouts to DB at load etc. YMMV > though. > > Henning is absolutely correct, you should update to the supported > versions. > > Thanks, > > John. > > > On Tue, 16 Apr 2024 at 14:41, Henning Westerholt via sr-users < > sr-users@lists.kamailio.org> wrote: > >> Hello, >> >> >> >> the usual suggestion is to first upgrade to a supported version, as 5.5.x >> is end of life. Please upgrade to e.g. 5.8.1 version. You will need >> probably a bit of kamailio cfg adaptions and maybe some DB script adaptions. >> >> >> >> Cheers, >> >> >> >> Henning >> >> >> >> *From:* satyaprakash ch via sr-users >> *Sent:* Dienstag, 16. April 2024 14:39 >> *To:* Kamailio (SER) - Users Mailing List >> *Cc:* satyaprakash ch >> *Subject:* [SR-Users] Kamailio crash due to UDP receiver child (kamailio >> 5.5.5) >> >> >> >> Hi, >> >> The kamailio version we are using is "5.5.5", We are facing a kamailio >> crash issue recently and it has generated the core-dump. Based on the >> core-dump analysis we could see that "*si_desc = "udp receiver child=3" >> *getting >> crashed. We could see the below error in the core-dump trace, >> >> #22 0x562c33524750 in udp_rcv_loop () at core/udp_server.c:543 >> >> tmp = 0x1150955ff0 >> >> >> Please suggest how to fix this and your inputs will be appreciated. >> >> Note: Due to confidentiality, I'm not able to share the core-dump trace. >> >> Thanks. >> >> >> __ >> Kamailio - Users Mailing List - Non Commercial Discussions >> To unsubscribe send an email to sr-users-le...@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-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] compile without downtime
HI I currently have two proxy servers running in my environment, and I want to upgrade Kamailio from version 5.4.7 to 5.6. Can I recompile the Kamailio service before restarting it without downtime ? Will there be any impact on my production environment if I recompile Kamailio to the newer version? If there is no impact, I expect approximately 2 minutes of downtime during the service restart. Here's the scenario: *No Downtime:* Clone the Kamailio repository with git clone https://github.com/kamailio/kamailio.git Navigate to the Kamailio directory with cd kamailio Update the modules.lst file with any necessary additions Compile with make Install with make install *Downtime:*Restart the Kamailio service. Please advise on this. Thanks. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Kamailio crash due to UDP receiver child (kamailio 5.5.5)
Hi, The kamailio version we are using is "5.5.5", We are facing a kamailio crash issue recently and it has generated the core-dump. Based on the core-dump analysis we could see that "*si_desc = "udp receiver child=3" *getting crashed. We could see the below error in the core-dump trace, #22 0x562c33524750 in udp_rcv_loop () at core/udp_server.c:543 tmp = 0x1150955ff0 Please suggest how to fix this and your inputs will be appreciated. Note: Due to confidentiality, I'm not able to share the core-dump trace. Thanks. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Urgent: High CPU Load and MySQL Connection Issue on Kamailio Proxy Server
Hi, We're encountering a CPU load of approximately 90% on the Kamailio proxy server. Additionally, there's an error logged indicating a lost connection to MySQL. Could this indicate a problem with the configuration file or is it related to MySQL itself? Your guidance would be appreciated. MySQL version: Ver 14.14 Distrib 5.5.47 Kamailio version: 5.5.5 Error in logs: /usr/local/sbin/kamailio[24933]: ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] 412 issue
Hi, Does the below link issue is improved in updated version of Kamailio, Or kindly anyone help on this 412 issue? Link - https://github.com/kamailio/kamailio/issues/2048 Thanks. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: 412 Conditional request failed
Hi, Please anyone can reply on the issue of 412 conditional request failed. On Thu, Jan 18, 2024 at 6:49 PM satyaprakash ch < chiramchetty.satyaprak...@gmail.com> wrote: > Hi > > There were two PUBLISH requests were sent by the Kamailio Proxy server to > the Kamailio Presence server. > > Processing of the first PUBLISH request resulted in the presentity table > being updated - the "etag" changed from "a.1705053846.16611.21.1" to > "a.1705053846.16613.23.2" > > Processing of the second PUBLISH failed because it also attempted to > update the etag in the presentity table but at this point in time there was > no match to the original etag value in the database > > > Logs in kamailio.log: > -- > ps_db_update_presentity(): No E-Tag match a.1705053846.16611.21.1 > DEBUG: tm [t_reply.c:637]: _reply_light(): reply sent out - > buf=0x7f81e5ca5fc0: SIP/2.0 412 Conditio... shmem=0x7f81de6da068: > SIP/2.0 412 Conditional request failed. > > > > Will any one suggest how to resolve the issue of 412 conditional request > failed. > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] 412 Conditional request failed
Hi There were two PUBLISH requests were sent by the Kamailio Proxy server to the Kamailio Presence server. Processing of the first PUBLISH request resulted in the presentity table being updated - the "etag" changed from "a.1705053846.16611.21.1" to "a.1705053846.16613.23.2" Processing of the second PUBLISH failed because it also attempted to update the etag in the presentity table but at this point in time there was no match to the original etag value in the database Logs in kamailio.log: -- ps_db_update_presentity(): No E-Tag match a.1705053846.16611.21.1 DEBUG: tm [t_reply.c:637]: _reply_light(): reply sent out - buf=0x7f81e5ca5fc0: SIP/2.0 412 Conditio... shmem=0x7f81de6da068: SIP/2.0 412 Conditional request failed. Will any one suggest how to resolve the issue of 412 conditional request failed. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: Proxy Inactivity and Kamailio Log Disruption Issue.
Hi,
Thanks for the reply,
The dispatcher params we are using are as below:
#--- Dispatcher params
modparam("dispatcher", "db_url", DBURL_LOCAL)
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "xavp_dst", "ds_dst")
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_ping_interval", 30)
modparam("dispatcher", "ds_ping_from", "sip:proxy@VAR_LOCAL_IP")
The version of the kamailio is *5.4.7.*
Above are the details which was asked, Please let me know if any thing is
needed.
On Thu, Dec 7, 2023 at 4:10 AM Who AmI wrote:
> Hi,
>
> Check the options you have set for the dispatcher params and then if you
> have any logic to mark dispatcher destination as IP on any timeout, or
> error response would be my first checks.
>
> Specifically - "ds_probing_threshold" and the "ds_inactive_threshold"
> params (first takes it out after x failed, second adds it back in after x
> successful.) We would need to see the kamailio version, dispatcher params
> and the dispatcher logic to help further though.
>
> Thanks,
>
> John.
>
> On Wed, 6 Dec 2023 at 20:03, satyaprakash ch via sr-users <
> sr-users@lists.kamailio.org> wrote:
>
>> HI,
>>
>>
>> Scenario:
>>
>> We possess 2 proxies and 2 registrar servers equipped with dmq
>> functionality. Unexpectedly, one of the Proxy IP addresses was marked as
>> inactive (FLAG: IP) in the dispatcher list, causing the proxy to cease
>> responding. Simultaneously, Kamailio logs stopped recording any activity.
>>
>> Upon restarting the Kamailio service, the problem was resolved, and the
>> proxy resumed normal operation, with the Flag changing back to AP (ACTIVE).
>>
>> The sudden occurrence of this issue is not clear, and due to the
>> cessation of logs during the incident, we lack information for the
>> investigation.
>>
>> Any suggestions on how to address this issue would be appreciated.
>>
>>
>> And is this scenario happened to any one in your experience?
>> __
>> Kamailio - Users Mailing List - Non Commercial Discussions
>> To unsubscribe send an email to sr-users-le...@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-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Proxy Inactivity and Kamailio Log Disruption Issue.
HI, Scenario: We possess 2 proxies and 2 registrar servers equipped with dmq functionality. Unexpectedly, one of the Proxy IP addresses was marked as inactive (FLAG: IP) in the dispatcher list, causing the proxy to cease responding. Simultaneously, Kamailio logs stopped recording any activity. Upon restarting the Kamailio service, the problem was resolved, and the proxy resumed normal operation, with the Flag changing back to AP (ACTIVE). The sudden occurrence of this issue is not clear, and due to the cessation of logs during the incident, we lack information for the investigation. Any suggestions on how to address this issue would be appreciated. And is this scenario happened to any one in your experience? __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: Inquiry Regarding Kamailio Behavior and Drop Requests
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 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
> 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
> 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
> >> > Sent: Dienstag, 24. Oktober 2023 17:55
> >> > To: Kamailio (SER) - Users Mailing List
> >> > Cc: satyaprakash ch ; James
> Browne
> >> >
> >> > 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 >> > us...@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-le...@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-le...@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-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: Inquiry Regarding Kamailio Behavior and Drop Requests
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.satyaprak...@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 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
>> > Sent: Dienstag, 24. Oktober 2023 17:55
>> > To: Kamailio (SER) - Users Mailing List
>> > Cc: satyaprakash ch ; James Browne
>> >
>> > 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 > > us...@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-le...@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-le...@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-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: Inquiry Regarding Kamailio Behavior and Drop Requests
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 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
> > Sent: Dienstag, 24. Oktober 2023 17:55
> > To: Kamailio (SER) - Users Mailing List
> > Cc: satyaprakash ch ; James Browne
> >
> > 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 > us...@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-le...@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-le...@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-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: ERROR: run_top_route
Hi,
Now the error was not coming,
Do you recommend making changes to the code as you have described?
On Fri, Oct 13, 2023 at 6:53 PM Patrick Karton
wrote:
> Hi,
>
> ok from kamailio source code, i see that the returned value of last
> function called in failure route is also taken also as value so that's why
> you have that log error.
>
> you have to find why t_relay() return -1
>
> or you can also do this
>
> failure_route["serial"] {
> if (!t_next_contacts()) {
> exit;
> }
>
> t_on_failure("serial");
> $tu = $ru;
> if (!t_relay())
>drop; // or exit
> }
> --
> *De :* satyaprakash ch
> *Envoyé :* vendredi 13 octobre 2023 13:43
> *À :* Patrick Karton
> *Cc :* Kamailio (SER) - Users Mailing List
> *Objet :* Re: [SR-Users] ERROR: run_top_route
>
> HI,
>
> failure_route[MANAGE_FAILURE] {
> if (t_check_status("3[0-9][0-9]")) {
> get_redirects("3:3");
> t_load_contacts();
> t_next_contacts();
> $tu = $ru;
> t_on_failure("serial");
> t_relay();
> exit;
> }
> }
>
> failure_route["serial"] {
> if (!t_next_contacts()) {
> exit;
> }
>
> t_on_failure("serial");
> $tu = $ru;
> t_relay();
> }
>
>
> t_relay function is returning -1 in serial failure route. Functionality
> wise this code is working fine.
> So is there any thing is wrong t_relay is returning -1. Let us know your
> suggestions further.
>
> On Wed, Oct 11, 2023 at 8:58 PM Patrick Karton
> wrote:
>
> Hi,
>
> no we don't need to change any code level.
> but in your script just remove the return with negative code.
>
> you probably have in your script
>
> failure_route[MY_FAILURE]{
>
>
> *return *-5; *//* *<-- you probably have this. remove this
> instruction*
>
>
> *return *route[ANOTHER_ROUTE] *// <-- or you have this flavour .
> remove the return instruction.*
>
>
> }
>
>
> you should remove any *return *instruction present in *faillure_route*.
> its not useful to have a return instruction in a faillure_route.
> --
> *De :* satyaprakash ch
> *Envoyé :* mercredi 11 octobre 2023 07:27
> *À :* Patrick Karton
> *Cc :* Kamailio (SER) - Users Mailing List
> *Objet :* Re: [SR-Users] ERROR: run_top_route
>
> Hi,
>
> Thanks for the reply,
>
> What if we would get a negative value, Do we need to change any code level,
> Will you please suggest what we need to do to resolve this?
>
> Waiting for your reply.
>
>
> On Mon, Oct 9, 2023 at 11:45 AM satyaprakash ch <
> chiramchetty.satyaprak...@gmail.com> wrote:
>
> Hi,
>
> Thanks for the reply,
>
> What if we would get a negative value, Do we need to change any code level,
> Will you please suggest what we need to do to resolve this?
>
>
>
> On Wed, Sep 27, 2023 at 9:26 PM Patrick Karton
> wrote:
>
> Hi,
>
> Probably because you are returning negative value in this failure_route
> --
> *De :* satyaprakash ch via sr-users
> *Envoyé :* mercredi 27 septembre 2023 06:45
> *À :* Kamailio (SER) - Users Mailing List
> *Cc :* satyaprakash ch
> *Objet :* [SR-Users] ERROR: run_top_route
>
> Hi,
>
> We are having an error in the Kamailio logs which we need to resolve this
> issue,
>
> ERROR is ::* /usr/local/sbin/kamailio[10149]: ERROR: tm
> [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for
> failure handler.*
>
> We are getting this error at the time of the 3xx response, Can anyone help
> me on this?
>
>
> Thank you.
>
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: Inquiry Regarding Kamailio Behavior and Drop Requests
Hi,
Any reply would be appreciated.
On Mon, Oct 16, 2023 at 10:10 PM satyaprakash ch <
chiramchetty.satyaprak...@gmail.com> wrote:
> 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?
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Inquiry Regarding Kamailio Behavior and Drop Requests
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?
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: ERROR: run_top_route
HI,
failure_route[MANAGE_FAILURE] {
if (t_check_status("3[0-9][0-9]")) {
get_redirects("3:3");
t_load_contacts();
t_next_contacts();
$tu = $ru;
t_on_failure("serial");
t_relay();
exit;
}
}
failure_route["serial"] {
if (!t_next_contacts()) {
exit;
}
t_on_failure("serial");
$tu = $ru;
t_relay();
}
t_relay function is returning -1 in serial failure route. Functionality
wise this code is working fine.
So is there any thing is wrong t_relay is returning -1. Let us know your
suggestions further.
On Wed, Oct 11, 2023 at 8:58 PM Patrick Karton
wrote:
> Hi,
>
> no we don't need to change any code level.
> but in your script just remove the return with negative code.
>
> you probably have in your script
>
> failure_route[MY_FAILURE]{
>
>
> *return *-5; *//* *<-- you probably have this. remove this
> instruction*
>
>
> *return *route[ANOTHER_ROUTE] *// <-- or you have this flavour .
> remove the return instruction.*
>
>
> }
>
>
> you should remove any *return *instruction present in *faillure_route*.
> its not useful to have a return instruction in a faillure_route.
> --
> *De :* satyaprakash ch
> *Envoyé :* mercredi 11 octobre 2023 07:27
> *À :* Patrick Karton
> *Cc :* Kamailio (SER) - Users Mailing List
> *Objet :* Re: [SR-Users] ERROR: run_top_route
>
> Hi,
>
> Thanks for the reply,
>
> What if we would get a negative value, Do we need to change any code level,
> Will you please suggest what we need to do to resolve this?
>
> Waiting for your reply.
>
>
> On Mon, Oct 9, 2023 at 11:45 AM satyaprakash ch <
> chiramchetty.satyaprak...@gmail.com> wrote:
>
> Hi,
>
> Thanks for the reply,
>
> What if we would get a negative value, Do we need to change any code level,
> Will you please suggest what we need to do to resolve this?
>
>
>
> On Wed, Sep 27, 2023 at 9:26 PM Patrick Karton
> wrote:
>
> Hi,
>
> Probably because you are returning negative value in this failure_route
> --
> *De :* satyaprakash ch via sr-users
> *Envoyé :* mercredi 27 septembre 2023 06:45
> *À :* Kamailio (SER) - Users Mailing List
> *Cc :* satyaprakash ch
> *Objet :* [SR-Users] ERROR: run_top_route
>
> Hi,
>
> We are having an error in the Kamailio logs which we need to resolve this
> issue,
>
> ERROR is ::* /usr/local/sbin/kamailio[10149]: ERROR: tm
> [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for
> failure handler.*
>
> We are getting this error at the time of the 3xx response, Can anyone help
> me on this?
>
>
> Thank you.
>
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: ERROR: run_top_route
Hi, Thanks for the reply, What if we would get a negative value, Do we need to change any code level, Will you please suggest what we need to do to resolve this? Waiting for your reply. On Mon, Oct 9, 2023 at 11:45 AM satyaprakash ch < chiramchetty.satyaprak...@gmail.com> wrote: > Hi, > > Thanks for the reply, > > What if we would get a negative value, Do we need to change any code level, > Will you please suggest what we need to do to resolve this? > > > > On Wed, Sep 27, 2023 at 9:26 PM Patrick Karton > wrote: > >> Hi, >> >> Probably because you are returning negative value in this failure_route >> ------ >> *De :* satyaprakash ch via sr-users >> *Envoyé :* mercredi 27 septembre 2023 06:45 >> *À :* Kamailio (SER) - Users Mailing List >> *Cc :* satyaprakash ch >> *Objet :* [SR-Users] ERROR: run_top_route >> >> Hi, >> >> We are having an error in the Kamailio logs which we need to resolve this >> issue, >> >> ERROR is ::* /usr/local/sbin/kamailio[10149]: ERROR: tm >> [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for >> failure handler.* >> >> We are getting this error at the time of the 3xx response, Can anyone >> help me on this? >> >> >> Thank you. >> > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: ERROR: run_top_route
Hi, Thanks for the reply, What if we would get a negative value, Do we need to change any code level, Will you please suggest what we need to do to resolve this? On Wed, Sep 27, 2023 at 9:26 PM Patrick Karton wrote: > Hi, > > Probably because you are returning negative value in this failure_route > -- > *De :* satyaprakash ch via sr-users > *Envoyé :* mercredi 27 septembre 2023 06:45 > *À :* Kamailio (SER) - Users Mailing List > *Cc :* satyaprakash ch > *Objet :* [SR-Users] ERROR: run_top_route > > Hi, > > We are having an error in the Kamailio logs which we need to resolve this > issue, > > ERROR is ::* /usr/local/sbin/kamailio[10149]: ERROR: tm > [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for > failure handler.* > > We are getting this error at the time of the 3xx response, Can anyone help > me on this? > > > Thank you. > __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] ERROR: run_top_route
Hi, We are having an error in the Kamailio logs which we need to resolve this issue, ERROR is ::* /usr/local/sbin/kamailio[10149]: ERROR: tm [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for failure handler.* We are getting this error at the time of the 3xx response, Can anyone help me on this? Thank you. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
