@riccardv commented on this pull request.
@@ -100,8 +100,15 @@ static void string_to_key(char*
dst, const str key_string)
}
}
+static uint choose_nlmsg_seq (void)
Hi @henningw ,
I choose the 1 micro seconds granulation due to the commit comment:
"improve nlmsg_seq choice for concurrent multi UEs Registrations at same time"
The reason is the previous choice of time(NULL) return a time value on seconds and it can
be too large in presence of multiple UE access in the same time. In high load condition it
can be happens.
IPsec Security Association must have this parameter as a unique identifier, since kamailio
can be configured to listen on single local ip:port for IPsec, it can be a problem,
resulting in a failure on activation of SA, and then a failure on VoLTE SIP REGISTRATION.
A time based choice is a good choice, but 1 second is not enough, so I propose the choice
of 1 micro second granularity that can be protect the registrations in a reasonable way.
Regarding other platforms that don't have the funtion, feel free to add a pre
processor condition on the function
--
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/pull/2731#discussion_r629325968