Hello!
Over the years, there have been discussions about what options could be
made available to donate to Kamailio project in order to support its
required infrastructure, administrative or development of complex
components. Creating a foundation or using a crowdfunding platform have
been explored, trying to take in consideration the needed man power and
overhead, the transparency and accountability.
To move forward on this matter, the Kamailio management team has decided
to use Open Collective, with the fiscal host Open Collective Europe, as
the platform for accepting and managing donations, more details,
including the link where donations can be made, are published at:
- https://www.kamailio.org/w/donations/
The donations should target either the support of project administration
or the development of new feature, therefore before donating it is
recommend to email to <management [at] lists.kamailio.org> providing
some details about the scope of your donation.
We also plan to discuss about it at the next Kamailio World Conference:
May 12-13, 2025, organized again in Berlin, Germany, where many
developers and members of the management board and our community get
together, being a good opportunity to clarify and decide how to use the
donations. More details about the event at:
- https://www.kamailioworld.com
Thanks for flying Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com
CAPCOMIN created an issue (kamailio/kamailio#4204)
<!--
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.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in pursuing 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.
-->
I am experimenting with fuzzing on Kamailio SIP. The messages in the attached file crash the Kamailio server.
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
You can build the image using this [dockerfile](https://github.com/profuzzbench/profuzzbench/blob/master/subjec….
I am running the server with a basic configuration (attached kamailio-basic.cfg), using the command:
```
./src/kamailio -f ../kamailio-basic.cfg -L ./src/modules -Y runtime_dir -n 1 -D -E
```
[kamailio-basic.cfg.txt](https://github.com/user-attachments/files/19615271/…
On the same machine, I am sending the malformed message using aflnet-replay:
```
aflnet-replay ~/sipcrash.txt SIP 5060
```
[sipcrash.txt](https://github.com/user-attachments/files/19615274/sipcrash.t…
#### 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.
-->
```
root@d3fd59910480:/home/ubuntu/experiments/kamailio# ./src/kamailio -f ../kamailio-basic.cfg -L ./src/modules -Y runtime_dir -n 1 -D -E #!!!
0(139581) INFO: <core> [core/sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module
Listening on
udp: 127.0.0.1 [127.0.0.1]:5060
Aliases:
WARNING: no fork mode
0(139581) INFO: rr [./../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded
0(139581) INFO: rr [rr_mod.c:188]: mod_init(): outbound module not available
0(139581) INFO: <core> [main.c:2841]: main(): processes (at least): 4 - shm size: 67108864 - pkg size: 8388608
0(139581) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992
0(139581) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984
0(139581) WARNING: {1 1 REGISTER 1-670(a)127.0.0.1} sanity [sanity.c:612]: check_cl(): content length header missing in request
=================================================================
==139581==ERROR: AddressSanitizer: global-buffer-overflow on address 0x000001d5e560 at pc 0x000000fcbc2f bp 0x7ffd115433d0 sp 0x7ffd115433c8
READ of size 1 at 0x000001d5e560 thread T0
#0 0xfcbc2e in skip_uri /home/ubuntu/experiments/kamailio/src/core/parser/contact/contact.c:53:10
#1 0xfcbc2e in parse_contacts /home/ubuntu/experiments/kamailio/src/core/parser/contact/contact.c:210:7
#2 0xfcdd18 in contact_parser /home/ubuntu/experiments/kamailio/src/core/parser/contact/parse_contact.c:55:7
#3 0xfcdd18 in parse_contact /home/ubuntu/experiments/kamailio/src/core/parser/contact/parse_contact.c:84:6
#4 0x7f0fe32590c4 in parse_message /home/ubuntu/experiments/kamailio/src/modules/registrar/sip_msg.c:125:26
#5 0x7f0fe3266f2f in save /home/ubuntu/experiments/kamailio/src/modules/registrar/save.c:897:6
#6 0x695413 in do_action /home/ubuntu/experiments/kamailio/src/core/action.c:1082:4
#7 0x6ce894 in run_actions /home/ubuntu/experiments/kamailio/src/core/action.c:1581:7
#8 0x6d161c in run_actions_safe /home/ubuntu/experiments/kamailio/src/core/action.c:1645:8
#9 0x5f8b1a in rval_get_int /home/ubuntu/experiments/kamailio/src/core/rvalue.c:915:9
#10 0x603507 in rval_expr_eval_int /home/ubuntu/experiments/kamailio/src/core/rvalue.c:1913:8
#11 0x60259f in rval_expr_eval_int /home/ubuntu/experiments/kamailio/src/core/rvalue.c:1921:8
#12 0x691381 in do_action /home/ubuntu/experiments/kamailio/src/core/action.c:1052:10
#13 0x6ce894 in run_actions /home/ubuntu/experiments/kamailio/src/core/action.c:1581:7
#14 0x6924cb in do_action /home/ubuntu/experiments/kamailio/src/core/action.c:700:8
#15 0x6ce894 in run_actions /home/ubuntu/experiments/kamailio/src/core/action.c:1581:7
#16 0x6d19fd in run_top_route /home/ubuntu/experiments/kamailio/src/core/action.c:1666:8
#17 0xb16ce6 in receive_msg /home/ubuntu/experiments/kamailio/src/core/receive.c:423:8
#18 0x7886fb in udp_rcv_loop /home/ubuntu/experiments/kamailio/src/core/udp_server.c:543:4
#19 0x4f9ab0 in main_loop /home/ubuntu/experiments/kamailio/src/main.c:1480:10
#20 0x51b219 in main /home/ubuntu/experiments/kamailio/src/main.c:2863:6
#21 0x7f0fe79b2082 in __libc_start_main /build/glibc-e2p3jK/glibc-2.31/csu/../csu/libc-start.c:308:16
#22 0x43479d in _start (/home/ubuntu/experiments/kamailio/src/kamailio+0x43479d)
0x000001d5e560 is located 0 bytes to the right of global variable 'buf' defined in 'core/udp_server.c:425:14' (0x1d4e560) of size 65536
SUMMARY: AddressSanitizer: global-buffer-overflow /home/ubuntu/experiments/kamailio/src/core/parser/contact/contact.c:53:10 in skip_uri
Shadow bytes around the buggy address:
0x0000803a3c50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0000803a3c60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0000803a3c70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0000803a3c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0000803a3c90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0000803a3ca0: 00 00 00 00 00 00 00 00 00 00 00 00[f9]f9 f9 f9
0x0000803a3cb0: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
0x0000803a3cc0: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
0x0000803a3cd0: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
0x0000803a3ce0: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
0x0000803a3cf0: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==139581==ABORTING
```
#### 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).
-->
In the Debugging Data
#### 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).
-->
[traffic.txt](https://github.com/user-attachments/files/19615184/traffic.txt)
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.5.0-dev2 (x86_64/linux) 2648eb-dirty
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, 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_BLACKLIST, HAVE_RESOLV_RES
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: 2648eb -dirty
compiled on 11:51:00 May 5 2024 with afl-clang-fast clang version 10.0.0-4ubuntu1
```
* **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`)
-->
```
Linux d3fd59910480 5.15.0-125-generic #135~20.04.1-Ubuntu SMP Mon Oct 7 13:56:22 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4204
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4204(a)github.com>
### Description
Let's assume we have a MO call from UE to P-CSCF that's over ipsec. Let's assume the picked ports are like UE(6101) -> P-CSCF(6100)
We have also set tcp_connection_lifetime to be 20 sec.
20 sec after INVITE connection is RST from Kamailio as expected.
Then ( > 20sec later) an INVITE response comes from B side, and must be delivered to the UE.
Kamailio opens a new connection and tries to establish a connection from 5060 (standard port)->6101 instead of 6100(P-CSCF) -> 6101(UE). IPSEC associations are not engaged and UE does not handle the request properly.
### Troubleshooting
#### Reproduction
#### Debugging Data
#### Log Messages
#### SIP Traffic
### Possible Solutions
The IPSEC module should re-open the tcp connection if it sees it's been dropped as core module has no awareness of IPSEC.
* **Operating System**:
All
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4138
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4138(a)github.com>
#### Pre-Submission Checklist
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
This PR allow usage of the new presence_dfks module with pua_json
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4195
-- Commit Summary --
* pua_json: add support for as-feature-event
-- File Changes --
M src/modules/pua_json/defs.h (16)
M src/modules/pua_json/pua_json_publish.c (55)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4195.patchhttps://github.com/kamailio/kamailio/pull/4195.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4195
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4195(a)github.com>
github-actions[bot] left a comment (kamailio/kamailio#4200)
This tracker is for reporting issues in the C code, for questions about kamailio use sr-users(a)lists.kamailio.org mailing list.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4200#issuecomment-2775212517
You are receiving this because you authored the thread.
Message ID: <kamailio/kamailio/issues/4200/2775212517(a)github.com>
Closed #4200 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4200#event-17110423595
You are receiving this because you authored the thread.
Message ID: <kamailio/kamailio/issue/4200/issue_event/17110423595(a)github.com>
github-actions[bot] left a comment (kamailio/kamailio#4200)
This tracker is for reporting issues in the C code, for questions about kamailio use sr-users(a)lists.kamailio.org mailing list.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4200#issuecomment-2775169027
You are receiving this because you authored the thread.
Message ID: <kamailio/kamailio/issues/4200/2775169027(a)github.com>
[kamailio/kamailio] manage labels from comments workflow run
Repository: kamailio/kamailio
Workflow: manage labels from comments
Duration: 7.0 seconds
Finished: 2025-04-03 09:48:00 UTC
View results: https://github.com/kamailio/kamailio/actions/runs/14240022482
Jobs:
* manage failed (1 annotation)
--
You are receiving this because you are subscribed to this thread.
Manage your GitHub Actions notifications: https://github.com/settings/notifications
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
KDMQ messages were added as a separate received request method in the statistic.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4197
-- Commit Summary --
* kex: add KDMQ to request statistic
-- File Changes --
M src/modules/kex/core_stats.c (5)
M src/modules/kex/core_stats.h (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4197.patchhttps://github.com/kamailio/kamailio/pull/4197.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4197
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4197(a)github.com>
Hello list,
Hope everyone is fine.
I'm trying to install the latest 6.0.1 version from
https://rpm.kamailio.org/centos/ but it doesn't seem to be updated...The
latest version available there is the 5.8.5. Version 6.0.0 isn't there as
well...
Is it still maintained? or just some rpmbuild command missed?
Thank you,
Patrick
Hello.
I just pushed by mistake own branch to the master.
@Daniel-Constantin Mierla <miconda(a)gmail.com> @Victor Seva
<linuxmaniac(a)torreviejawireless.org> could you force push correct commit
95d0c1fc38da00dc6bbda19dba1ac4b20535abf5
Sergey
### Description
Currently calling `route()` within the `onsend_route` will cause kamailio to fail to start with an error that `command not allowed in onsend_route`
### Expected behavior
While there is a limited amount of functions that can be allowed within the `onsend_route`, calling `route()` here would be done simply for code organization.
#### Actual observed behavior
Kamailio fails to start;
### Possible Solutions
Allow `route()` to be called from `onsend_route`.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4130
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4130(a)github.com>
Module: kamailio
Branch: master
Commit: d99f040463805a8f7438409e41a9a270ec298092
URL: https://github.com/kamailio/kamailio/commit/d99f040463805a8f7438409e41a9a27…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2025-03-25T22:21:52+01:00
tm: t flags field made int
- short size is full, flag 15 already used
---
Modified: src/modules/tm/h_table.h
Modified: src/modules/tm/uac.h
---
Diff: https://github.com/kamailio/kamailio/commit/d99f040463805a8f7438409e41a9a27…
Patch: https://github.com/kamailio/kamailio/commit/d99f040463805a8f7438409e41a9a27…
---
diff --git a/src/modules/tm/h_table.h b/src/modules/tm/h_table.h
index 59e229d068d..3e8136cbdac 100644
--- a/src/modules/tm/h_table.h
+++ b/src/modules/tm/h_table.h
@@ -346,9 +346,9 @@ typedef struct cell
/* sequence number within hash collision slot */
unsigned int label;
/* different information about the transaction */
- unsigned short flags;
+ unsigned int flags;
/* number of forks */
- short nr_of_outgoings;
+ int nr_of_outgoings;
/* free operations counter - debug */
int fcount;
diff --git a/src/modules/tm/uac.h b/src/modules/tm/uac.h
index a76d8ea63a7..00dc32d2a5b 100644
--- a/src/modules/tm/uac.h
+++ b/src/modules/tm/uac.h
@@ -32,6 +32,7 @@
#define DEFAULT_CSEQ 10 /* Default CSeq number */
+
/* structure for UAC interface
*
* You can free the memory allocated
### RTPEngine + RTIMER + SEGFAULT + unable to ping
When unable to ping RTPEngine instances kamailio crashes.
### Troubleshooting
Determined issue was related to the ping failures, resolved AWS SG issue, allowing successful pings. Issue subsequently went away.
#### Reproduction
Use rtpengine with RDS backend
Load rtpengine with ~ 20 destinations you do not expect a response from on
Use rtimer to call rtpengine.reload via jsonrpcs:
```
modparam("rtimer", "timer", "name=rtpengine;interval=60;mode=0;")
modparam("rtimer", "exec", "timer=rtpengine;route=RELOAD_RTPENGINE")
route[RELOAD_RTPENGINE] {
xinfo("RTPEngine database reloading");
jsonrpc_exec('{"jsonrpc": "2.0", "method": "rtpengine.reload", "id": 1}');
}
```
#### Debugging Data
Got a core dump -- although I deleted quickly (not thinking) as they were running instances out of disk quickly. bt full did not show much to step through all though clearly pointed to rtpengine.
#### Log Messages
```
send_rtpp_command(): timeout waiting reply for command "ping" from RTPEngine <udp:10.0.X.X>
```
### Possible Solutions
TBD / do not have ping failures under heavy load.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.8.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_SEND_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 with gcc 10.2.1
```
* **Operating System**:
```
uname -a
Linux 5.10.0-27-cloud-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) x86_64 GNU/Linux
cat /proc/version
Linux version 5.10.0-27-cloud-amd64 (debian-kernel(a)lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.205-2 (2023-12-31)
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4122
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4122(a)github.com>