Hi,
we do this on the application level with the siptrace [1] module:
loadmodule "proto_hep.so"
loadmodule "siptrace.so"
listen = hep_udp:127.0.0.1:60PRIMARYVIP
modparam("proto_hep", "hep_id", "[hep_dst] 127.0.0.1:50667; version=2")
modparam("siptrace", "trace_on", 0)
modparam("siptrace", "trace_id", "[tid]uri=hep:hep_dst")
################## MAIN ROUTING ######################
route {
sip_trace("tid");
Now you can trace the unencrypted packets on 127.0.0.1:50667 via
ngrep/tcpdump/...
Maybe this helps you a little.
Fabian
[1] https://opensips.org/html/docs/modules/2.4.x/siptrace
----- Ursprüngliche Mail -----
Von: "Mark Farmer" <farm...@gmail.com>
An: "OpenSIPS users mailling list" <users@lists.opensips.org>
Gesendet: Mittwoch, 11. März 2020 17:48:06
Betreff: [OpenSIPS-Users] Advice on TLS debugging
Hi everyone
I am trying to setup a SIP/TLS connection using OpenSIPS 2.4 and I am
struggling to find a good way to examine SIP messages/responses due to them
being encrypted.
Normally I just sngrep but using the -k arg doesn't seem to be working.
How do others deal with this?
Many thanks
Mark.
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
