Overview
EVVR encoders and Containers are licensed by the number of input cameras and the number of output streams that they are configured to use.
Each encoder requests licences automatically, when required, by sending a request to 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 encoders/containers that a customer is running.
Data collected by CLS.
Licence lifecycle
When you add a camera/output stream your encoder/Container will, if necessary, obtain a licence automatically from the CLS. The downloaded licences issued to the encoder are temporary and have a limited lifetime that needs to be renewed within 10 days to continue to be valid. The renewal process happens automatically as long as the EdgeVis Server that the encoder is attached to is able to contact the Central Licensing Service.
The encoder will check for licence updates at random intervals, averaging out at roughly once every 18 hours.
If the encoder 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:
When a new encoder instance is added to the server
When a new camera is added to an existing encoder
When a new output stream is added to an encoder
When a camera or output stream is deleted from your encoder
A daily check to verify that each encoder instance remains licensed
Note
The periodic license refresh interval is randomised per encoder instance. If you have many encoders 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.