That socket in that line is the result of `$RAut` in the `onsend_route` and it
shows the expected IP address, but the actual outgoing packet is coming from a
private address anyway. The current configuration is huge, so I will create a
minimal config to reproduce the issue. I need one or two
No problem and thanks for looking into this. The debug logs can be found here.
The IP addresses and hostnames are anonymised (as required by my client). In
this scenario, traffic should go to `185.10.20.29` first, and failover to
`185.10.20.30` or `185.10.20.31` based on DNS SRV.
What I was
Thanks Daniel! For our configuration `mhomed` is not working well. Besides the
documentation states that the incoming socket would be used by default (as long
as we don't switch protocol) which is why I reported this as a bug. I would
expect consistency between the first and any subsequent
### Description
When relaying an `INVITE` from a Kamailio proxy to an interconnect we are using
DNS SRV records for load-balancing and failover. The proxy is listening on both
a private interface and a public interface with an rfc1918 (ie. `10.0.0.14`)
and a public IP address (ie.
Thank you all for the good tips. I found the issue! Luckily not an issue with
Kamailio after all. The issue is that Linux enables reverse path filtering by
default. I tried to substitute Kamailio with a simple Python server, and I
noticed that it wasn't showing me any output either. So I
Closed #1703.
--
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/1703#event-1944999417___
Kamailio (SER) - Development Mailing List
See here two screenshots from Wireshark. The capture was made on one interface
on the internal proxy `10.x.x.x`. When it's receiving a SIP packet from another
host in the same subnet, everything is working normally.
Hi @joelsdc thanks so much for your suggestion! I have tried that now. If I'm
correct, this will have the same behaviour as setting the source socket by
changing `$fs` yourself, but then instead it's choosing the right socket
automatically for you.
Unfortunately this is not entirely fixing my
To start off. Please forgive me, I'm not completely sure if this is an issue in
Kamailio, or an issue in Linux that I'm overseeing. But I could really use a
helping hand.
### Description
I have a setup with a Kamailio load-balancer and a secondary proxy that is
handling all the complex work,
