A valid power source is connected to the PSU and the PSU is operational.
Amber (Blinking)
Indicates an issue with the PSU.
Not Lit
Power is not connected to the PSU.
Green (Blinking)
PSU firmware is being updated.
WARNING: Do not disconnect power or unplug the PSU while firmware is updating. Interruption of this process could lead to PSUs ceasing to function.
Green (Blinking and powers off)
When hot-plugging a PSU, it will blink 5 times at a rate of 4Hz then power off. This indicates a mismatch due to efficiency, features, health status, or supported voltage.
WARNING: If two PSUs are installed, both PSUs must have the same type of label. Mixing PSUs is not supported, even if they have the same power rating.
WARNING: If two identical PSUs receive different input voltages, this can cause different output wattage and trigger a mismatch.
CORRECTION: When correcting a PSU mismatch, remove all power from the system then replace the PSU with the blinking indicator.
<br>
System Health and ID Indicators
The left control panel on the front of the system acts a button and provides an LED indicator. System ID mode, activated by pressing the control panel on the front of the system, or the ID button on the rear of the system will flash these LEDs to make identification in a server rack, from either side, easier.
LED Indicator
Description
Blue (Solid)
The system is powered on, healthy, and system ID mode is not active. Press the system ID button to switch to system ID mode.
Blue (Blinking)
System ID mode is active. Press the system ID button to switch to system health mode.
Amber (Solid)
The system is in fail-safe mode and should be inspected for issues or troubleshooting.
Amber (Blinking)
The system is experiencing a fault. Check the System Event Log for error messages. Look up specific error codes using Quick Resource Locator.
<br>
Drive Indicators
The LEDs on the drive carrier indicate the state of each drive. Each drive carrier has two LEDs: an activity LED (green) and a status LED (bicolor green/amber). The activity LED blinks whenever the drive is accessed.
Drive status LED indicator
Drive activity LED indicator
Drive capacity label
LED Indicator
Description
Green (Solid)
Indicates the drive is online.
Green (Blinks twice per second)
Indicates the drive is being identified, or preparing for removal.
Off
Indicates the drive is ready for removal.
NOTE: Drive status indicator remains off until all drives are initialized after the system is powered on. Drives are not ready for removal during this period.
Green/Amber (Blinks green, ambers, then powers off)
Indicates that there is an unexpected drive failure.
Amber (Blinking 4 times per second)
Indicates the drive has failed.
Green (Blinking slowly)
Indicates the drive is rebuilding.
Green/Amber (Blinks green 3 seconds, amber 3 seconds, then powers off after 6 seconds)
Indicates that the rebuild has stopped.
<br>
iDRAC Direct (micro USB) Indicators
LED Indicator
Description
Solid green for 2 seconds
Laptop or tablet is connected.
Blinking green (on for 2 seconds, off for 2 seconds)
Integrated Dell Remote Access Controller (iDRAC) is a proprietary technology that allows IT administrators to remotely manage and monitor Dell-built servers. This includes software and hardware components.
The Exacq X-Series NVRs include iDRAC micro ports on the front of the system and iDRAC network interfaces on the back. The location of these is noted on the X-Series Quick Start Guide.
<br>
Out of the Box
iDRAC ports are not enabled out of the box. To enable either, or both interfaces, you must access the Lifecycle Control Center on the system.
Enabling iDRAC Ports
During boot up of the system, watch for the boot options to appear on screen.<br><br>
When shown, press the F10 key to boot into the Lifecycle Control Center. <br><br>
The Lifecycle Controller automatically begins a network configuration wizard if it has not been configured before. You may select the Back button to exit the wizard.<br><br>
From the Lifecycle Controller Home screen, navigate to System Setup > Advanced Hardware Configuration. <br><br>
Select iDRAC Settings. Continue to Step 6 to enable iDRAC Direct on the iDRAC micro port. Skip to Step 7 to enable iDRAC networking.<br><br>
To enable the iDRAC micro port, select Media and USB Port Settings. <br>
Beneath USB Management Port, locate the iDRAC Direct: USB Configuration XML setting.
The default setting is ‘Enabled while server has default credential settings only.’ However, for the security of your system, these credentials are changed before shipping from the factory.
Change the above-mentioned setting to ‘Enabled‘.
Select the Back button.<br><br>
To enable the iDRAC network port on the rear of the system, select Network.
NOTE: A VLAN is recommended as a best security practice when iDRAC is in Dedicated or Shared LOM mode, to isolate network access to iDRAC’s management interfaces. Technologies such as VLANs and firewalls help ensure that only authorized users can access network resources.<br><br>
Beneath Network Settings, change the Enabled NIC setting to ‘Enabled‘.
Leave the NIC Selection set to ‘Dedicated‘.
Scroll down to the IPv4 Settings section. The default settings are as follows:
Enable IPv4: Enabled
Enable DHCP: Enabled
Static IP Address: 0.0.0.0
Static Gateway: 0.0.0.0
Static Subnet Mask: 0.0.0.0
Use DHCP to obtain DNS server addresses: Disabled
Static Preferred DNS Server: 0.0.0.0
If you plan to connect this interface to a network with a DHCP server, you may leave the settings as they are.
If you wish to use a static IP address for the iDRAC interface, change the Enable DHCP setting to ‘Disabled‘ and enter the proper Static IP address settings in the fields below.
Select the Back button when done.
Press the Finish button to save your changes and return to the System Setup menu.<br><br>
Press Finish again to return to the Lifecycle Controller main menu.<br><br>
Leave the Lifecycle Control Center and boot to the operating system by selecting the Exit option in the corner of the screen.
<br>
Accessing the iDRAC9 Dashboard
The iDRAC9 Dashboard is accessible using any modern web browser, but there are various methods available to reach it: Local, Network, and USB (iDRAC Direct). <br>
Local Browser Access
Accessing the iDRAC9 Dashboard locally requires a keyboard, mouse, and monitor connected to the system.
Log into the system’s operating system (Windows or Linux).<br><br>
Open a web browser.<br><br>
In the browser address bar, enter: https://169.254.1.1<br><br>
Use the browser’s advanced settings to continue past the warning message. This message appears because the SSL certificate is self-signed.<br><br>
Log into iDRAC using the proper credentials.
<br>
Network Access
iDRAC network interfaces support RJ45 jacks, with 1G BASE-T Ethernet Cat5/6 cables.
The Lifecycle Control Center provides the ability to set the iDRAC network interface to DHCP or static IP address.
If set to a static IP address, a site administrator should be able to provide the configured address.
If configured for DHCP, but a DHCP server is not available, or has no available addresses to offer, this interface should fall back to 192.168.0.120. Otherwise, you may need to determine what address the DHCP server assigned to the system.
Whether using a static or dynamically allocated IP address, you will enter this address into the browser’s address bar.
Example: https://172.10.10.4
<br>
USB Access (iDRAC Direct)
iDRAC Direct allows you to utilize the front-facing iDRAC micro port to connect directly to the system over USB, say from a laptop, which makes ad hoc management in a server room/stack easily accessible.
iDRAC micro ports couple with a USB 2.0 Micro-A or Micro-B connector. You will need a cable with either of these interfaces to connect between the X-Series system and your laptop/workstation. Cable length should not exceed 3ft (0.91m). Cable quality could affect performance. The iDRAC micro port is a Micro-A type port, which will accept either Micro-A or Micro-B connectors, but will not accept USB 3.0/SS Micro-B.
Before beginning, you MUST disable all other network or wireless interfaces on the laptop/workstation you wish to connect from.<br><br>
Make sure the iDRAC micro port is enabled, see Step 6 of Enabling iDRAC Ports above.<br><br>
Turn the flat side of the USB micro connector to the right, so that the beveled side of the USB micro connector faces left, then insert the connector into the iDRAC micro port.<br><br>
Wait a few moments and the laptop/workstation should detect a new virtual network interface.<br> This can be seen using the ipconfig command on Windows, or ifconfig command on Ubuntu/Linux.<br> The IP assigned to this interface should be 169.254.0.4.<br><br>
Open a web browser on the laptop/workstation. In the browser address bar, enter the IP of the iDRAC micro port: https://169.254.0.3<br><br>
Log into the iDRAC Dashboard with the proper credentials.
<br>
Logging into the iDRAC9 Dashboard
When logging into the iDRAC9 Dashboard, use the following credentials
Username: root
Password: admin256
Consider changing your iDRAC Dashboard password using the steps below.
<br>
Changing the iDRAC credentials
Most system users will probably only use the default root user account and factory set password. However, up to 16 local users may be configured in iDRAC with specific access permissions.
If you are already connected to the iDRAC9 Dashboard, you may do this using the following steps:
Select the iDRAC Settings menu.<br><br>
Select Users from the menu drop-down, or from the tabs on the iDRAC Settings page. <br><br>
Select Local Users. <br><br>
Edit an existing account or add a new user account.
If you are not connected to the iDRAC9 Dashboard, you will need physical access to the system.
During boot up of the system, watch for the boot options to appear on screen.<br><br>
When shown, press the F10 key to boot into the Lifecycle Control Center. <br><br>
The Lifecycle Control Center automatically begins a network configuration wizard if it has not been configured before. You may select the Back button to exit the wizard.<br><br>
From the Lifecycle Controller Home screen, navigate to System Setup > Advanced Hardware Configuration. <br><br>
Select iDRAC Settings. <br><br>
Scroll down to find and select User Configuration. <br><br>
Select the text field beside Change Password to enter a new password. <br><br>
When done, select the Back button.<br><br>
Click the Finish button to save your changes.
<br>
iDRAC9 Dashboard Basics
The iDRAC9 Dashboard provides a quick overview of the system. Describing all aspects and controls is outside the scope of this document. The items you should pay the most attention to are your system and drive health.
The Dashboard home page shows a high-level overview of System Health and Drive Health.
Clicking on Details for either of these will bring you to the corresponding pages. You may also reach these pages by selecting System or Storage from the top menu bar.
The System > Overview page displays the status of many hardware components, such as memory, CPU, power supplies, and cooling (system fans). Selecting any of these will provide greater detail on each.
The Storage > Overview page lists the number of physical disks, virtual disks, and graphics of drive status. 2U systems will also display a graphic of the system’s front panel to help identify the drive bays.
Each Virtual Disk is comprised of multiple Physical Disks. These are listed on the corresponding Virtual Disks and Physical Disks pages.
<br>
Virtual Console
iDRAC9 provides a Virtual Console feature which provides a desktop environment as if you were sitting in front of the system. This negates the need to also configure RDP or VNC to configure the system using a GUI.
IMPORTANT: Do not use the Virtual Console for client monitoring of cameras. This method may be used to configure exacqVision software only: add and configure cameras, managing licensing, check system statuses and logs, etc. For regular camera monitoring, install the exacqVision Client on a client workstation suitable for this purpose. See system hardware requirements.
NOTE: Virtual Console performs better when connected via the iDRAC network interface than when connected using iDRAC Direct using the micro USB port.
Enabling the Virtual Console
Virtual Console is disabled by default. Once logged into the iDRAC9 Dashboard, you may enable this feature for use.
From the iDRAC9 Dashboard, locate the Virtual Console panel. The message in this panel indicates the feature is currently disabled for use. <br><br>
Click on the Settings option above the empty panel.<br><br>
From the Virtual Console settings page, change the Enabled setting from ‘Disabled’ to ‘Enabled’, then press the Apply button below. <br><br>
Return to the Dashboard and note that the Virtual Console panel will display an image from the system based on its current state.<br><br>
Select the inset image or press the Start the Virtual Console bar below to open a Virtual Console session.
<br>
Virtual Console Basics
Virtual Console will open a session in a new browser window. Note that the frame rate of the console display is included in the window’s title bar. The console provides some of the following features from the menu buttons. <br><br>
Menu Item
Description
Boot
Chooses what the system will boot to on the next boot up. Options include the Lifecycle Controller, as well as physical or virtual media.
Power
Allows the user to remotely power cycle or shutdown the system.
Chat
Provides a chat window for use when more than one person is using the machine’s Virtual Console.
Keyboard
Displays a virtual keyboard. May be useful when attempting to enter multi-key commands such as CTRL+ALT+DEL.
Screen Capture
Allows the user to save a screen capture PNG image to their local machine.
Refresh
Refreshes the console window.
Fullscreen
Displays the Virtual Console in fullscreen mode. Press ESC to exit fullscreen mode.
Virtual Media
Virtual media allows the managed server to access media devices on the management station or ISO CD/DVD images on a network share as if they were devices on the managed server.
Select Connect Virtual Media to begin, select your chosen media. Use Disconnect to remove that media from the machine’s console connection.
Disconnect Viewer
Closes the console session and window.
Console Controls
Provides settings for viewing, including a virtual clipboard for copying text between the managed server and the management workstation.
DebugView is a tool that can be used to collect more data from PS files in cases where we are missing data from streams or exhibiting issues with exported files.
Once you have exported the PS file from a server you can download the DebugView application and open the program. With Debug View opened, perform the following steps:
Run CMD on a Windows machine using Run as Administrator<br><br>
Change your working directory to the directory where the PS file is located, using the ‘cd’ command. Example: In this example the file is located on the Desktop cd C:\Users\username\Desktop<br><br>
Run the file by entering the file name, and add the ‘-V’ parameter to the end. If located in a different directory, enter the file path. Example: In this example the file name is ‘3505-001A0280.ps’ 3505-001A0280.ps -V or C:\Users\username\Desktop\3505-001A0280.ps -V<br><br>
When the Exacq ePlayer opens, press the play button.<br><br>
DebugView will log activity during playback. Save the file as soon as the clip has finished playback to avoid logging your mouse and keyboard activity.
In this Example- We have an issue where the data that was recorded is not viewable when searching, exporting the video. This tells us that the cameras were getting some of the stream information but not all of the stream information that is vital to play back the video that was recorded. This might suggest that the camera was in a bad state, low power mode or there was something taking place.
As part of the exacqVision 24.03 software release, we are announcing the deprecation of specific installers that were previously part of the collection of software downloads available on the Exacq web site, https://exacq.com.
What installers are being retired?
On both Windows and Ubuntu – the 32-bit installers, also known as “x86” installers, of server, client, and web service will no longer be made available for new releases. The Enterprise Manager 32-bit installer had been deprecated from the 21.12 release. In addition, Illustra 610 and 825 (Edge), and ARM Debian (M-Series) installers will be retired as well.
Why is Exacq taking this step?
This change helps address cyber security/robustness concerns by removing support for those installations that are potentially deployed on operating systems no longer fully supported by the vendor. Additionally, retiring support for older/obsolete technology helps Exacq to streamline engineering resources to focus their efforts on faster delivery of customer outcomes that are needed now and in the future.
What if I have been using 32-bit installers for exacqVision all the time? How do I update to the 24.03 release?
If a customer is currently using 32-bit installers, they would have to move to the 64-bit installers – provided the hardware and the operating system are 64-bit enabled. 32-bit and 64-bit installers cannot co-exist. To move to the 64-bit installation, the 32-bit installation should be uninstalled.
So as to not lose the current configuration, it is recommended that the current configuration be backed up – then restored after the 64-bit installation has been deployed. Please refer to this user guide section for understanding how to do a backup and restore of the exacqVision Server configuration.
If Enterprise Manager is deployed, you may refer to this video to understand how to backup and restore configurations across multiple servers at once.
How do I know if the hardware and operating system on my NVR is 64-bit capable?
It will depend on how old the NVR is.
If the NVR was built by Exacq and is a Windows machine – Any system that shipped on or after May 2013 is capable of running a 64-bit installer.
If the NVR was built by Exacq and is a Ubuntu machine – Any system that shipped on or after August 2017 is capable of running a 64-bit installer.
If the NVR was not built by Exacq, please contact your IT department or the manufacturer of the NVR to assess if it is capable of running a 64-bit installer. As a reference point, Windows started 64-bit support from Windows Vista, with mainstream support adopted in Windows 7, and Ubuntu from Ubuntu 16.04. So it is more than likely that the NVR in question is 64-bit capable. With that said, please double-check with relevant departments and resources to be sure.
NOTE: Operating system vendors, whether or not they support 64-bit, have set time tables for end-of-life (EOL). It is not recommended to use a system for which critical cyber security patches are no longer available. For example, Microsoft no longer supports Windows 7 or 8. Ubuntu does not support systems older than 14.04 today – and they will continue to obsolete older versions as they release new ones.
I can see my NVR is not capable of running a 64-bit installer. What is the recommended course of action?
It is likely that you are running an old NVR that is probably not in compliance with the cyber security standards of your IT department. In addition, you will not benefit from new features, integrations, cyber security patches, and bug fixes that make up the 24.03 and future exacqVision releases. Our recommendation is that you upgrade to newer hardware and operating system for your NVR. Please reach out to your local exacqVision dealer or call Exacq Inside Sales for better understanding of your options.
Some users may desire to record a different resolution or frame rate from a camera when an event such as motion or an analytic is triggered. Reasons for this vary by site, but often comes down to wishing to record a lower amount of data when very little is happening, but they require high frame rates or high resolution recordings for forensic playback.
In the steps below, we step through creating a secondary stream but configuring them with different settings and schedules. These steps are examples and you will need to adjust the settings for your site’s needs. Mix and match resolution, frame rate, or recording format as desired.
<br>
Setup Steps
Navigate to the Camera Settings page for the camera you wish to configure.<br><br>
Configure the settings for your first stream using the Recording tab on the bottom half of the page. It’s best to use this primary stream for your highest resolution and frame rate settings simply because most cameras provide fewer options for secondary streams. <br>In this example, our primary stream is configured for a resolution of 3840 x 2160 (4K/8MP) and an image rate of 25 fps.<br><br>
Assuming your camera supports Multistreaming, select a new Context from the Multistreaming settings and click the Add Stream button. <br><br>
After pressing the Add Stream a new sub-stream, or child stream, will appear on the system navigation tree to the left, nested beneath the primary, or parent, stream you just configured. The Camera Settings page should update to display the settings for this stream. <br><br>
Configure the Format as needed, then configure the Resolution and Image Rate desired for your lower end stream. <br>In this example, the stream is configured for a resolution of 1024 x 576 and an image rate of just 10 fps.<br><br>
Select the high resolution, high frame rate primary stream from the system tree and choose the Schedule tab. In this example, we’re going to configure the high resolution, high frame rate stream to only record on an analytic, in this case person detection.<br><br>
Highlight the entire schedule grid and change these from the default of Motion to None. Apply your change. <br><br>
Select the lower resolution, lower frame rate, secondary stream from the system tree, then select the Schedule tab. You could choose to set it to Free Run recording for continuous recording, or highlight the entire schedule and change it to Motion recording. <br><br>
The low resolution, low frame rate stream will record based on the schedule configured on the Schedule tab. We need to tell the system when to record the higher resolution, high frame rate stream. Click the New button.<br><br>
Navigate to the Event Linking node on the system tree.<br><br>
We’re triggering off an analytic in this example, but you may use any Event Type you wish, such as Motion or an Input Trigger. We select Analytics, then choose the Enter Rule analytic, previously configured on the camera, from the Event Source panel.<br><br>
Our Action Type will be Record Video.<br><br>
The Action Target will be the high resolution, high frame rate primary stream. <br><br>
Returning to the Schedule for this primary stream, we see the red corner flags are set indicating hours of the day in which our configured Event Link will record this camera stream. By default this will occur for all hours and days. Event Linking Source Groups could be used to configure specific days and hours to record on this event. <br><br>
Save your configuration by selecting the Apply button.<br><br>
Your configuration is complete and ready for testing. When performing a search you may search for recordings from either, or both, the primary and secondary streams but will likely rely on the primary stream for those high resolution or high frame rate forensic investigations of incidents.<br><br>
Repeat these steps for other cameras where you may want the similar recording behavior.<br><br>
Learn how to use the new Quick Add feature, introduced in exacqVision Server/Client 24.03 to remove the multistage process of setting up and adding new cameras to your exacqVision system. Quick Add combined with the Illustra Registration License tool provide an easy to use experience when pairing Illustra cameras with Exacq.
exacqVision Edge is a complete video management system (VMS) software solution that runs directly on an IP camera and stores video to an microSD/SD card inserted in the camera.
Download the appropriate installer for your device. Installers are listed by device model on the Software Downloads page.
Upload
Devices will vary by manufacturer and firmware version. The steps for Illustra IQ cameras are depicted below.
Log into the device through the web browser interface. Out-of-box or factory defaulted devices will likely require steps to choose basic device settings and configure the administrator user account and credentials. Refer to the device’s documentation for details.<br><br>
Locate the application management page within the device. Pictured below, Illustra IQ devices feature an Applications page from within the Applications menu. <br><br>
Select the installer file previously downloaded from Exacq.com to upload.
NOTE: Some cameras may not allow the application to upload until a microSD/SD card has been inserted, formated, and mounted.<br><br>
Uploaded applications typically begin running automatically after uploading. If the application does not appear to be running, use the device controls to start the application. <br><br>
The exacqVision Edge application is NOT licensed through the device itself. Disregard the License option within the camera’s web interface and proceed to the Licensing steps below.<br><br>
Licensing
If you have not already done so, download and install the exacqVision Client software on a workstation you intend to you for viewing and management of the Edge device.<br><br>
Within the exacqVision Client, use the cog wheel icon to access the Configuration screen.<br><br>
Navigate to the Add Systems page and add the Edge VMS using the IP address of the camera you installed the Edge application on as the server Hostname/IP Address. Rather than entering the credentials to log into the camera, the system credentials will still be default. Enter the following for intial setup: Username: admin Password: admin256<br><br>
Upon initial connection with the default credentials the exacqVision software will prompt you to change the default credentials to those known only to you.<br><br>
After changing the Edge Server credentials, you will see the exacqVision Server appear on your system tree to the left. Expand the server node and click to select the Configure System option. <br><br>
Select the System tab from the top of the Configure System page.<br><br>
Within the License section of this page, either manually enter the license key or use the Import button options to upload the license key to authorize your Edge application. <br><br>
Navigate to the Add IP Cameras page and confirm the camera is now shown as connected in the IP Camera List. It is normal to see that the Address is 127.0.0.1 because the Edge application is running directly on the camera, thus it will display the local loopback address rather than the networked IP address of the camera. <br><br>
The Quick Add tab, found on the Add IP Cameras page of the exacqVision Client is a recently added feature. Introduced in version 24.03, this feature accelerates the configuration and addition of supported camera models to your exacqVision system.
<br>
Products
exacqVision Server 24.03 and higher
exacqVision Client 24.03 and higher
Illustra IQ Pro Gen4
Illustra IQ Pro Gen3
Illustra IQ Flex Gen4
Illustra IQ Flex Gen3
Quick add requires both exacqVision Server and exacqVision Client versions 24.03 or higher. Only Illustra Pro and Flex Gen3/4 cameras are supported at this time. The Flex Multisensor (IFS16-M10-BT03) does not support Quick Add.
<br>
Pro Tip: If your Illustra IQ cameras are eligible for free licensing, apply your updated license key prior to adding cameras to avoid consuming paid camera channels. Contact your integrator or dealer for details.
<br>
Steps
Connect out-of-the-box or factory defaulted Illustra IQ cameras to your NVR’s network.<br><br>
Navigate to the Add IP Cameras page within the exacqVision Client.<br><br>
Select the Find IP Cameras tab on the bottom half of the page.<br><br>
Discover cameras by pressing the Rescan Network button. <br><br>
The Find IP Cameras tab will list all discovered devices whether Quick Add is supported or not. The Quick Add tab will display the number of Quick add supported devices found. You will also see a note beside the Add Selected button. Select either of these to be taken to the Quick Add tab. <br><br>
Select the Quick Add supported devices you wish to configure and add using the checkboxes from the list.<br><br>
Press the Edit button and enter the desired Username and Password credentials to be used for the selected devices. Click Save when done. <br><br>
Press the Add Selected button in the bottom corner to begin the Quick Add process. The status of the devices will change as each configuration stage is completed on the device. Each selected device will then appear in the IP Camera List above and begin the process of securely connecting to the server. <br><br>
After initial use of the Quick Add feature, the created credentials may be used for subsequent Quick Add operations. Username and Password fields are pre-filled with the previously used credentials when returning to the Quick Add tab.<br><br>
Selecting the Edit button allows you to enter a different set of credentials from those previously used.<br><br>
Selecting the View button will prompt users to authenticate to the server with Admin credentials. Once authenticated, the Password will display in plain text for 20 seconds. You may choose to use the copy icon beside the Password field to copy this to the system’s clipboard. The clipboard contents are also cleared after 20 seconds. <br><br>
exacqVision Server and Client versions 24.09 introduce our Remote Connections feature. This added feature currently only supports exacqVision Mobile. Connections for the Desktop Client, Exacq Mobile 3, or Web Client remain unchanged.
Products
exacqVision Server 24.09 and higher
exacqVision Client 24.09 and higher
exacqVision Mobile 24.09 and higher
What benefit does Remote Connections provide?
Ease of Setup – There is no need to configure routers to open ports and/or port forwarding, or configure additional software. This relay previously required configuration through the Web Service.
Authorization – Mobile users enter a single-use code provided by the exacqVision administrator to add a server connection.
Encryption – Enforces SSL/TLS connections.
Why don’t I have to configure port forwarding?
Traditionally, users outside of a LAN wishing to connect to services inside a LAN initiated the connection request. This can still be done if users choose this method.
However, when Remote Connectivity is enabled, the exacqVision software takes advantage of the fact that routers usually permit devices already inside the private network to initiate connections to outside services. This is what allows your web browser to load web pages without configuring port forwarding on your router. The exacqVision server establishes a secure connection to our Remote Connectivity agent. Users of the exacqVision Mobile app then connect to this Remote Connectivity agent. The Remote Connectivity agent handles the secure passing of data between the exacqVision Server and the user’s app.
What is this code users enter?
The Remote Connections feature provides another layer of security over just usernames and passwords. exacqVision administrators press a button within the exacqVision Client to create one or several single-use codes. A user wishing to add an exacqVision Server instance to their mobile app must enter the code provided by their system administrator before it expires (within 24hrs). The code is only needed for the initial connection to the server. Unless the user deletes the system from their mobile app, there is no need to enter a code the next time the app is used.
<br><br>
<br><br>
<br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br>In this example, our primary stream is configured for a resolution of 3840 x 2160 (4K/8MP) and an image rate of 25 fps.<br><br>
<br><br>
<br><br>
<br>In this example, the stream is configured for a resolution of 1024 x 576 and an image rate of just 10 fps.<br><br>
<br><br>
<br><br>
<br><br>
<br><br> 
<br><br>
<br><br>
<br><br>
<br><br>
<br><br> 
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>