Thanks Daniel,
The changes seem to be fine. Please go ahead with making these available for
the previous releases as well.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2322#issuecomment-633429846
Hi kamailio-sync,
Thanks for the inputs. However, I was referring to the usage of lock in the
function that calculates the dispatcher latency stats and suggesting to use the
same lock while accessing the 'dload' parameter so as to avoid concurrent
access issues related to the 'dload' parameter a
Thanks Daniel,
I will await your response on the issue then, regarding using the lock or
atomic integers. I presume the atomic integer usage must be faster than the
locking approach.
FWIW, a similar locking is being used in 'dp_init_relative_weights()' and
'ds_update_latency' APIs in dispatch.c
Thanks for the quick look and review henningw. I'll try to do this tonight post
work, else max by tomorrow. I am in IST timezone.
--
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/23
### Description
While running a simple load with a UAC(Sipp) and two UAS(Both Sipp) , with
Kamailio in the middle, acting as a Call Stateful Proxy, I observed that the
Dispatcher Module reports one call stuck despite NO calls being reported as
Active in the Dialog Module.
Setup:
---
