We are using OpenVidu 2.15 CE on server and OpenVidu Browser 2.15 on the client. We have two challenges primarily: -
Initial connection to the session not being successful and sometimes user having to do multiple connection attempts.
Network disconnection in the middle of the video call.
In both cases, we want to have 1) better logging of connection issues so we can pro actively review issues our customers are seeing 2) robust error handling and implement Re-connecting feature similar to other video conferencing applications.
We have logging in place to trap connectionDestroyed event and while in some cases we do see the event getting logged (in client browser) and sometimes not.
I can imagine that if the user’s signal plane is going away, the connectionDestroyed event may not even reach that user? Is that a correct assumption?
Should we use webhooks as a more reliable way to record lifecycle of connections?
Sometimes we see errors like below: -
For #2, What is the suggested approach here?
Trap connectionDestroyed event + Have our own mechanism of detecting if the user’s network connection went down? As I mentioned above, it seems like relying on connectionDestroyed may not always be reliable.
Do we simply reconnect with a new token and republish the streams?
Any suggestions here will be helpful as without a robust reconnection policy in place, the user experience suffers and causes friction in an other wise well working application.