Interaction between the Eocortex and antivirus and network protection🔗
Using antivirus and network protection software reduces the performance of Eocortex applications and, if configured incorrectly, may block access to video surveillance system components. In this regard, it is recommended to adhere to the following recommendations:
Do not use antivirus software and firewalls on servers and client workstations Eocortex. This will prevent performance degradation and blocking of video surveillance system data.
If security policies require the use of antivirus and network protection tools, these tools should be configured in accordance with the recommendations below.
In the firewall settings, open the network ports that allow the video surveillance system server to interact with cameras, client devices, and also with other servers in multiserver systems.
Add the Eocortex application files to the list of trusted applications in your antivirus software.
Exclude antivirus scanning of video streams from cameras to the server, from the server to clients, and, when using client connection proxying in multiserver systems, from server to server.
Warning
Some antivirus software check video streams even when disabled, since they “embedding” their own components at the system drivers level when installed.
For proper operation and to ensure the performance of the Eocortex applications, it is recommended to not install such antivirus software on servers and client workstations of the video surveillance system, if possible.
The network ports used by the Eocortex video system are listed below.
The Eocortex server. Outgoing TCP connections:
Port 80 (Can be changed in the settings of some cameras): For connecting to the camera via HTTP and ONVIF.
Port 443 (Can be changed in the settings of some cameras): For connecting to the camera via HTTPS.
Port 554 (Can be changed in the settings of some cameras): For connecting to the camera via HTTP and ONVIF.
Port 8080 (By default. Can be changed in the Eocortex Configurator application): For non-secure connections to other servers in a multiserver system.
Port 18080 (By default. Can be changed in the Eocortex Configurator application): For secure SSL connections to other servers in a multiserver system.
The Eocortex server. Incoming TCP connections:
Port 8080 (By default. Can be changed in the Eocortex Configurator application): For non-secure connections to the client and server applications.
Port 18080 (By default. Can be changed in the Eocortex Configurator application): For secure SSL connections to the client and server applications.
Port 8089 (By default. Can be changed in the Eocortex Configurator application): For mobile application and web client connections when server-side proxying for them is disabled (this feature is enabled by default; it can be disabled in the server settings within the Eocortex Configurator application).
The Eocortex server. Outgoing and incoming TCP connections:
Port 5432 (By default. Can't be changed): For connection to the PostgreSQL DBMS;
Port 8899 (By default. Can't be changed): For connection to the Episode archive service;
Port 8999 (By default. Can't be changed): For connection to the Long-term database service;
Port 8889 (By default. Can't be changed): For connection to the Eocortex System Health Monitoring service.
Eocortex Client. Outgoing TCP connections:
Port 8080 (By default. Can be changed in the Eocortex Configurator application): For non-secure connections to the client and server applications.
Port 18080 (By default. Can be changed in the Eocortex Configurator applicatio): For secure SSL connections to the client and server applications.
Note
Also, depending on the settings of the cameras used and the Eocortex features enabled, it may be necessary to open other ports for incoming and outgoing connections.