Hello,

 

this seems not generally true. Just testing it with Kamailio 5.3.4.

 

modparam("siptrace", "trace_to_database", 0)

modparam("siptrace", "trace_on", 1)

modparam("siptrace", "duplicate_uri", "sip:XXXX:YYYY")

 

route{ …        sip_trace_mode("t");… }

 

This is ignored, no messages are traced. If I add a sip_trace(“XXXX:YYYY”) as well, it trace one message (not two).

 

It seems that the sip_trace_mode(“t”) is just ignored. If I remove the URI from the sip_trace, it also does not trace anything, it seems to also ignore the duplicate_uri. No error messages etc.. in the logs.

 

Cheers,

 

Henning

 

--

Henning Westerholt – https://skalatan.de/blog/

Kamailio services – https://gilawa.com

 

From: sr-users <sr-users-bounces@lists.kamailio.org> On Behalf Of Federico Cabiddu
Sent: Thursday, June 4, 2020 5:16 PM
To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Subject: Re: [SR-Users] Kamailio 5.3.0 and HEPv3 oversized traffic

 

Hi Karsten,

you don't have to call sip_trace() if you call sep_trace_mode("t") otherwise you'll have duplicated messages.

 

Cheers,

 

Federico

 

On Thu, Jun 4, 2020 at 4:54 PM Karsten Horsmann <khorsmann@gmail.com> wrote:

Hi Sergiu,

 

thanks for pointing that out. I tried kamailio 5.3.4 with the settings below.

Works now. I see the answers of kamailio itself.

 

Unfortunately my UAC input messages are now doubled in homer.

Will check that tomorrow.

 

And for fun - with sip_trace i can send to more than one target, nice.

 

#!ifdef WITH_HOMER
        # start duplicate the SIP message here
        sip_trace();
        # address - The address in form of SIP URI where to send a duplicate of traced message.
        sip_trace("sip:127.0.0.1:9060");
        sip_trace_mode("t");

        #setflag(22);
#!endif


modparam("siptrace", "force_send_sock", "MY_LOCAL_SENDSOCK")
modparam("siptrace", "duplicate_uri", "MY_HOMER_CAPTURE")
modparam("siptrace", "hep_mode_on", 1)
modparam("siptrace", "hep_version", 3)
modparam("siptrace", "trace_to_database", 0)
##modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_mode", 3)
modparam("siptrace", "hep_capture_id", MY_HEP_NODE_ID)

 

Cheers

Karsten Horsmann

 

Am Mi., 3. Juni 2020 um 23:25 Uhr schrieb Sergiu Pojoga <pojogas@gmail.com>:

Compared to previous versions, under 5.3, one must invoke the sip_trace_mode() function if you wanted to see the full SIP flow in Homer. It's not clear from documentation that it's a must function, but it did fix the problem in my case.

 

For example:

 

sip_trace();
sip_trace_mode("t")

 

On Wed, Jun 3, 2020 at 3:25 PM Karsten Horsmann <khorsmann@gmail.com> wrote:

Hi Frederico,

 

good point. Will also update my test setup and have a look at the new functions. 

 

Cheers 

Karsten Horsmann 

Federico Cabiddu <federico.cabiddu@gmail.com> schrieb am Mi., 3. Juni 2020, 20:41:

Hi,

did you try to capture the traffic going towards homer?

Siptrace module has internally changed in release 5.3 and some things that used to work in 5.2 are not working or are not doing it in the expected way.

There have been several fixes since 5.3.0, some of them are still only in master branch, I suggest you to use the latest 5.3.4 and have a look at the new capture modes and http://www.kamailio.org/docs/modules/5.3.x/modules/siptrace.html#siptrace.f.sip_trace_mode function.

Hope this helps.

 

Cheers,

 

Federico

 

On Wed, Jun 3, 2020 at 7:16 PM Karsten Horsmann <khorsmann@gmail.com> wrote:

Hi,

 

yes same config file. Forgot that to mention. 

 

Cheers

Karsten Horsmann 

 

David Villasmil <david.villasmil.work@gmail.com> schrieb am Mi., 3. Juni 2020, 18:48:

Same config file?

 

On Wed, 3 Jun 2020 at 17:20, Karsten Horsmann <khorsmann@gmail.com> wrote:

Hi list,

 

I saw some strange behavior in Kamailio 5.3.0 with HEPv3. My Kamailio serves webrtc and sip tls and captures that to an Homer 7.7 instance. 

 

I see only the UAC Parts of the message and not the answers from Kamailio in that scenario. 

 

Maybe I reached the max Paket size for udp. Hard to debug. In production I saw everything (but there I used and older Kamailio 5.2.x and Homer 5.5 which can handle fragment udp). 

 

Any ideas how to hunt the root cause of the problem? 

 

Cheers 

Karsten 

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

--

Regards,

 

David Villasmil

phone: +34669448337

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


 

--

Mit freundlichen Grüßen
*Karsten Horsmann*

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users