IBB-only Jingle transfer stops after one <data/>, with incorrect <close/> sid
I'm writing a component (source code is at https://gitlab.com/ossguy/sgx-catapult/tree/master ) that uses IBB for Jingle file transfers; it does not support S5B. When I try to send a file using Gajim (version 0.16.6 from Debian stretch), Gajim sends a single message even though the file is much larger than that (progress bar gets stuck around 18%), and when I manually choose to cancel the transfer, Gajim sends the wrong sid in the message (it uses the sid of the Jingle session rather than the sid of the transport, even though both the and messages correctly used the transport sid).
I've attached a log that demonstrates this issue. If you would like to test Gajim with a live version of my component, please send a message to my JID (firstname.lastname@example.org) and I will register you with the component so you can send messages to it.