Hello Henning,
We did few more test and its found good. In our side may had some issue. We will let you know if anything new found.
Thank you,
Salah
On Fri, Aug 2, 2019 at 7:03 AM Salahuddin Ahmed <txrubel@gmail.com> wrote:
Hello Henning,
Thanks for your reply. Actually its for sip_trace. Normal call working as well. The issue is, forwarded 200 OK not traced by the sip_trace method.
Thanks,Salah
On Fri, Aug 2, 2019 at 5:12 AM Henning Westerholt <hw@skalatan.de> wrote:
Hello Salah,
sorry I don't fully understand your problem. Are you facing an issue for the "normal" SIP routing during call setup after upgrade to 5.2? Or do you have an issue related to the sip_trace functionality? The 200 OK should be "just routed" in the cfg file, you should not process this with sl_reply etc..
Cheers,
Henning
Am 01.08.19 um 21:30 schrieb Salahuddin Ahmed:
Hello,
Recently we update kamailio fromversion 4.1.1 to 5.2. In this new version we have facing following issue.
We tried to catch this message using t_on_reply and on_sl_reply but no luck. Actually we need to forward those message to another server using sip_trace. If using trace_mode=1 then all message forwarded perfectly. But I need to set correlation_id with sip_trace method. So we need to catch that message and tag the correlation_id with that. Could anyone please help me on this? Is there anything I missing or any way to fix this?
Thanks in advance,Salah
_______________________________________________ Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services