Re: [OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl
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 : > 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 > OpenSIPS Summit 27-30 Sept 2022, Athens > 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 : > >> 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 >> >> 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 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 >> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl
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 : > 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 > > 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 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 > listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl
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@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] opensips 3.2 and latest github rtpengine
Hello, Alberto.
You can modify it by using an optional parameter in rtpengine_offer
(sdp_var -
https://opensips.org/html/docs/modules/3.2.x/rtpengine#func_rtpengine_offer
).
Logic:
You can write new sdp body to the variable instead of rewrite of existing
SDP. After that you can modify "s" parameter in this variable.
Next - you delete existing SDP (remove_body_part()) and add new SDP with
content from variable (add_body_part()).
Best regards,
Artiom Druz
чт, 24 мар. 2022 г., 04:34 Alberto :
> Hi,
>
> I'm trying to change the session name, the s= line, while using rtpengine.
>
> If I remove rtpengine and do replace_body_all("^s=.*$", "s=abczzz"); it
> works just fine and I see the new session name in the second leg of the
> call.
>
> But when rtpengine_offer is called, the original sdp body is used instead
> of the modified body.
> I tried to do replace_body_all before and after rtpengine_offer, but it
> doesn't work, the second leg always has the original session name.
>
> Any advice?
> Thanks
> ___
> 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
Re: [OpenSIPS-Users] mid_registrar multi domains
Hello, Andrei. You can do that by taking $tU (user from "To" header) and using some transformation function. In your example can be used s.select function. ( https://www.opensips.org/Documentation/Script-Tran-3-2#toc7) Best regards, Artiom Druz ср, 23 мар. 2022 г., 21:11 Andrei G. : > Hey guys, > > I successfully tested opensips with mid_registrar for one domain > > Is it possible to use opensips in front of 2 asterisk boxes and redirect > registrations based on a prefix username, not domain prefix? > > Something like > asterisk1-user@mid-registrar.domain - where opensips manage registration > for user@asterisk1 > asterisk2-user@mid-registrar.domain - where opensips manage registration > for user@asterisk2 > > Regards > Andrei G. > > ___ > 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
[OpenSIPS-Users] Problem with nathelper and anycast+fullsharing cluster
Hello. I have a problem with configuration of anycast + fullshare cluster with 3 nodes. When I'm trying to use nathelper with pings to sip-users by OPTIONS - the 200 OK responses sent to random nodes of anycast cluster. If response came to node different the "checker-node" - the "checker-node" thinks that sip-user is unavailable and deletes his location. I thought that I can fix this by using t_anycast_replicate(), but it is impossible - opensips stops on start with error (btw there is no limits about usage of this function in docs) I'm using OpenSIPS 3.1.0 (git rev. d36fa2b15) Regards, Artiom Druz ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
