Hello Georgi,
you might want to look into the code to see if there is maybe some condition where it not
send out a SAR message.
Maybe also investigating the size of the difference is worthwhile as well. It might be a
particular bug, but is hard to say without going more into the details. If you enable
debug log level for Kamailio you will get more information about the internal processing
from many modules and the core.
Cheers,
Henning
--
Henning Westerholt –
https://skalatan.de/blog/
Kamailio services –
https://gilawa.com<https://gilawa.com/>
From: sr-dev <sr-dev-bounces(a)lists.kamailio.org> On Behalf Of Georgi Rosenov
Stefanov
Sent: Wednesday, June 3, 2020 4:10 PM
To: sr-dev(a)lists.kamailio.org
Subject: [sr-dev] missing SAR messages
I found that pcscf_save_pending("location"); from route[REGISTER] from
pcscf/route/register.cfg is responsible for SAR sending.
Again the number of invocation of pcscf_save_pending("location") is not the same
as the REGISTER requests.
Hi All,
I am experimenting with Kamailio 5.3.3 as an IMS and I am trying to do load tests
I am using SIPp to generate SIP.REGISTER and MariaDB and a DIAMETER tool ( seagull)
For now I achieved registrations with "speed" 200 per/sec.
When I send SIP.REGISTER faster(let's say 500 per/sec) I see some SARs missing, not
sent at all.
I start debugging and found that cxdx_send_sar is responsible to creating SAR message. I
put my debug message in it.
The strange thing: there is a mismatch of my debug message (cxdx_send_sar invocation) and
real SAR send over the network.
What is the thing I missing ?
Is there anything else responsible for SAR creating except cxdx_send_sar ?
Did someone made similar tests ?
my test machine is Centos 7 with 3.10.0
Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
16G RAM
During this tests I see kamailio very low CPU usage, even when I push it with 500/sec
The biggest CPU load is in MariaDB, but I do not have issues with UAR and MAR