Johan, Unfortunately, the server on which I am tracing is only transaction-aware and does not have Dialog, so I cannot verify this.
I will say that we call trace() very early in message processing, almost first thing, and we do still see all changes on the outbound message. Ben Newlin From: Users <[email protected]> on behalf of johan <[email protected]> Date: Friday, January 22, 2021 at 9:38 AM To: [email protected] <[email protected]> Subject: Re: [OpenSIPS-Users] feasablity / interest in a feature request. I use this for invite based dialogs. trace("hep_id","d","sip"); I call it just before topology_hiding() I don't see from/to header changes. Can you check on your side Ben ? wkr, On 22/01/2021 15:28, Ben Newlin wrote: We are using siptrace and we get both the incoming and outbound message captured, with all changes. I think it depends on the scope you provide [1]. We use scope T for transactions and we get both. Although, we are using OpenSIPS 2.4. It’s possible the functionality has changed in 3.x. In which case, I would agree that it is not good. [1] - https://opensips.org/docs/modules/3.1.x/tracer.html#func_trace<https://opensips.org/docs/modules/3.1.x/tracer.html#func_trace> Ben Newlin From: Users <[email protected]><mailto:[email protected]> on behalf of Andy Dierlam <[email protected]><mailto:[email protected]> Date: Friday, January 22, 2021 at 9:13 AM To: OpenSIPS users mailling list <[email protected]><mailto:[email protected]> Subject: Re: [OpenSIPS-Users] feasablity / interest in a feature request. How about running a continuous tshark/pcap/ngrep on interfaces of interest. you can run every 10min. putting in 10min files. On Fri, Jan 22, 2021 at 6:36 AM johan <[email protected]<mailto:[email protected]>> wrote: yeah me too. but I want also to see the forwarded packet with all changes. On 22/01/2021 12:13, Nick Altmann wrote: It depends on purpose. For example, I need an initial (untouched) packet there. -- Nick пт, 22 нв. 2021 г. в 09:18, johan <[email protected]<mailto:[email protected]>>: Hi, when you use the siptrace module and you go to homer from opensips (hence without a port mirror/span port on a switch), when you change from /to header, then the homer trace doesnot reflect the real packet that exits opensips (as we all know, from to header changes are only active when the packet is send out). I find this annoying as the purpose of having a tracer is defeated by this : we want to see the real packets with the changes applied. Therefore : are there more people on the list who are ennoyed by this ? If yes, then I will open a feature request for it. wkr, _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users> _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users> _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users> _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
