Client P2P connection to server🔗

The P2P (Peer-to-peer) technology allows to connect to the Eocortex server using the Eocortex Client application running on a remote computer from anywhere in the world, provided that both of them have internet access. At that, the Eocortex server does not have to have a public static IP address or to be in the same VPN with the client computer. Thus, when it is required to connect to the Eocortex servers via internet, is becomes significantly easier to set up the networks and the need to rent public static IP addresses or VPN servers is eliminated.

Before connecting to the Eocortex server via the Eocortex Client application using the P2P technology, it is required to do the following:

  1. Create an account in Eocortex Cloud.

  2. Connect Eocortex servers to Eocortex Cloud.

  3. Connect to Eocortex Cloud via Eocortex Client.

Creating an account in Eocortex Cloud

To create an account in Eocortex Cloud, it is required to follow the link https://cloud.eocortex.com/account/register

After creating an account, a message will be sent to the indicated address. To confirm, go to the link in the message or press Activate.

Connecting servers to Eocortex Cloud

After creating the account in Eocortex Cloud, it is required to connect a video surveillance system to it. To do that, go to the general server settings in the Eocortex Configurator application, then go to the Eocortex Cloud tab, enter the Eocortex Cloud account data (email and password) and, finally, press the Connect button.

Warning

The Eocortex Cloud connection setup is only available to the users with full rights (in case of the Enterprise and ULTRA licenses these are the users who are included in the group with the Senior administrators rights).

After the successful connection, the status will change to System connected.

Warning

The settings will come into effect only after they are applied.

Client P2P connection

After having connected the video surveillance system to Eocortex Cloud, it becomes possible to connect to it using P2P. For that end, a new type of connection was added to the authorization window of the Eocortex Client application called Connection to Eocortex Cloud. To connect, it is required to enter the email and password of the Eocortex Cloud account.

Description of Eocortex Client in case of its connection to server via P2P:

Warning

When making a connection via P2P using Eocortex Cloud, the user of Eocortex Client will have full rights for the access to the video surveillance system.

On the other hand, the Eocortex Configurator application does not support the P2P access; thus, the user who has connected to the system vis P2P, will not be able to launch Eocortex Configurator from the client application.

Besides, when connecting via P2P, the Eocortex Configurator application will not be able to perform an automatic upgrade to the server’s version.

Note

When connected to a multi-server system via P2P, it is possible to view the cameras only from those servers that are connected to Eocortex Cloud have internet access.

At the same time, if the main server has access to the internet, it is possible to gain the P2P access to the cameras of the servers without internet access but which are in the same local network or VPN with the main server by enabling a proxy access thru the main server.

Warning

If the Eocortex server is disconnected from the system that is already connected to Eocortex Cloud, that server will be disconnected from Eocortex Cloud and its Eocortex Cloud connection settings will be deleted.

Note

When combining two systems connected to Eocortex Cloud, the system being connected will be disconnected from the initial Eocortex Cloud account and connected to the account of the system to which it is being connected.

Note

Since in case of a P2P connection the data, in most instances, will be transmitted via internet, a secure connection will be employed.

Failure to connect to system via P2P

First, it is required to make sure that the system is connected to Eocortex Cloud. To do so, go to the Eocortex Cloud account and check the list of the connected servers. If the list is empty, it may be possible that the main server has no internet access and cannot connect to Eocortex Cloud.

If there are servers in the list but the main server has the Disconnected status, it is required to make sure that the server is in a working order.

In case the main server has the Connected status, but it is impossible to connect to the system, it is likely that the server or the client are in the network that does not support P2P connections.

Below are the options of the network organization that do not support P2P connections:

  • Server and client are on the computer that is in the network after the router with Symmetric NAT.

  • Server and client are on the computer that is in the network after two or more routers with different NATs.

Questions and answers
How many video surveillance systems can be connected to a single Eocortex Cloud account?

Only one video surveillance system can be connected to a single Eocortex Cloud account.

Are there any limitations as regards the number of system servers connected to Eocortex Cloud?

There are no such limitations.

Is the load on the client and the server different depending on the type of connection (standard or P2P)?

On the client, the load is the same in both cases. The server, on the contrary, may consume somewhat more CPU resources when connected via P2P. The load depends on the volume of traffic sent by the server via P2P. The maximum increase of the load via P2P can reach 50% of the standard connection load. For example, if the server used 20% of the CPU capacity to transmit data to the client applications under the standard connection, this load can increase to 30% when all the clients are connected via P2P.

Are there any traffic limitations in case of a P2P connection?

Yes. First, the maximum throughput of a single channel with the camera stream is around 40 Mbps. Second, since in the majority of cases the connection is via internet, the speed depends on a provider’s internet plan.