<p>Thank you for your fast and clarifying response.</p>
<p>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?</p>
<p>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:</p>
<pre><code>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
</code></pre>
<p>which happens at kamailio 5.1.4.</p>
<p>Also only the following keys are present in redis when using 5.2.0-dev4:</p>
<pre><code>1) "d:z:atpsh-5b2a4f80-218-1"
2) "b:x:z9hG4bKb1d4.26a1938596920d3714191be44ad2684a.0"
</code></pre>
<p>When 5.1.4 had also <code>b:x:INVITE:1e004b4343c496750f1de6f156c779e8@pbx.example.com:h7g4Esbg_07000304592032</code></p>
<p>Call case is the same, configuration is the same and all of the participants are the same. I only rebuilt kamailio and retried.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/1569#issuecomment-398742935">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36Zb9-IMz-M7zAUm3hH8bunDyFmSnMks5t-knngaJpZM4Uuu6-">mute the thread</a>.<img src="https://github.com/notifications/beacon/AF36ZWnrkxoJ4rHheBlvA5A9igpEsQxOks5t-knngaJpZM4Uuu6-.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/kamailio/kamailio/issues/1569#issuecomment-398742935","url":"https://github.com/kamailio/kamailio/issues/1569#issuecomment-398742935","name":"View Issue"},"description":"View this Issue on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}</script>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/kamailio/kamailio","title":"kamailio/kamailio","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@Joonake in #1569: Thank you for your fast and clarifying response.\r\n\r\nThe 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?\r\n\r\nAbout 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:\r\n```\r\nJun 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\r\n```\r\nwhich happens at kamailio 5.1.4.\r\n\r\nAlso only the following keys are present in redis when using 5.2.0-dev4:\r\n```\r\n1) \"d:z:atpsh-5b2a4f80-218-1\"\r\n2) \"b:x:z9hG4bKb1d4.26a1938596920d3714191be44ad2684a.0\"\r\n```\r\n\r\nWhen 5.1.4 had also `b:x:INVITE:1e004b4343c496750f1de6f156c779e8@pbx.example.com:h7g4Esbg_07000304592032`\r\n\r\nCall case is the same, configuration is the same and all of the participants are the same. I only rebuilt kamailio and retried."}],"action":{"name":"View Issue","url":"https://github.com/kamailio/kamailio/issues/1569#issuecomment-398742935"}}}</script>
<script type="application/ld+json">{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [kamailio/kamailio] TOPOS with event_route filter fails with BYE message (#1569)",
"sections": [
{
"text": "",
"activityTitle": "**Joonas Keskitalo**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@Joonake",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"kamailio/kamailio\",\n\"issueId\": 1569,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"kamailio/kamailio\",\n\"issueId\": 1569\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/kamailio/kamailio/issues/1569#issuecomment-398742935"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 347795134\n}"
}
],
"themeColor": "26292E"
}</script>