### Description
Topos still seems to break early-dialog UPDATEs in my configuration. This is on 5.6.0~rc0+bpo11.20220506004754.1 from 56-nightly which I believe includes c309122 and ceb688b. I haven't tested rc1 yet (there are no debs at this time) but there doesn't seem to be any topos-related commits since rc0 either.
### Troubleshooting
#### SIP Traffic
Attaching pcaps from a lab environment to demonstrate the problem. One with topos on (failure), one with off (success). There were no other configuration changes between these tests.
### Possible Solutions
Only turning topos off seems to resolve this for me.
### Additional Information
``` version: kamailio 5.6.0-rc0 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1 ```
* **Operating System**:
``` Linux sbcprov0-stage-tis0-cn1 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 GNU/Linux ``` [pcaps.tar.gz](https://github.com/kamailio/kamailio/files/8704222/pcaps.tar.gz)
Update: Just tested with ~rc1, same result: ``` version: kamailio 5.6.0-rc1 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1
```
Its interesting, your scenario must be then somehow different then the one that was fixed previously.
UPDATE: I tried again with mariadb as topos backend, and the issue doesn't manifest. This seems to only affect topos_redis.
Let me know if there's any further information I could share that could help dissect this issue. Thanks!
Thanks for adding the bit about topos_redis, this was important to differentiate.
I pushed a commit to master and 5.6 branches, hopefully catching it. If not, reopen.
Closed #3112 as completed.