<div dir="auto"><div>Hi Bogdan.</div><div dir="auto">I use trace_on parameter of proto_tls module and subroute for sending messages to Homer.</div><div dir="auto"><br></div><div dir="auto">I enabled trace_on parameter for proto_tcp module and now it works correct. I'm not sure if this is the only fix I made because it may have been a misconfiguration in the script logic.<br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">вт, 9 авг. 2022 г., 13:42 Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<font face="monospace">Hi Artiom,<br>
<br>
Do you use any proto TCP or TLS specific tracing (like [1]), or
only pure SIP TLS tracing ?<br>
<br>
[1]
<a href="https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on" target="_blank" rel="noreferrer">https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on</a><br>
<br>
Regards,<br>
</font>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="https://www.opensips-solutions.com" target="_blank" rel="noreferrer">https://www.opensips-solutions.com</a>
OpenSIPS Summit 27-30 Sept 2022, Athens
<a href="https://www.opensips.org/events/Summit-2022Athens/" target="_blank" rel="noreferrer">https://www.opensips.org/events/Summit-2022Athens/</a></pre>
<div>On 7/25/22 11:20 AM, Artiom Druz wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">Hello Everyone.
<div dir="auto">I have a problem with monitoring SIPS/TLS based
on tls_wolfssl module via proto_hep (target monitoring service
is Homer 7).</div>
<div dir="auto">My opensips config works ok with SIP/UDP, but
when I make a call via TLS (OpenSIPS convert TLS from VoIP
provider to internal SIP/UDP software PBX) in dump file on
Homer 7 side I see that all packets in HEP3 payload has this
info:</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div dir="auto">HEP3 Protocol</div>
<div dir="auto"> HEP Version: HEP3</div>
<div dir="auto"> HEP Packet Size (Bytes): 152</div>
<div dir="auto"> IP family: IPv4</div>
<div dir="auto"> Ingested Transport Protocol: IPv4</div>
<div dir="auto"> Source port: 0</div>
<div dir="auto"> Destination port: 0</div>
<div dir="auto"> Unix Timestamp: 1658731857</div>
<div dir="auto"> Timestamp µs: 106136</div>
<div dir="auto"> Application Protocol: Unknown Application
Protocol</div>
<div dir="auto"> Capture Node ID: 1301</div>
<div dir="auto"> Source IPv4 address: 127.0.0.2</div>
<div dir="auto"> Destination IPv4 address: 127.0.0.2</div>
<div dir="auto"> Encapsulated Payload:
TLS:CLOSED:SUCCESS:Read error</div>
<div dir="auto"> Correlation ID: 350784072629638188</div>
<div dir="auto"><br>
</div>
<div dir="auto">Only unix timestamp and capture node id is
correct.</div>
<div dir="auto">As you can see in encapsulated payload I have
an error with read. What can be wrong?</div>
<div dir="auto"><br>
</div>
<div dir="auto">OpenSIPS 3.2.5 (git revision 7e284ab03)
compiled from source.</div>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank" rel="noreferrer">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank" rel="noreferrer">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div></div></div>