Overview
EVVR Containers are licensed by the number of cameras that they are configured to stream from.
Each EVVR Container requests licences for the correct number of cameras via the EdgeVis Server it is connected to.
EdgeVis Server fulfils these requests by asking the Central Licensing Service for a licence that matches the request details.
The Central Licensing Service maintains a record of the EdgeVis Server and EVVR Containers that a customer is running. This allows it to tie licences issued to the number of camera licences owned by the customer.
Data collected by CLS.
EVVR Container licence lifecycle
When an EVVR Container is created, it needs to obtain a licence for each camera that it is configured to connect to. This happens using by way of an automatic requests that the container makes as cameras are added or removed via the container web interface. The licences issued to the EVVR Container have a limited life time and need to be renewed within 30 days to continue to be valid. The renewal process happens automatically as long as the EdgeVis Server that the container is attached to is able to contact the Central Licensing Service.
The EVVR Container will check for licence updates at random intervals averaging out at about once every 30 minutes or so. The licensing status of the container can be refreshed manually using a button in the EVVR Container’s web interface.
If the EVVR Container has a licence that has expired and it can’t renew it, it will continue to operate in a reduced functionality mode for 30 days after the expiry.
CLS Connectivity
EdgeVis Server communicates with the Central Licensing Service (CLS) over the internet under the following conditions:
1. When a new container instance is added to the server
2. When a new camera is added to an existing container
3. A daily check, to verify that each container instance remains licensed
Note
The periodic license refresh interval is randomised per container instance. If you have many containers connected to a single server, calls to the CLS will occur more frequently and at staggered times.
All communication with the CLS is made via TLS over port 443 to the following endpoint:
https://licensing.digitalbarriers.com
This domain is hosted behind the AWS Content Delivery Network (CDN) and supports both IPv4 and IPv6 connections. Because the underlying IP addresses are managed by AWS and subject to change, they are not suitable for IP-based firewall whitelisting.
CLS Redundancy and Availability
The CLS infrastructure leverages AWS’s CDN with any-cast routing, which ensures:
Requests are routed through the shortest available network path
Automatic rerouting in case of network disruptions or node failures
The CLS itself consists of four redundant Points of Presence (PoPs):
Two in North America
Two in Europe
The CDN directs traffic to the nearest available PoP to optimise performance and automatically fails over if one becomes unreachable.