When having Kantech Board connected to the Exacq Server, Client Software keeps refreshing the configs and that prevents the Exacq client from creating an Email notifications profile.
affected version is 23.03 or lower
Solution
Updating ExacqVision Server and Client to version 24.03 or above.
Updating the Kantech Entrapass to version 8.80 or above.
In order to succeed in the remote client authentication via LDAP, We will need to make sure that we have the following three points.
ExacqVision Server uses an enterprise license and is connected to an AD/LDAP server.
ExacqVison Client is able to reach the Exacq Server via port 22609, and the LDAP via port 636 if LDAP with SSL or 389 if LDAP without SSL.
Active Directory server can reach the Exacq Server and Exacq Client workstation.
The way Kerberos tickets work is that we need all three points able to see and connect to each other, so we need to check these requirements before establishing the Exacq client connection to the Exacq server via the SSO method.
Customer notice the toolbar with extremely large icons after updating to 23.06.2.0 Client. This was seen with multiple 4k monitor on a single client work station.
Product
Client 23.06.2.0
Steps to Reproduce
Removed software and install client version 23.06.2.0 and issue would appear.
Installed 23.03 no issues seen.
Updated the client to 23.06.2.0 version from 23.03 version of the client and toolbar icons were large.
Expected Results
Update from 23.03 Client to 23.06.2.0 OR New install of 23.06.2.0 Client should not have large Toolbar/icons than previous version (23.03).
Actual Results
The Toolbar section of the client that houses the Icons are extremely large on 4k Monitors.
Solution
We found that 23.03 Client was not working as expected with 4K monitors. There is a build that will correct this upon updating the client. Build exacqVisionClient_23.06.1412707.0_x64
When adding an IP device to your ExacqVision Server, each device will be associated with a Device Type that selects the underlying plugin used for communication.
You are unable to find the required Device Type when attempting to add the device. <br><br>
Cause
When using an existing ExacqVision install, possible reasons are:
The plugin was not selected to be included in the initial installation.<br><br>
The first version of the plugin was released after your initial server installation version.<br><br>
In the first example, running the installer manually, a dialogue window appears providing users with the option to select or deselect each individual plugin to be included with the server installation. Most users are fine using the default selections. There are some plugins not selected by default because they may be older or used only in rare instances.
When performing automated updates using the Check for Updates button the software updates only the plugins already installed. It does not install additional plugins.
In the second example, you may be looking for a plugin used for a newer integration. This may also eventually lead to the cause mentioned above. <br><br>
Resolution
Download the ExacqVision Server installer directly from the Software Downloads page.<br><br>
Run the downloaded installer file manually.<br><br>
Watch for the dialogue in which the listed plugins may be selected for install.<br><br>
Scroll to the plugin you need and be sure it is check marked for install.<br><br>
Complete the remainder of the installation steps. After the service restarts, the desired plugin should be listed in the Device Type options.
This article applies to the Axis A8207-VE and A8207-VE MkII Network Video Door Stations using firmware 11.5.64.
exacqVision does not currently support SIP calling functions. However, these door stations 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.<br><br>
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 A8207-VE and A8207-VE MkII 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. <br><br>
Add the Device
You will want to use a web browser to log into the door station and perform the initial setup, which at this stage usually means setting a non-default username/password, and possibly setting a static IP address.<br><br>
The call button should be enabled by default. <br><br>
If you do not already know the IP address of the door station, you will need to discover it on the network.<br>
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 want 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. <br><br>
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. <br><br>
Enable Two-Way Audio
Expand the Add IP Cameras node from the navigation tree.<br><br>
Select the Audio Inputs/Outputs node nested beneath the Add IP Cameras node.<br><br>
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.’ <br><br>
Find the Record Enable column. Place a check in the box for both of these rows for the door station. This enables two-way audio functions within exacqVision.<br><br>
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.<br><br>
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.<br><br>
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.<br><br>
The panel along the left lists existing cameras. Find and click to select the door station.<br><br>
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.<br><br>
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.<br><br>
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.<br><br>
Click Apply to save your changes when done.
<br><br>
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.<br><br>
Click the New View button, then enter a descriptive name. In this example, we name our view ‘East Entry.'<br><br>
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.<br><br>
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. <br><br>
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.<br><br>
Click Apply to save you changes when done.<br><br>
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.’
<br><br>
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.<br><br>
Click the New button under the Profiles panel to begin creating a new profile.<br><br>
Enter a descriptive Name under the Profile Configuration panel. Our example will name this ‘East Entry’ for the door where it is being placed.<br><br>
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.<br><br>
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.<br><br>
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.<br><br>
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.<br><br>
From the Event Type panel list below, select ‘Default’.<br><br>
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.<br><br>
From the Action Target panel list, select the default View you created earlier.<br><br>
Click the New button under the Client Actions panel in the middle of the window. This adds a new row to configure.<br><br>
With the newly created row highlighted, select Input Trigger from the Event Type list.<br><br>
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.<br><br>
From the Action Type list, select Switch View.<br><br>
From the Action Target list, select the door station View you created earlier. In our example we named this ‘East Entry’.<br><br>
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.<br><br>
Click the Apply button to save your changes when done.
<br><br>
Handling Calls From exacqVision
Using the exacqVision Client software, browse to Live mode.<br><br>
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.<br><br>
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. <br><br>
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.<br><br>
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.<br><br>
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. <br><br>
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.<br><br>
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><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.<br><br>
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 is initiated by dialing a designated SIP extension number prior to pressing the Call Button.
Note: When used together with SIP, any press of the Call Button will trigger the Event Monitoring profile regardless of whether it was used when dialing an extension number or not.<br><br>
At times it may be necessary to drop (delete) and create the smartvuedb database. WARNING VIDEO LOSS is expected, and except for rare occasions this should only be performed on newly deployed NVRs.
Product
Cloudvue Gateway
Prerequisite
ssh access to the Cloudvue Gateway
see KB #13051 “Cloudvue SSH Tunneling” or KB #13667 “Tunneling to a Cloudvue Gateway From a Local Windows Machine”
Solution
Issue the following commands from terminal
** WARNING ** WILL RESULT IN VIDEO LOSS
<code>sudo service cron stop <br>mysqldump -u root -p smartvuedb camera camera_setting camera_view nvr_setting schedule user user_setting user_Status User_view view > /home/smartvue/smartvuedb_backup.sql <br>sudo mysql smartvuedb -s -e “drop database smartvuedb;”<br>sudo mysql -s -e “create database smartvuedb;”<br>sudo -i <br> bash /opt/smartvue/services/nvr-database-migrate/installer.sh<br>bash /smartvue/updater.sh<br>mysql -u root smartvuedb -p < /smartvue/mysql/multi-tables_smartvuedb_backup_file.sql<br>exit<br>sudo service cron start</code>
Command Explanation
cron stop – Stops scripts from being launched by cron during this process
msyqldump – (Optional) can be used to create a backup of specified tables within the existing smartvuedb database
drop database smartvuedb – Removes the existing smartvuedb database
create database smartvuedb – creates an empty smartvuedb database
sudo -i – switch to root user
installer.sh – runs the installer script which sets permissions for smartvuedb and will return the following lines if successful
++ pwd -P <br>+ SERVICE_DIR=/root <br>SERVICE_DIR=/root <br>SMV_NVR_DB_USER=root <br>/root/node_modules/db-migrate/bin/db-migrate up <br> /opt/smartvue/services/nvr-database-migrate/installer.sh: line 4: /root/node_modules/db-migrate/bin/db-migrate: No such file or directory <br>exit 127
updater.sh – runs the updater script which populates default values in certain tables within smartvuedb database and takes several minutes to complete.
mysql -u root smartvuedb -p – (Optional) can be used to import tables previously backed up with the mysqldump
The license being transferred “From” must have a current SSA.<br><br>
“From” and “To” licenses must be the same level. (Start, Professional, Enterprise)<br><br>
An existing “To” license keeps its SSA end date. This includes “To” licenses with an expired SSA.<br><br>
New “To” or “Zero” licenses: NOTE: A “Zero” license is an existing license that has had all IP channels transferred away
If it is an Exacq-built server “Zero” license and the SSA end date is more than a year in the future, then it keeps its own SSA end date. If less than a year, it receives a full year.
If it is a new license then it receives the SSA end date of the “From” license regardless of the existing “From” SSA end date. Again, the “From” license cannot be expired. This may be the next day or five years in the future.
If it is a “Zero” license for server hardware built by a third-party, then it receives the SSA end date of the “From” license regardless of the existing “From” SSA end date. Again, the “From” license cannot be expired. This may be the next day or five years in the future.<br><br>
An Edge or Edge Plus (Edge+) IP channel may only be transferred to a new MAC address.<br><br>
A Lifetime SSA does not transfer when an IP channel is transferred from a Lifetime SSA server to a non-Lifetime SSA server.
Licenses with Lifetime SSAs can be renewed at no charge by the Exacq Orders Team at exacqorders@tycoint.com<br><br>
Enterprise Manager
IP channels transferred from an Enterprise Manager license pool come with one year of SSA. That SSA is then distributed among any existing IP channels on the “To” license.<br><br>
Channels cannot be transferred from an existing license to an Enterprise Manager pool.<br><br>
Per the above rule, once a license has been transferred from the license pool, it cannot be moved back to the pool.<br><br>
At times you may need to remotely access the web interface of either a Cloudvue Gateway or camera. The following instructions can be used to establish a tunnel, gain ssh access and setup remote port forwarding via the reverse tunnel script. Once setup you will be able to access the terminal (ssh) or the Web Interface of equipment local to the video device, such as Cloudvue Local or C2C cameras (reverse port forwarding).
Product
C2C
Cloudvue Gateway
Solution
From Cloudvue Manager
Setup a Tunneling port, see “Cloudvue SSH Tunneling” KB# 13051
From your Tunneling Machine
Terminal Window #1 – Establish a Tunnel
./createTunnel.sh -t PNUM
Note: PNUM is the port number created in Cloudvue Manager
Terminal Window #2 – Establish SSH Connection
./sshTunnel.sh -p PNUM
$ watch -n 30 ls -alh
Note: PNUM is the port number created in Cloudvue Manager and the watch command is used to keep the connection from timing out use Ctrl+c to stop the watch command.
In the event the following warning appears run the full “ssh-keygen” command found in the message to clear the /root/.ssh/known_hosts file, then try establishing the ssh connection again.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Terminal Window #3 Establish Port Forwarding via Reverse Tunnel
./reverseTunnel.sh -p 80 -l 80
NOTE: it may be necessary to manually configure the correct tunneling port by changing ./config/tunnelInfo.txt
Account changes cannot be made through Cloudvue Manager. A ticket will need to be raised with engineering so they can make the necessary changes in the cloud database.
Product
Cloudvue Access
KT-1
ioSmart Readers
Solution
Gather the following information to include on the engineering ticket.