7 May
2019
7 May
'19
4:07 p.m.
Hello,
you can also check out by commit id to a version before the update of
siptrace, it should be possible to do it for the files of siptrace, all
the rest be the latest master.
This will be fixed, just a time when a lot of devs are traveling to
Berlin. It's a regression by a large enhancement of the module, there
are many commits there, so reverting is not the easiest option here,
because the enhancement has to stay, only the regression needs to be fixed.
There is also the alternative of using sipdump module if your only
purpose is to look at tls traffic -- it has also more context
information and some metadata.
Cheers,
Daniel
On 07.05.19 17:12, Juha Heinanen wrote:
Henning Westerholt writes:
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
In the end this is the git master development and
should be not used
in production.
I'm not using it for production but for testing where I need
siptrace
module due to tls.
There should be some kind of policy regarding broken commits, i.e., for
how long K can remain broken until a revert is done.
-- Juha
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev