Closed #2032.
--
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/2032#event-2555766339___
Kamailio (SER) - Development Mailing List
sr-dev@l
Thanks for opening our eyes once again, @miconda! We already thought of
something like this, but got stuck in the second parameter. Indeed we set the
user id as result identifier. We changed it to a static string now, I think the
problem should disappear.
--
You are receiving this because you
I pushed a patch to set an upper limit to the number of result containers that
can be defined.
Probably there are couple of other places in different modules where a similar
case can happen, because in the native kamailio.cfg such parameters are
typically restricted to static string, expecting
What is the third parameter of the sql query function: `user`? A javascript
variable that can have random value? If yes, then you create result containers
for each of its values. You should use there a static string.
--
You are receiving this because you are subscribed to this thread.
Reply to
Hello Sebastian, thanks for the report. Do you observe this as well with 5.1.8
or latest 5.1 branch? There have been almost 450 commits since release of 5.1.4
to this branch.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
### Description
We are running Kamailio 5.1.x in a mixed native/Kemi environment. That means,
most of the config is still native Kamailio language, but some newer functions
were written in JS and included via `jsdt_run("...");`.
In one of those functions, we place an sqlops query. And since in