jami-daemon issueshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues2019-08-29T14:44:21Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/140ios (lte) -> android, sometimes there is a 30 seconds delay during media nego...2019-08-29T14:44:21ZSébastien Blinios (lte) -> android, sometimes there is a 30 seconds delay during media negotiationMakes the call unusable.Makes the call unusable.Iteration 14Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/138SIP over TCP: separate rx_buffer by active sock in stun_sock.c2019-08-29T14:44:21ZSébastien BlinSIP over TCP: separate rx_buffer by active sock in stun_sock.cTo avoid to mix packets. This causes "TLS decryption failed" errorsTo avoid to mix packets. This causes "TLS decryption failed" errorsIteration 14Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/134Call can cut after 30 secs if bad transport selected2019-08-29T14:44:20ZSébastien BlinCall can cut after 30 secs if bad transport selectedIf we see the following logs at the start of a call:
```
[1565812513.241| 1648|instant_messaging.cpp:184 ] pjsip_dlg_send_request failed: Unsuitable transport selected (PJSIP_ETPNOTSUITABLE)
```
The call will cut after 30 secs because...If we see the following logs at the start of a call:
```
[1565812513.241| 1648|instant_messaging.cpp:184 ] pjsip_dlg_send_request failed: Unsuitable transport selected (PJSIP_ETPNOTSUITABLE)
```
The call will cut after 30 secs because the SIP message is not sent.
A bad ip is resolved in sip_resolve.c. Currently digging.Iteration 14Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/128Multi device regression: file transfer doesn't work for all devices2019-08-29T14:44:19ZSébastien BlinMulti device regression: file transfer doesn't work for all devicesOnly file transfer seems a bit broken. Calls and text messages are ok.
# Reproduce step
Device A with account X, Device B,C with account Y
X send a file to Y, sometimes only one device (eg B) is receiving the file, the second can star...Only file transfer seems a bit broken. Calls and text messages are ok.
# Reproduce step
Device A with account X, Device B,C with account Y
X send a file to Y, sometimes only one device (eg B) is receiving the file, the second can start a ICE negotiation, but never receives the headers of the file.Iteration 14Sébastien BlinSébastien Blin