Reconnect after transport connectionstate = failed

[zaidiqbal]

@techtruth

Conducting a server-side then client-side re-ice will ‘fix’ the connection, but its better to understand the underlying issue than to skip it with re-ice.

To understand the underlying issue, you will have to dig into server logs to see what is happening but most of the time if transport is getting failed it is because of the network conditions.

And if this is because of network conditions then the only thing you need to do is ‘restartIce’ like after every 10 seconds and when ‘connectionstatechange’ event tells you that it is connected then stop that restartIce process.

This is all so listen for this ‘connectionstatechange’ event, as mentioned by ibc, it should go to ‘connected’ state after successful restartIce:

mediasoup :: API

One example is here:

Transport connectionstate never changes to 'failed', stuck on 'disconnected'

Here’s an example: transport.appData.idletimer = setTimeout(async (wss, room, handle) => { console.log("User had disconnected before transport connected. Alert them to request again."); if (Transports.has(room)) { Transports.get(room).delete(handle); if (Transports.get(room).size == 0) Transports.delete(room); } await transport.close(); wss.send(JSON.stringify({ …