Damm that was a rabbit hole...
So the key pointers were found thanks to reading two very helpful links [1]
[2].
The TL;DR is that I use setcap to add capabilities to Kamailio to allow to
listen on ports <1024 without root. Once you add capabilities, any LD_* env
var gets stripped out and is not a
Does your sslkeylog.so work on that same host with the openssl test? I
noticed you're using ansible, so I'm curious if you're compiling on
some other host that could have different versions of the openssl-dev
stuff. Other things could be file or path permissions, or maybe a
security tool blocking i
if(proto == TCP)
$ru = $(ru{s.replace,transport=TCP,}{s.replace,transport=tcp,});
...
t_relay();
-- Alex
> On 7 Mar 2024, at 10:46, Alberto Diez via sr-users
> wrote:
>
> Hi kamailio community,
>
> I have an issue with a Kamailio 5.7. It's listening both in TCP and UDP. In
> my sc
If you just strip the incoming ;transport=tcp attribute, I think all should be
well when t_relay() consumes the modified RURI.
> On 7 Mar 2024, at 12:48, Alberto Diez via sr-users
> wrote:
>
> Hi Sergiu,
> yes I am pretty sure something is going wrong.
> I do have kamailio listening udp socket
I have found the issue! For future reference, here is the explanation.
The JSON object returned from the Routing Logique Engine is the standard
object as per module's description, but with the "extra" property filled
with an extra header value.
The resulting SIP Message is :
INVITE sip:129292929@
Hi Sergiu,
yes I am pretty sure something is going wrong.
I do have kamailio listening udp sockets and also the dispatcher is on
UDP doing SIP OPTIONS over UDP all the time without any problem.
I have not tried forcing the socket I tried to find out why kamailio is
trying to use TCP with the
You must be doing something essentially wrong if it came down to checking C
functions for something as trivial as transport conversion..
Are you sure you have a UDP listening socket?
kamcmd corex.list_sockets
Result of:
kamcmd dispatcher.list
Have you tried forcing the send socket?
https://www.k
Hi kamailio community,
I have an issue with a Kamailio 5.7. It's listening both in TCP and
UDP. In my scenario requests arrive from devices on TCP, but I want to
forward to the next hops on UDP. I am avoiding using any type of DNS
resolution; since I am always forwarding to predefined next h
Hi all!
some additional details for this issue.
Currently, Kamailio is using RTJSON to get routes from the routing engine
and forward calls to the correct route.
Please note that the 2 testing endpoints and Kamailio are all in the same
network, no NAT involved, and firewalls are disabled!
Follow
Kamailio v5.8.0 is out – it comes with 4 new modules and a large set of
improvements touching again more than 50 existing modules.
You can read a bit more detailed release notes at:
* https://www.kamailio.org/w/kamailio-v5-8-0-release-notes/
Many thanks to all developers and community members
> On 7 Mar 2024, at 06:25, Marrold via sr-users
> wrote:
>
> After digging through old mailing posts I've been able to resolve this by
> applying the changes in the BRANCH route. This fixes the corruption, although
> the logs still show a warning for applying it twice.
This is the way. :-)
After digging through old mailing posts I've been able to resolve this by
applying the changes in the BRANCH route. This fixes the corruption,
although the logs still show a warning for applying it twice.
Cheers
On Thu, 7 Mar 2024 at 09:23, Benoit Panizzon wrote:
> Hi Matthew
>
> > However in m
Hi Matthew
> However in my scenario I wish to first try one endpoint and then if it gets
> a 4XX response forward it to another UAC, and update the TO accordingly.
>
> Currently trying to call uac_replace_to twice shows an error and corrupts
> the TO header. Is there a work around for this?
I h
Hello,
short notification that v5.8.0 is going to be released today, therefore
any commits to branch 5.8 have to be announced to sr-dev and wait for
the ack before pushing to git repository in order to avoid conflicts
with the release building process. Once the announcement is out, commits
can be
14 matches
Mail list logo
