Thank you for your fast and clarifying response.

The problem here is that I simply can't use event_route to disable topos on calls destined to Asterisk since it will break every call made to another direction. That means that current event_route feature allows topos to be disabled but only if the SIP peers are for one-way traffic?

About my second comment on differences between branches, I noticed that for some reason when I tested with 5.2 I had different kind of keys on redis than on my tests on 5.1. The call scenario was exactly the same on both cases. I managed to reproduce this and I can't find the following log row on 5.2.0-dev4 kamailio at all:

Jun 20 13:09:53 edge3 /usr/local/sbin/kamailio[3686]: DEBUG: topos_redis [topos_redis_storage.c:363]: tps_redis_insert_invite_branch(): inserting branch record for [b:x:INVITE:1e004b4343c496750f1de6f156c779e8@pbx.example.com:h7g4Esbg_07000304592032] with argc 6

which happens at kamailio 5.1.4.

Also only the following keys are present in redis when using 5.2.0-dev4:

1) "d:z:atpsh-5b2a4f80-218-1"
2) "b:x:z9hG4bKb1d4.26a1938596920d3714191be44ad2684a.0"

When 5.1.4 had also b:x:INVITE:1e004b4343c496750f1de6f156c779e8@pbx.example.com:h7g4Esbg_07000304592032

Call case is the same, configuration is the same and all of the participants are the same. I only rebuilt kamailio and retried.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.