[OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl

[Bogdan-Andrei Iancu]

Right, and that's good :). Still I'm trying to understand what were the 
settings that were not properly working - trace_on only in TLS, but not 
in TCP? or?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/11/22 9:05 AM, Artiom Druz wrote:
> Hi Bogdan.
> For now I see that Homer is catching info correctly, and I can see 
> what was happened inside TLS calls in Homer's web-interface.
>
> ср, 10 авг. 2022 г., 12:53 Bogdan-Andrei Iancu <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>>:
>
>     Hi Artiom,
>
>     So you initially had only the trace_on set in the proto_tls
>     module, generating some HEP packages which were not understood by
>     HOMER, right ?
>
>     And after setting the trace_on in the proto_tcp module, the issue
>     went away? but do you get HEP packages about about the TCP and TLS
>     events in OpenSIPS - I'm asking as I have to say this part was not
>     tested by some time :-/
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS Summit 27-30 Sept 2022, Athens
>        https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>
>     On 8/10/22 5:44 AM, Artiom Druz wrote:
>>     Hi Bogdan.
>>     I use trace_on parameter of proto_tls module and subroute for
>>     sending messages to Homer.
>>
>>     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.
>>
>>     вт, 9 авг. 2022 г., 13:42 Bogdan-Andrei Iancu
>>     <bogdan at opensips.org <mailto:bogdan at opensips.org>>:
>>
>>         Hi Artiom,
>>
>>         Do you use any proto TCP or TLS specific tracing (like [1]),
>>         or only pure SIP TLS tracing ?
>>
>>         [1]
>>         https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on
>>         <https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on>
>>
>>         Regards,
>>
>>         Bogdan-Andrei Iancu
>>
>>         OpenSIPS Founder and Developer
>>            https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>>         OpenSIPS Summit 27-30 Sept 2022, Athens
>>            https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>>
>>         On 7/25/22 11:20 AM, Artiom Druz wrote:
>>>         Hello Everyone.
>>>         I have a problem with monitoring SIPS/TLS based on
>>>         tls_wolfssl module via proto_hep (target monitoring service
>>>         is Homer 7).
>>>         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:
>>>
>>>         HEP3 Protocol
>>>             HEP Version: HEP3
>>>             HEP Packet Size (Bytes): 152
>>>             IP family: IPv4
>>>             Ingested Transport Protocol: IPv4
>>>             Source port: 0
>>>             Destination port: 0
>>>             Unix Timestamp: 1658731857
>>>             Timestamp µs: 106136
>>>             Application Protocol: Unknown Application Protocol
>>>             Capture Node ID: 1301
>>>             Source IPv4 address: 127.0.0.2
>>>             Destination IPv4 address: 127.0.0.2
>>>             Encapsulated Payload: TLS:CLOSED:SUCCESS:Read error
>>>             Correlation ID: 350784072629638188
>>>
>>>         Only unix timestamp and capture node id is correct.
>>>         As you can see in encapsulated payload I have an error with
>>>         read. What can be wrong?
>>>
>>>         OpenSIPS 3.2.5 (git revision 7e284ab03) compiled from source.
>>>
>>>         _______________________________________________
>>>         Users mailing list
>>>         Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users  <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220811/cd836394/attachment.html>