For speed reasons, the event_route was designed to allow testing only destination address and decide to do topos or not, meaning that all traffic with an ip is either with topos processing or without.

In your case I understand that you want calls initiated by Asterisk to be with topos, but not the calls towards Asterisk. This would require testing at a later point in topos processing, so this can be another event_route to get access to the SIP message and other related attributes, so this would be a feature request. It was somehow discussed when added the current event route, but the needs at that time were for address checking and the speed was considered relevant, otherwise is not something that complex to add.

If you want it, then open a new issue as a feature request.

Now here, I want to clarify your second comment, where I got it like you report a different behaviour between master and 5.1 branches, am I right? Is it a bug that you discovered? Not sure if the record was not found by topos_redis because you dropped topos for INVITE or there was some different scenario that you tried.

I think master and 5.1 branches should be the same from perspective of topos/topos_redis modules.

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