<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Works!!</p>
<p>Thank you<br>
</p>
<pre class="moz-signature" cols="72">-----
Andrea Sannucci - @AS</pre>
<div class="moz-cite-prefix">El 13/12/2024 a las 6:39 p. m., Ovidiu
Sas escribió:<br>
</div>
<blockquote type="cite"
cite="mid:CAND0Lkuev_RLm67zqM5Yo7kZx3WEKVw8wJV=3-BNkUcCrGLqKA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Take a look here:</div>
<div dir="auto">
<div><a
href="https://voipembedded.wordpress.com/2021/03/23/troubleshooting-opensips-encrypted-sip-traffic/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://voipembedded.wordpress.com/2021/03/23/troubleshooting-opensips-encrypted-sip-traffic/</a></div>
<br>
</div>
<div dir="auto">-ovidiu</div>
<div><br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Fri, Dec 13, 2024 at
17:29 Social Boh <<a href="mailto:social@bohboh.info"
moz-do-not-send="true" class="moz-txt-link-freetext">social@bohboh.info</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Hello,<br>
<br>
from proto_hep module DOC: "Once loaded, you will be able to
define HEP <br>
listeners in your configuration file by adding their IP and,
optionally, <br>
a listening port. You can define both TCP, UDP, and TLS
listeners. On <br>
UDP you will be able to receive HEP v1, v2 and v3 packets,
on TCP and <br>
TLS only HEPv3."<br>
<br>
but<br>
<br>
socket= hep_tls:<a href="http://127.0.0.1:6061"
rel="noreferrer" target="_blank" moz-do-not-send="true">127.0.0.1:6061</a><br>
<br>
CRITICAL:core:yyerror: parse error in <br>
/etc/opensips/opensips.cfg:44:8-15: cannot handle protocol
<hep_tls><br>
<br>
Regards<br>
<br>
---<br>
I'm SoCIaL, MayBe<br>
<br>
El 13/12/2024 a las 4:59 p. m., Social Boh escribió:<br>
> Hello everyone and to this fascinating list,<br>
><br>
> before spending more time than I already have, I would
like to know if <br>
> there is a way to send the capture of the SIP/TLS
signal to SNGREP. In <br>
> Kamailio I can easily do it with the SIPTRACE module
but in OpenSIPs I <br>
> have not yet found the configuration. The acquisition
of the SIP UDP <br>
> and TCP signaling works smoothly.<br>
><br>
> Thanks to everyone for sharing<br>
><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">Users@lists.opensips.org</a><br>
<a
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</body>
</html>