Hello,
Kamailio SIP Server v5.6.1 stable release is out.
This is a maintenance release of the latest stable branch, 5.6, that
includes fixes since the release of v5.6.0. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.6.x. Deployments running previous v5.6.x
versions are strongly recommended to be upgraded to v5.6.1.
For more details about version 5.6.1 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2022/07/kamailio-v5-6-1-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Adding a short note that the dates of next Kamailio World Conference -
Online have been set for September 7-8, 2022. Event website and more
details will be published soon!
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
im using dns failover with tm module.
i set parameter reparse_on_dns_failover to 0 so that branch_route is called .
but when trying next peer of dns failover initial transaction branch_route is not called.
do i missing something ?
for the first peer branch_route is called and the peer timeout
so kamailio tries next peer but branch_route is not called !.
do i need again to set branch_route in failure_route ?
Thanks for help.
Hey All,
I'm just trying to change the From user before I do a 301 Redirect within a
Failure Route. Here's the code snippet:
$fu = "+15555555555";
append_to_reply("Contact: sip:+1$var(redirect_did)@$si:$sp\r\n");
t_reply("302", "Redirect");
The From user is not changed and msg_apply_changes() isn't allowed. What
am I doing wrong?
Thanks
Hi,
I am trying STIR/SHAKEN using libstirshaken in Kamailio 5.5.
I used a self signed certificate as this is just a test in the local docker
environment. However, when I try to add identity with private key
(stirshaken_add_identity_with_key), I get "[error_code: 447] Buffer for key
from file /tmp/cert/private.pem too short (2000 <= 3247)"
I have tried using 2048 and 4096 size
root@5907e44bd056:/tmp/cert# openssl rsa -in private.pem -text -noout |
grep "Private-Key"
RSA Private-Key: (4096 bit, 2 primes)
Could you tell me what is wrong with the certificate?
Kamailio version:
root@5907e44bd056:/usr/local/kamailio/etc/kamailio# kamailio -v
version: kamailio 5.5.4 (x86_64/linux) 469465
Error:
0(404) ERROR: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken
[stirshaken_mod.c:761]: ki_stirshaken_add_identity_with_key(): Failed to
load private key
0(404) DEBUG: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken
[stirshaken_mod.c:117]: stirshaken_print_error_details(): failure details:
0(404) DEBUG: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken
[stirshaken_mod.c:118]: stirshaken_print_error_details(): failure reason
is: src/stir_shaken_ssl.c:2112: [error_code: 447] Buffer for key from file
/tmp/cert/private.pem too short (2000 <= 3247)
0(404) DEBUG: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} stirshaken
[stirshaken_mod.c:119]: stirshaken_print_error_details(): failure error
code is: 447
0(404) ERROR: {1 30587 INVITE NzIhM1-2YABveZZ1mPvs3m3tw8K7meSq} <script>:
Failed
Regards
*Maharaja Azhagiah*
Hi, thank you for your reply, I have tried it at kamailio 5.5 and 5.6
versions, and there are two network interfaces. Actually, I have created a
testing vm for this, with a simple almost default kamailio configuration.
And yes, with forcing socket everything is working fine, but I just want to
know maybe there is a kamailio params that allow "mhomed" params to work
with tcp/tls destinations, or is it impossible by TCP design, or is it a
kamailio bug.
I wonder if anyone uses kamailio with 2+ network interfaces and uses tls
and don't use $fs?
--
Aidar
on 5.5 kamailio wiki for core it is stated that return (0) is the same as exit. but that's not true
request_route {
if (route(POS)){
xlog("POS PASS\r\n");
}
if (!route(NEG)){
xlog("NEG PASS\r\n");
}
if (!route(ZERO)) {
xlog("ZERO PASS\r\n");
}
xlog("AFTER ZERO\r\n");
send_reply("400","Error");
return;
}
route[POS]{
return 1;
}
route[NEG]{
return -1;
}
route[ZERO] {
return 0;
}
for example from the config above not only ZERO PASS will be printed but also all the actions after route(ZERO) are still executed.
instead if i replace return 0 with exit in route[ZERO]. this work as expected.
Hello,
I have faced an issue when mhomed parameter working well only for udp
destinations in systems with multiple network interfaces.
If kamailio forward call to the UDP destination, mhomed option chooses the
correct Via and the correct network interface for sending.
But if the destination is tls, mhomed chooses first described in
configuration file "listen=" interface and use this IP in Via header
Network routes in the system are correct and "ip r get IP" returns the
correct route and interface.
Should mhomed work with tcp/tls or is this impossible with TCP design?
--
Aidar
