Hi,
I just tried to send numbers of SIP register to kamailio (release 5.8.2). It is reported that there are some memory leakage in shared memory after the expiry of all the registration sessions. After drill down the code. function save_pending(...) is called. (in ims_registrar_pcscf/save.c). Inside that function, it seems that "sec_verify_params" is not deallocated upon the function completes.
Findings:
- sec_verify_params uses the result from function cscf_get_security_verify(...)
- Function cscf_get_security_verify(...) returns the result of function parse_sec_agree(...)
- Function parse_sec_agree(...) returns "params" where "shm_malloc(...)" is called
It seems that the memory pointed by 'sec_verify_params' is not further referenced by others. Should shm_free(...) be called when leaving function save_pending(...) in order to free the unused memory of 'sec_verify_params'?
Please advice.
Thank you.
Regards,
Hong
Hello,
I was wondering if icc or suncc compilers are still used in the
community, and by that if it still worth trying to support them via
Makefiles and compile time flags (defines). Personally I haven't had to
deal with them for more than 10-15 years, I have no access with a system
offering them. Furthermore, I am not even sure if the code compiles with
them.
Maybe someone (or many) in the community use one or the other and
confirm that they still worth to be kept.
If not, maybe we can consider them for removing, it can be a good task
to be done during Kamailio development meeting planned in Dusseldorf,
Germany during November.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, October 8-10, 2024 -- asipto.com
Hi,
I just tried to use kamailio 5.8.3 as an IMS-PCSCF. After handling SIP registration, it seems that value of port in the "via" header in the request sent from PCSCF to UE is a bit strange.
When using uac_req to send OPTIONS to UE, it is found that in the OPTIONS sent out from kamailio, the value of port inside the "via" header is set to port_pc (pcscf ipsec client port). Is this correct? Or should the via header port be set to port_ps (pcscf ipsec server port) instead?
Also, in uac_req, is the value of via port header configurable?
Please advise.
Thank you.
Regards,
Hong
Hello,
I'm using async task group to handle some pourcentage of the traffic, while testing with traffic of 1200cps I got the following error :
ERROR: {1910812149 INVITE 6785db25bc3f2478@ip} <core> [core/async_task.c:439]: async_task_group_push(): failed to pass the task [0x7f4000c3a5c0] to group [async_group_name].
conf:
async_workers_group="name=async_group_name;workers=45;nonblock=1;usleep=100"
If someone can help please?
Hello!
I need to disable topos for one specific SIP trunk (in-out), it looks like
it’s enough to use event_route with IP address filtering.
But for some reason, the incoming INVITE from the peer still gets processed
by topos and I also don’t see a mention of [msg-incoming] in the logs, only
this:
WARNING: <script>: [msg-outgoing] OPTIONS/you/1.1.1.1
Code snippet:
loadmodule "topos.so"
modparam("topos", "db_url", DBURL)
modparam("topos", "contact_mode", 1)
modparam("topos", "header_mode", 1)
modparam("topos", "methods_noinitial", "OPTIONS,SUBSCRIBE,PUBLISH")
modparam("topos", "dialog_expire", 7210)
modparam("topos", "rr_update", 1)
modparam("topos", "event_mode", 5)
/*
1 - execute event_route[topos:msg-outgoing]
2 - execute event_route[topos:msg-sending]
4 - execute event_route[topos:msg-incoming]
8 - execute event_route[topos:msg-receiving]
*/
request_route {
....
event_route[topos:msg-outgoing] {
if ( $sndto(ip) == "1.1.1.1" ) {
xlog("L_WARN","[msg-outgoing] $rm/$rU/$sndto(ip) \n");
drop;
}
}
}
event_route[topos:msg-incoming] {
if ( $si == "1.1.1.1" ) {
xlog("L_WARN","[msg-incoming] $rm/$rU/$si \n");
drop;
}
}
# kamailio -v
version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty
--
BR,
Denys Pozniak
Dear experts,
Would appreciate if anyone can explain why in the given sample Lua script the 'Handle Retransmission' block checks the return code of t_check_trans (if KSR.tm.t_check_trans == 0 then), but in the Kamailio native config standard file if just calls the t_check_trans() function without checking the return code. What is the intention here and how does it work? Thank you in advance.
Handle retransmission script from native config file:
if (!is_method("ACK")) {
if(t_precheck_trans()) {
t_check_trans();
exit;
}
t_check_trans();
}
Handle retransmission from sample Lua script:
if not KSR.is_ACK() then
if KSR.tmx.t_precheck_trans() > 0 then
KSR.tm.t_check_trans();
return 1;
end
if KSR.tm.t_check_trans() == 0 then
return 1;
end
end
How can I set the destination URI for an INVITE to be a
websocket-secure destination? Is it possible?
Summary
I've a proxy with tcp_connection_match=1, but websocket URIs always
have transport=ws (never transport=wss) in them, so relaying a call to
a WSS connection always fails.
I tested running kamailio 6.0.0-dev2 compiled from a commit made this
week. This proxy server uses nathelper rather than outbound module.
Detail
We know that "transport=ws" is used for both WS and WSS. I've a proxy
server that receives an INVITE for a WSS destination, and this proxy
supports both WS and WSS.
This proxy server must have core parameter tcp_connection_match=1 set,
and this leads the t_relay() to fail.
When an INVITE comes, these are the steps.
- The URI is something like
sip:user@anonymous.invalid;alias=198.51.100.10~52833~6;transport=ws.
- First handle_ruri_alias() removes the alias (which has ~6 in it, for
wss) and sets the $du to something like
sip:198.51.100.10:52833;transport=ws.
- Then loose_route_preloaded() processes the Route header fields and
forces the outbound socket to the TLS websocket one.
- Then t_relay() fails to relay the INVITE and responds with 477 or 500.
If, however, there's a non-TLS websocket connection open to the proxy,
the INVITE would be erroneously relayed over that (using the wrong
kamailio-side TCP port).
I can go deeper with testing if required. I wonder whether this is a bug.
James
Hello!
I was wondering if someone was trying to build Kamailio RPM packages
containing modules secsipid and secsipid_proc and faced the same problem.
I compiled secsipidx library and copied secsipid.h, libsecsipid.h as well
as libsecsipid.a files into the source directory of secsipid_proc module.
And when I'm trying to build RPM packages, I get the following error:
CC (gcc) [M secsipid_proc.so] secsipid_proc_mod.o
secsipid_proc_mod.c:28:10: fatal error: secsipid.h: No such file or
directory
#include <secsipid.h>
^~~~~~~~~~~~
compilation terminated.
make[2]: *** [../../Makefile.rules:100: secsipid_proc_mod.o] Error 1
make[1]: *** [Makefile:508: modules] Error 1
make[1]: Leaving directory '/builddir/build/BUILD/kamailio-5.8.2/src'
make: *** [Makefile:34: every-module] Error 2
Thanks a lot!
Hello,
Kamailio SIP Server v5.8.3 stable release is out.
This is a maintenance release of the latest stable branch, 5.8, that
includes fixes since the release of v5.8.2. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.8.x. Deployments running previous v5.8.x
versions are strongly recommended to be upgraded to v5.8.3.
For more details about version 5.8.3 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2024/09/kamailio-v5-8-3-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, October 8-10, 2024 -- asipto.com
Hi all,
Just need some clarifications about the Permissions module: I currently use
it with db_mode = 1 and was expecting that the
parameter "trusted_cleanup_interval" would refresh the cache tables every X
seconds, but apparently this is not the case.
I was looking for a way for Kamailio to automatically reload the address
table into memory every 5 minutes, for example, and I (mis)understood
that "trusted_cleanup_interval" would do the trick, but it doesn't work as
expected.
Question: is there any command, besides kamcmd, to automatically reload the
permissions table? I would like to avoid having to add a line in the
crontab....
Atenciosamente / Kind Regards / Cordialement / Un saludo,
*Sérgio Charrua*
