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

Just my two cents:

When a user requests for a transport, there should ideally be a timeout setup to safely close the transport and as well alert the user of an audio/video could not be connected at this time error; try again.
If the transport is not connected within several seconds to throw this timeout.

With each transport requiring to be connected once or be closed, you can watch at a client level the connectionstate and if that hits disconnected you can wait several seconds for recovery (unless they closed broadcast/etc) if recovery doesn’t occur and the stream is still hosted you can request ice every so often till connection returns to solid.

If user disconnects entirely from websocket, you should completely destroy any transports they were using.

2 Likes