ITNOA
I suggest port Kamailio to windows, if you agree with me, I can try to port that
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4109
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4109(a)github.com>
ovedeneev created an issue (kamailio/kamailio#4187)
### Description
[tcp_send_timeout](https://www.kamailio.org/wikidocs/cookbooks/5.8.x/core/#t… option does not apply for outbound connections.
#### Reproduction
1. Establish TCP OPTIONS between Kamailio and target node.
2. On target node block incoming traffic from Kamailio node using iptables.
3. Notice on Kamailio node that TCP retransmission packets don't follow tcp_send_timeout settings, instead they fall back to kernel's net.ipv4.tcp_retries2 settings.
### Additional Information
* **Kamailio Version**
```
# kamailio -V
version: kamailio 5.8.2 (aarch64/linux) 446039
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-NOSMP, 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: 446039
compiled on 14:32:09 Nov 14 2024 with gcc 8.5.0
```
* **Operating System**:
```
Linux xxx 4.18.0-553.6.1.el8.aarch64 #1 SMP Thu May 30 04:10:32 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4187
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4187(a)github.com>
- add dispatcher modparam `ds_ping_socket`
- add gateway param `ping_socket`
<!-- 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)
- [ ] 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)
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
could be useful for HA use cases where multiple kamailio nodes share a common Virtual IP (e.g.: managed by the VRRP).
we need to route requests using Virtual IP socket configured with `ds_default_sockname`/`socket` and to perform destinations probing using self-IP socket configured with `ds_ping_socket`/`ping_socket`.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4186
-- Commit Summary --
* dispatcher: added ping socket configuration
-- File Changes --
M src/modules/dispatcher/dispatch.c (32)
M src/modules/dispatcher/dispatch.h (2)
M src/modules/dispatcher/dispatcher.c (25)
M src/modules/dispatcher/doc/dispatcher_admin.xml (20)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4186.patchhttps://github.com/kamailio/kamailio/pull/4186.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4186
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4186(a)github.com>
Opening this generic issue to track how some commands from old Makefiles can be done when using the new CMake-based build system, or what the possible alternatives. Hopefully we can build some knowledge here that can be then transferred to the wiki cmake tutorials.
### Compiling core only
With the old makefiles, the `make` compiled only the core of Kamailio. With cmake, `make` compiles everything.
Would it be possible to have a command with cmake that compiles only the core? Like:
```
make core
```
Or maybe there is a way to do it already?!?
### Compile a single module
With the old makefiles, compiling a single module, say acc, was possible with:
```
make modules modules=src/modules/acc
```
With cmake, this is possible with:
```
make acc
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4052
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4052(a)github.com>
Mercury109 created an issue (kamailio/kamailio#4169)
### Description
I loop through the active dialogs in a timer functions and based on some conditions, a dialog may be ended by setting a short timeout or using the dlg_bye function. **Sometimes** when a dialog times out or the dlg_bye("all") function is used, the BYE is not being sent in both directions, only towards the caller.
There's a warning:
send_bye(): dlg [25641:71143] with callid XXXXXXXXX already in deleted state, BYE not sent.
I noticed this check was added in the commit below:
https://github.com/kamailio/kamailio/commit/d411c6ea4358e6d9dd367349e877ed5…
Is there a race condition between marking the dialog as terminated and sending the BYE?
Not sending a BYE towards the callee when it should is much worse than sending an unnecessary BYE as it causes billing issues. If this can't be resolved to be 100% reliable, it's safer to remove this check all together.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.7.6 (x86_64/linux))
```
* **Operating System**:
Debian GNU/Linux 12 (bookworm)
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4169
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4169(a)github.com>
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4183
-- Commit Summary --
* lcr: add counters per gateway
* lcr: add counters per gateway documentation
* Typo on sanity module error
-- File Changes --
M src/modules/lcr/doc/lcr_admin.xml (58)
M src/modules/lcr/lcr_mod.c (306)
M src/modules/lcr/lcr_mod.h (52)
M src/modules/lcr/lcr_rpc.c (460)
M src/modules/sanity/sanity.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4183.patchhttps://github.com/kamailio/kamailio/pull/4183.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4183
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4183(a)github.com>
there's no ``kamailio-ims_dialog.xml`` at ``src/lib/srdb1/schema`` but there's a manual file created at ``utils/kamctl/mysql/ims_dialog-create.sql``
Same thing for:
- ``utils/kamctl/mysql/ims_charging-create.sql``
- ``utils/kamctl/mysql/ims_usrloc_pcscf-create.sql``
- ``utils/kamctl/mysql/ims_usrloc_scscf-create.sql``
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4100
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4100(a)github.com>
schneuwlym created an issue (kamailio/kamailio#4174)
### Description
A NAPTR record in dns cache may be skipped if all IPs are unreachable. The NAPTR record contains the internal parameter `skip_record`. From outside, it is not possible to view the state of a certain NAPTR record.
Extend the return value of `dns_cache_print_entry` with the parameter `skip_record`.
### Expected behavior
The answer of `kamcmd dns.view` shows `yes` or `no` depending on the internal state of `skip_record`.
```
{
name: skipped.example.com
type: NAPTR
size_bytes: 208
reference_counter: 2
permanent: no
expires: 268
last_used: 29
negative_entry: no
records: {
{
rr_idx: 0
rr_order: 10
rr_preference: 10
-> rr_skip_record: yes
rr_flags: S
rr_service: SIPS+D2T
rr_regexp:
rr_regexp: _sips._tcp.skipped.example.com
rr_permanent: no
rr_expires: 268
}
}
}
{
name: valid.example.com
type: NAPTR
size_bytes: 328
reference_counter: 1
permanent: no
expires: 294
last_used: 5
negative_entry: no
records: {
{
rr_idx: 0
rr_order: 20
rr_preference: 20
-> rr_skip_record: no
rr_flags: S
rr_service: SIP+D2U
rr_regexp:
rr_regexp: _sip._udp.valid.example.com
rr_permanent: no
rr_expires: 294
}
{
rr_idx: 1
rr_order: 10
rr_preference: 10
-> rr_skip_record: no
rr_flags: S
rr_service: SIPS+D2T
rr_regexp:
rr_regexp: _sips._tcp.valid.example.com
rr_permanent: no
rr_expires: 294
}
}
}
```
#### Actual observed behavior
At the moment it is not visible why a NAPTR record is not used.
### Possible Solutions
The following patch extends the output of `dns_cache_print_entry` with the parameter `rr_skip_record`.
The patch has been tested locally.
```patch
From c4d559f12892fb5a2c3b572f9660b637299fcafb Mon Sep 17 00:00:00 2001
From: Mathias Schneuwly <mathias.schneuwly(a)ruag.ch>
Date: Tue, 11 Mar 2025 12:38:44 +0000
Subject: [PATCH] Print parameter skip_record in dns_cache_print_entry
---
src/core/dns_cache.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/src/core/dns_cache.c b/src/core/dns_cache.c
index 1507e89015..1bb95a2d41 100644
--- a/src/core/dns_cache.c
+++ b/src/core/dns_cache.c
@@ -3898,6 +3898,13 @@ int dns_cache_print_entry(rpc_t *rpc, void *ctx, struct dns_hash_entry *e)
rpc->fault(ctx, 500, "Internal error adding naptr order");
return -1;
}
+ if(rpc->struct_add(sh, "s", "rr_skip_record",
+ ((struct naptr_rdata *)(rr->rdata))->skip_record ? "yes" : "no")
+ < 0) {
+ rpc->fault(
+ ctx, 500, "Internal error adding naptr rr_skip_record");
+ return -1;
+ }
s.s = ((struct naptr_rdata *)(rr->rdata))->flags;
s.len = ((struct naptr_rdata *)(rr->rdata))->flags_len;
if(rpc->struct_add(sh, "S", "rr_flags", &s) < 0) {
--
2.44.1
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.8.4 (x86_64/linux) f1d83d
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
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: f1d83d
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4174
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4174(a)github.com>
Discussion to define cmake format options and coding/naming styles. It is better to define most of them now to have coherency in the future. Started from the discussion on #4066.
Comment with what you would like to have, describing when useful why your proposal is a good/better option.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4075
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4075(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>