I may find a little bit more time to add another version that will take 4
parameters and would be able to select a destination anywhere in the stack. I
believe this should be easy given the set of helper functions available. But
this PR seems to be working fine for me.
--
You are receiving th
- URL:
https://github.com/kamailio/kamailio/commit/3849f7f07cdac109ea6ddb055315fef1ce73133e
Author: Daniel-Constantin Mierla
Date: 2019-09-24T18:01:14+02:00
apy_python: fixed condition in matching parameter types
- GH #1944
(cherry picked from commit cbec7f92213de1ff096ea00c5a7a3b6354f7ede9
Module: kamailio
Branch: master
Commit: 24988041d42c752c8202829d8e92d7a75762ab96
URL:
https://github.com/kamailio/kamailio/commit/24988041d42c752c8202829d8e92d7a75762ab96
Author: Henning Westerholt
Committer: Henning Westerholt
Date: 2019-09-24T22:29:25+02:00
Makefile.defs: fix doc URL for pre
Module: kamailio
Branch: master
Commit: 0d8a19fde8f46d175302f5fe77caed1bdef1a8bc
URL:
https://github.com/kamailio/kamailio/commit/0d8a19fde8f46d175302f5fe77caed1bdef1a8bc
Author: Henning Westerholt
Committer: Henning Westerholt
Date: 2019-09-24T22:29:25+02:00
core: enable mem_join memory manag
Module: kamailio
Branch: master
Commit: 9ac7c87edb1c9fdbaaeaf413dc0586f32c646276
URL:
https://github.com/kamailio/kamailio/commit/9ac7c87edb1c9fdbaaeaf413dc0586f32c646276
Author: Kamailio Dev
Committer: Kamailio Dev
Date: 2019-09-24T16:31:56+02:00
modules: readme files regenerated - acc ... [s
Module: kamailio
Branch: master
Commit: 659e2c3ebb50f4a7362b4de2340883885391ebe6
URL:
https://github.com/kamailio/kamailio/commit/659e2c3ebb50f4a7362b4de2340883885391ebe6
Author: Victor Seva
Committer: Victor Seva
Date: 2019-09-24T16:25:28+02:00
acc: update doc reference to wiki [skip ci]
---
Module: kamailio
Branch: 5.2
Commit: f8f056b9e822aa7a6fa7abc0e335a6fc64cf603e
URL:
https://github.com/kamailio/kamailio/commit/f8f056b9e822aa7a6fa7abc0e335a6fc64cf603e
Author: Kamailio Dev
Committer: Kamailio Dev
Date: 2019-09-24T12:17:23+02:00
modules: readme files regenerated - modules ... [
- URL:
https://github.com/kamailio/kamailio/commit/09ac3e47ef79dbd599b7dec5b84ae3b792f025ed
Author: Daniel-Constantin Mierla
Date: 2019-09-24T11:49:37+02:00
tm: set send socket flag when computing the destination and local socket is
found
(cherry picked from commit 8d608d1c3ed0fe4c69cb02868
Thanks for feedback, I am going to backport to stable branches.
--
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/2063#issuecomment-534479943__
Closed #1834.
--
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/1834#event-2657116708___
Kamailio (SER) - Development Mailing List
sr-dev@l
There were a memory leak present in the xavp_clone_level_nodata function. From
a look to the code it looks that it was used also in the registrar lookup
function if the xavp_rcd parameter was set.
This was fixed in 0c93efec739 and also backported to 5.2 and 5.1 branch. This
fix is included in 5.
Hello,
Yes, all is working fine either with the openssl_mutex_shared.so
preload at start or the next 5.3.0 release.
I close the issue.
Thanks !
--
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/
Closed #2063.
--
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/2063#event-2657070930___
Kamailio (SER) - Development Mailing List
sr-dev@l
Thank you. From the code it looks good to me. I think it can be merged when git
master is opened again (after 5.3.0 release).
--
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/2070#iss
@bodji How does it works out for you, can this be closed? About the question
related to the libressl team, I am not aware of any news here. For 5.3.0(-pre)
the library workaround have been added to the core.
--
You are receiving this because you are subscribed to this thread.
Reply to this emai
Hello,
quick note to say that the release ov v5.1.9 is likely to be done on
Thursday, given there was not enough time to sort out some patches for
backporting.
Cheers,
Daniel
On 19.09.19 17:02, Daniel-Constantin Mierla wrote:
> Hello,
>
> I am considering to release v5.1.9 out of the branch 5.1
16 matches
Mail list logo