One-sided turn issue

Scenario

(Not on all devices, seems a timing issue)

• Alice got TURN disabled (ipv4 only, no upnp)
• Bob got TURN enabled
• Bob calls TURN

Expected

• TURN should be used

Current result

• Bob negotiation's failed (normal), but he doesn't wait any TURN connection (controlling_passive_timeout)

---

Second scenario

• First call fails sometimes

Observations

• Peer stop to connect to the TURN server too soon:

[1659635463.681|10859|manager.cpp       :261 ]13:51:03.681         0x7ff984184290  Check 2: [1] 192.168.49.92:9-->192.252.140.236:19442: connection failed after 8 attempts

[1659635463.681|10859|manager.cpp       :261 ]13:51:03.681         0x7ff984184290  Check 2: [1] 192.168.49.92:9-->192.252.140.236:19442: state changed from Pending to Failed

However, the peer is only creating the permission one second after:

[1659635464.702|23173|manager.cpp       :261 ]13:51:04.702   tcprel0x7fa41412a670  .TX 124 bytes STUN message to 192.252.140.236:3478:
--- begin STUN message ---
STUN CreatePermission request

Because the first put encrypted on a hash is slower than the others

added connectivity BacklogHigh + 1 deleted label

assigned to @sblin

added SprintIn progress label

Not sure if this makes any sense to this issue / or generally:

But what happens (while connecting/ or starting a video call) if Alice suddenly enables turn?

And what happens (while connecting/ or starting a video call) if Bob suddenly disables turn? In that case the connection and the call will just fail?

this will stop the call as you changes the connection settings anyway, but it's unrelated

changed the description

mentioned in issue jami-client-android#999

removed SprintIn progress label

closed