We are using Individual recording in our application. When any participants’s network conditions got bad when he is trying to publish some stream, the recording could not start at all.
Steps to reproduce:
In Microsoft Edge, throttle the network condition and then turn on the Camera in openvidu app. Then try to start the recording, it wont’ start with an error “500, Recording could not be started”.
We suspect that when any connection in a session is not healthy then recording can not be started by open vidu server.
We are trying to overcome this issue, by calling /getConnections API and to know which steam is unhealthy, so we can kick out that connection from the session programatically before attempting to start the recording. But the API contains no data to tell us whether that particular stream is healthy or not i.e. recordable or not.
This issue is becoming a headache for us now.
Please suggest something to fix this.