connectivity issues leading to unstable file transfer
The file transfer feature is quite unreliable on my devices/network, around 1/3 of attempted file transfers fail.
Devices: Android (WiFi + 4G), GNOME client (Ethernet)
I have investigated the issue, and many of these failures seem to be due to connectivity issues at unfavorable moments.
First scenario:
- A sends rx DHT request to B
- B receives rx DHT request and replies with a list of addresses on the DHT
- A does not receive the answer in time and timeouts
Typical logs:
[1542546917.185|27153|p2p.cpp :526 ] [Account b9243250525b44cb] [CNX] rx DHT request from 8004386f1052cae68e543ebb87992612f218ded6
[1542546917.186|27153|ringaccount.cpp :2438 ] Found peer device: 8004386f1052cae68e543ebb87992612f218ded6 account:3c2a2fae84be1713e6d68d39360
faa7441220c00 CA:310d17e467cfb06ee20e2ddc0e75ebee0ba55640
[1542546917.187|27153|sip_utils.cpp :203 ] Registered thread 0x7f7cd12ac158 (0x69A0)
[1542546917.187| 7535|sip_utils.cpp :203 ] Registered thread 0x7f7cb77fd158 (0x69A0)
[1542546917.187|27153|turn_transport.cpp:357 ] Connecting to TURN 51.254.39.157:3478
[1542546917.187|27153|turn_transport.cpp:357 ] Connecting to TURN 51.254.39.157:3478
[1542546917.187| 7536|sip_utils.cpp :203 ] Registered thread 0x7f7cb6ffc158 (0x69A0)
[1542546917.210| 7536|turn_transport.cpp:214 ] TURN server disconnected (Deallocated)
[1542546917.212| 7535|turn_transport.cpp:211 ] TURN server ready, peer relay address: 51.254.39.157:28253
[1542546917.218|27153|p2p.cpp :558 ] [Account b9243250525b44cb] [CNX] authorized peer connection from 141.x.x.x
[1542546917.218|27153|p2p.cpp :582 ] [Account b9243250525b44cb] [CNX] connection accepted, DHT reply to 8004386f1052cae68e543ebb8799
2612f218ded6
[1542546920.329|27857|ringaccount.cpp :2051 ] [Account b9243250525b44cb] Dht status : IPv4 connected; IPv6 connecting
[1542546920.336|27857|ringaccount.cpp :2051 ] [Account b9243250525b44cb] Dht status : IPv4 connected; IPv6 connected
[1542546921.933|27149|siptransport.cpp :223 ] pjsip transport@0x7f7c8800bfb0 DTLS to 100.124.24.241 -> DESTROY
[1542546921.933|27149|siptransport.cpp :249 ] unmap pjsip transport@0x7f7c8800bfb0 {SipTransport@(nil)}
[1542546921.933|27149|sips_transport_ice.cpp:214 ] SipsIceTransport@0x7f7c8800bf40: destroying
[1542546921.933|27149|sips_transport_ice.cpp:256 ] ~SipIceTransport@0x7f7c8800bf40 {tr=0x7f7c8800bfb0}
[1542546921.934|27149|sips_transport_ice.cpp:277 ] ~SipIceTransport@0x7f7c8800bf40 {tr=0x7f7c8800bfb0} bye
Nothing comes after that. Peer seems to time out.
The SIP logs are not are not always present and might be unrelated, but I didn't remove them just in case.
The IPv4 connected; IPv6 connecting
lines mean changes in IPv6 connectivity right ?