Category: exacqVision Client

Using the Axis I8116-E Network Video Intercom with ExacqVision

Post author By Bhargav Atturu
Post date January 26, 2024

This article applies to the Axis I8116-E Network Video Intercom using firmware 11.8.66.

ExacqVision does not currently support SIP calling functions. However, this device can be integrated for interactive operation with ExacqVision as detailed here.

In the example that follows we will step through an example scenario wherein pressing the door station call button brings the door station camera to the attention of the ExacqVision operator to trigger a door lock.

The following topics are discussed:

Wiring an electric door strike to the door station
Adding the device to ExacqVision
Enabling Two-Way Audio
Adding Associations
Creating custom Views
Creating an Event Monitoring profile

You will combine several features and functions within the ExacqVision Client. It is recommended that users acquaint themselves with the ExacqVision Client prior to use. We provide User Training Videos on these topics.

Wire a Door Strike

The simplest configuration is that of a single electric door strike, or maglock, wired directly to the door controller.

The Axis I8116-E can be wired in a number of different ways, using PoE, external power sources, A9801 Relay, A9161 Network I/O Relay, or an Axis access control system. For more information on the many wiring and hardware configurations please refer to the manufacturer’s website or documentation.

Add the Device

You will want to use a web browser to log into the device and perform the initial setup, which at this state usually means setting a non-default username/password, and possibly setting a static IP address.
The call button should be enabled by default.
The device’s default settings create a ‘VMS’ entry under the Contact List menu. This ‘VMS’ contact will already be listed in the Recipients field. If you do not see this, enter it now.
If you do not already know the IP address of the door station, you will need to discover it on the network. 
- If using the Find IP Cameras tab on the Add IP Cameras page, note that you may find the device listed twice. Ignore results with a 169.254.x.x address. You will ant to use the IP address in the same range as your ExacqVision VMS, however this result may be discovered with ‘Onvif’ displayed in the ‘Type’ column. Access the discovered IP address in your web browser to set the username and password.
Add the device manually by clicking the New button under the IP Camera List in the top half of the page. Select AXIS VAPIX from the Device Type Selector. Enter the IP address in the same range as your ExacqVision VMS, then enter the username and password credentials before clicking Apply to add the device. The device should display a ‘Connected’ status in the IP Camera List before continuing.

Enable Two-Way Audio

Expand the Add IP Cameras node from the navigation tree.
Select the Audio Inputs/Outputs node nested beneath the Add IP Cameras node.
The resulting list displayed will show each door station device listed twice. Note the column, titled Audio. One of these rows shows ‘Audio,’ while the other displays ‘Audio Output.’ For easier identification we can apply our own labels here. We change ‘Audio Output’ to ‘Talk’ and change ‘Audio’ to ‘Listen.’
Find the Record Enable column. Place a check in the box for both of these rows for the device. This enables two-way audio functions within ExacqVision
Press the Apply button to save your changes. Use the Talk and Listen buttons to verify audio is functioning and adjust the audio gain as desired in the door station’s web browser interface.

IMPORTANT: Client workstations intended for use with two-way audio devices MUST have a microphone enabled. Two-way audio menus and controls are disabled or hidden until a microphone is recognized by the operating system. Each client workstation used for two-way audio must have its own microphone.

Add Associations

You have the option of using soft triggers and audio controls from the top toolbar in live view, but these will open dialogues showing all system options. Controls that are used frequently and directly related to the specific camera being displayed in a panel may be easier for operators to use when added as Association buttons within the camera panel.

Select the Associations node from the navigation tree.
The panel along the left lists existing cameras. Find and click to select the door station.
From the Available Controls panel, we select the ‘Listen’ option we relabeled earlier and click Add. There will be two controls labeled ‘Talk’ that we relabeled earlier. Select and add the one showing the microphone icon.
So that your ExacqVision operators can unlock the door remotely, find and add the control labeled ‘Door.’
Note: This control may be relabeled from within the door station’s web browser interface, but is labeled ‘Door’ by default for us.
You should now have three Associated Controls listed. You may wish to edit the Button Style listed. ‘Sustained’ requires a click on, and another click to turn off. ‘Momentary’ functions only while a user is pressing down the button which will also prevent a user from accidentally forgetting to lock the door or leaving a microphone on. You may refer to the User Manual or Associations training video for more information on customizing your Associations.
Click Apply to save your changes when done.

Create Custom Views

In our example we will create a View to display when triggered, rather than changing a single video panel. Learn more about these two options in the Event Monitoring training video. To make this work, we will create two custom Views to use later when creating an Event Monitoring profile. Refer to the Views training video if you need more details on performing these steps.

Select the Views node from the navigation tree.
Click the New View button, then enter a descriptive name. In this example, we name our view ‘East Entry.'
Select a layout for the view from the layout toolbar above. This view may have a single panel layout showing only the camera view from the door station, or you may use a multi-panel layout displaying the door station and other cameras showing the entry from different angles.
Use the Available Items panel to find your door station camera and drag it to the empty panel in the layout. If using a multi-panel layout, fill the other panels as you like.
Because the Associations are already displayed, an ExacqVision operator may easily enable/disable each when viewing in Live mode. However, if you’d like the Microphone or Speaker to be on automatically upon the view changing, you may also drag one of these onto the layout as well. Only one may be active.
Click Apply to save you changes when done.
Since we are changing the entire view displayed in Live mode, we will also want to create a view that is displayed when the door station is not in use. Repeat the steps above to create another view titled ‘Default View.’

Create an Event Monitoring Profile

Next you will create the Event Monitoring profile that changes the view displayed while in Live mode.

Select the Event Monitoring node from the navigation tree.
Click the New button under the Profiles panel to begin creating a new profile.
Enter a descriptive Name under the Profile Configuration panel. Our example will name this ‘East Entry’ for the door where it is being placed.
The option you select for the Show Event List menu will depend on your intended use.
- Never is the less obtrusive option as it hides the Event List from popping up in our view. The trade off for this is you will probably want to set Timeout later so the View changes back to the default display after a given amount of time. Without this, the displayed View will remain on the door station camera.
- On Event will pop open the Event List window which some users do not like. However, the benefit of this is the ExacqVision user can decide when to return to the default View and the View will not change in the middle of being used simply because a timer ended. When the event is cleared the Event List window will disappear.
- Always will always be displayed whether or not the door station is being utilized.
Checking the Show Newest Event box is optional. This feature is most useful when many possible events are included in an Event Monitoring profile. An example may be a site with multiple door stations, in which case checking this box will change the view to display the station with the most recently pressed Call Button.
As mentioned previously, this example will use ‘View’ from the Type field. Refer to the Event Monitoring training video for more on the ‘Video Panel’ option, which does not require creating custom Views.
Under Client Actions in the middle of the window is where you will create the actions that occur when triggered by various events. Our first row, currently labeled ‘Unknown’ should already be highlighted because we are creating a new profile.
From the Event Type panel list below, select ‘Default’.
From the Action Type panel list, select Switch View. Note that you could also opt to make your default display a Tour, which is covered in the Tours training video.
From the Action Target panel list, select the default View you created earlier.
Click the New button under the Client Actions panel in the middle of the window. This adds a new row to configure.
With the newly created row highlighted, select Input Trigger from the Event Type list.
The door station has already named the input for you. Locate the door station in the list. It has several inputs, select the one labeled ‘Call button’. Do not enable the ‘Lasts at Least’ checkbox.
From the Action Type list, select Switch View.
From the Action Target list, select the door station View you created earlier. In our example we named this ‘East Entry’.
Your next choice will depend on the option you selected from the Show Event List, in step 4, above.
- If you chose Never and want the Live view to return to your default view after a set number of seconds, uncheck the Confirm box and set your Timeout as desired.
- If you chose On Event or Always and want to allow your ExacqVision users to acknowledge the event to return to the default view, leave the Confirm box checked.
Click the Apply button to save your changes when done.

Handling Calls From ExacqVision

Using the ExacqVision Client software, browse to Live mode.
By default, the panel along the left side of the window displays a list of Live Cameras. Using the options at the bottom select Views to update this panel to Live Views.
The Live navigation panel lists System Views, User Role Views, User Views, and System Tours, which includes any Views created earlier in the process of configuring our profile. Towards the bottom is a list of Event Monitors.
Find the name of the Event Monitoring profile you created. Again, our example was named ‘East Entry’. Drag this profile to the cameras panel to the right.
You should now be viewing your default View. When the Call Button on the door station is pressed the View will change to display the door station camera view you created earlier.
The Association icons we added earlier can be seen at the bottom corner. The door station will continue to ring until an ExacqVision user presses the Talk button or the configured ring timeout is reached.
Press the Talk button to transmit audio from your client workstation microphone to speak to door station users. Press the Listen button to hear door station users speaking.

Note: Audio from Talk and Listen actions may be buffered, presenting a delay. Practice with the system to gain a feel for this on your network.
If you have correctly wired a door strike, maglock, or other electronic locking mechanism to the door station, pressing the icon for the output will unlock the door.

Note: Door controls may be customized within the door station’s web browser interface. <br

Door Station Visitor Operation

A visitor using the door station may simply press the Call Button to activate the Event Monitoring profile, as created above.
The use case detailed in this article does not prevent the door station from being used for SIP calls.

Once a SIP server has been configured within the door station’s web browser interface, a SIP call may be initiated by pressing the Call Button.

Note: When used together with SIP, any press of the Call Button will continue to trigger an Event Monitoring profile configured to do so.

Tags Door Station, SIP, I8116, 18685, Guest, Axis, Audio, Access Control, Associations, Two-Way, Intercom

Knowledge Support exacqVision Enterprise exacqVision Client exacqVision Server

Updating Enterprise Manager to 23.09.5.0 can cause legacy server versions to have user account log in failure.

Post author By Brandon Powell
Post date December 6, 2023

Support has identified an issue with updating Enterprise Manager to version 23.09.5.0 prior to running updates to ExacqVision server 23.09.6.0. This issue will manifest after updating Enterprise Manager by users experiencing disconnection from the client with errors ” log in failed / invalid username or password or account locked or disabled” or ” log in failed – invalid response”.

Product

ExacqVision Enterprise Manager
ExacqVision Server

Steps to Reproduce

Update Enterprise Manager to version 23.09.5.0 while leaving ExacqVision server versions on 23.06 or lower.

Expected Results

– Users should remain logged in successfully.

Actual Results

– Users will be disconnected from the Client with error – ” log in failed / invalid username or password or account locked or disabled” or ” log in failed – invalid response”

Solution

Engineering is currently working on a patch to resolve this issue.

For customers that updated from 23.06 to 23.09 prior to the patch, installing the version with the patch should fix all login issues customers are facing.

For customers that performed a fresh install of 23.09 prior to the patch, user server passwords will become scrambled and customers will need to change/reset user passwords.

Until the patch is released, if customer has an Enterprise Manager backup that contains no issues from 23.06 that can be applied, the following steps can be taken:

Take a backup from 23.09 prior to making any changes.
Access a recent prior backup off of Enterprise Manager (this must be taken on version 23.06 previously).
Completely remove Enterprise Manager.
Install Enterprise Manager previous version 23.06.0.0.
Follow on screen prompts during install.
Login to Enterprise Manager as the root admin user.
Upload previously taken backup using the upload button in the backups screen in Enterprise Manager user interface.
Wait for this to complete.
Restore from uploaded backup.
Wait for restoration completion.
Confirm log-in capability has been restored.
Re-setup scheduled backups as these will be defaulted.

It should be noted that downgrading is not a normal solution, and should be prevented with Enterprise Manager. These instructions are only for situations where the customer has already performed this update and is now locked out of Client software and critically needs to be restored in a timely manner.

Tags Enterprise System Manager (ESM), Level2, Users, Enterprise Manager Users, Exacq Enterprise Manager Users, Log-In Failed, Account Locked or Disabled, 18174

Video Library Configuration Demo Illustra exacqVision Client Youtube Video Library Categories Products

Exacq Scenario Series – Illustra IQ Perimeter Object Classification to Change ExacqVision Views

Post author By Bhargav Atturu
Post date November 30, 2023

The Scenario Series of videos addresses setup configurations for specific use cases. In this video our scenario is that of a user that wants to use Event Monitoring to bring attention to an ExacqVision operator when a perimeter area is crossed. This could be used to monitor property and fence lines. We walk through setting up AI Object Classfication within an Illustra IQ camera and configuring Event Monitoring in ExacqVision to change our displayed camera views when triggered.

Tags Illustra IQ, AI Object Classification, Illustra, 18152, Event Monitoring, Analytics

Knowledge Support Support exacqVision Client Products

macOS Client Live Views are 1/16th to 1/4 of the Normal Size

Post author By Brian Lakin
Post date November 29, 2023

Description

When running 23.03 Exacq Client on Mac some cameras intermittently show up very small in live view. Instead of filling the available space, they are 1/16th to 1/4 of the view area and the rest is black. Macs running two different versions of macOS (Sonoma and Big Sur) have been seen.

Product

Exacq Client 23.03-23.06 versions.

Steps to Reproduce

Update Mac Client to 23.03 and 23.06 version and views will show behavior.

Expected Results

This should not been seen.

Actual Results

The live views will be shown as 1/16th or 1/4 the size in the live pane.

Solution

Exacq Client 23.09.7.0 releases on 11-20-2023 will resolve both OS’s.

AESW-7704

Tags MacOS, 181168, 18116, exacqVision Client, Public

Knowledge Support Support exacqVision Client Categories Products Uncategorized

XDV Reference

Post author By Bhargav Atturu
Post date November 22, 2023

*** INTERNAL USE ***

Type Definitions

Integer – Numeric value
Bool – 1 or 0 value where 1 is ‘enabled’ and 0 is ‘disabled’
String – Any text value
DIP – Device Independent Pixel (represents screen coordinates and sizes)
- Windows
  - If the system is not using any sort of DPI or screen scaling represents actual pixel values
  - If screen scaling is in use then this number is multiplied by the scaling value
    - Example: A 4k monitor would typically use 200% scaling. A value of 1920 would represent your full display width (1920 * 200% = 3840)
- Other platforms
Epoch – Numeric value representing the number of seconds since January 1st, 1970

The options described in the documentation below are listed in dictionary values, where possible. This is indicated by the key values listed between curly braces ‘{ }’. The key is followed by the description of the key value is colon separated, as in the following example:

    {key1:description1, key2:description2, …}

More than one Instance or Item tag may be defined.

Tags and attributes not included use client defaults.

XDV / XML Structure

<exacqVision Init>
    <Instance>
        <Live>
            <Layout>
                <Item/>
            </Layout>
            <System>
               <Video>
                   <Input/>
               </Video>
               <Audio>
                   <Input>
               </Audio>
            </System>
        </Live>
    </Instance>
    <Systems>
    </Systems>
    <SecurityIntegrations/>
    <Sync/>
    <Alerts/>
    <HWAccel/>
    <Joystick>
    &lt/Joystick>
</exacqVision Init>

exacqVision Init Attributes

AllowAccelerators
ShowSunkenBorder	bool {0:disabled, 1:enabled}
ShowRecStatusBorder	bool {0:disabled, 1:enabled}
ShowPTZFocusBorder	bool {0:disabled, 1:enabled}
ShowOnScreeDisplay	bool {0:disabled, 1:enabled}
UseOsdColor	bool {0:disabled, 1:enabled} Use OSD color for Serial Profiles
KeepAspectRatio	bool {0:disabled, 1:enabled} Keep aspect ratio during resize
RestoreOnAttnReq	bool {0:disabled, 1:enabled} Restore client on user attention request
MySystemsColMask
EntCamColMask
AnalogCamColMask
IPCamColMask
EntCamFilterTreeSize	integer (DIP value) Width of filter tree panel on Enterprise Cameras
NonEntCamFilterTreeSize	integer (DIP value) Width of filter tree panel on Camera Recordings
VGAAccelMode
VGAAccelColorspace
DisplayAdapter
TimelapsePlaybackInterval	integer {0-15} Immediate jump to next frame if gap exceeds X seconds
PanelSizeRatio	integer {0:content, 1:window, 2:16×9, 3:4×3}
CameraSortOrder	integer {0:default order, 1:ascending, 2:descending}
GroupsSortOrder	integer {0:default order, 1:ascending, 2:descending}
MapsSortOrder	integer {0:default order, 1:ascending, 2:descending}
ViewsSortOrder	integer {0:default order, 1:ascending, 2:descending}
EventsSortOrder	integer {0:default order, 1:ascending, 2:descending}
BookmarksSortOrder	integer {0:default order, 1:ascending, 2:descending}
ReportsSortOrder	integer {0:default order, 1:ascending, 2:descending}
LiveAudioLipSync	integer {0:auto, 1:enabled, 2:disabled}
AudioInputDevice	integer 0 indexed list based on client detected devices
MuteDuringTwoWayAudio	bool {0:disabled, 1:enabled}
AutoFillEmptyVideoPanels	bool {0:disabled, 1:enabled}
CPUDecompResult
EnableIndicators	bool {0:disabled, 1:enabled} Show notifications for indicators
ConfirmClose	bool {0:disabled, 1:enabled} Prompts user for confirmation when attempting to close client window
CollapseLiveAutoContexts	bool {0:disabled, 1:enabled} Hide individual quality streams
CombineRegionOfInterestStreams	bool {0:disabled, 1:enabled} Manage all streams as quality streams
CameraPreviewMode	integer {0:no preview, 1:thumbnail, 2:video
ShowSystemGroups	bool {0:disabled, 1:enabled} Show system group folders
RequireSSLCert	bool {0:disabled, 1:enabled} Require SSL certificate validation
UseSparseConnections	bool {0:disabled, 1:enabled} Use dynamic connections
SparseSystemCount	integer Number of systems using dynamic connections
EnableAllAnalytics	bool {0:disabled, 1:enabled}
NormalLayoutCollapseMode	integer {0:auto, 1:expanded, 2:collapsed}
EventButtonCollapseMode
LastUsedNormalLayout
LastUsedWidescreenLayout	deprecated
LastUsedEventButton
DeblockingMode	integer {0:auto, 1:enabled, 2:disabled} H.264 deblocking, attempts to smooth sharp edges of decoded compressed video blocks
DirectSearch	integer {0:disabled, 1:prefer system video, 2:prefer archive video, 3:prefer cloud video}
LastUsedLayout	string
Language
Caption	string Title of the client window
ViewLayout	integer Number of panels in startup layout
LegacyAuthentication	integer {0:only if required, 1:force, 2:never} To be deprecated
TimeoutEnabled	bool {0:disabled, 1:enabled} Inactivity timeout
TimeoutMinutes	integer {1-100}
KeepAliveSeconds
CurrentTheme	string {light:Light, dark:Dark, classic:Classic}
DisableLiveStreams	bool {0:disabled, 1:enabled} Prevents user from viewing live video, does not affect search
Use12HourClock	bool {0:disabled, 1:enabled}
TemperatureScale	bool {0:Fahrenheit, 1:Celsius}
LicenseWarningAck	bool {0:disabled, 1:enabled}
LicenseExpirationAck	epoch
AutoCheckForClientUpdates	bool {0:disabled, 1:enabled} Found on client About pop-up
ShowNotificationsForIndicators	bool {0:disabled, 1:enabled}
StartUpInstanceCount	integer Number of client instances to open
IgnoredVersion
SendAnonymousData	bool {0:disabled, 1:enabled} Found on client About pop-up
MotionColor	integer {0-16777215} Decimal color value
AlarmColor	integer {0-16777215} Decimal color value
FreeRunColor	integer {0-16777215} Decimal color value
PTZFocusColor	integer {0-16777215} Decimal color value
EventMonitorColor	integer {0-16777215} Decimal color value
BookmarkColor	integer {0-16777215} Decimal color value
NoColor	integer {0-16777215} Decimal color value
ClientIniAutoUpdateEna	bool {0:disabled, 1:enabled} Toggles automatic import on Add Systems
ClientIniAutoUpdateUrl	string (path or url address to XDV file to import)
HWAccelLimit
ShowTrayIcon	bool {0:disabled, 1:enabled} Shows icon for Client instance in System Tray See also: How to Configure No Close Client Usage
Delete	bool {0:disabled, 1:enabled} Disabling prevents Client instance closure. See also: How to Configure No Close Client Usage

Instance Attributes

Number	integer Client instance number
Top	integer (distance from top of desktop where client window begins)
Left	integer (distance from left edge of desktop where client window begins)
Width	integer (width of client window from left point)
Height	integer (height of client window from top point)
Maximize	bool {0:disabled, 1:enabled} Client window fills screen or not
FullScreen	bool {0:disabled, 1:enabled} Fills screen and hides window controls (F11)
ShowToolbars	bool {0:disabled, 1:enabled} Hide/show toolbar (F8)
ShowNavPanel	bool {0:disabled, 1:enabled} Hide/show nav panel (F4)
LiveMode	integer {0:cameras, 1:groups, 2:maps, 3:views} Client opens with Live nav panel to the selected option
LiveModeNavButtons	integer {0:collapsed, 1:cameras, 2:groups, 3:maps, 4:all expanded} Expanded or collapsed level of nav panel buttons
SearchModeNavButtons	integer {0:collapsed, 1:cameras, 2:groups, 3:maps, 4:views, 5:events, 6:bookmarks/cases} Expanded or collapsed level of search panel buttons
RemoteControlEnabled	bool {0:disabled, 1:enabled} Toggles receiving of video push display
RemoteControlName	string
MainSashPos	integer (width of left side nav panel)
PTZControlLeft	integer (distance from left edge of desktop where ptz pop-up begins)
PTZControlTop	integer (distance from top edge of desktop where ptz pop-up begins)
SoftTriggerControlWidth	integer (width of soft trigger pop-up from left point)
SoftTriggerControlHeight	integer (height of soft trigger pop-up from top point)
SoftTriggerControlLeft	integer (distance from left edge of desktop where soft trigger pop-up begins)
SoftTriggerControlTop	integer (distance from top edge of desktop where soft trigger pop-up begins)
TwoWayAudioDialogWidth	integer (width of two-way audio pop-up from left point)
TwoWayAudioDialogHeight	integer (height of two-way audio pop-up from top point)
TwoWayAudioDialogLeft	integer (distance from left edge of desktop where two-way audio pop-up begins)
TwoWayAudioDialogTop	integer (distance from top edge of desktop where two-way audio pop-up begins)
RemoteControlDialogWidth	integer (width of video push pop-up from left point)
RemoteControlDialogHeight	integer (height of video push pop-up from top point)
RemoteControlDialogLeft	integer (distance from left edge of desktop where video push pop-up begins)
RemoteControlDialogTop	integer (distance from top edge of desktop where video push pop-up begins)
RemoteControlGUID	string

Live Attributes

View	string (name of View)
Tour	string (name of Tour)
EventMonitor	string (name of Event Monitoring profile) Must be Switch View type
StartLayout

Layout Attributes

Name	string (layout name)
Rows	integer (number of video panel rows to allot)
Cols	integer (number of video panel columns to allot)

Item Attributes

X	integer (beginning column number)
Y	integer (beginning row number)
Width	integer (number of columns to merge)
Height	integer (number of rows to merge

System Attributes

Name	string (host/IP:port)

Video Attributes

Position
Name	string
CameraID	integer
Device	string (IP address)
DeviceMac	string (MAC address)
Number	integer
Context
AutoContext	integer
ToggleAnalytics	integer

Audio Attributes

Name	string
Device	string (IP address)
DeviceMac	string (MAC address)
Number	integer
Context

Systems Attributes

Address
Port
Group
Name
AllowSave
Username
Password
PasswordType
Enabled
Latency
ExportPermission
EnterpriseManaged
UseSystemLogin
SupportsTargetSearch
IsEdgeServer
ExpandedInCamTree
FailoverState
Model
Serial
Package
Version
MAC
License
IsLicensed
IsEnterprise
IsEnterpriseEx
Expiration

Security Integrations

AlwaysPrompt

bool

Sync Attributes

Enabled
ConnectedOnce
SyncFrequency
CredsSingleSignOn
CredsPrompt
Username
Password
PasswordType
UpdaterPath
UpdateCheckInterval
ForcedUpdates

Tags exacqVision Client, Client Software, Level2, XDV, 18034, Client

Knowledge Support Support exacqVision Client Categories Products

Deploying System Lists to Client Users

Post author By Bhargav Atturu
Post date October 27, 2023

In large organizations, such as multi-site enterprises, K-12 school districts, or university campuses, some admins will desire the ability to remotely manage the server connections their users have added within their ExacqVision Client application. This can result in faster deployments as well as less user support from their IT/Desktop Support teams, avoiding emailing, printing, or reciting information over the phone on how to enter each server’s IP address and that user’s login credentials.

This guide is written for ExacqVision Client version 9.4 and higher. Versions 9.2 and earlier used alternative file types.

This guide is broken into sections for readability but it is recommended to review each section.

Client Configuration File

The ExacqVision Desktop Client application saves settings information for each user account on the system, allowing users who share the same workstation to login with different operating system accounts and retain different server lists and client settings from each other. These settings are stored in an XML file titled, ‘edvrclient.xml‘, located in the following location:

Windows
C:\Users\%username%\AppData\Roaming\edvrclient\edvrclient.xml

Linux (Ubuntu)
/home/%username%/.edvrclient.dir/edvrclient.xml

macOS
/Users/%username%/Library/Application Support/edvrclient/edvrclient.xml

Each time the ExacqVision Client is opened, it refers to this file for its configuration, unless told otherwise.

Importing Via Client

There are four methods for populating a system list for client users. Within the client, these can be found on the ‘Add Systems‘ page by selecting the ‘Import/Export‘ tab.

Manual Import
Automatic Import – File on startup
Automatic Import – URL on startup
Automatic Import – Synchronize with Enterprise Manager

The first option is ‘Manual Import‘, using an XDV file. XDV is the file format ExacqVision exports, allowing you to configure one client as you’d like it, then export your System List in this XDV file for others to import. This method does little to help those deploying to many systems since it requires manually importing on each client instance.

XDV files are written in standard XML format, but are encrypted and associated to a MIME type which tells the workstation to open it with the ExacqVision Client application. XDVs contain a large amount of information about each connected server as well as client instance settings. XML tags and attributes not included in manually created files are filled in by the software with default information, meaning you only need to include the specific attributes relevant to your case. In this article we focus on providing a list of systems for users to connect to.

Beneath this is the ‘Automatic Import‘ section, which provides a few options. ‘File on startup‘ tells the client software to import client settings from the specified XDV file. This may reside on the local client workstation or on a network file share, but the share must be reachable when the client application is opened.

‘URL on startup‘ works in much the same way as ‘File on startup’, but allows the XDV file to reside at a web URL rather than a local directory or file share.

Finally, ‘Synchronize with ExacqVision Enterprise Manager‘, authenticates to an EM server for a list of ExacqVision Servers the authenticated account has access to and populates the System List based on the systems and user roles EM provides to that account. This method requires an Enterprise Manager instance as well as Enterprise licensed servers.

A benefit of using the ‘Automatic Import’ options is that administrators have control over which systems users have added to their client software and since the software checks this each time it opens, it changes any client settings the user may have tried to make since it was last used. This last part is important since users that you choose to prompt for credentials with each use may try to check the ‘Save credentials’ option, but forcing the client to use this file each time it opens causes them to be prompted for credentials anyway. It also adds or removes systems from their System List as you make changes to your systems and network.

Creating a Populated System List

The following steps will detail how to populate a user’s System List, which may be a common administrative task in environments where workstations are often reimaged or new users need to add several systems to their client instances.

Using a text edit, you will edit your own files following the examples below.

Ex. 1 – Always prompt for credentials
<exacqVisionInit>
    <Systems>
        <System Address="192.168.0.200" Port="22609"/>
        <System Address="192.168.0.201" Port="22609"/>
        <System Address="exacq.mysite.com" Port="22609"/>
    </Systems>
</exacqVisionInit>

Within the System tag, in the Address attribute, you will enter the IP address or hostname of your systems. The template provides examples. The default listening port for ExacqVision Server software is 22609. If you have changed this, enter your port number in the corresponding Port attribute for each system.

In this, the most basic configuration, the System rows above end there and the client software will prompt the user to enter their credentials each time the client is opened. Repeat the System rows as many times as needed.

Ex. 2 – Use credentials entered below
<exacqVisionInit>    &nbsp<Systems>         <System Address="192.168.0.200" Port="22609" Username="myusername" Password="mypassword" PasswordType="0"/>         <System Address="192.168.0.201" Port="22609" Username="myusername" Password="mypassword" PasswordType="0"/>         <System Address="exacq.mysite.com" Port="22609" Username="myusername" Password="mypassword" PasswordType="0"/>    &nbsp</Systems> </exacqVisionInit>

Adding Username and Password attributes provide additional customization. If you choose to add these attributes you will need to enter the user account credentials you’ve previously created on the system for this user. You must also set the PasswordType attribute to a value of 0. After the client imports the settings, it encrypts the plaintext password entered into the edvrclient.xml files mentioned above and the PasswordType value is changed to 3.

Ex. 3 – Synchronize with Enterprise Manager
<exacqVisionInit>    &nbsp<Systems>         <System Address="192.168.0.200" Port="22609" UseSystemLogin="1"/>         <System Address="192.168.0.201" Port="22609" UseSystemLogin="1"/>         <System Address="exacq.mysite.com" Port="22609" UseSystemLogin="1"/>    &nbsp</Systems> </exacqVisionInit>

The above example will add the listed systems for the client, but rather than including login credentials or prompting the user for credentials, will tell the client to login with Single Sign-On. Note that this requires the servers to have Active Directory/LDAP configured and the client workstation must be a member of the domain. See other guides for help configuring Active Directory/LDAP.

You may mix and match the examples of System authentication from the previous examples. For instance, you may add one system that logs the user in with credentials provided, but prompt for credentials for another system.

Enabling Your Configuration on Client Workstations

With the file created, you may now save it in a couple of ways.

If you save the file as an XML file, named ‘edvrclient.xml’, and replace the existing ‘edvrclient.xml’ file in the client directory mentioned earlier, the client will use this the next time it opens.

You may also save the file with a descriptive name of your choice and ensure that the file extension is not XML, but is XDV instead. This XDV file will not be encrypted yet. If you wish to encrypt it, you must first open it with the ExacqVision Client then export a new XDV file from the ‘Import/Export‘ tab on the ‘Add Systems‘ page. Exporting automatically encrypts the contents but you will be unable to edit it again after this process. As mentioned previously XDV files are associated with a MIME type, allowing a user to double-click on the file to open the ExacqVision Client with its configuration. For this reason an XDV file placed on a user’s Desktop provides an easy way for them to open the client with your desired configuration.

With this in mind, you may create one or more XMLs or XDVs to help specific users populate and login to a list of systems, or control a list of systems for a group of users. You will then need to find a method to deploy this to your user’s client workstations. You may choose to use third-party software deployment tools or you may opt to create a script that copies the file(s) to the desired workstations. Note, Exacq Support does not provide such scripts or provide help creating such scripts for your organization. We review some deployment options below.

Copy an XDV file to the user’s Desktop. When the user clicks to run it, the ExacqVision Client opens with the included configuration parameters.
Copy the XML file to the client settings directory to replace the existing ‘edvrclient.xml’ file.

The client automatically uses this configuration when it is launched again. Don’t forget that each user account on a workstation with multiple users will have their own ‘edvrclient.xml’ file in the directories listed near the top of this guide.
Save the XDV file to a network location or directory on the client workstation. Copy an ‘edvrclient.xml’ file to the client settings directory on the workstation to instruct the client, when launched, to automatically import the XDV file configuration.

This method makes the most sense using a networked location because you only need to deploy one file to the workstation (‘edvrclient.xml’), rather than two, but we will cover how to perform both options below.

Instruct edvrclient.xml to Auto Import XDV

Using a text editor, you will edit your own files using the examples below.

Ex. 4 – Auto Import File on Startup
<exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="C:\Users\RSmith\Documents\Demo.xdv">     <Systems>     </Systems> </exacqVisionInit>

In this example we add the attribute ClientInitAutoUpdate=”1″ to the exacqVisionInit tag, which enables the ‘Auto Import’ option. The ClientIniAutoUpdateUrl attribute sets the value to the location of the XDV file you want to import, with a list of servers we want the user to have. In this example, the location is a local directory on a Windows workstation for a user named ‘RSmith’, within his Documents directory. If you want to maintain your XDV files on a network share, be sure the share is always available, or the client will be unable to import the file.

Ex. 5 – Auto Import URL on Startup
<exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="https://demo.exacq.com/Demo.xdv">     <Systems>     </Systems> </exacqVisionInit>

To import from a URL instead, simply change the ClientIniAutoUpdateUrl value to the URL, as shown in the above example.

Changing the file to force client synchronization with your ExacqVision Enterprise Manager server requires a few more edits.

Ex. 6 – Auto Import Synchronize with Enterprise Manager with credentials
<exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="https://192.168.0.4">     <Sync Enabled="1" Username="myusername" Password="mypassword" PasswordType="0"/> </exacqVisionInit>

The value of the ClientIniAutoUpdateUrl attribute changes to the address/hostname of your Enterprise Manager server.

A new Sync tag replaces the Systems tag in this example, and our Enabled attribute for it has a value of 1. The Username and Password values will be for the user credentials for the Enterprise Manager user. Once again, if opting to enter the Username and Password, you must add the PasswordType attribute and set the value to 0.

Ex. 7 – Auto Import Synchronize with Enterprise Manager prompt for credentials
<exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="https://192.168.0.4">     <Sync Enabled="1" CredsPrompt="1"/> </exacqVisionInit>

To prompt the user to enter their Enterprise Manager credentials each time the client is opened, remove the Username and Password attributes and add the CredsPrompt attribute with a value of 1, as shown above.

Ex. 8 – Auto Import Synchronize with Enterprise Manager single sign-on
<exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="https://192.168.0.4">     <Sync Enabled="1" CredsSingleSignOn="1"/> </exacqVisionInit>

If your Enterprise Manager instance is configured for Active Directory/LDAP and the client workstations are members of your domain, you may also set the option to connect using Single Sign-On.

This example removes the CredsPrompt attribute and uses the CredsSingleSignOn attribute instead, setting the value to 1.

Tags System List, Enterprise Administration, 17888, Guest, Client, Enterprise Manager, Deploying Client Settings, Add Systems, XML, XDV, Client Configuration

Knowledge Support Cloudvue exacqVision EDGE Support exacqVision Enterprise exacqVision Client exacqVision Server exacqVision Webservice Categories Products exacqVision Hardware exacqVision Integrations

PortCheck Utility

Post author By Isaac Penrod
Post date October 12, 2023

When troubleshooting TCP/IP connectivity issues, it is often helpful to confirm that the network path is open over a specified port and that there is no interference from a firewall or antivirus. This also rules out software level problems that may be causing a failure to connect.

While there exists many utilities to accomplish this task (telnet, putty, nmap, etc…), often these utilities aren’t previously isntalled and can’t be accessed when troubleshooting.

This utility will attempt to make a TCP connection to a specified IP Address or hostname over a specified port and return either success or failure.

PortCheck – Windows

PortCheck.bat

If you are unable to transfer the file, the contents can be copy and pasted into a file manually and run from command line.

::PortCheck.bat

::This utility will check the network path to the specified IP address/Hostname.

::It will accept the first argument as the IP Address/Hostname, and the second argument as the port.

::Author - Isaac Penrod



@echo off



set $IP=%1

set $PORT=%2



IF "%~1" == "" set /p $IP="Enter the IP Address or Hostname: "

IF "%~2" == "" set /p $PORT="What TCP Port: "

set $COMMAND="^(New-Object System.Net.Sockets.TcpClient^).ConnectAsync^('%$IP%', '%$PORT%'^).Wait^(800^)"

echo.

echo Checking connectivity to %$IP%:%$PORT%

echo If the network path is open and something is listening
at that location, the result will be "True"

echo.

powershell -command " %$COMMAND% "

echo.

pause

PortCheck – Linux

portcheck.sh

If you are unable to transfer the file, the contents can be copy and pasted into a file manually and run from terminal.

You will also need to make the file executable with – chmod +x portcheck.sh

#!/bin/bash

#This utility will check the network path to the specified IP address/Hostname.

#It will accept the first argument as the IP Address/Hostname, and the second argument as the port.

#Author Isaac Penrod



IP=$1

PORT=$2



if test -z "$IP"

  then

    read -p "Enter the IP Address or Hostname: " IP

  fi



if test -z "$PORT"

  then

    read -p "What TCP Port: " PORT

  fi



echo

echo Checking connectivity to $IP:$PORT

echo If the network path is open and something is listening at that location, the result will be "success"

echo

timeout 2 bash -c 'if > /dev/tcp/'$IP'/'$PORT'; then echo success; fi'

if [ $? != "0" ]; then

  echo failure

  fi

echo

Arguments

This utility will also accept command line arguments.
$1 – IP Address/Hostname
$2 – Port

Tags Test, Network, Port, Internal, Telnet, Scanner, Putty, 17692

Knowledge Support Highlighted Support exacqVision Client exacqVision Server Categories Products

Where can I access Training Courses?

Post author By Lauren McTeague
Post date October 6, 2023

Exacq-Training-Courses.pdf

Tags Training, 17600, Where can I access Training Courses?, Training Courses, E-Learning, Solutionwhere

S2 Knowledge Support Support exacqVision Enterprise exacqVision Client exacqVision Server exacqVision Webservice Categories Products exacqVision Integrations

2023-09 September Quarterly Release Training

Post author By Bhargav Atturu
Post date September 13, 2023

2023-09-September-Quarterly-Release-Training

ExacqVision Server

Bug Fix – Fixed issue causing server crash due to missing microSD card in Illustra multisensor cameras.
If camera has no microSD for one sensor, but does for another, network loss recording action caused a crash. (AESW-7549)

Bug Fix – Prevent offload from Illustra BWC from hanging

Bug Fix – If camera does not support metadata over HTTPS, allow metadata over HTTP when camera is added with “HTTPS if Available” setting with illustra3pi and illustramultipi

Bug Fix – Added camera detection for all Illustra 2023 released models, this includes Flex 4 PTZ, Pro 4 Bullet, Pro 4 Compact Dome, Pro 4 Corner, and Flex 4 Dome models (AESW-5896)

Bug Fix – Support for motion windows when adding Onvif cameras to server, some Onvif cameras would not detect motion after adding even with enabled motion windows (AESW-7220)

Bug Fix – Fix for issue when Onvif cameras send ‘out of bounds’ motion window coordinates
(AESW-7373)

Bug Fix – Decouple iris and focus debuffering from PTZs using Onvif

Feature – Improvements to core, logpi, softtriggerpi, tdvrpi, and videotestpi for logging and performance
(AESW-5801)

Feature – Updated database structure and management for eventpi to improve metadata search performance, queries, and data purging (AESW-6286)

Feature – Added new retention options for AI / Object metadata
Provides ability to help manage eventpi database size (AESW-6082)

Feature – Onvif motion and transport ‘plug-n-play’ support removes the need for manually updated Onvif JSON files and now Onvif plugin can dynamically read the motion topics from Onvif cameras (AESW-6069, AESW-3746)

Feature – New ‘Power User (No Video)’ security user role
Supports countries where strict laws exist around video access (AESW-6387)

Enhancement – Added ability to set oldest desired content age for Cloud Drive content (AESW-3064)

Enhancement – Axispi now supports upper and lower clothing color metadata (AESW-7031)

Enhancement – Added paging support for brivopi

Enhancement – Added support for additional WDR modes on illustra3pi and illustramultipi (AESW-4618)

Enhancement – Added audit and logging of Illustra BWC privacy mode (AESW-7546)

Enhancement – Support added for Illustra BWC GPS data (AESW-5429, AESW-5528)

Enhancement – Added support for PCM16 audio for live streaming from Illustra BWC (AESW-423)

Enhancement – Added encrypted password storage to notify.xml for notifications (AESW-2085)

Build – Plugins for Basler, IoImage, IPX, Sanyo, Stardot, and UDP now unchecked by default during installation

Build – Upgraded aws-sdk-cpp to version 1.11.1

Build – Upgraded cURL to version 7.87.0

Build – Upgraded OpenSSL to version 3.1

Build – Upgraded libwebsockets to version 4.3.2

Build – Upgraded zlib to version 1.2.13

ExacqVision Client

Bug Fix – Enable appropriate buttons on the Add IP Cameras page after deleting cameras
(AESW-6809)

Bug Fix – Fixed issue where Live view navigation tree reloaded on camera double-click (AESW-5618)

Bug Fix – Properly size toolbar icons for 4K monitors (AESW-7231)

Bug Fix – Properly display the disabled Analytics buttons on Linux. Buttons were appearing as enabled when they should be disabled (AESW-6662)

Enhancement – Client support for the Oldest Content setting for Cloud Drive content
(AESW-6779, AESW-7710)

Enhancement – Added new UX field for Frame-by-frame metadata retention period (AESW-6307)

Enhancement – Optimization for search speeds (AESW-5121)

Enhancement – Live analytic support for Illustra BWC (AESW-2846)

Enhancement – Moved generic dewarper to top of fisheye dewarper selection list (AESW-7389) Client side support for new WDR settings (AESW-5690)

Enhancement – Client side support for the new ‘Power User (No Video)’ user role. ‘Not Allowed’ text displayed for camera panels, Cameras hidden entirely from search (AESW-6388)

ExacqVision Web Service

Bug Fix – Removed no longer supported SCGI proxy folder. Action taken to prevent cross site scripting errors when performing vulnerability scans (AESW-6677)

Enhancement – Added evAPI support for detecting restricted view configuration (AESW-4288)

Enhancement – Change endpoint for S2 integration to ‘video.web’ (AESW-4903)

Enhancement – Scale web client search playback buffer with the playback speed selected (AESW-4757)

ExacqVision Enterprise Manager

Bug Fix – Update VMS audit log entries to use valid JSON (AESW-7458)

Bug Fix – Use the correct logger sync

Bug Fix – Add missing Seq settings validation

Enhancement – Add support for ‘Power User (No Video)’ user role (AESW-7169)

Enhancement – Add VMS audit trails to the EM audit logs (AESW-5498)

Enhancement – Added API endpoint for retrieving individual audit log entries (AESW-1340)

Enhancement – Add slug to audit logs where applicable (AESW-7176)

Enhancement – Add a user configurable timer for VMS audit log retrieval (AESW-6087)

Enhancement – Integration of EM/ISP logs into Seq. Provides the ability to extract logs into external Seq logging systems

Enhancement – Add migration files to upgrade AES encryption over the older ARC4 to enhance security
(AESW-7512)

Enhancement – Update Apache to version 2.4.57 (AESW-6957)

Illustra IQ

Targeted product launches:

October
- Pro Gen4 Bullet
- Pro Gen4 Corner
November
- Flex Gen 4 Dual Sensor
December
- Flex Gen4 Dome
- Flex Gen4 Compact
- Flex Gen4 Bullet

Tags Level2, Quarterly, Release Training, Training, 17439

Video Library Configuration Demo exacqVision Client Illustra Youtube Video Library Categories Products

Scenario Series – Illustra IQ Object Classification to Change ExacqVision Views

Post author By Bhargav Atturu
Post date September 6, 2023

The Scenario Series of videos addresses setup configurations for specific use cases.

In this video our scenario is that of a user that wants to use Event Monitoring to bring attention to an ExacqVision operator when someone parks in specific parking spaces. This could be used to prevent people from parking in forbidden areas, to alert someone to customers in curb-side pickup spots, and more.

We walk through setting up AI Object Classfication within an Illustra IQ camera and configuring Event Monitoring in ExacqVision to change our displayed camera views when triggered.

Tags 17361, Guest, AI Object Classification, Illustra, Scenario, Views, Event Monitoring