Hi,
we are using OpenVidu PRO for our platform in Italy.
We deployed OpenVidu on AWS following this procedure: Deploying OpenVidu Pro
So far so good, we are able to connect peers properly and the video session works fine.
However after some time of usage, and some complains from the users, we noticed in Kibana an increasing amount of “networkDisconnect”.
On average: 20% of the sessions show this event (multiple times per session).
In the docs here we saw that this event is triggered when the remote user connection drops.
We tested it and is triggered correctly after some time (15 seconds I believe).
The weird thing is, after not being able to do a proper video call, the users usually useother software (like Skype) and the call with works fine with no issues. Therefore we are starting to exlude networking issues from the client side.
So here is the question: is the 20% of “networkDisconnect” events average or too high? If so, is it stricly related on the internet connection of the peers or it may depends on the development of the application?
Is there something we could do to improve the situation?
If you need more information please let me know.
Thank you for your support.
Best Regards
Hello @DDFranky,
We are very sorry to know that you are having unexpected problems. We will try to discover the root cause of the problem and solve it.
When have you started to get problems? Do you find a pattern in users with problems? Or all users have same problems? Problems exist independently of OpenVidu load usage? Or problem appear with high load? Have you seen something unusual before networkDisconnection? Media quality has problems in that scenario?
If you can not share this info in public, please contact with us in private using info@openvidu.io.
Regards
Hi @micael.gallego
thank you for your response.
We started to have some feedback from the users after a week or so in production.
From Kibana we saw the networkDisconnected and we confirmed the data.
The version of OpenVidu we are using is the 2.11.0, OpenVidu Docker Container version 2.9.0
We never upgraded to or from any other version.
Is not a constant 20%, some days is very low with just 1 or 2 cases.
We analyzed the browsers and the devices, but we where not able to find a pattern. At first we also tought that some users used an old version of Chrome (wich they did, they use version 63.0.3239.132 ) but after some testing we could not replicate the problem.
We also saw a high usage of CPU from Kurento if one of the peers is using Safari, but we are aware of what it is and that is a problem not related to OpenVidu itself.
Not all users have the same problem, some user are able to make the video call without any issue whatsoever.
The load usage of OpenVidu is very low: CPU usage 1-2% and memory usage 30-35% on average, the max CPU usage was 4% and memory 35%. We took this informations from Kibana.
The number of sessions per day on average is around ~100 with a max of 218 and a min of 1.
We saw no correlation between high number of sessions and increase of networkDisconnection.
We saw nothing unusual before the networkDisconnection but asking the users they saw a great decrease in the quality of the stream up to the point that they were not able to see the other person properly.
On client side we do not set a resolution sticking with the default one (640X480).
Thank you again for your support.
Best Regards
1 Like
It is possible that you have some network problem between clients and openvidu server? Can you see values of bandwidth in the failing communications? networkDisconnect event is raised when openvidu-browser is unable to send ping messages to openvidu-server. These messages goes over websocket communication.
As you understand, it is really difficult for us to know what can be the problem if there is no evident pattern about the problem and all was working some days ago.
Can you take a look to the number of sessions in OpenVidu server? It is consistent with real sessions? We fix a bug some weeks ago regarding to phantom sessions in OpenVidu related with high response times. Maybe it is related with your problem.
We are very near to release the new 2.12.0 version of OpenVidu with latest Kurento version. We hope it can solve the issues.
Regards