Jingle SOCKS5 fallback does not work correctly if Gajim is the initiator
This is similar, but different from #9692, where a different problem happens if Gajim is the responder for a SOCKS5 to IBB fallback.
- OS: Arch Linux
- Gajim version: 1.1.3
- GTK version: 3.24.10
- Python-nbxmpp version: 0.6.10
Steps to reproduce the problem
- Inititate a file transfer to an entity.
- (Ensure that all SOCKS5 candidates fail.)
- Observe the outgoing
transport-replacefor IBB by Gajim.
- Observe the incoming
transport-acceptby another client (e.g. Dino after https://github.com/dino/dino/pull/592 is merged).
Gajim opens the in-band bytestream (as it is the initiator).
Nothing happens after the
transport-accept is acknowledged by Gajim.