[sr-dev] Re: [kamailio/kamailio] possible memory corruption in sipcapture module (Issue #3835)

2024-05-06 Thread Alexandr Dubovikov via sr-dev
another way to do it (just as a workaround) `` modparam("sipdump", "event_callback", "sipdump_event") //you can check everything here - method, si, RI and send to a destination. event_route[sipdump_event] { sip_trace("sip:10.1.1.2:5085", "$ci-abc"); } `` -- Reply to this email d

[sr-dev] Re: [kamailio/kamailio] possible memory corruption in sipcapture module (Issue #3835)

2024-05-06 Thread Alexandr Dubovikov via sr-dev
btw, same you can do for sipcapture:request - execute manual sip_trace and after send return 0 or exit; -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3835#issuecomment-2096390828 You are receiving this because you are subscribed to this thread.

[sr-dev] Re: [kamailio/kamailio] possible memory corruption in sipcapture module (Issue #3835)

2024-05-06 Thread Alexandr Dubovikov via sr-dev
> @adubovikov: as I see it right now, by replicating at SIP level (e.g., via > sip dump) to another system, the original source ip/destination IP are lost > in the receiving system. They can eventually be added as custom headers. or we should set the hep variables. Anyway @sipgate-uhlig is talki

[sr-dev] Re: [kamailio/kamailio] possible memory corruption in sipcapture module (Issue #3835)

2024-05-08 Thread Alexandr Dubovikov via sr-dev
> Thank you for your input so far. All the alternatives seem to work-around the > issue but not fulfill our needs. > > We have debugged a little using `gdb`. We noticed that the value of > `msg->rcv->bind_address->address_str` is correct before calling `do_action`. > Afterwards, it is wrong. >