@wkampich Thanks - did you pushed to the wkampich/lost branch in your fork? I
just asked because it does not seems to be updated yet.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Thank you Henning, I just pushed an updated version with your feedback
incorporated.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
wkampich commented on this pull request.
> +static int mod_init(void)
+{
+ LM_DBG("init lost module\n");
+
+ if(httpc_load_api() != 0) {
+ LM_ERR("Can not bind to http_client API \n");
+ return -1;
+ }
+
+ LM_DBG(" init lost module
Hi Daniel,
good tip about the crypto module.
It will indeed hide the IP address in the call-id, just tried it:
Call-ID: d810d369-aa60-4d79-aee5-9c03d2e66781
I think if we would feed the sruid unique ID (in libs/srutils) into the SHA256
hash (also available there) this it should be secure
Module: kamailio
Branch: 5.1
Commit: f031ae7792ab487b6bbcae7c5df3103431441668
URL:
https://github.com/kamailio/kamailio/commit/f031ae7792ab487b6bbcae7c5df3103431441668
Author: Kamailio Dev
Committer: Kamailio Dev
Date: 2019-08-14T19:37:55+02:00
add ims_usrloc_scscf README
---
Added:
Module: kamailio
Branch: 5.2
Commit: 6670a3b6403fb43670042103ce4e087f92fa0c1b
URL:
https://github.com/kamailio/kamailio/commit/6670a3b6403fb43670042103ce4e087f92fa0c1b
Author: Kamailio Dev
Committer: Kamailio Dev
Date: 2019-08-14T19:37:37+02:00
add ims_usrloc_scscf README
---
Added:
You are right. Unfortunately it was not backported after the merge in the
referenced ticket. I did it just now for 5.1 branch and 5.2 branch.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
You are right. Unfortunately it was not backported after the merge in the
referenced ticket. I did it just now for 5.1 branch and 5.2 branch.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Module: kamailio
Branch: 5.1
Commit: 263a078e581c11173d89f1114fa8827ee6259c35
URL:
https://github.com/kamailio/kamailio/commit/263a078e581c11173d89f1114fa8827ee6259c35
Author: Yasin CANER
Committer: Henning Westerholt
Date: 2019-08-14T18:15:12+02:00
ims_usrloc_scscf: doc is added
Module: kamailio
Branch: 5.2
Commit: 3dc241b48be634ff43ef9e0a4c4f4ddf33a6
URL:
https://github.com/kamailio/kamailio/commit/3dc241b48be634ff43ef9e0a4c4f4ddf33a6
Author: Yasin CANER
Committer: Henning Westerholt
Date: 2019-08-14T18:14:03+02:00
ims_usrloc_scscf: doc is added
Branch **5.2** now has README file missing in ims_usrloc_scscf module.
This causes _kamailio-ims_ package built to fail:
```
Processing files: kamailio-ims-5.2.4-1.el6.x86_64
error: File not found:
Hello,
Kamailio SIP Server v5.2.4 stable release is out.
This is a maintenance release of the latest stable branch, 5.2, that
includes fixes since the release of v5.2.3. There is no change to
database schema or configuration language structure that you have to do
on previous installations of
Module: kamailio
Branch: 5.2
Commit: 759867b67e1031d037378168984b87b2590fb7c5
URL:
https://github.com/kamailio/kamailio/commit/759867b67e1031d037378168984b87b2590fb7c5
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-08-14T11:35:30+02:00
ChangeLog: content
Module: kamailio
Branch: 5.2
Commit: 0c23deeaad6b54236966807172388f4073e54dde
URL:
https://github.com/kamailio/kamailio/commit/0c23deeaad6b54236966807172388f4073e54dde
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-08-14T11:17:03+02:00
Makefile.defs: version
Module: kamailio
Branch: 5.2
Commit: 7218d1fdad903fabaff224cf2be8212013e35221
URL:
https://github.com/kamailio/kamailio/commit/7218d1fdad903fabaff224cf2be8212013e35221
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-08-14T11:13:54+02:00
pkg/kamailio: updated
Whoops! Thanks Daniel, looks like I forgot to make install on my UAT server.
I'll re-test and update ASAP.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
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
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
Module: kamailio
Branch: master
Commit: 897f58fd48c68d88df7967c1390a23f8b9069a61
URL:
https://github.com/kamailio/kamailio/commit/897f58fd48c68d88df7967c1390a23f8b9069a61
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-08-14T09:53:17+02:00
sqlops: add a limit
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
Module: kamailio
Branch: 5.2
Commit: f4f08a901bd798acd237851c7299c6d07083974e
URL:
https://github.com/kamailio/kamailio/commit/f4f08a901bd798acd237851c7299c6d07083974e
Author: Victor Seva
Committer: Victor Seva
Date: 2019-08-14T08:32:33+02:00
pkg/kamailio/deb: version set to 5.2.4 [skip ci]
Hello,
the usual reminder that the v5.2.4 is going to be released today from
git branch 5.2, therefore any commits to that branch should be announced
first on sr-dev or irc channel and wait for ack, in order to avoid
conflicts with release building process. Once the announcement of the
release is
The version you used is before the fix -- the commit id in your version points
to:
```
commit 4c537a618949eb48ffed9297f3abc8cdc879b70d
Author: Daniel-Constantin Mierla
Date: Tue Aug 6 21:37:56 2019 +0200
misc_radius: increase MAX_EXTRA from 4 to 8
```
To have the version with the fix,
24 matches
Mail list logo