Fixed at d7c117b961b6c5b6d40cec9b81de94780578d5f2
--
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/1935#issuecomment-486818600___
Closed #1935.
--
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/1935#event-2301337486___
Kamailio (SER) - Development Mailing List
Module: kamailio
Branch: master
Commit: 4b160fd72bc0e532d189d565b86e3f7c1e15926b
URL:
https://github.com/kamailio/kamailio/commit/4b160fd72bc0e532d189d565b86e3f7c1e15926b
Author: Ovidiu Sas
Committer: Ovidiu Sas
Date: 2019-04-25T14:58:55-05:00
lcr: make rpc command lcr.load_gw more verbose
@linuxmaniac - is this still an issue in the current master branch or was it
fixed in the last years?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
No update since a few months. As the issue is from 2016 I am going to close
this one. Please re-open with more details if the problem is still valid.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #569.
--
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/569#event-2301295326___
Kamailio (SER) - Development Mailing List
@ionutionita92 any news on this enhancement idea from your side?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@kirill-usov did you managed to trace the complete traffic? Please also include
the debug output as mentioned before.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Thank you, can you try with the patch 280eabf1 and report back the result? I
will then backport it to the stable branches as well.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Module: kamailio
Branch: master
Commit: 280eabf16a45f522655f8b49677e46c75d34024f
URL:
https://github.com/kamailio/kamailio/commit/280eabf16a45f522655f8b49677e46c75d34024f
Author: Henning Westerholt
Committer: Henning Westerholt
Date: 2019-04-25T21:38:44+02:00
pv: clone string in all substr
Module: kamailio
Branch: master
Commit: 600490c546502786eaef1f2bfbeb18a5bb2a2ee1
URL:
https://github.com/kamailio/kamailio/commit/600490c546502786eaef1f2bfbeb18a5bb2a2ee1
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-04-25T21:01:12+02:00
core: new global
I'm using Kamailio 5.2.2+xenial.
Set up a basic tls.cfg like this:
```
[server:default]
verify_certificate = no
require_certificate = no
private_key = /tmp/default.key
certificate = /tmp/default.pem
[server:any]
method = TLSv1
verify_certificate = no
require_certificate = no
private_key =
@miconda We got rid of the trunks/accounts causing 500 errors and auth failure,
yet are still seeing the leak in the kamailio process.
Any other way to troubleshoot this?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
13 matches
Mail list logo