Version 5 taking too long to load
Completed
Since I have upgraded my servers to version 5.0.0.35270 both the mobile and desktop apps take 15-20 seconds longer (approx. 26-33 seconds) to load than when I was on version 4.
Is there a known cause for this and will a fix be made available soon?
-
Hi Sam Boon and Anders Knutsen,
Soon - likely next week - we'll publish a new 5.0 release that have some optimizations included which should reduce the time it takes to start.
Please wait and test this next build and in case this doesn't resolve the issue, we can dive deeper.
-
Dear shabeer neyyan,
Thank you for bringing to our attention the issues you are experiencing with your cameras. It seems that you are encountering two different issues that may be stemming from a common cause.
Firstly, you have mentioned that the cameras are loading slowly in the client. This is usually due to requests being sent to the mediaserver and returned to the client too slow to establish the connection. But also could occur when there is a cloud connection between server and client, and a proxy connection is required, due to firewall blocking UDP hole punching. Adding the FQDN addresses to the firewall passlist, should resolve such issues.
Additionally, you have also encountered an error message "CONNECTION TO CAMERA (PRIMARY STREAM) WAS UNEXPECTEDLY CLOSED," which usually means that the devices do not comply with the rfc2326 and a TEARDOWN was expected. If there is no TEARDOWN, the notification you mentioned will be displayed.
It is worth noting that the server requests streams from the camera, and when responses are not quick enough, a TEARDOWN is expected. If this TEARDOWN has not been implemented, the notification will be shown. Both of these issues may be due to slow responses within the network.
To verify this, we suggest checking the network settings. Ensure that the Quality of Service (QoS) is set correctly for the system. The system should prioritize communication in the QoS setting in the network switches. Other factors such as the use of cables with insufficient bandwidth capacity or unsuitable materials (CCA or CCS instead of CU, for example) or too long cable runs may also cause these issues. In addition, too many network hops due to daisy-chaining of network switches have been known to cause similar issues in the past.
We hope that the above suggestions can help resolve them. Please note that these are only preliminary suggestions as we do not have a complete understanding of your system and network architecture.
Thank you for your patience and understanding. If you require further assistance, please do not hesitate to contact us.
Best regards.
Ps. Could you clarify which operating system you're using for the server(s) and the client(s)?
Please sign in to leave a comment.
Comments
5 comments