<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
Kamailio does not properly release connected WebSocket TCP connections, leading to a situation where the maximum number of allowable connections is reached and new connection requests are rejected.
### Troubleshooting
When examining the logs, we identified an issue where Kamailio is failing to release connected WebSocket TCP connections, causing a backlog of TIME_WAIT connections. The logs show a warning message indicating that the maximum number of allowable sockets per IP has been reached, leading to the rejection of further WebSocket requests.
#### Reproduction
Establish WebSocket connections with Kamailio.
Monitor the number of TIME_WAIT connections using netstat.
Observe the warning message in Kamailio logs when the maximum allowable sockets per IP are reached.
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
2023-10-03T13:19:33.699043+00:00 apps001 kamailio[23781]: WARNING: |<null>|websockets-role.cfg:224 (websocket_request) 223.233.86.93 is at the maximum 50 allowable sockets per IP, rejecting request for another websocket
netstat -punta | grep 223.233.86.93 | grep 5065
tcp 0 0 45.79.166.214:5065 223.233.86.93:52158 TIME_WAIT -
tcp 0 0 45.79.166.214:5065 223.233.86.93:52195 TIME_WAIT -
tcp 0 0 45.79.166.214:5065 223.233.86.93:52292 TIME_WAIT -
tcp 0 0 45.79.166.214:5065 223.233.86.93:52248 TIME_WAIT -
tcp 0 0 45.79.166.214:5065 223.233.86.93:52108 TIME_WAIT -
tcp 0 0 45.79.166.214:5065 223.233.86.93:52071 TIME_WAIT -
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
restarting kamailio solves the problem.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.7.2 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled on 14:39:54 Sep 27 2023 with gcc 7.3.1
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
-->
```
CentOS Linux release 7.9.2009 (Core)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3589
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3589(a)github.com>
Hi,
I have sample json data as below:
$var(mapjson) = {"1.1.1.1": "cloudflare", "2.2.2.2": "ANY"};
I add this line to kamailio script but it does NOT work,
jansson_get("1.1.1.1", "$var(mapjson) ", “$var(domain)“);
or
jansson_get("1\.1\.1\.1", "$var(mapjson) ", “$var(domain)“);
Seem kamailio thinks it is a **path** not **a single key**?
Thanks
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3658
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3658(a)github.com>
Module: kamailio
Branch: master
Commit: 006cca915275f8ca3ea52a9d978961e0842f1dcd
URL: https://github.com/kamailio/kamailio/commit/006cca915275f8ca3ea52a9d978961e…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-11-30T10:18:47+01:00
ims_ipsec_pcscf: docs for ipsec_destroy_by_contact()
---
Modified: src/modules/ims_ipsec_pcscf/doc/ims_ipsec_pcscf_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/006cca915275f8ca3ea52a9d978961e…
Patch: https://github.com/kamailio/kamailio/commit/006cca915275f8ca3ea52a9d978961e…
---
diff --git a/src/modules/ims_ipsec_pcscf/doc/ims_ipsec_pcscf_admin.xml b/src/modules/ims_ipsec_pcscf/doc/ims_ipsec_pcscf_admin.xml
index d50c66ed45a..24d77440d89 100644
--- a/src/modules/ims_ipsec_pcscf/doc/ims_ipsec_pcscf_admin.xml
+++ b/src/modules/ims_ipsec_pcscf/doc/ims_ipsec_pcscf_admin.xml
@@ -367,6 +367,40 @@ ipsec_forward("location", "1");
<programlisting format="linespecific">
...
ipsec_destroy("location");
+...
+ </programlisting>
+ </example>
+ </section>
+ <section>
+ <title><function moreinfo="none">ipsec_destroy_by_contact(domain, aor, recv_host, recv_port)</function></title>
+ <para>The function destroys IPSec tunnel, created with ipsec_create.</para>
+ <para>Meaning of the parameters is as follows:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>domain</emphasis> - Logical domain within the registrar.
+ If a database is used then this must be name of the table which
+ stores the contacts.
+ </para>
+ <para>
+ <emphasis>aor</emphasis> - SIP URI to match the record.
+ </para>
+ <para>
+ <emphasis>recv_host</emphasis> - received host to match the record.
+ </para>
+ <para>
+ <emphasis>recv_port</emphasis> - received port to match the record.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>The last three parameters have to be string valies and can contain
+ variables.</para>
+ <example>
+ <title>ipsec_destroy_by_contact()</title>
+
+ <programlisting format="linespecific">
+...
+ipsec_destroy_by_contact("location", "...", "...", "...");
...
</programlisting>
</example>
Module: kamailio
Branch: master
Commit: 279454ff8d4e5804d92a8690c4de3a507efbc44f
URL: https://github.com/kamailio/kamailio/commit/279454ff8d4e5804d92a8690c4de3a5…
Author: Supreeth Herle <herlesupreeth(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-11-30T10:18:47+01:00
ims_ipsec_pcscf: new function to destroy IPSec based on Contact and received IP and port
- the default ipsec_destroy() cannot be used to used destroy IPSec in any route and
needed to be used exactly after all the de-registration process was complete. But,
as per the kamailio P-CSCF config script, ipsec_destroy() was used in reply route of
NATPING, which didn't have any idea about SIP Register message used for de-registration.
Thus, resulting in IPSec not being destroyed even after de-registration was complete.
- the newly introduced function ipsec_destroy_by_contact() takes domain, contact, received host
and received port in order to determine the exact UE's IPSec tunnel to destroy.
---
Modified: src/modules/ims_ipsec_pcscf/cmd.c
Modified: src/modules/ims_ipsec_pcscf/cmd.h
Modified: src/modules/ims_ipsec_pcscf/ims_ipsec_pcscf_mod.c
---
Diff: https://github.com/kamailio/kamailio/commit/279454ff8d4e5804d92a8690c4de3a5…
Patch: https://github.com/kamailio/kamailio/commit/279454ff8d4e5804d92a8690c4de3a5…