[sr-dev] Failed to catch some reply message with reply_route block

[Salah Ahmed]

Hello Henning,

Thanks for quick reply, We armed the t_on_reply just before t_relay() in
the route block.

        t_on_reply("LOGRPL");
        if (!t_relay()) {
                sl_reply_error();
        }

Thanks,
Salah

On Thu, Aug 22, 2019 at 2:03 PM Henning Westerholt <hw at skalatan.de> wrote:

> Hello Salah,
>
> the replies are going from the UAS to the UAC over Kamailo as a proxy,
> with the exception of the hop-by-hop 100.
>
> So you should see the 200 OK in the Kamailio in reply_route and
> onreply_route. Maybe you can check if you armed the onreply_route with
> t_on_reply for the INVITE routing.
>
> Cheers,
>
> Henning
> Am 22.08.19 um 19:50 schrieb Salah Ahmed:
>
> Hello,
>
> We facing an issue on capturing sip message in Kamailio(Version: 5.2.3).
> The scenario is very simple.
>
> UAC                    Kamailio                UAS
>  |--------INVITE--------->|                     |
>  |                        |-------INVITE------->|
>  |                        |<------100 Trying----|
>  |<-------100 Trying------|                     |
>  |                        |<------200 Ok--------|
>  |<-------200 Ok----------|                     |
>
> In this simple scenario, we can't catch any reply messages in between the
> Kamailio and UAC. We have tried reply_route, onreply_route,
> and onsend_route. But no one work to grep that reply on that side.
> onsend_route was bad try as its only for forwarded reply message. Is there
> any other magic to capture those replies. A debug=3 log message attached
> here.
>
> Thanks,
> Salah
>
>
>
>
> _______________________________________________
> Kamailio (SER) - Development Mailing Listsr-dev at lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
>
> --
> Henning Westerholt - https://skalatan.de/blog/
> Kamailio services - https://skalatan.de/services
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20190822/2103ea9f/attachment.html>