On Sat, 2025-06-28 at 09:25 +, c7897009--- via sr-dev wrote:
> Hey everyone,
>
> I am diving into Kamailio & trying to wrap my head around how to
> handle some custom SIP scenarios, when it comes to module
> integration. I have gone through some of the docs but still feel a
> bit lost on choos
g", but was done years ago. This
edge case was missed in the conversion.
+1 to "archive"
HTH
Nathan
___
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
### Description
I have some buggy devices that get upset by SRTP payloads in SDP that are
marked inactive. As a hack, I was attempting to delete them when going to
certain endpoints that are known to be problematic:
```
if (is_method("INVITE"))
sdp_remove_transport("RT
On Tue, 2023-04-18 at 17:16 +0200, Olle E. Johansson wrote:
> Hi!
> Sorry if I’ve brought this up before. Was looking at the package
> definitions in our repo today and
> did go through Alpine. It’s not following the template set by the
> Debian packages,
Correct. It tries to follow (as closely a
### Description
For secure websocket connections (wss), Kamailio seems to forget that the
connection is secure, later trying to use a regular TCP `listen` option to send
out messags.
I'd be happy to propose a patch, but I'm not sure what the expected behavior of
Kamailio would be here.
Setup:
On Fri, 2022-12-30 at 14:26 +0100, Olle E. Johansson wrote:
> Dear Kamailians!
>
> I’m trying to figure out DMQ and see how it reacts to server outages
> and downtime - the base protocol.
>
Same here. The best I could figure is "it works when it works, until
it doesn't" In our tests, the "ed
Closed #2700.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2700#event-4574867789___
Kamailio (SER) - Development Mailing List
sr-dev@l
Yes, I can confirm this patch fixes our problem. Thanks!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2700#issuecomment-816735849___
K
### Description
When updating from Kamailio 5.2.2 to 5.4.4, we're encountering an issue: the
pua_dialoginfo module publishes a `confirmed` state for the dialog, even though
it's still ringing.
It turns out this commit introduces the problem since 5.3.0: 4efe19f
So since 5.3.0, the dialog modul
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 mo
### Description
`dns_int_match_ip` is broken on 5.3.0 and above
### Troubleshooting
Reproduction
Try this dialplan:
```
if (dns_int_match_ip('dns.google', '8.8.8.8')) {
xlog("L_INFO", "OK dns-ip match with dns_int_match_ip");
} else {
xlog("L_ERR", "FAIL dns-ip match with dns_int_ma
To be honest, I rather stay with the upstream Kamailio from Xenial and accept
this bug for now.
The burden of having to maintain a custom Kamailio build and package does not
outweigh the complications caused by this issue, in our case.
I can understand that fixing Xenial bugs are not your prior
We settled on accepting this as known issue for now. We just don't ds-reload
this instance...
Updating to a non-Xenial libmysqlclient or libssl feels like it could introduce
a whole range of new problems (also outside of Kamailio).
--
You are receiving this because you are subscribed to this t
Yes, same story here. Using 'localhost' for DB connection URL solves the
problem.
But we can't use this for our production scenario, as our DB is not on
localhost...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://
I finally isolated the problem here. I was trying to deal with some NAT
nonsense involving dropped Contact headers from my SIP trunk provider and had a
block like this in the WITHINDLG route:
```
if (uri==myself && $ru=~";alias=10") {
# Deal with BS on ACKs
Hi,
I'm attaching a zip containing all files needed for repro. Just use `start.sh`
and it should reproduce the segfault.
[kam-2274.zip](https://github.com/kamailio/kamailio/files/4558686/kam-2274.zip)
--
You are receiving this because you are subscribed to this thread.
Reply to this email dire
Yes, I was adding that to test for repro on Ubuntu Bionic.
It's not needed for Xenial. When removed, we still have the same segfault.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issue
Attached is the debug log from Kamailio:
[xenial-debug3.log](https://github.com/kamailio/kamailio/files/4472261/xenial-debug3.log)
I have a docker-based reproduction for various OS versions, if you want to test.
--
You are receiving this because you are subscribed to this thread.
Reply to this
Kamailio version (latest stable xenial version from kamailio repo):
```
version: kamailio 5.3.3 (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, Q_MALLOC, F_MALLOC, TLSF_MALLOC,
DBG_SR_MEMORY, USE_FUTEX, FAS
[kamailio.cfg.example.txt](https://github.com/kamailio/kamailio/files/4435235/kamailio.cfg.example.txt)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2274#issuecomment-609501792_
### Description
Segfault in Kamailio when using mysql (over ssl) and tls listeners.
We have a reproducible segfault with Kamailio on Ubuntu Xenial. The problems is
revealed when two modules (db_mysql and tls) and both using the openssl
library. The mysql module is using openssl indirectly, beca