Pro-Vigil Fixed Site Installations - Network Setup

This document provides guidelines for creating an isolated network for Pro-Vigil’s video monitoring components (cameras, deterrent devices, etc) within the customer’s network to allow access to Pro-Vigil’s components from Pro-Vigil’s private-cloud-based systems.

There are 2 supported scenarios for Fixed Site Installations: 1) Pro-Vigil is provided a static IP address by the customer 2) Pro-Vigil equipment is configured using DHCP. 

Scenario 1

Step 1: The customer-provided static IP address is configured on Pro-Vigil’s router WAN interface and port forwarding is set up on  Pro-Vigil’s router to access Pro-Vigil’s video monitoring components (which are on a separate LAN)and configuring VPN on Pro-Vigil’s CPU box (NVR) for access from Pro-Vigil’s cloud.

Step 2: The Customer’s IT Department is requested to update firewall settings to allow incoming traffic on specific ports necessary for access from Pro-Vigil’s cloud on  HTTP/HTTPS, SSH, and VPN protocols.

An example of a Site Setup on Pro-Vigil’s Router is below

 Scenario 2

If the customer did not provide a static public IP, then they are requested to provide a LAN extension from their network switch which will be terminated on Pro-Vigil’s router as a WAN interface (DHCP). Then VPN is configured on Pro-Vigil’s CPU box for access by Pro-Vigil Cloud.

The table below lists DNS and IP addresses that need to be whitelisted by customer IT for non-vpn.sss: