Siveillance™ Video Administrator Manual 2019 R3
Contents Copyright ........................................................................................................................................ 16 Product overview ............................................................................................................................ 17 Main system components .......................................................................................................... 17 Management server .........................................................
Time servers (explained) ........................................................................................................... 42 Limit size of database ................................................................................................................ 42 IPv6 and IPv4 (explained) ......................................................................................................... 43 Using the system with IPv6 (explained) ...............................................................
Device drivers (explained) .................................................................................................... 62 Requirements for offline installation ..................................................................................... 62 Install the system ....................................................................................................................... 63 Install your system - Single computer option ...................................................................
Network tab (options) ........................................................................................................... 99 Bookmark tab (options) ........................................................................................................ 99 User Settings tab (options) ................................................................................................. 100 Evidence Lock tab (options) ..........................................................................................
Enable encryption from the management server ............................................................... 126 Recording server status icons ............................................................................................ 128 Info tab (recording server) .................................................................................................. 128 Info tab properties (recording server) .................................................................................
Group failover recording servers for cold standby ............................................................. 159 Read failover recording server status icons ....................................................................... 160 Multicast tab (failover server) ............................................................................................. 160 Info tab properties (failover server) ....................................................................................
Working with device groups .................................................................................................... 179 Device groups (explained) ................................................................................................. 179 Add a device group ............................................................................................................ 180 Specify which devices to include in a device group ...........................................................
Storage of the temporary pre-buffer recordings ................................................................. 201 Manage pre-buffering ......................................................................................................... 201 Enable and disable pre-buffering: ...................................................................................... 201 Specify storage location and pre-buffer period: .................................................................
Client tab (explained) ......................................................................................................... 231 Privacy masking tab (devices) ........................................................................................... 234 Privacy masking tab (explained) ........................................................................................ 235 Privacy masking (explained) ..............................................................................................
Timeline tab (Client profiles) .............................................................................................. 260 Access Control tab (Client profiles) .................................................................................... 260 Smart map tab (Client profiles) .......................................................................................... 261 View Layout tab (Client profiles) ........................................................................................
Refresh site hierarchy ........................................................................................................ 394 Log into other sites in the hierarchy ................................................................................... 394 Detach a site from the hierarchy ........................................................................................ 395 Federated site properties ...................................................................................................
Enter Bing Maps key or Google Maps private key and client ID in Siveillance Video Client ............................................................................................................................................ 411 Changing OpenStreetMap tile server ............................................................................. 411 Set an alternative OpenStreetMap tile server ................................................................
Back up system configuration manually ....................................................................... 505 Restore system configuration from a manual backup ................................................. 505 Select shared backup folder ........................................................................................... 506 Scheduled backup and restore .......................................................................................
Add and edit registered services .................................................................................... 526 Manage network configuration ....................................................................................... 526 Registered services properties ....................................................................................... 526 Removing device drivers (explained) ......................................................................................
Copyright Copyright © 2019. Siemens Switzerland Ltd. All rights reserved. The information contained in this publication is company-proprietary to Siemens Switzerland Ltd. This publication and related software are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering / copying of any Siemens Switzerland Ltd hardware, software, documentation, or training materials is strictly prohibited.
Product overview The Siveillance Video products are video management software designed for installations of all shapes and sizes. Whether you want to protect your store from vandalism or you want to manage a multi-site, high security installation, Siveillance Video makes it possible. The solutions offer centralized management of all devices, servers, and users, and provide an extremely flexible rule system driven by schedules and events.
audio and video. The recording server is also responsible for communicating with other Siemens products connected via the Siveillance Video Interconnect technology.
SQL Server The management server, event server and log server uses a SQL Server to store, for example, the configuration, alarms, events and log messages. The system installer includes Microsoft SQL Server Express which is free edition of SQL Server.
The difference between the cold and hot standby modes is that in the cold standby mode, the failover recording server does not know which server to take over from, so it cannot start until a recording server fails. In the hot standby mode, the failover time is significantly shorter, as the failover recording server already knows which recording server it should take over from and can preload the configuration and start up completely - except for the last step of connecting to the cameras.
The interface allows you to tailor your viewing experience to specific working environments by selecting a light or dark theme. It also features work-optimized tabs and an integrated video timeline for easy surveillance operation. Using the MIP SDK, users can integrate various types of security and business systems and video analytics applications, which you manage through Siveillance Video Client. Siveillance Video Client must be installed on operators' computers.
live video, play back recorded video, print and export evidence. Access to features depends on individual user rights which are set up in the management client. To enable access to the Siveillance Video Web Client, you must have a Siveillance Video Mobile server to establish the connection between the Siveillance Video Web Client and your system. The Siveillance Video Web Client itself does not require any installation itself and works with most Internet browsers.
• • • • • • • Siveillance Video Client(s) IP video cameras Video encoder Analog cameras PTZ IP camera Camera network Server network Add-on products Siemens has developed add-on products that fully integrate with Siveillance Video to give you extra functionality. Access to add-on products are controlled by your software license code (SLC).
Siveillance Video Monitoring Wall (explained) Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information. Siveillance Video Monitoring Wall is an advanced video wall product that provides supreme situation awareness in larger surveillance centers and helps the surveillance operators to focus on what is important ensuring higher efficiency and shorter response times.
• • Instructions for installing and configuring the Siveillance Video Mobile ONVIF Bridge in your Siveillance Video product Examples of how to enable various types of ONVIF clients to stream live and recorded video from Siveillance Video products Siveillance Video DLNA Server (explained) DLNA (Digital Living Network Alliance) is a standard for connecting multimedia devices.
Ports used by the system All Siveillance Video components and the ports needed by them are listed in individual sections below. To ensure, for example, that the firewall blocks only unwanted traffic, you need to specify the ports that the system uses. You should only enable these ports. The lists also include the ports used for local processes.
Management Server service and related processes Port number Protocol Process Connections from... All Siveillance Video components 80 HTTP Siveillance Video Client and the Management Client 6473 8080 9000 HTTPS Main communication, for example, authentication and configurations. IIS The Management Server service and Recording Server services 443 Purpose IIS Handles registration of recording servers and management servers via the Authorization Server service. Authentication of basic users.
Port number 9993 12345 Protocol TCP TCP Process Management Server service Management Server service Connections from... Recording Server services Siveillance Video Client Purpose Authentication, configuration, token exchange. Communication between the system and Matrix recipients. You can change the port number in the Management Client. Communication with the SNMP extension agent. Do not use the port for other purposes even if your system does not apply SNMP.
Port number Protocol Process Connections from... Purpose 1433 TCP SQL Server Event Server service Storing and retrieving events. 1433 TCP SQL Server Log Server service Storing and retrieving log entries. Data Collector service Port number Protocol Process Connections from... Purpose On the management server computer: Data Collector services on all other servers. 7609 HTTP IIS System Monitor . On other computers: Data Collector service on the Management Server.
Port number 1235 Protocol TCP Process Connections from... Event Server service Any server sending generic events to your Siveillance Video system. Purpose Listening for generic events from external systems or devices. Only if the relevant data source is enabled. 9090 TCP Event Server service Any system or device that sends analytics events to your Siveillance Video system.
Port number 25 5210 5432 7563 8966 Protocol SMTP TCP TCP TCP TCP Process Recording Server Service Recording Server Service Recording Server Service Connections from... Cameras, encoders, and I/O devices. Failover recording servers. Cameras, encoders, and I/O devices. Purpose Listening for event messages from devices. The port is disabled by default. Merging of databases after a failover recording server had been running. Listening for event messages from devices.
Port number 11000 Protocol TCP Process Recording Server Service Connections from... Failover recording servers Purpose Polling the state of recording servers. Communication with the SNMP extension agent. Do not use the port for other purposes even if your system does not apply SNMP. 12975 TCP Recording Server Service Windows SNMP service In Siveillance Video 2014 systems or older, the port number was 6474. In Siveillance Video 2019 R2 systems and older, the port number was 7474.
Port number 5210 5432 Protocol TCP TCP Process Connections from... Recording Server Service Failover recording servers Recording Server Service Cameras, encoders, and I/O devices. Purpose Merging of databases after a failover recording server had been running. Listening for event messages from devices. The port is disabled by default. Communication with the SNMP extension agent.
Port number 8990 9001 Protocol Process TCP Failover Server Service HTTP Failover Server Service Protocol Process Connections from... Purpose Management Server service Monitoring the status of the Failover Server service. Management server Web service for internal communication between servers. Log Server service Port number 22337 HTTP Connections from... Log Server service Purpose All Siveillance Video components except for Management Client and the recording server.
Siveillance Video Mobile ONVIF Bridge service Port number Protocol Connections from... Process Purpose 580 TCP ONVIF Bridge Service ONVIF clients Authentication and requests for video stream configuration. 554 RTSP RTSP Service ONVIF clients Streaming of requested video to ONVIF clients. Siveillance Video DLNA Server service Port number Protocol Connections Purpose from... Process 9100 HTTP DLNA Server Service DLNA device Device discovery and providing DLNA channels configuration.
Port number Protocol Connections from... Purpose 443 HTTPS Recording servers and failover recording servers Authentication, configuration, and data streams; video and audio. 554 RTSP Recording servers and failover recording servers Data streams; video and audio. Cameras, encoders, and I/O devices (outbound connections) Port number 25 Protocol SMTP Connections to... Purpose Recording servers and failover recording servers Sending event notifications (deprecated).
Port number Protocol 22331 TCP Connections to... Purpose Event Server service Alarms. Siveillance Video Web Client, Siveillance Video Mobile client Port number Protocol Connections to... Purpose 8081 HTTP Siveillance Video Mobile server Retrieving video and audio streams. 8082 HTTPS Siveillance Video Mobile server Retrieving video and audio streams.
Name Siveillance VMS Video Core Siveillance VMS Video Core Plus Siveillance VMS Siveillance Video Advanced VMS Video Pro Siveillance Video Interconne ct Remote site Remote site Remote site Central/remote site Siveillance Video Federated Architecture™ - - Remote site Central/remote site Recording server failover - - Cold and hot standby Cold and hot standby Remote connect services - - - ✓ Edge storage support - ✓ ✓ ✓ Multi-stage video storage Live databases + 1 archive Live dat
Name Siveillance VMS Video Core Siveillance VMS Video Core Plus Siveillance VMS Siveillance Video Advanced VMS Video Pro Database signing (recording server) - - ✓ ✓ PTZ priority levels 1 3 32000 32000 Extended PTZ (Reserve PTZ session and patrolling from Siveillance Video Client) - - ✓ ✓ Evidence lock - - - ✓ Bookmark function - Manual only Manual and rule-based Manual and rule-based Live multistreaming or multicasting - - ✓ ✓ Client user rights/ Overall security Client us
Siveillance VMS Video Core Name Siveillance VMS Video Core Plus Siveillance VMS Siveillance Video Advanced VMS Video Pro System Monitor - - ✓ ✓ Smart map - - ✓ ✓ Two-step verification - - - ✓ DLNA support ✓ ✓ ✓ ✓ Privacy masking ✓ ✓ ✓ ✓ ✓ ✓ ✓ Device password management Licenses (explained) When you purchase your software and licenses, you receive: • • An order confirmation A software license file named after your SLC (Software License Code) and with the .
You have purchased at least two types of licenses: Base licenses: As a minimum, you have a base license for one of the Siveillance Video products. You may also have one or more base licenses for Siveillance Video add-on products. Hardware device licenses: Every hardware device that you add to your Siveillance Video system requires a hardware device license. You do not need additional hardware device licenses for speakers, microphones or input and output devices attached to your cameras.
Fall: Switch from DST to Standard Time When you switch from DST to standard time in the fall, you jump one hour back. Example: The clock jumps backward from 02:00 DST to 01:00 standard time, repeating that hour, and the day has 25 hours. You reach 01:59:59, then immediately revert to 01:00:00. If the system did not react, it would essentially re-record that hour, so the first instance of 01:30 would be overwritten by the second instance of 01:30.
1. • Click Options > Alarms and Events tab. Make the required settings. For more information, see Alarms and Events tab (options) on page 103. IPv6 and IPv4 (explained) Your system supports IPv6 as well as IPv4. So does Siveillance Video Client. IPv6 is the latest version of the Internet Protocol (IP). The Internet protocol determines the format and use of IP addresses. IPv6 coexists with the still much more widely used IP version IPv4.
Using the system with IPv6 (explained) The following conditions apply when using the system with IPv6: Servers Servers can often use IPv4 as well as IPv6. However, if just one server in your system (for example, a management server or recording server) requires a particular IP version, all other servers in your system must communicate using the same IP version. Example: All of the servers in your system except one can use IPv4 as well as IPv6. The exception is a server which is only capable of using IPv6.
Writing IPv6 addresses (explained) An IPv6 address is usually written as eight blocks of four hexadecimal digits, with each block separated by a colon. Example: 2001:0B80:0000:0000:0000:0F80:3FA8:18AB You may shorten addresses by eliminating leading zeros in a block. Also, note that some of the fourdigit blocks may consist of zeros only.
with traffic to other virtual servers. If the network adapter is used for several virtual servers, the network traffic might result in the recording server not retrieving and recording the configured number of images. Multiple management servers (clustering) (explained) The management server can be installed on multiple servers within a cluster of servers. This ensures that the system has very little downtime.
Windows Task Manager: be careful when you end processes When you work in Windows Task Manager, be careful not to end any processes which affect the surveillance system. If you end an application or system service by clicking End Process in the Windows Task Manager, the process is not given the chance to save its state or data before it is terminated. This may lead to corrupt camera databases. Windows Task Manager typically displays a warning if you attempt to end a process.
Before you start installation Siemens recommends that you go through the requirements described in the next sections, before you start the actual installation. Prepare your servers and network Operating system Make sure that all servers have a clean installation of a Microsoft Windows operating system, and that it is updated with all the latest Windows updates. For information about the minimum system requirements to the various components of your system, go to the Siemens website (https://www.siemens.
Basic users are not supported in Siveillance Video Federated Architecture systems, so if you plan to use Siveillance Video Federated Architecture, you must add users as Windows users through the Active Directory service. If you do not install Active Directory, follow the steps in Installation for workgroups on page 76 when you install. Installation method As part of the installation wizard, you must decide which installation method to use.
Single Computer installation Typical system components in a system: 1. Active Directory 2. Devices 3. SQL server 4. Event server 5. Log server 6. Siveillance Video Client 7. Management Client 8. Management server 9. Recording server 10.
11. Siveillance Video Mobile server 12. Siveillance Video Web Client 13. Siveillance Video Mobile client 14. Siveillance Video Client with Siveillance Video Monitoring Wall Custom installation - example of distributed system components Decide on a SQL Server edition Microsoft® SQL Server® Express is a free edition of SQL Server and is easy to install and prepare for use compared to the other SQL Server editions.
Select service account As part of the installation, you are asked to specify an account to run the Siemens services on this computer. The services always run on this account no matter which user is logged in. Make sure that the account has all necessary user rights, for example, the proper rights to perform tasks, proper network and file access, and access to network shared folders. You can select either a predefined account, or a user account.
service, the web service sends the server certificate including the public key to the client. The service client can validate the server certificate using the already installed public CA certificate. The client and the server can now use the public and private server certificate to exchange a secret key and thereby establish a secure SSL/TLS connection. For more information about TLS: https://en.wikipedia.org/wiki/Transport_Layer_Security Certificates have an expiry date.
A CA certificate acts as a trusted third party, trusted by both the subject/owner (management server) and by the party that verifies the certificate (recording servers) The CA certificate must be trusted on all recording servers.
Recording server data encryption (explained) Encryption to clients and servers that retrieve data from the recording server When you enable encryption on a recording server, communication to all clients, servers, and integrations that retrieve data streams from the recording server are encrypted.
A CA certificate acts as a trusted third-party, trusted by both the Subject/owner (recording server) and by the party that verify the certificate (clients) The public CA certificate must be trusted on all client computers.
Encryption from the management server You can encrypt the two-way connection between the management server and the recording server. When you enable encryption on the management server, it applies to connections from all the recording servers that connect to the management server. Therefore, you need to enable encryption on all the recording servers. Before you enable encryption, you must install security certificates on the management server and all recording servers.
Requirements for the private recording server certificate: • Issued to the recording server so that the recording server's host name is included in the certificate, either as subject (owner) or in the list of DNS names that the certificate is issued to • Trusted on the management server, by trusting the CA certificate that was used to issue the recording server certificate • The service account that runs the recording server must have access to the private key of the certificate on the recording server
The CA certificate must be trusted on all clients.
Service Port number Recording Server - Data Collector 7609 Failover Server 8990 Event Server 22331 The number of services you need to register in the active directory depends on your current installation. Data Collector is installed automatically when installing the Management Server, Recording Server, Event Server or Failover Server service. You must register two SPNs for the user running the service: one with the host name and one with the fully qualified domain name.
When you need to perform virus scanning, do not scan Recording Server folders that contain recording databases (by default C:\mediadatabase\, as well as all subfolders). Also, avoid performing virus scanning on archive storage directories. Create the following additional exclusions: • File types: .blk, .idx, .pic • Folders and subfolders: • • C:\Program Files\Siemens or C:\Program Files (x86)\Siemens • C:\ProgramData\Siemens\MIPSDK • C:\ProgramData\Siemens\Siveillance VMS Mobile Server\Logs • C:
Register Software License Code Before you install, you must have the name and location of the software license file that you received from Siemens. Siemens recommends that you register your SLC before you start to work on the system. If the license is not activated before expiry of grace period, there is a chance to lose video from the connected cameras. There are two methods to activate the SLC. • Offline: Send the lrq file to Siveillance.support.industry@siemens.com for activating the lrq file.
• OS installation media including the required .NET version (https://www.siemens.com/siveillance-vms/) Install the system This section describes how to install your Siveillance Video system. Depending on your product and the installation option below that you choose, the flow of the installation wizard is slightly different. To learn more about consideration before you start the installation, see Before you start installation on page 48.
3. 4. When done, the Siemens Siveillance Video installation wizard appears, 1. Select the Language to use during the installation (this is not the language that your system uses once installed; this is selected later). Click Continue. 2. Read the Siemens End-user License Agreement. Select the I accept the terms in the license agreement check box and click Continue. 3. In the Enter or browse to the location of the license file, enter your license file from your Siveillance Video provider.
You can also enable encryption after installation from the Recording Server Manager tray icon in the notification area. 7. 8. On the Specify recording server settings page, specify the different recording server settings: 1. In the Recording server name field, enter the name of the recording server. The default is the name of the computer. 2. The Management server address field shows the address and port number of the management server: localhost:80. 3.
Click Continue to add hardware and users to the system. If you click Close now, you bypass the configuration wizard and Siveillance Video Management Client opens. You can configure the system, for example add hardware and users to the system, in Management Client. 12. On the Enter user names and passwords for hardware page, enter the user names and passwords for hardware that you have changed from the manufacturer defaults.
selected in the component list. Depending on your selections, you can install the not selected components afterward on other computers. Installation on other computers is done through the management server's download web page named Download Manager. For more information about installation through the Download Manager, see Install system components through Download Manager on page 70. 1. Download the software from the internet (https://www.siemens.
8. On the Select service account page, select either This predefined account or This account to select the service account for all system components except for the recording server. If needed, enter a password. Click Continue. 9. On the Select service account for recording server, select either This predefined account or This account to select the service account for the recording server. If needed, enter a password. Click Continue. 10.
13. 3. In the Select your media database location field, select the location where you want to save your video recording. Siemens recommends that you save your video recordings in a separate location from where you install the software and not on the system drive. The default location is the drive with the most space available. 4. In Retention time for video recordings field, define for how long you want to save the video recordings.
• Select a SQL Server on your network through search: Enables you to search for all SQL Servers that are discoverable on your network subnet • Select a SQL Server on your network: Enables you to enter the address (host name or IP address) of a SQL Server that you might not be able to find through search SQL database options: • Create new database: Mainly for new installations • Use existing database: Mainly for upgrades of existing installations.
The recording server is already installed if you made a Single Computer installation, but you can use the same instructions to add more recording servers if you need more capacity. If you need to install a failover recording server, see Install a failover recording server on page 75. 1. From the computer where Management Server is installed, go to the Management Server's download web page.
10. On the Specify recording server encryption page, you can secure communication by encrypting the connections to and from server and client components that retrieve data streams from the recording server. You can use the same certificate file for all system components or use different certificate files depending on the system components.
SiemensSiveillanceVMSRecordingServerInstaller_x64.exe --quiet -parameters=SERVERHOSTNAME:DKWS-OKR-02> Silent installation uses the existing encryption settings on the recording server. See Install a recording server silently - Command line parameters on page 73 for all the parameters that you may use on the command line.
In the specified location you will find .xml file with the parameters. So, you would need to change parameters in this file and run your installation with the newly modified file. • To change location of the installation: INSTALLDIR - path where Recording Server should be installed to TARGETDIR – should be the same as INSTALLDIR INSTALLLOCATION – should be the same as INSTALLDIR • To change location of recordings: MEDIADBPATH – path to the Media database with all recordings E.g.
• Run SiemensSiveillanceVMSRecordingServerInstaller_x64.exe --generateargsfile=C:\temp and then open the Arguments.xml in the specified folder. How do I see the parameters that were used during a Custom installation? • Browse to and open the C:\ProgramData\Siemens\Installer\Siemens Siveillance VMS Recording Server (64_bit)I.log file and then search for Command line. How do I see a full list of possible parameters? • Run SiemensSiveillanceVMSRecordingServerInstaller_x64.exe --help.
3. Open an internet browser, enter the address of the Management Server's download web page into the address field and download the recording server installer. Save the installer or run it directly from the web page. 4. Download the recording server installer by selecting All Languages below the Recording Server Installer. Save the installer or run it directly from the web page. 5. Select the Language you want to use during the installation. Click Continue. 6.
5. Repeat steps 1-4 to install any other systems you want to connect. They must all be installed using a common administrator account. You cannot use this approach when you upgrade workgroup installations. See instead Upgrade in a workgroup setup on page 533. Install in a cluster Before you install in a cluster, see Multiple management servers (clustering) (explained) on page 46 and Requirements for clustering on page 46. Descriptions and illustrations might differ from what you see on your screen.
5. In the Add/Remove Registered Services window, click Close. Exit the Management Client. 6. Stop the Management Server service and the IIS. Read about how to stop the IIS on the Microsoft website (https://technet.microsoft.com/library/cc732317(WS.10).aspx/). 7. Repeat these steps for all subsequent servers in the cluster, this time pointing to the existing SQL database. However, for the last server in the cluster on which you install the management server, do not stop the Management Server service.
• In C:\ProgramData\Siemens\Siveillance VMS Management Server\ServerConfig.xml: http://ClusterRoleAddress/IDP • In C:\Program Files\Siemens\Siveillance VMS Management Server\IIS\IDP\appsettings.json: "Authority": "http://ClusterRoleAddress/IDP" On the Recording Servers, verify that the authorizationserveraddress is also set to the cluster role address: In C:\ProgramData\Siemens\Siveillance VMS Recording Server\RecorderConfig.
• Run with customized default parameters using an xml argument file as input: To customize the default installation settings, provide an xml file with modified values as input. To generate the xml file with default values, open a command prompt in the directory where the installation program is located and perform the following command: Siemens Siveillance VMS Client 2019 R3 Installer.exe --generateargsfile=[path] Open the generated Arguments.
The web page can display two sets of content, both in a language version that by default matches the language of the system installation: • One web page is targeted at administrators, enabling them to download and install key system components. Most often the web page is automatically loaded at the end of the management server installation and the default content is displayed.
[management server address] is the IP address or host name of the management server, and [port] is the port number which you have configured IIS to use on the management server. • One web page is targeted at end users, providing them access to client applications with default configuration. On the management server, you can access the web page from Windows' Start menu, select Programs > Siemens > Public Installation Page.
• The first level: Refers to your Siveillance Video product • The second level: Refers to the two targeted versions of the web page. Default refers to the web page version viewed by end users.
• The third level: Refers to the languages in which the web page is available • The fourth level: Refers to the components which are - or can be made - available to users • The fifth level: Refers to particular versions of each component, which are - or can be made available to users • The sixth level: Refers to the language versions of the components which are - or can be made - available to users The fact that only standard components are initially available - and only in the same language version
1. On the computer where you downloaded the component(s), go to Windows' Start, enter a Command Prompt 2. In the Command Prompt, execute the name of the file (.exe) with:[space]--ss_registration Example: SiemensSiveillanceVMSRecordingServerInstaller_x64.exe --ss_registration The file is now added to the Download Manager, but not installed on the current computer.
• 2. In the Remove Features window, select the feature(s) you want to remove. 3. Click OK and Yes. Remove installation files for non-required features from the management server. This can help save disk space on the server if you know that your organization is not going to use certain features Device pack installer - must be downloaded The device pack (containing device drivers) included in your original installation is not included on the Download Manager.
Navigating the Management Client This section provides an introduction to the Management Client user interface. Login overview When you launch the Management Client, you must first enter your login information to connect to a system. With Siveillance VMS Video Pro 2016 or Siveillance VMS Video Advanced 2016 or newer installed, you can log into systems that run older versions of the product after installing a patch.
• When you work with recording servers and devices: • When you work with rules, time and notification profiles, users, roles: Siveillance Video 2019 R3 88 SI SSP SH LPS COS Video
• When you view logs: Panes overview The illustration outlines a typical window layout. You can customize the layout so it may look different on your computer. 1. Site Navigation pane and Federated Site Hierarchy pane 2. Overview pane 3.
4. Preview pane Site Navigation pane: This is your main navigation element in the Management Client. It reflects the name, settings and configurations of the site that you have logged into. The site name is visible at the top of the pane. The features are grouped into categories that reflect the functionality of the software. Federated Site Hierarchy pane: This is your navigation element that displays all Siveillance Video Federated Architecture sites in a parent/child site hierarchy.
Menu overview Example only - some menus change depending on context. File menu You can save changes to the configuration and exit the application. You can also back up your configuration, see Backing up and restoring your system configuration (explained) on page 503. Edit menu You can undo changes. View menu Name Description Reset Application Layout Reset the layout of the different panes in the Management Client to their default settings.
Action menu The content of the Action menu differs depending on the element you have selected in the Site Navigation pane. The actions you can choose from are the same as when you right-click the element. The elements are described in Configuring the system in the Site Navigation pane on page 109. The pre-buffer period for each camera, see Manage pre-buffering on page 201 Name Refresh Description Is always available and reloads the requested information from the management server.
The Options dialog box features the following tabs: • General tab (see General tab (options) on page 94) • Server Logs tab (see Server Logs tab (options) on page 96) • Mail Server tab (see Mail Server tab (options) on page 97) • AVI Generation tab (see AVI Generation tab (options) on page 98) • Network tab (see Network tab (options) on page 99) • Bookmark tab (see Bookmark tab (options) on page 99) • User Settings tab (see User Settings tab (options) on page 100) • Evidence Lock tab (see Evid
• Analytics Events tab (see Analytics Events tab (options) on page 102) • Alarms and Events tab (see Alarms and Events tab (options) on page 103) • Generic Events tab (see Generic Events tab (options) on page 105) General tab (options) On the General tab, you can specify general settings for the Management Client and the recording server. Management Client Name Description Select frame rate for the thumbnail camera images displayed in the Preview pane. Default is 1 frame per second.
Name Description Generation of motion data for smart search requires that motion detection is enabled for the camera. When adding new camera devices automatically enable: Generate motion data for smart search Select the check box to enable generation of smart search motion data on new cameras, when you add them to the system with the Add Hardware wizard. This setting does not affect motion detection settings on existing cameras.
Name Timeout for pause patrolling sessions Description Client users with a sufficient PTZ priority can pause patrolling on PTZ cameras. Select how much time should pass before regular patrolling is resumed after a pause. The setting applies for all PTZ cameras on your system. Default setting is 10 minutes. If you want individual timeouts on the cameras, you specify this on the Presets tab for the camera. Timeout for reserved PTZ sessions Set the default timeout period for reserved PTZ sessions.
Name Description Disable or enable the logs and specify the retention period. Allow 2018 R2 and earlier components to write logs.
Name Description The TCP port used for connecting to the mail server. Default port is 25 for unencrypted connections, Encrypted connections typically use port 465 or 587. Mail server port If you want to secure the communication between the management server and the SMTP mail server, select this check box. Encrypt the connection to the server The connection is secured using the STARTTLS email protocol command.
Name Description (Not available for all codecs). If you want to use keyframes, select the check box and specify the required number of frames between keyframes. Keyframe every A keyframe is a single frame stored at specified intervals. The keyframe contains the entire view of the camera, whereas the following frames contain only the pixels that change. This helps greatly reduce the size of files. If the check box is not available, or not selected, every frame contains the entire view of the camera.
Name Description Specify a prefix for all the bookmarks that is made by the users of Siveillance Video Client. Bookmark ID prefix Specify the default start and end time of a bookmark is set in Siveillance Video Client.
Name Description The duration the client users can select to lock evidence. Lock time options Available time options are hour(s), day(s), week(s), month(s), year(s), indefinite or user-defined. To specify the evidence lock access rights of a role, see the Device tab (see Device tab (roles) on page 352) for role settings. Audio messages tab (options) On the Audio messages tab, you can upload files with audio messages that are used for broadcasting messages, triggered by rules.
Name Play Description Click this button to listen to the audio message from the computer that runs the Management Client. To create a rule that triggers playback of audio messages, see Add a rule on page 299. To learn more about actions in general that you can use in rules, see Actions and stop actions (explained) on page 269. Access Control Settings tab (options) The use of Siveillance Video Access requires that you have purchased a base license that allows you to access this feature.
Name Description Specify a list of trusted IP addresses/hostnames. The list filters incoming data so that only events from certain IP addresses/hostnames are allowed. You can use both Domain Name System (DNS), IPv4 and IPv6 address formats. Address list You can add addresses to your list by manually entering each IP address or host name, or by importing an external list of addresses. • Manual entering: Enter the IP address/hostname in the address list.
Name Description Specify the number of days for storing alarms with the state New, In progress, or On hold. If you set the value to 0, the alarm appears in the system, but will not be stored. Keep all other alarms for Alarms always have timestamps. If the alarm is triggered by a camera, the timestamp has an image from the time of the alarm.
Generic Events tab (options) On the Generic Events tab, you can specify generic events and data source related settings. For more information about how to configure actual generic events, see Generic events (explained) on page 316. Name Description You can choose between two default data sources and define a custom data source.
Name Description Protocols which the system should listen for, and analyze, in order to detect generic events: Any: TCP as well as UDP. Protocol type selector TCP: TCP only. UDP: UDP only. TCP and UDP packages used for generic events may contain special characters, such as @, #, +, ~, and more. IP type selector Selectable IP address types: IPv4, IPv6 or both. Separator bytes Select the separator bytes used to separate individual generic event records.
Name Allowed external IPv6 addresses Description Specify the IP addresses, that the management server must be able to communicate with in order to manage external events. You can also use this to exclude IP addresses that you do not want data from. Initial configuration tasks list The checklist below lists the initial tasks for configuring your system. Some of them, you may already have completed during installation.
Step Description Verify that each recording server's archiving settings meet your needs. See Archive Settings properties on page 145. Detect the hardware, cameras or video encoders to add to each recording server. See Add hardware on page 167. Configure each recording server's individual cameras. See Camera devices (explained) on page 182. Enable storage and archiving for individual cameras or for a group of cameras. This is done from the individual cameras or from the device group.
Step Description Add users or groups of users to each of the roles. See Assign/remove users and groups to/from roles on page 326. Activate licenses. See Activate licenses online on page 113 or Activate licenses offline on page 113. Configuring the system in the Site Navigation pane In the Site Navigation pane, you can configure and manage your system so it matches your needs.
• Products and versions • The products' software license code (SLC) • The expiration date of your SLC. Typically, unlimited • The expiration date of your Software Upgrade Plan subscription License Overview - All sites Lists the number of activated hardware device licenses or other licenses in your software license file and the total number of available licenses on your system. Here you can easily see if you can still grow your system without purchasing additional licenses.
Hardware devices without licenses are identified by an exclamation mark in the Management Client. The exclamation mark is also used for other purposes. Place your mouse over the exclamation mark to see the purpose. Features for activating licenses Below the three tables are: • A check box for enabling automatic license activation and a link to edit the user credentials for automatic activation.
Automatic license activation (explained) For easy maintenance and flexibility, Siemens recommends that you enable automatic license activation (see Enable automatic license activation on page 112) because it means less maintenance for you. Automatic license activation requires the management server to be online.
Disable automatic license activation and delete password: 1. On the License Information page, click Edit activation credentials. 2. Click Delete password. 3. Confirm that you want to delete the user name and password from the management server. Activate licenses online Activate your licenses online if the computer that runs the management server has Internet access. 1. On the License Information node, select Activate License Manually and then Online. 2. The Activate Online dialog box opens: 3.
Activate licenses after grace period If you do not activate a license within the grace period (hardware device, Siveillance Video Interconnect camera, or door licenses), the device becomes unavailable and cannot be used in the surveillance system: • Configuration of the camera and other settings are not removed from the Management Client • The license is not removed from the system configuration • To enable the unavailable devices again, activate the licenses as usual.
If you have enabled automatic license activation (see Enable automatic license activation on page 112), the new hardware device is automatically activated. If you have used all your device changes without activation (see Device changes without activation (explained) on page 111), you must manually activate your licenses. For more information about activating licenses, see Activate licenses offline on page 113 or Activate licenses online on page 113.
Servers and hardware This section describes how to install and configure recording servers and failover recording servers. You also learn how to add new hardware to the system and interconnect other sites. Recording servers Recording servers (explained) The system uses recording servers for recording of video feeds, and for communicating with cameras and other devices. A surveillance system typically consists of several recording servers.
• Add hardware on page 167 • Move hardware on page 511 • Delete all hardware on a recording server on page 528 • Remove a recording server on page 528 When the Recording Server service is running, it is very important that Windows Explorer or other programs do not access Media Database files or folders associated with your system setup. If they do, it is likely that the recording server cannot rename or move relevant media files. This might bring the recording server to a halt.
• Management Server (for System Monitor and for images and AVI video clips in email notifications) • Siveillance Video Mobile Server • Siveillance Video Event Server • DLNA Server • ONVIF Bridge • Sites that retrieve data streams from the recording server through Siveillance Video Interconnect • Some third-party MIP SDK integrations If you enable encryption, and the selected server authentication certificate is not trusted on all computers running clients and services that retrieve data stream
A CA issues digital certificates. A CA acts as a trusted third-party, trusted by both the subject/owner (recording server) and by the party that verify the certificate (clients). The recording server has the private key and the clients have the public key. The public CA certificate must be trusted on all client computers. In this way the clients verify the validity of the certificates issued by the CA. The private CA certificate issues private server authentication certificates to the recording servers.
Register a recording server When you install a recording server, it is automatically registered in most cases. But you need to do the registration manually if: • The recording server was installed offline and then added to the management server afterward • Your management server does not use the default ports. Port 80 is the default port in a system with no encryption between the recording server and the management server.
3. Enter the address of the management server that you want the recording server to connect to and click OK. 4. Enter the user name and password of a system administrator of Siveillance Video and click OK. 5. A confirmation window pops up and the recording server is registered. Right-click the Recording Server Manager tray icon in the notification area and start the Recording Server service.
1. On the computer that runs the recording server, right-click the Recording Server icon in the notification area. 2. Select Stop Recording Server service. 3. Right-click the Recording Server icon again and select Change Settings. The Recording Server Settings window appears. 4.
• Encrypt connections from clients and servers that retrieve data streams from the recording server: Before you enable encryption, read the requirements listed in this topic • Select a certificate: Contains a list of unique subject names of certificates installed on the local computer in the Windows Certificate Store that has a private key. The recording server service user has been given access to the private key. It is required that this certificate is trusted on all clients.
To verify if the recording server uses encryption, see View encryption status to clients on page 124. View encryption status to clients To verify if your recording server encrypt connections: 1. Open the Management Client. 2. In the Site Navigation pane, select Servers > Recording Servers. This opens a list of recording servers. 3. In the Overview pane, select the relevant recording server and go to the Info tab.
Enable encryption to the management server You can encrypt the two-way connection between the management server and the recording server. If your system contains multiple recording servers, you must enable encryption on all the recording servers. For more information, see Secure communication (explained) on page 52.
To complete the enabling of encryption, next step is to update the encryption settings on each recording server. For more information, see Enable encryption from the management server on page 126. Enable encryption from the management server You can encrypt the two-way connection between the management server and the recording server. If your system contains multiple recording servers, you must enable encryption on all the recording servers.
• Encrypt connections from the management server to the recording server: Before you enable encryption, read the requirements listed in this topic • You can select the Use one configuration for all server option, if you use the same certificate on all the servers. • Select a certificate: Contains a list of unique subject names of certificates installed on the local computer in the Windows Certificate Store that has a private key.
Stopping the Recording Server service means that you cannot record and view live video while you are verifying or changing the recording server's basic configuration. Recording server status icons Management Client uses the following icons to indicate the state of individual recording servers: Icon Description Recording server is running Recording server requires attention: Either the recording server is not running or it is running with errors. 1.
Info tab properties (recording server) Name Description You can choose to enter a name for the recording server. The name is used in the system and clients when the recording server is listed. The name does not have to be unique. Name When you rename a recording server, the name is changed globally in the Management Client. Description You can choose to enter a description that appears in a number of listings within the system. A description is not mandatory.
Name Description Displays the local address of the recording server's web server. You use the local address, for example, for handling PTZ camera control commands, and for handling browsing and live requests from Siveillance Video Client. Local web server address The address includes the port number that is used for web server communication (typically port 7563).
Storage and archiving (explained) Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information. When a camera records video or audio, all specified recordings are by default stored in the storage defined for the device. Each storage consists of a recording storage that saves recordings in the recording database Recording. A storage has no default archive(s), but you can create these.
Archiving is the automatic transfer of recordings from, for example, a camera's recording database to another location. In this way, the amount of recordings that you can store is not limited to the size of the recording database. With archiving you can also back up your recordings to another media. You configure storage and archiving on each recording server. As long as you store archived recordings locally or on accessible network drives, you can use Siveillance Video Client to view them.
By setting up your archiving in an effective way, you can optimize storage needs. Often, you want to make archived recordings take up as little space as possible especially on a long-term basis, where it is perhaps even possible to slacken image quality a bit.
archive includes all retention stated earlier in the process. Archiving must also always take place more frequently than the retention period, otherwise you risk losing data. If you have a retention time of 24 hours, any data older than 24 hours is deleted. Therefore, to get your data safely moved to the next archive, it is important to run archiving more often than every 24 hours.
Add a new storage When you add a new storage, you always create one recording storage with a predefined recording database named Recording. You cannot rename the database. Apart from the recording storage, a storage can contain a number of archives. 1. To add an extra storage to a selected recording server, click the button located below the Storage configuration list. This opens the Storage and Recording Settings dialog box.
2. Specify the relevant settings (see Storage and Recording Settings properties on page 144). 3. Click OK. If needed, you are now ready to create archive(s) within your new storage. See Create an archive within a storage on page 136. Create an archive within a storage A storage has no default archive, but you can create archives as needed. 1. Select the relevant storage in the Recording and archiving configuration list. 2. Click the 3.
If you change the maximum size of a database, the system auto-archives recordings that exceed the new limit. It auto-archives the recordings to the next archive or deletes them depending on archiving settings. Enable digital signing for export Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information.
5. In the Recording and archiving configuration section, double-click the horizontal bar that represents the recording database. The Storage and Recording Settings window appears. 6. Select the Signing check box. 7. Click OK. For information about securing your exported recordings, see Encrypt your recordings on page 138. Encrypt your recordings Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information.
Enabling or changing encryption settings or password can potentially be time consuming, depending on the size of the database and performance of the drive. You can follow the progress under Current Tasks. Do not stop the recording server while this task is ongoing. 1. Click the Edit Recording Storage button below the Recording and archiving configuration list. 2. In the dialog box that appears, specify encryption level.
3. You are automatically directed to Set Password dialog box. Enter password and click OK. Back up archived recordings Many organizations want to back up their recordings by using tape drives or similar. Exactly how you do this is highly individual and depends on the backup media used in your organization. However, the following is worth bearing in mind: Back up archives rather than camera databases Always create backups based on the content of archives, not based on individual camera databases.
During all regular use of your system, the sub-directory structure is completely transparent to the system's users when they browse recordings with Siveillance Video Client. This is true both with archived and non-archived recordings. It is relevant to know the sub-directory structure (see Archive structure (explained) on page 141 if you want to back up your archived recordings (see Backing up and restoring system configuration on page 503).
...F:\OurArchive\Archive1\Camera 1 on Axis Q7404 Video Encoder(10.100.50.137) - 2011-1005T11:23:47+02:00\ Sub-directories: Even further sub-directories are automatically added. The amount and nature of these sub-directories depend on the nature of the actual recordings. For example, several different sub-directories are added if the recordings are technically divided into sequences. This is often the case if you have used motion detection to trigger recordings.
It is only possible to delete the last archive in the list. The archive does not have to be empty. 2. Click the button located below the Recording and archiving configuration list. 3. Click Yes. 4. If the archive is unavailable, for example, offline, you need to restore the connection before you can delete the archive. Delete a storage You cannot delete the default storage or storages that devices use as the recording storage for live recordings.
Storage and Recording Settings properties Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information. In the Storage and Recording Settings dialog box, specify the following: Name Name Description Rename the storage if needed. Names must be unique. Specify the path to the directory to which you save recordings in this storage. The storage does not necessarily have to be located on the recording server computer.
Name Signing Description Enables a digital signature to the recordings. This means, for example, that the system confirms that exported video has not been modified or tampered with when played back. The system uses the SHA-2 algorithm for digital signing. Select the encryption level of the recordings: Encryption • None • Light (less CPU usage) • Strong (more CPU usage) The system uses the AES-256 algorithm for encryption. If you select Light, a part of the recording is encrypted.
Name Description Specify the path to the directory to which you save recordings in this storage. The storage does not necessarily have to be located on the recording server computer. Path If the directory does not exist, you can create it. Network drives must be specified by using UNC (Universal Naming Convention) format, example: \\server\volume\directory\. Specify for how long recordings should stay in the archive before they are deleted or moved to the next archive (depending on archive settings).
Name Description To reduce FPS when archiving, select the Reduce frame rate check box and set a frame per second (FPS). Reduce frame rate Reduction of frame rates by a selected number of FPS makes your recordings take up less space in the archive, but it also reduces the quality of your archive. MPEG-4/H.264/H.265 reduces automatically to key-frames as a minimum. 0.1 = 1 frame per 10 seconds. Failover tab (recording server) Available functionality depends on the system you are using.
For details on failover recording servers, installation and settings, failover groups and their settings, see Failover recording servers (explained) on page 155. Assign failover recording servers On the Failover tab of a recording server, you can choose between three types of failover setups: • No failover setup • A primary/secondary failover setup (cold standby) • A hot standby setup If you select b and c, you must select the specific server/groups.
primary failover group are busy. In this way, you only risk not having a failover solution in the rare case when all failover recording servers in the primary, as well as in the secondary, failover group are busy. 1. In the Site Navigation pane, select Servers > Recording Servers. This opens a list of recording servers. 2. In the Overview pane, select the wanted recording server, go to the Failover tab. 3.
Name Description Opens the Advanced Failover Settings window: Advanced failover settings Failover service communication port (TCP) • Full Support: Enables full failover support for the device • Live Only: Enables only failover support for live streams on the device • Disabled: Disables failover support for the device By default, the port number is 11000. You use this port for communication between recording servers and failover recording servers.
Multicasting (explained) In regular network communication, each data packet is sent from a single sender to a single recipient a process known as unicasting. But with multicasting you can send a single data packet (from a server) to multiple recipients (clients) within a group. Multicasting can help save bandwidth.
Multicast streams are not encrypted, even if the recording server uses encryption. Multicasting should not be confused with broadcasting, which sends data to everyone connected to the network, even if the data is perhaps not relevant for everyone: Name Description Unicasting Sends data from a single source to a single recipient. Multicasting Sends data from a single source to multiple recipients within a clearly defined group. Broadcasting Sends data from a single source to everyone on a network.
Name Description IP address In the Start field, specify the first IP address in the required range. Then specify the last IP address in the range in the End field. Port In the Start field, specify the first port number in the required range. Then specify the last port number in the range in the End field.
2. On the Client tab, select the Live multicast check box. Repeat for all relevant cameras. Multicast streams are not encrypted, even if the recording server uses encryption. Network tab (recording server) You define a recording server's public IP address on the Network tab. Why use a public address? When an access client, such as Siveillance Video Client, connects to a surveillance system, an amount of initial data communication, including the exchange of contact addresses, is shared in the background.
Assign local IP ranges You define a list of local IP ranges which the surveillance system should recognize as coming from a local network: • On the Network tab, click Configure Failover servers Failover recording servers (explained) Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information. A failover recording server is an extra recording server which takes over from the standard recording server if this becomes unavailable.
Grouping has a clear benefit: when you later specify which failover recording servers should take over from a recording server, you select a group of failover recording servers. If the selected group contains more than one failover recording server, this offers you the security of having more than one failover recording server ready to take over if a recording server becomes unavailable.
Description Involved servers (numbers in red): 1. Recording Server 2. Failover Recording Server 3. Management Server Failover steps for Cold standby setups: 1. To check whether it is running or not, a failover recording server has a non-stop TCP connection to a recording server. 2. This connection is interrupted. 3. The failover recording server requests the current configuration of the recording server from the management server.
• A cold standby failover recording server takes over for the recording server that has become unavailable after five seconds plus the time it takes for the failover recording server's Recording Server service to start and the time it takes to connect to the cameras. In contrast, a hot standby failover recording server takes over faster because the Recording Server service is already running with the correct configuration and only has to start its cameras to deliver feeds.
Set up and enable failover recording servers If you have disabled the failover recording server, you must enable it before it can take over from the standard recording servers. Do the following to enable a failover recording server and edit its basic properties: 1. In the Site Navigation pane, select Servers > Failover Servers. This opens a list of installed failover recording servers and failover groups. 2. In the Overview pane, select the required failover recording server. 3.
Read failover recording server status icons The following icons represent the status of failover recording servers (icons are visible in the Overview pane): Icon Description The failover recording server is either waiting or "watching". When waiting, the failover recording server is not configured to take over from any recording server yet. When "watching", the failover recording server is configured to watch one or more recording servers.
For more information about multicasting, see Multicasting (explained) on page 151 or Multicast tab (recording server) on page 150. Info tab properties (failover server) Specify the following failover recording server properties: Name Description Name The name of the failover recording server as it appears in the Management Client, logs and more. Description An optional field that you can use to describe the failover recording server, for example which recording server it takes over from.
Name Description Displays the local address of the failover recording server's web server. You use the local address, for example, for handling PTZ camera control commands, and for handling browsing and live requests from Siveillance Video Client. The address includes the port number that is used for web server communication (typically port 7563).
Name Description Enable this failover server Clear to disable the failover recording server (selected by default). You must disable failover recording servers before they can take over from recording servers. Info tab properties (failover group) Field Description Name The name of the failover group as it appears in the Management Client, logs and more. Description An optional description, for example the server's physical location.
1. On the failover recording server, stop the Failover Recording Server service. 2. Right-click the notification area's Failover Recording Server service icon again. 3. Select Change Settings. The Failover Recording Server Settings window appears, so you can specify the IP address or host name of the management server with which the failover recording server should communicate.
View status messages 1. On the failover recording server, right-click the Siemens Siveillance Video Failover Recording Server service icon. 2. Select Show Status Messages. The Failover Server Status Messages window appears, listing time-stamped status messages. View version information Knowing the exact version of your Failover Recording Server service is an advantage if you need to contact product support.
1. On the failover recording server, right-click the Siemens Siveillance Video Failover Recording Server service icon. 2. Select About. 3. A small dialog box opens that shows the exact version of your Failover Recording Server service.
Hardware Hardware (explained) Hardware represents either: • The physical unit that connects directly to the recording server of the surveillance system via IP, for example a camera, a video encoder, an I/O module • A recording server on a remote site in a Siveillance Video Interconnect setup For more information about how to add hardware to your system, see Add hardware on page 167. Add hardware You have several options for adding hardware to each recording server in your system.
Name Description The system scans automatically for new hardware on the recording server's local network. Select the Show hardware running on other recording servers check box to see if detected hardware is running on other recording servers. Express (Recommended) You can select this option every time you add new hardware to your network and want to use it in your system. You cannot use this option to add remote systems in Siveillance Video Interconnect setups.
Disable/enable hardware Added hardware is by default enabled. You can see if hardware is enabled or disabled in this way: Enabled Disabled To disable added hardware, for example, for licensing or performance purposes: 1. Expand the recording server, right-click the hardware you want to disable. 2. Select Enabled to clear or select it. Edit hardware You can edit basic settings, such as IP address/host name, for added hardware: 1. Expand the recording server, right-click the hardware you want to edit.
2. Select Enabled to clear or select it. Set up a secure connection to the hardware You can set up a secure HTTPS connection using SSL (Secure Sockets Layer) between the hardware and the recording server. Consult your camera vendor to get a certificate for your hardware and upload it to the hardware, before you continue with the steps below: 1. In the Overview pane, right-click the recording server and select the hardware. 2. On the Settings tab, enable HTTPS. This is not enabled by default. 3.
4. In the PTZ Protocol column, select which positioning scheme you want to use: • Absolute: When operators use PTZ controls for the camera, the camera is adjusted relative to a fixed position, often referred to as the camera's home position • Relative: When operators use PTZ controls for the camera, the camera is adjusted relative to its current position The content of the PTZ protocol column varies a lot depending on the hardware. Some have 5 to 8 different protocols.
Name Description Enter a description of the hardware (optional). The description appears in a number of listings within the system. For example, when moving the mouse pointer over the hardware name in the Overview pane: Description Model Identifies the hardware model. Serial number Hardware serial number as specified by the manufacturer. The serial number is often, but not always, identical to the MAC address. Driver Identifies the driver that handles the connection to the hardware.
PTZ tab (video encoders) On the PTZ tab, you can enable PTZ (pan-tilt-zoom) for video encoders. The tab is available if the selected device is a video encoder or if the driver supports both non-PTZ and PTZ cameras. You must enable the use of PTZ separately for each of the video encoder's channels on the PTZ tab before you can use the PTZ features of the PTZ cameras attached to the video encoder. Not all video encoders support the use of PTZ cameras.
Name Description Enter a password for the hardware. Password As a system administrator, you need to give other users permission to view the password in the Management Client. For more information, see Overall Security tab (roles) on page 330 under Hardware. The password that you enter here does not change the user name on the actual hardware device. For information about how to change passwords on hardware devices, see Change passwords on hardware devices on page 175.
information. From within the wizard, you can create a report of successful and failed password changes, but the results are also logged under Server logs. For hardware devices with ONVIF drivers and multiple user accounts, only an administrator of Siveillance Video with administrative rights of the hardware device can change passwords from the Video. For information about how to change passwords in one operation, see Change passwords on hardware devices on page 175.
9. Due to security restrictions, some hardware devices might become unavailable for a certain period if you fail to change password several times in a row. Security restrictions vary for different manufacturers. Manage remote servers Info tab (remote server) Name Description The system uses the name whenever the remote server is listed in the system and clients. The name does not have to be unique. Name When you rename a server, the name is changed globally in the Management Client.
Name Description Opens a remote connection to the remote site (if Windows credentials are approved). Connect Settings tab (remote server) On the Settings tab, you can view the name of the remote system. Events tab (remote server) You can add events from the remote system to your central site in order to create rules and thereby respond immediately to events from the remote system. The number of events depend on the events configured in the remote system. You cannot delete default events.
Name Description Determines that retrieval of recordings from a remote site are limited to a specific time interval. Unfinished jobs at the end time continue until completion, so if the end time is critical, you need to set it earlier to allow for unfinished jobs to complete.
• Outputs See Devices (explained) on page 181. Working with device groups Device groups (explained) Grouping of devices into device groups is part of the Add Hardware wizard, but you can always modify the groups and add more groups if needed.
Add a device group on page 180 Specify which devices to include in a device group on page 180 Specify common properties for all devices in a device group on page 181 Add a device group 1. In the Overview pane, right-click the device type under which you want to create a device group. 2. Select Add Device Group. 3.
5. Click OK. 6. If you exceed the limit of 400 devices in one group, you can add device groups as subgroups under other device groups: Specify common properties for all devices in a device group With device groups, you can specify common properties for all devices within a given device group: 1. In the Overview pane, click the device group. In the Properties pane, all properties which are available on all of the device group's devices are listed and grouped on tabs. 2.
• A physical camera has devices that represent the camera part (lenses) as well as microphones, speakers, metadata, input and output either attached or built-in • A video encoder has multiple analog cameras connected that appear in one list of devices that represent the camera part (lenses) as well as microphones, speakers, metadata, input and output either attached or built-in • An I/O module has devices that represent the input and output channels for, for example, lights • A dedicated audio module
1. Configure camera settings (see Settings tab (devices) on page 193). 2. Configure streams (see Streams tab (devices) on page 195). 3. Configure motion (see Motion tab (devices) on page 206). 4. Configure recording (see Record tab (devices) on page 198). 5. Configure the remaining settings as needed. Microphone devices (explained) On many devices, you can attach external microphones. Some devices have built-in microphones.
• Record tab (see Record tab (devices) on page 198) • Events tab (see Events tab (devices) on page 229) Speaker devices (explained) On many devices you can attach external speakers. Some devices have built-in speakers. Speaker devices are added automatically when you add hardware to the system. They are by default disabled, so you must enable them before use, either as part of the Add Hardware wizard or afterwards. Speakers do not require separate licenses.
Metadata devices (explained) Metadata devices deliver data streams to the system that the client users can use to view data about data, for example, data that describes the video image, the content or objects in the image, or the location of where the image was recorded. Metadata can be attached to cameras, microphones, or speakers.
You can use such events in rules. For example, you could create a rule specifying that a camera should begin recording when an input is activated, and stop recording 30 seconds after the input is deactivated. You can use input devices completely independently of cameras. Before you specify use of external input units on a device, verify that the device itself recognize the sensor operation. Most devices can show this in their configuration interfaces, or via Common Gateway Interface (CGI) script commands.
Output devices (explained) On many devices, you can attach external units to output ports on the device. This allows you to activate/deactivate lights, sirens, etc. through the system. You can use output when creating rules. You can create rules that automatically activate or deactivate outputs, and rules that trigger actions when the state of an output is changed. Output can be triggered manually from the Management Client and Siveillance Video Client.
With the rules feature, you define rules that automatically activate or deactivate output or you can activate them manually from a client. You can activate an output manually from the Management Client to test the functionality: 1. In the Overview pan e, select the relevant output device. 2. Typically, the following elements are shown for each output in the Preview pane: 3. Select/clear the check box to activate/deactivate the selected output.
Camera Micropho ne Speak er Metadat a Input Outpu t Description Device enabled and retrieving data: The device is enabled and you retrieve a live stream. Device recording: The device is recording data on the system. Device temporarily stopped or has no feed: When stopped, no information is transferred to the system. If it is a camera, you cannot view live video. A stopped device can still communicate with the recording server for retrieving events, setting settings etc.
Camera Micropho ne Speak er Metadat a Input Outpu t Description Status unknown: Status of the device is unknown, for example, if the recording server is offline. Some icons can be combined, as in this example where Device enabled and retrieving data is combined with Device recording. Info tab (devices) Info tab (explained) On the Info tab, you can view and edit basic information about a device in a number of fields. All devices have an Info tab.
Info tab properties Name Description The name is used whenever the device is listed in the system and clients. Name When you rename a device, the name is changed globally in the Management Client. Enter a description of the device (optional). Description Siveillance Video 2019 R3 The description appears in a number of listings within the system. For example, when you pause the mouse pointer over the name in the Overview pane.
Name Hardware name Description Displays the name of the hardware, with which the device is connected. The field is non-editable from here, but you can change it by clicking Go To next to it. This takes you to hardware information where you can change the name. Displays the port on which the device is attached on the hardware. Port number For single-device hardware, the port number is typically 1.
Name Description Enter the field of view in degrees. The value you enter determines the field of view of the camera icon on the smart map in Siveillance Video Client. Field of view The default value is 0.0. The field is mainly for smart map and third party integrations. Enter the depth of the camera in meters or feet. The value you enter determines the depth of the camera icon on the smart map in Siveillance Video Client. Depth The default value is 0.0.
Camera settings (explained) You can view or edit settings, such as: • Default frame rate • Resolution • Compression • The maximum number of frames between keyframes • On-screen date/time/text display for a selected camera, or for all cameras within a device group The drivers for the cameras determine the content of the Settings tab. The drivers vary depending on the type of camera.
For cameras that support more than one type of stream, for example MJPEG and MPEG4/H.264/H.265, you can use multi-streaming, see Multi-streaming (explained) on page 196. When you change a setting, you can quickly verify the effect of your change if you have the Preview pane enabled. You cannot use the Preview pane to judge the effect of frame rate changes because the Preview pane's thumbnail images use another frame rate defined in the Options dialog box. If you change the settings for Max.
Multi-streaming (explained) Viewing live video and playing back recorded video do not necessarily require the same video quality and frame rate. You can have either one stream for live viewing and another stream for playback purposes or multiple separate live streams with different resolution, encoding, and frame rate settings. Example 1, live and recorded video: • For viewing live video, your organization may prefer H.
• For viewing live video from a local connected operating point, your organization may prefer H.
Record tab (devices) Record tab (explained) The following devices have a Record tab: • Cameras • Microphones • Speakers • Metadata Recordings from a device are only saved in the database when you have enabled recording and the recording-related rule criteria are met. Parameters that cannot be configured for a device are grayed out.
Siveillance Video 2019 R3 199 SI SSP SH LPS COS Video
Enable/disable recording Recording is by default enabled. To enable/disable recording: 1. In the Site Navigation pane, select Recording Servers. 2. Select the relevant device in the Overview pane. 3. On the Record tab, select or clear the Recording check box. You must enable recording for the device before you can record data from the camera. A rule that specifies the circumstances for a device to record does not work if you have disabled recording for the device.
Devices that support pre-buffering Cameras, microphones and speakers support pre-buffering. For speakers, the streams are only sent when the Siveillance Video Client user uses the Talk to speaker function. This means that depending on how your speaker streams are triggered to be recorded there is little or no pre-buffering available. In most cases, you set up speakers to record when the Siveillance Video Client user uses the Talk to speaker function. In such cases, no speaker pre-buffer is available.
When you create rules that trigger recording, you can select that recordings should start some time before the actual event (pre-buffer). Example: The below rule specifies that recording should start on the camera 5 seconds before motion is detected on the camera. To use the pre-buffer recording function in the rule, you must enable pre-buffering on the device being recorded and you must set the pre-buffer length to at least the same length as specified in the rule.
• Select or enter the recording frame rate (in FPS, frames per second) in the Recording frame rate: (JPEG) box. Enable keyframe recording You can enable keyframe recording for MPEG-4/H.264/H.265 streams. It means that the system switches between recording keyframes only and recording all frames depending on your rule settings. You can, for example, let the system record keyframes when there is no motion in the view and switch to all frames only in case of motion detection to save storage. 1.
Possible statuses for selected database: Name Description Recordings also located on other recording servers The database is active and running and has recordings located in storages on other recording servers as well. Archives also located in old storage The database is active and running and has archives located in other storages as well. Active The database is active and running.
Name Description Information unavailable in failover mode The system cannot collect status information about the database when the database is in failover mode. Further down in the window, you can see the status of each database (OK, Offline or Old Storage), the location of each database and how much space each database uses. If all servers are online, you can see the total spaced used for the entire storage in the Total used space field.
Motion tab (devices) Motion tab (explained) The following devices have a Motion tab: • Cameras On the Motion tab, you can enable and configure motion detection for the selected camera. Motion detection configuration is a key element in your system: Your motion detection configuration determines when the system generates motion events and typically also when video is recorded.
Siveillance Video 2019 R3 207 SI SSP SH LPS COS Video
You can configure all the settings for a group of cameras, but you would typically set the exclude regions per camera. • Enable and disable motion detection on page 208 • Specify motion detection settings on page 208 Enable and disable motion detection You specify the default setting of motion detection for cameras on the Tools > Options > General tab.
If the load is too high, you can add GPU resources to your recording server by installing multiple NVIDIA display adapters. Siemens does not recommend the use of Scalable Link Interface (SLI) configuration of your NVIDIA display adapters. NVIDIA products have different compute capabilities. To verify that your NVIDIA product supports hardware acceleration for the codecs used in your Siemens Siveillance Video system, look up the supported codecs for the compute capability version in the table below.
2. Drag the slider to the left for a higher sensitivity level, and to the right for a lower sensitivity level. The higher the sensitivity level, the less change is allowed in each pixel before it is regarded as motion. The lower the sensitivity level, the more change in each pixel is allowed before it is regarded as motion. Pixels in which motion is detected are highlighted in green in the preview image. 3. Select a slider position in which only detections you consider motion are highlighted.
Select keyframes settings Determines if motion detection is done on keyframes only instead of on the entire video stream. Only applies to MPEG-4/H.264/H.265. Motion detection on keyframes reduces the amount of processing power used to carry out the analysis. Select Keyframes only (MPEG-4/H.264/H.265) box to do motion detection on keyframes only. Select image processing interval You can select how often the system performs the motion detection analysis.
You specify the default setting of generating smart search data for cameras on the Tools > Options > General tab. Specify exclude regions You can exclude motion detection from specific areas of a camera view. Areas with permanent privacy masks, are also excluded from motion detection. Select the Show privacy masks check box to display them.
• PTZ cameras that support preset positions On the Presets tab, you can create or import preset positions, for example: • In rules for making a PTZ (pan-tilt-zoom) camera move to a specific preset position when an event occurs • In patrolling, for the automatic movement of a PTZ camera between a number of preset positions • For manual activation by the Siveillance Video Client users You can lock a preset position if you want to prevent users in Siveillance Video Client or users with limited security
Add a preset position (type 1) on page 215 Use preset positions from the camera (type 2) on page 217 Siveillance Video 2019 R3 214 SI SSP SH LPS COS Video
Assign a default preset position on page 217 Edit a preset position (type 1 only) on page 217 Test a preset position (type 1 only) on page 219 Add a preset position (type 1) To add a preset position for the camera: 1. Click Add New.
2. The Add Preset window displays a live preview image from the camera. Use the navigation buttons and/or sliders to move the camera to the required position. 3. Specify a name for the preset position in the Name field. 4. Optionally, enter a description of the preset position in the Description field. 5. Select Locked if you want to lock the preset position. Only users with sufficient rights can unlock the position afterwards. 6. Click Add to specify presets.
7. Click OK. The Add Preset window closes, and adds the position to the Presets tab's list of available preset positions for the camera. Use preset positions from the camera (type 2) As an alternative to specifying preset positions in the system, you can specify preset positions for some PTZ cameras on the camera itself. You can typically do this by accessing a product-specific configuration web page. 1. Import the presets into the system by selecting Use presets from device.
3. The Edit Preset window displays live video from the preset position. Use the navigation buttons and/or sliders to change the preset position as required. 4. Change the name/number and description of the preset position if needed. 5. Select Locked if you want to lock the preset position. Only users with sufficient rights can unlock the position afterwards. 6. Click OK.
Rename a preset position (type 2 only) To edit the name of a preset position defined in the camera: 1. Select the preset position in the Presets tab's list of available presets for the camera. 2. Click Edit. This opens the Edit Preset window: 3. Change the name and add a description of the preset position if needed. 4. Select Locked if you want to lock the preset name.
3. The camera moves to the selected preset position. Reserved PTZ sessions (explained) Depending on your surveillance system, you can reserve PTZ sessions. Administrators with security rights to run a reserved PTZ session can run the PTZ camera in this mode. This prevents other users from taking control over the camera. In a reserved PTZ session, the standard PTZ priority system is disregarded to avoid that users with a higher PTZ priority interrupt the session.
The settings apply for all PTZ cameras on your system. You can change the timeouts individually for each camera. 1. In the Site Navigation pane, click Camera. 2. In the Overview pane, select the camera. 3. On the Presets tab, select the amount of time in the: • Timeout for manual PTZ session list (default is 15 seconds). • Timeout for pause patrolling session list (default is 10 minutes). • Timeout for reserved PTZ session list (default is 1 hour). The settings apply for this camera only.
Name Description Timeout for manual PTZ session Specify the timeout period for manual PTZ sessions on this camera if you want the timeout to be different from the default period. You specify the default period in the Tools menu under Options. Timeout for pause patrolling PTZ session Specify the timeout period for pause patrolling PTZ sessions on this camera if you want the timeout to be different from the default period. You specify the default period in the Tools menu under Options.
Patrolling tab, displaying a patrolling profile with customized transitions.
Customize transitions (PTZ) on page 225 Specify an end position on page 226 Specify manual PTZ session timeout (see Specify PTZ session timeouts on page 220) Add a patrolling profile Add a profile that you want to use in a rule: 1. Click Add. The Add Profile dialog box appears. 2. In the Add Profile dialog box, specify a name for the patrolling profile. 3. Click OK. The button is disabled if the name is not unique. The new patrolling profile is added to the Profile list.
5. The camera uses the preset position at the top of the list as the first stop when it patrols according to the patrolling profile. The preset position in the second position from the top is the second stop, and so forth. Specify the time at each preset position When patrolling, the PTZ camera by default remains for 5 seconds at each preset position specified in the patrolling profile. To change the number of seconds: 1. Select the patrolling profile in the Profile list. 2.
To customize transitions between the different preset positions: 1. Select the patrolling profile in the Profile list. 2. Select the Customize transitions check box. Transition indications are added to the list of preset positions. 3. In the list, select the transition. 4. Specify the estimated transition time (in number of seconds) in the Expected time (sec) field. 5. Use the Speed slider to specify the transition speed.
Manual patrolling (explained) When you have designed a patrolling profile, you can test it with manual patrolling before you apply it in the system. Use the Start and Stop buttons to initiate and stop manual patrolling. If the camera is already patrolling or controlled by another user, you can only start manual patrolling if you have a higher priority.
Fisheye lens tab (devices) Fisheye Lens tab (explained) The following devices have a Fisheye Lens tab: • Fixed cameras with a fisheye lens On the Fisheye Lens tab, you can enable and configure fisheye lens support for the selected camera. Enable and disable fisheye lens support on page 228 Specify fisheye lens settings on page 229 Enable and disable fisheye lens support The fisheye lens support is disabled by default.
Specify fisheye lens settings When you enable the fisheye lens support: 1. Select the lens type. 2. Specify the physical position/orientation of the camera from the Camera position/orientation list. 3. Select a Registered Panomorph Lens (RPL) number from the ImmerVision Enables® panomorph RPL number list. This ensures the identification and correct configuration of the lens used with the camera. You usually find the RPL number on the lens itself or on the box it came in.
When you delete an event, it affects all rules that use the event. • Add an event on page 230 • Specify event properties on page 230 • Use several instances of an event on page 230 Add an event 1. In the Overview pane, select a device. 2. Select the Events tab and click Add. This opens the Select Driver Event window. 3. Select an event. You can only select one event at a time. 4. Click OK. 5. In the toolbar, click Save.
Event tab (properties) Name Description Configured events Which events you may select and add in the Configured events list is determined entirely by the device and its configuration. For some types of devices, the list is empty. General The list of properties depends on the device and the event. In order for the event to work as intended, you must specify some or all of the properties identically on the device as well as on this tab.
Client tab properties Name Siveillance Video 2019 R3 Description 232 SI SSP SH LPS COS Video
Name Description Specify the microphone on the camera that Siveillance Video Client users by default listen to audio. The Siveillance Video Client user can manually select to listen to another microphone if needed. Related microphone Specify the microphone that is related to the video push camera for streaming video with audio. The related microphones record when the camera records. Specify through which speakers on the camera, that Siveillance Video Client users speak by default.
Name Description To ease the selection of cameras for the Siveillance Video Client users, define keyboard shortcuts to the camera. Shortcut • Create each shortcut so it uniquely identifies the camera • A camera shortcut number cannot be longer than four digits The system supports multicast of live streams from the recording server to Siveillance Video Client. To enable multicast of live streams from the camera, select the check box.
Privacy masking tab (explained) The following devices have a Privacy masking tab: • Cameras On the Privacy masking tab, you can enable and configure privacy protection for the selected camera. Privacy masks are applied and locked to an area of the camera image, so the covered area does not follow the pan-til-zoom movements, but constantly cover the same area of the camera image. On some PTZ cameras, you can enable position based privacy masking on the camera itself.
• Create a report of your privacy masking configuration on page 241 Privacy masking (explained) With privacy masking, you can define which areas of the video from a camera you want to cover with privacy masks when shown in the clients. For example, if a surveillance camera covers a street, you can cover certain areas of a building (could be windows and doors) with privacy masks, to protect the privacy of residents. In some countries, this is a legal requirement.
And this is how they appear in the clients: You can inform the client users about the settings of permanent and liftable privacy masks.
Enable/disable privacy masking The privacy masking feature is disabled by default. To enable/disable the privacy masking feature for a camera: • On the Privacy masking tab, select or clear Privacy masking check box Define privacy masks When you enable the privacy masking feature on the Privacy masking tab, a grid is applied to the camera preview. 1. To cover an area with a privacy mask, first select if you want a permanent or liftable privacy mask. 2. Drag the mouse pointer over the preview.
4. Define how the covering of the areas should appear in the video when shown in the clients. Use the sliders to go from a light blurring to a full nontransparent mask. Permanent privacy masks also appear on the Motion tab. 5. In Siveillance Video Client, check that the privacy masks appear as you defined. Give users permission to lift privacy masks By default, no users have permissions to lift privacy masks in Siveillance Video Client. To enable/disable the permission: 1.
When you change the timeout, remember to do it for the Client profile associated with the role that has the permission to lift privacy masks. To change the timeout: 1. Under Client Profiles, select the relevant Client profile. 2. On the General tab, locate Lift privacy masks timeout. 3. Select between the values: 4. • 2 minutes • 10 minutes • 30 minutes • 1 hour • 2 hours • Until logged out Click Save.
Create a report of your privacy masking configuration The devices report include information about your cameras' current privacy masking settings. To configure a report: 1. Under Configuration Reports, select the Devices report. 2. If you want to modify the report, you can change the front page and the formatting. 3. Click Export, and the system creates the report as a PDF file. For more information about reports, see Configuration reports (explained) on page 374.
Privacy masking tab (properties) Name Description The selected grid size determines the density of the grid, regardless whether the grid is visible in the preview or not. Grid size Select between the values 8×8, 16×16, 32×32 or 64×64. Clear Clears all privacy masks you have specified. Show grid Select the Show grid check box to make the grid visible. When you select the Show privacy masks check box (default), permanent privacy masks appear in purple in the preview and liftable privacy masks in green.
Name Description Appears in green in the preview on this tab. Liftable mask Liftable privacy masks can be lifted in Siveillance Video Client by users with sufficient user rights. By default, the privacy masks are lifted for 30 minutes, or until the user apply them again. Be aware that the privacy masks are lifted on video from all the cameras that the user has access to.
Name Description Siveillance Video Monitoring Wall is an add-on that allows you to send view content from Siveillance Video Client to a dedicated video wall. Siveillance Video Monitoring Wall For more detailed information about Siveillance Video Monitoring Wall, see Siveillance Video Monitoring Wall (explained (see Siveillance Video Monitoring Wall (explained) on page 24). View groups The way in which video from cameras is presented is called a view.
Siveillance Video Monitoring Wall enables swift change of live video displayed on the video wall to meet specific security scenarios and needs. One way to change what is displayed on the video wall is with Monitoring Wall presets. The surveillance administrator defines the Monitoring Wall presets in the Management Client for optimizing the surveillance coverage for different recurring surveillance scenarios.
If you want to use rules to change automatically what is displayed on the video wall, or if you have typical surveillance scenarios where you want to display the same content on the video wall each time the scenario happens, you should define Monitoring Wall presets. The configuration of the Monitoring Wall is very flexible. You can include all monitors on the video wall in one Monitoring Wall or group the monitors and configure a Monitoring Wall for each group.
2. Enter a name and a description and click OK. 3. Click Activate to display the Monitoring Wall preset on the video wall. 4. Create as many Monitoring Wall presets as you need. d. Add layout and cameras to the monitors (requires a Monitoring Wall preset): 1. Select one of the monitors you created and from the Presets tab, select a preset from the list to configure what you want the selected monitor to show when used with the selected Monitoring Wall preset. 2. Click Edit. 3.
• Read - View Monitoring Walls in client applications • Edit - Modify Monitoring Walls in client applications • Delete - Delete Monitoring Walls in client applications • Operate - Apply layouts on the selected monitor in client applications, and activate presets • Playback - Review and manage live and recorded video If you do not select the Playback permission, users can view but not change the content that is displayed on the video wall.
Name Description Status text If selected, camera and system status information is displayed across cameras' layout items on the video wall. No title bar If selected, all Monitoring Wall layout items have no title bars on the video wall. Title bar If selected, all Monitoring Wall layout items have title bars on the video wall. Title bar with live indicator When selected, all Monitoring Wall layout items' title bars display live and motion indicators on the video wall.
Name Description Edit Click to adjust the positioning of the monitors. Movement To move a monitor to a new position, select the relevant monitor and drag it to the desired position, or click one of the arrow buttons to move the monitor in the selected direction. Zoom buttons Click buttons to zoom in/out of the Monitoring Wall layout preview to ensure you position the monitors correctly. Name The name of the monitor. The name is displayed in Siveillance Video Client.
Name Description Defines what should be displayed on a monitor with an empty preset layout when a new Monitoring Wall preset is triggered or selected in Siveillance Video Client. Empty preset Select Preserve to keep the current content on the monitor. Select Clear to clear all content so nothing is displayed on the monitor. Defines what should be displayed in an empty preset layout item when a new Monitoring Wall preset is triggered or selected in Siveillance Video Client.
Name Preset Description A list of Monitoring Wall presets for the select Monitoring Wall. Click Edit to edit the layout and the content of the selected monitor. Double-click a camera to remove a single camera. Click Clear to define a new layout or to exclude the monitor in the Monitoring Wall preset so the monitor is available for other content not controlled by the Monitoring Wall preset. Edit Click to select the layout you want to use with your monitor in the selected preset, and click OK.
• You can assign a view group based on a role to users/groups assigned to the relevant role. You may change these view group rights by setting this up in the role afterwards • A view group based on a role carries the role's name. Example: If you create a role with the name Building A Security Staff, it appears in Siveillance Video Client as a view group called Building A Security Staff. In addition to the view groups you get when adding roles, you may create as many other view groups as you like.
Add and configure a Client profile You must create a Client profile before you can configure it. 1. Right-click Client Profiles. 2. Select Add Client Profile. 3. In the Add Client Profile dialog box, enter a name and description of the new profile and click OK. 4. In the Overview pane, click the profile you created to configure it. 5. Adjust settings on one, more or all of the available tabs and click OK.
4. Specify the needed time period on Daytime only. 5. Create a new role and name it, for example, Guard (Selected cameras). 6. Specify which cameras Guard (Selected cameras) can use. 7. Assign the Live onlyClient profile and the Daytime only time profile to the Guard (Selected cameras) role to connect the three elements. You now have a mix of the three features creating the wanted result and allowing you room for easy fine-tuning and adjustments.
3. Click the General tab. 4. In the Default Client mode list, select Simplified. Siveillance Video Client now opens in simplified mode for those users associated with the current Client profile.
Prevent operators from switching between simple and advanced mode In Siveillance Video Client, operators can switch between simple and advanced mode. However, you can prevent the Siveillance Video Client operators from switching between modes. Technically, you must lock the setting that determines whether Siveillance Video Client opens in simple mode or advanced mode. 1. In Management Client, expand the Client node. 2. Select the relevant Client profile. 3. Click the General tab. 4.
5. Select the Locked check box. The mode toggling button in Siveillance Video Client is hidden. See also Set simple mode as the default mode (see Set simplified mode as the default mode on page 255) Client profile properties The following tabs allow you to specify the properties of each Client profile. You can lock the settings in the Management Client if required, so the users of Siveillance Video Client cannot change them.
Tab Description Advanced settings such as maximum decoding threads, deinterlacing and time zone settings. Maximum decoding threads controls how many decoding threads are used to decode video streams. It can help improve performance on multi-core computers in live as well as playback mode. The exact performance improvement depends on the video stream. It is mainly relevant if using heavily coded high-resolution video streams like H.264/H.
Tab Description Availability of playback tabs/panes, layout of print reports, independent playback, bookmarks, bounding boxes, and playback-related MIP plugins. Playback Setup tab (Client profiles) This tab allows you to specify the following properties: Tab Description Availability of general setup/panes/buttons, setup-related MIP plug-in and rights to edit a map and to edit live video buffering.
Tab Description Access Control Select if access request notifications should pop up on the Siveillance Video Client screen when triggered by events. Smart map tab (Client profiles) This tab allows you to specify the following properties: View Layout tab (Client profiles) This tab allows you to specify the following properties: Tab Description Specify settings for the Smart Map feature.
To associate a role with a Management Client profile, see the Role Settings' Info tab (see Info tab (roles) on page 327).Management Client profiles only handle the visual representation of system functionality, not the actual access to it. To limit the overall access to system functionality for a role, see the Role Settings' Overall Security tab (see Management ClientOverall Security tab (roles) on page 330).
Management Client profile properties Info tab (Management Client Profiles) On the Info tab, you can set the following for Management Client profiles: Component Requirement Name Enter a name for the Management Client profile. Priority Use the up and down arrows to set a priority for the Management Client profile. Description Enter a description for the profile. This is optional.
Navigation element Description Remote Connect Services Allows the administrator user associated with the Management Client profile to see Axis One-click Camera Connection. Servers Allows the administrator user associated with the Management Client profile to see Recording Servers and Failover Servers. Devices Allows the administrator user associated with the Management Client profile to see Cameras, Microphones, Speakers, Metadata, Input and Output.
Device channel Description Cameras Allows the administrator user associated with the Management Client profile to see some or all camera-related settings and tabs. Microphones Allows the administrator user associated with the Management Client profile to see some or all microphone-related settings and tabs. Speakers Allows the administrator user associated with the Management Client profile to see some or all speaker-related settings and tabs.
Matrix Matrix (explained) With Matrix, you can send video from any camera on a network operating your system to Matrixrecipients. A Matrix recipient is a computer that can display Matrix-triggered video. There are two kinds of Matrix recipients: • computers running a dedicated Matrix application • computers running Siveillance Video Client To see a list of Matrix recipients configured in the Management Client, expand Client in the Site Navigation pane, then select Matrix.
1. In the Site Navigation pane, expand Rules and Events > Rules. Right-click Rules to open the Manage Rule wizard. In the first step, select a rule type and in the second step, a condition. 2. In Manage Rule's step 3 (Step 3: Actions) select the Set Matrix to view action. 3. Click the Matrix link in the initial rule description. 4. In the Select Matrix Configuration dialog box, select the relevant Matrix-recipient, and click OK. 5.
detected motion, the surveillance system should take the action of starting recording of video from a particular camera. The following types of conditions can trigger rules: Name Description Events When events occur on the surveillance system, for example when motion is detected or the system receives input from external sensors. When you enter specific periods of time, for example: Time interval Thursday 16th August 2007 from 07.00 to 07.
• User-defined events: User-defined events are custom-made events that makes it possible for users to manually trigger events in the system or react to inputs from the system • Analytics events: Analytics events are data received from an external third-party video content analysis (VCA) providers.
Action Description Start recording and saving data in the database from the selected devices. When your select this type of action, the Manage Rule wizard prompts you to specify: When recording should start. This happens either immediately or a number of seconds before the triggering event/beginning of the triggering time interval and on which devices the action should take place.
Action Description Begin data feed from devices to the system. When the feed from a device is started, data is transferred from the device to the system, in which case you may view and record, depending on the data type. When you select this type of action, the Manage Rule wizard prompts you to specify on which devices to start the feeds. Your system includes a default rule which ensures that feeds are always started on all cameras.
Action Set to show text Remove from monitor Description Sets a specific Siveillance Video Monitoring Wall monitor to display a userdefined text message of up to 200 characters. No mandatory stop action: This type of action does not require a stop action.You can specify optional stop actions to be performed on either an event or after a period of time. Stop displaying video from a specific camera.
Action Description Sets a particular frame rate to use when the system saves recorded video from the selected cameras in the database, instead of the cameras' default recording frame rate. When you select this type of action, the Manage Rule wizard prompts you to specify which recording frame rate to set, and on which cameras. Set recording frame rate on You can only specify a recording frame rate for JPEG, a video codec with which each frame is separately compressed into a JPEG image.
Action Description Begins PTZ patrolling according to a particular patrolling profile for a particular PTZ camera with a particular priority. This is an exact definition of how patrolling should be carried out, including the sequence of preset positions, timing settings, and more.
Action Description Pauses PTZ patrolling. When you select this type of action, the Manage Rule wizard prompts you to specify the devices on which to pause patrolling. This type of action requires that the devices to which the action is linked are PTZ devices. You must define at least one patrolling profile for the device(s). You define patrolling profiles for a PTZ camera on the Patrolling tab. Pause patrolling on Stop action required: This type of action requires one or more stop actions.
Action Description Moves one or more particular cameras to their respective default preset positions - however always according to priority. When you select this type of action, the Manage Rule wizard prompts you to select which devices the action should apply for. Move to default preset on with PTZ priority This type of action requires that the devices to which the action is linked are PTZ devices.
Action Description Plays back an audio message on selected devices triggered by an event. Devices are mostly speakers or cameras. This type of action requires that you have uploaded the message to the system on Tools > Options > Audio messages tab. Play audio on with You can create more rules to the same event and send different messages to each device, but always according to priority.
Action Make new Description Generates an entry in the rule log. When selecting this type of action, the Manage Rule wizard prompts you to specify a text for the log entry. When you specify the log text, you can insert variables, such as $DeviceName$, $EventName$, into the log message. No mandatory stop action: This type of action does not require a stop action.You can specify optional stop actions to be performed on either an event or after a period of time. Starts one or more plug-ins.
Action Description Changes device settings on one or more devices. When you select this type of action, the Manage Rule wizard prompts you to select relevant devices, and you can define the relevant settings on the devices you have specified. If you define settings for more than one device, you can only change settings that are available for all of the specified devices. Apply new settings on Example: You specify that the action should be linked to Device 1 and Device 2.
Action Description Generates a small message which logs events on selected devices. The text of SNMP traps is auto-generated and cannot be customized. It can contain the source type and name of the device on which the event occurred. Send SNMP trap No mandatory stop action: This type of action does not require a stop action.You can specify optional stop actions to be performed on either an event or after a period of time.
Action Description Starts archiving on one or more archives. When you select this type of action, the Manage Rule wizard prompts you to select relevant archives. Activate archiving on On trigger No mandatory stop action: This type of action does not require a stop action. You can specify optional stop actions to be performed on either an event or after a period of time.
Action Remove current camera from Description The camera with the active stream is removed from the rule-based DLNA channel based on events. This type of action requires that you have a DLNA server installed on your system. No mandatory stop action: This type of action does not require a stop action. You can specify optional stop actions to be performed on either an event or after a period of time.
Some hardware is capable of creating events themselves, for example to detect motion. You can use these as events but you must configure them on the hardware before you can use them in the system. You may only be able to use the events listed on some hardware as not all types of cameras can detect tampering or temperature changes. Hardware - Configurable events: Configurable events from hardware are automatically imported from device drivers.
Event Description Communication Started (Device) Occurs when communication with a device is successfully established. Communication Stopped (Device) Occurs when communication with a device is successfully stopped. Evidence Lock Changed Occurs when an evidence lock is changed for devices by a client user or via the MIP SDK. Evidence Locked Occurs when an evidence lock is created for devices by a client user or via the MIP SDK.
Event Live Client Feed Terminated Description Occurs when client users no longer request a live stream from a device. Occurs when a client user starts a recording session for a camera. Manual Recording Started The event is triggered even if the device is already recording via rule actions. Occurs when a client user stops a recording session for a camera.
Event Description Occurs when an external output port on a device is activated. Output Activated This type of event requires that at least one device on your system supports output ports. Occurs when the state of an external output port on a device is changed. Output Changed This type of event requires that at least one device on your system supports output ports. Occurs when an external output port on a device is deactivated.
Event Description Settings Changed Error Occurs when an attempt is made to change settings on a device, and the attempt is unsuccessful. External events - Predefined events: Event Description Activated when play audio messages are requested via the MIP SDK. Request Play Audio Message Through the MIP SDK a third-party vendor can develop custom plugins (for example, integration to external access control systems or similar) for your system. Activated when start recordings are requested via the MIP SDK.
• Countless other purposes. For example, you may create user-defined events which occur if a particular type of data is received from a device See User-defined events (explained) on page 310 for more information Recording servers: Event Description Archive Available Occurs when an archive for a recording server becomes available after having been unavailable (see Archive Unavailable).
Event Description Database Full - Auto Archiving Occurs when an archive for a recording server is full and needs to autoarchive to an archive in the storage. Database Repair Occurs if a database becomes corrupted, in which case the system automatically attempts two different database repair methods: a fast repair and a thorough repair. Occurs when a storage for a recording server becomes available after having been unavailable (see Database Storage Unavailable).
Event Description CPU usage critical Occurs when the CPU usage exceeds the critical CPU threshold. CPU usage normal Occurs when the CPU usage falls back below the warning CPU threshold. CPU usage warning Occurs when the CPU usage exceeds the warning CPU threshold or falls back below the critical CPU threshold. Memory usage critical Occurs when the memory usage exceeds the critical memory threshold. Memory usage normal Occurs when the memory usage falls back below the warning memory threshold.
Event Description NVIDIA rendering normal Occurs when the NVIDIA rendering usage falls back below the warning NVIDIA rendering threshold. NVIDIA rendering warning Occurs when the NVIDIA rendering usage exceeds the warning NVIDIA rendering threshold or falls back below the critical NVIDIA rendering threshold. Occurs when a server service stops running. Service available critical There are no threshold values for this event. Occurs when a server service status changes to running.
Event Description Used space normal Occurs when the storage used for recordings by a specific camera falls back below the warning used space threshold. Used space warning Occurs when the storage used for recordings by a specific camera exceeds the warning used space threshold or falls back below the critical used space threshold. System Monitor - Disk: Event Description Free space critical Occurs when the disk space usage exceeds the critical free space threshold.
Other: Event Description Occurs when online automatic license activation fails. Automatic license activation failed There are no thresholds values for this event. Scheduled password change started Scheduled password change completed successfully Scheduled password change completed with errors Occurs when a scheduled password change starts. Occurs when a scheduled password change completes without errors. Occurs when a scheduled password change completes with errors..
• Make video appear in Matrix recipients • Start and stop plug-ins • Start and stop feeds from devices Stopping a device means that video is no longer transferred from the device to the system, in which case you cannot view live video nor record video.
Default rule Description Ensures that video is recorded automatically when an operator sets a bookmark in Siveillance Video Client. This is provided you have enabled recording for the relevant cameras. Recording is enabled by default. Record on Bookmark The default recording time for this rule is three seconds before the bookmark is set and 30 seconds after the bookmark is set. You can edit the default recording times in the rule.
Default rule Description Ensures that video feeds from all connected cameras are automatically fed to the system. Start Feed While the default rule enables access to connected cameras' video feeds immediately upon installing the system, it does not guarantee that video is recorded, as cameras' recording settings must be specified separately. Ensures that data feeds from all connected cameras are automatically fed to the system.
Default rule Record on Bookmark Text to enter Perform an action on Bookmark Reference Requested from All Cameras, All Microphones, All Speakers start recording three seconds before on the device on which event occurred Perform action 30 seconds after stop recording immediately Perform an action on Motion Started from All Cameras start recording three seconds before on the device on which event occurred Record on Motion Perform stop action on Motion Stopped from All Cameras stop recording three seconds a
Rule complexity (explained) Your exact number of options depends on the type of rule you want to create, and on the number of devices available on your system. Rules provide a high degree of flexibility: you can combine event and time conditions, specify several actions in a single rule, and very often create rules covering several or all of the devices on your system. You can make your rules as simple or complex as required.
rule may no longer work. For example, if a rule is triggered by a particular time profile, the rule does not work if you have deleted that time profile or if you no longer have permissions to it. Such unintended effects of configuration may be hard to keep an overview of. Rule validation helps you keep track of which rules have been affected. Validation takes place on a per-rule basis and each rule is validated by themselves.
2. Specifying a name and a description of the new rule in the Name and Description fields respectively. 3. Select the relevant type of condition for the rule: either a rule which performs one or more actions when a particular event occurs, or a rule which performs one or more actions when you enter a specific period of time. 4. Click Next to go to the wizard's second step. On the wizard's second step, define further conditions for the rule. 5.
Deactivate and activate a rule Your system applies a rule as soon as the rule's conditions apply which means it is active. If you do not want a rule to be active, you can deactivate the rule. When you deactivate the rule, the system does not apply the rule even if the rule's conditions apply. You can easily activate a deactivated rule later. Deactivating a rule 1. In the Overview pane, select the rule. 2. Clear the Active check box in the Properties pane. 3. Click Save in the toolbar. 4.
For general instructions on how to set up a new rule, see Add a rule on page 299. For information about time profiles, see Time profiles (explained) on page 302. Time profiles Time profiles (explained) Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information. Time profiles are periods of time defined by the administrator.
Specify a time profile 1. In the Time Profiles list, right-click Time Profiles > Add Time Profile. This opens the Time Profile window. 2. In the Time Profile window, enter a name for the new time profile in the Name field. Optionally, enter a description of the new time profile in the Description field. 3. In the Time Profile window's calendar, select either Day View, Week View or Month View, then right-click inside the calendar and select either Add Single Time or Add Recurring Time. 4.
1. In the Select Time window, specify time range, recurrence pattern and range of recurrence. 2. Click OK. A time profile can contain several periods of time. If you want your time profile to contain further periods of time, add more single times or recurring times. Edit a time profile 1. In the Overview pane's Time Profiles list, right-click the relevant time profile, and select Edit Time Profile. This opens the Time Profile window. 2. Edit the time profile as needed.
Day length time profiles (explained) When you place cameras outside, you must often lower the camera resolution, enable black/white or change other settings when it gets dark or when it gets light. The further north or south from the equator the cameras are placed, the more the sunrise and sunset time varies during the year. This makes it impossible to use normal fixed time profiles to adjusts camera settings according to light conditions.
Name Description Sunrise offset Number of minutes (+/-) by which activation of the profile is offset by sunrise. Sunset offset Number of minutes (+/-) by which deactivation of the profile is offset by sunset. Time zone Time zone indicating the physical location of the camera(s). Notification profiles Notification profiles (explained) Notification profiles allow you to set up ready-made email notifications.
Add notification profiles 1. Expand Rules and Events, right-click Notification Profiles > Add Notification Profile. This opens the Add Notification Profile wizard. 2. Specify name and description. Click Next. 3. Specify recipient, subject, message text and time between emails: 4. To send a test email notification to the specified recipients, click Test E-mail. 5.
Notifications containing H.265 encoded video require a computer that supports hardware acceleration. 7. Click Finish. Use rules to trigger email notifications You use the Manage Rule for creating rules. The wizard takes you through all relevant steps. You specify the use of a notification profile during the step on which you specify the rule's actions.
Component Requirement Description (optional) Enter a description of the notification profile. The description appears when you pause your mouse pointer over the notification profile in the Overview pane's Notification Profiles list. Recipients Enter the e-mail addresses to which the notification profile's e-mail notifications should be sent. To enter more than one e-mail address, separate addresses with a semicolon. Example: aa@aaaa.aa;bb@bbbb.bb;cc@cccc.
Component Requirement Time between images (ms) Specify the number of milliseconds you want between the recordings presented on the included images. Example: With the default value of 500 milliseconds, the included images show recordings with half a second between them. Time before event (sec.) This setting is used to specify the start of the AVI file. By default, the AVI file contains recordings from 2 seconds before the notification profile is triggered.
Events For providing the ability to manually trigger events in Siveillance Video Client Description In this case, user-defined events make it possible for end users to manually trigger events while viewing live video in Siveillance Video Client. When a user-defined event occurs because a user of Siveillance Video Client triggers it manually, a rule can trigger that one or more actions should take place on the system. In this case, you can trigger user-defined events outside the surveillance system.
Add a user-defined event 1. Expand Rules and Events > User-defined Events. 2. In the Overview pane, right-click Events > Add User-defined Event. 3. Enter a name for the new user-defined event, and click OK. The newly added user-defined event now appears in the list in the Overview pane. The user can now trigger the user-defined event manually in Siveillance Video Client if the user has rights to do so. Rename a user-defined event 1. Expand Rules and Events > User-defined Events. 2.
Add and edit an analytics event Add an analytics event 1. Expand Rules and Events, right-click Analytics Events and select Add New. 2. In the Properties window, enter a name for the event in the Name field. 3. Enter a description text in the Description field if needed. 4. In the toolbar, click Save. You can test the validity of the event by clicking Test Event. You can continually correct errors indicated in the test and run the test as many times as you want and from anywhere in the process.
3. Select the source of your test event, for example a camera. The window is closed and a new window appears that goes through four conditions that must be fulfilled for the analytics event to work. As an additional test, in Siveillance Video Client you can verify that the analytics event was sent to the event server. To do this, open Siveillance Video Client and view the event in the Alarm Manager tab.
Each step is marked by either failed: or successful: . Error messages and solutions for the condition Send analytics event: Error message Solution Event server not found Unable to find the event server on the list of registered services. Error connecting to event server Unable to connect to the event server on the stated port. The error occurs most likely because of network problems, or the Event Server service has stopped.
Error message Solution The response is valid, but not understood. The error occurs possibly because of network problems, or the port is busy. Unknown response from event server See the event server log, typically located at ProgramData\Siemens\Siveillance VMS Event Server\Logs\. Unexpected error Please contact Siemens support for help. Edit analytics events settings In the toolbar, go to the Tools > Options > Analytics Events tab to edit relevant settings.
Add a generic event You can define generic events to help the Video recognize specific strings in TCP or UDP packets from an external system. Based on a generic event, you can configure Management Client to trigger actions, for example to start recording, or alarms. Requirements You have enabled generic events and specified the source destinations allowed. For more information, see Generic Events tab (see Generic Events tab (options) on page 105). To add a generic event: 1. Expand Rules and Events. 2.
Component Requirement Expression that the system should look out for when analyzing data packages. You can use the following operators: • ( ): Used to ensure that related terms are processed together as a logical unit. They can be used to force a certain processing order in the analysis Example: The search criteria "(User001 OR Door053) AND Sunday" first processes the two terms inside the parenthesis, then combines the result with the last part of the string.
Component Requirement Indicates how particular the system should be when analyzing received data packages.
Component Requirement You can choose between two default data sources and define a custom data source. What to choose depends on your third party program and/or the hardor software you want to interface from: Compatible: Factory default settings are enabled, echoes all bytes, TCP and UDP, IPv4 only, port 1234, no separator, local host only, current code page encoding (ANSI).
Component Requirement Protocols which the system should listen for, and analyze, in order to detect generic events: Any: TCP as well as UDP. Protocol type selector TCP: TCP only. UDP: UDP only. TCP and UDP packages used for generic events may contain special characters, such as @, #, +, ~, and more. IP type selector Selectable IP address types: IPv4, IPv6 or both. Separator bytes Select the separator bytes used to separate individual generic event records.
Component Requirement Allowed external IPv4 addresses Specify the IP addresses, that the management server must be able to communicate with in order to manage external events. You can also use this to exclude IP addresses that you do not want data from. Allowed external IPv6 addresses Specify the IP addresses, that the management server must be able to communicate with in order to manage external events. You can also use this to exclude IP addresses that you do not want data from.
In addition to the Administrators role, you can add as many roles as required to suit your needs. You may, for example, have different roles for users of Siveillance Video Client depending on which cameras you want them to access or similar restrictions. To set up roles in your system, expand the Security > Roles. Rights of a role (explained) Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information.
Users (explained) The term users primarily refers to users who connect to the surveillance system through the clients. You can configure such users in two ways: • As basic users, authenticated by a user name/password combination • As Windows users, authenticated based on their Windows login Windows Users You add Windows Users through the use of Active Directory. Active Directory (AD) is a directory service implemented by Microsoft for Windows domain networks.
• You do not have to configure any authentication of users on the system as Active Directory handles authentication Before you can add users and groups through the Active Directory service, you must have a server with Active Directory installed on your network. Basic users If your system does not have access to Active Directory, create a basic user (see Basic users (explained) on page 364). For information about how to set up basic users, see Create basic user (see Create basic users on page 365).
If you rename a role, this does not change the name of the view group based upon the role. 1. Expand Security, and right-click Roles. 2. Right-click required role and select Rename Role. 3. In the dialog box that opens, change the name of the role. 4. Click OK. Delete a role 1. Expand Security and click Roles. 2. Right-click the unwanted role and select Delete Role. 3. Click Yes. If you delete a role, this does not delete the view group based upon the role.
1. Select Basic User. This opens the Select Basic Users to add to Role dialog box: 2. Select the basic user(s) that you want to assign to this role. 3. Optional: Click New to create a new basic user. 4. Click OK. The selected basic user(s) are now added to the Users and Groups tab's list of basic users who you have assigned the selected role. Remove users and groups from a role 1. On the Users and Groups tab, select the user or group you want to remove and click Remove in the lower part of the tab.
Name Description Name Enter a name for the role. Description Enter a description for the role. Select a Management Client profile to associate with the role. Management Client profile You cannot apply this to the default Administrators role. Requires permissions to manage security on the management server. Select a Client profile to associate with the role. Client profile Requires permissions to manage security on the management server. Select a default time profile to associate with the role.
Name Description Allow Siveillance Video Mobile client login Allow Siveillance Video Web Client login Select the check box to allow users associated with this role to log in to Siveillance Video Mobile client. Access to Siveillance Video Mobile client is allowed by default. Clear the check box to deny access to Siveillance Video Mobile client. Select the check box to allow users associated with this role to log in to Siveillance Video Web Client.
Overall Security tab (roles) Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information. On the Overall Security tab, you set up overall rights for roles. For every component available in your system, define access rights for the roles by setting Allow or Deny. You can define more access rights for Siveillance VMS Video Pro than for Siveillance VMS Video Advanced, Siveillance VMS Video Core Plus, and Siveillance VMS Video Core.
Security right Full control Siveillance VMS Video Pro Description Enables the right to manage all security entries on this part of the system. Enables users to connect to the Management Server. This permission is enabled by default. Connect You can temporarily deny connection permission on roles for maintenance purposes, and then reapply access to the system. This permission must be selected to allow access to the system.
Security right Siveillance VMS Video Pro Description Enables the right to modify data in a wide range of functionality, including: • Options • License Management It also enables users to create, delete, and edit the following: Edit • Remote Connect Services • Device groups • Matrix • Time Profiles • Notification Profiles • Registered Servers Only available Enables the right to configure local IP ranges when configuring the network on the recording server.
Security right Authorize users Siveillance VMS Video Pro Description Enables the right to authorize users when they are asked for a second login in Siveillance Video Client or Management Client. You define if a role requires login authorization on the Info tab. Enables the right to manage permissions for the Management Server.
Security right Description Manage storage Enables the right to administrate storage containers on recording server, that is, to create, delete, move, and empty storage containers. Manage security Enables the right to manage security permissions for recording servers. Failover Servers The following settings are only available in Siveillance VMS Video Pro. Security right Description Full control Enables the right to manage all security entries on this part of the system.
Security right Description Manage security Enables the right to manage security permissions for the mobile servers. Create Enables the right to add mobile servers to the system. Hardware The following settings are only available in Siveillance VMS Video Pro. Security right Description Full control Enables the right to manage all security entries on this part of the system. Edit Enables the right to edit properties on hardware. Enables the right to delete hardware.
Security right Siveillance VMS Video Pro Description Read Enables the right to view camera devices in the clients and the Management Client. Edit Enables the right to edit properties for cameras in the Management Client. It also enables users to enable or disable a camera. View Live Enables the right to view live video from cameras in the clients and the Management Client. Playback Enables the right to play back recorded video from cameras in all clients.
Security right Siveillance VMS Video Pro Description Read evidence locks Enables the right to search and read evidence locks in the clients. Only available Delete and reduce evidence locks Enables the right to delete or reduce evidence locks in the clients. Only available Start manual recording Enables the right to start manual recording of video in the clients. Stop manual recording Enables the right to stop manual recording of video in the clients.
Security right Lock/unlock PTZ presets Siveillance VMS Video Pro Description Enables the right to lock and unlock PTZ presets in the Management Client. This prevents or allows other users from changing preset positions in the clients and in the Management Client. Only available Enables the right to set PTZ cameras in reserved PTZ session mode in the clients and the Management Client.
Microphones Security right Siveillance VMS Video Pro Description Full control Enables the right to manage all security entries on this part of the system. Read Enables the right to view microphone devices in the clients and the Management Client. Edit Enables the right to edit microphone properties in the Management Client. It also allows users to enable or disable microphones. Listen Enables the right to listen to live audio from microphones in the clients and the Management Client.
Security right Siveillance VMS Video Pro Description Read evidence locks Enables the right to search and read evidence lock details in the clients. Only available Delete and reduce evidence locks Enables the right to delete or reduce evidence locks in the clients. Only available Start manual recording Enables the right to start manual recording of audio in the clients. Stop manual recording Enables the right to stop manual recording of audio in the clients.
Security right Siveillance VMS Video Pro Description Playback Enables the right to play back recorded audio from speakers in the clients. Retrieve remote recordings Enables the right to retrieve recordings in the clients from speakers on remotes sites or from edge storages on cameras. Read sequences Enables the right to use the Sequences feature while browsing recorded audio from speakers in the clients. Export Enables the right to export recorded audio from speakers in the clients.
Security right Siveillance VMS Video Pro Description Delete recordings Enables the right to delete stored recordings from the system. Only available Manage security Enables the right to manage security permissions in the Management Client for speakers. Only available Metadata Security right Siveillance VMS Video Pro Description Full control Enables the right to manage all security entries on this part of the system. Read Enables the right to receive metadata in the clients.
Security right Siveillance VMS Video Pro Description Read evidence locks Enables the right to view evidence locks in the clients. Only available Delete and reduce evidence locks Enables the right to delete or reduce evidence locks in the clients. Only available Start manual recording Enables the right to start manual recording of metadata in the clients. Stop manual recording Enables the right to stop manual recording of metadata in the clients.
Output Security right Siveillance VMS Video Pro Description Full control Enables the right to manage all security entries on this part of the system. Read Enables the right to view output devices in the clients. Edit Enables the right to edit properties for output devices in the Management Client. It also enables users to enable or disable an output device. Activate Enables the right to activate outputs in the clients.
Security right Siveillance VMS Video Pro Description Create Monitoring Wall Enables the right to create new Monitoring Walls in the Management Client. Only available Manage security Enables the right to manage security permissions in the Management Client for the Monitoring Wall. Only available Playback Enables the right to play back recorded data from within Monitoring Walls in the clients.
User-defined Events Security right Siveillance VMS Video Pro Description Full control Enables the right to manage all security entries on this part of the system. Read Enables the right to view user-defined events in the clients. Edit Enables the right to edit properties on user-defined events in the Management Client. Only available Delete Enables the right to delete user-defined events in the Management Client.
Security right Description Delete Enables the right to delete analytics events in the Management Client. Create Enables the right to create new analytics events in the Management Client. Manage security Enables the right to manage security permissions in the Management Client for analytics events. Generic Events Security right Description Full control Enables the right to manage all security entries on this part of the system.
Matrix Security right Siveillance VMS Video Pro Description Full control Enables the right to manage all security entries on this part of the system. Read Enables the right to select and send video to the Matrix recipient from the clients. Edit Enables the right to edit properties for a Matrix in the Management Client. Only available Delete Enables the right to delete a Matrix in the Management Client.
Security right Description Enables the right to delete rules from the Management Client. Delete It also requires that the user has read permissions on all devices that are impacted by the rule. Enables the right to create new rules in the Management Client. Create rule It also requires that the user has read permissions on all devices that are impacted by the rule. Manage security Enables the right to manage security permissions in the Management Client for all rules.
Security right Description Full control Enables the right to manage all security entries on this part of the system. Read Enables the right to view system monitors in Siveillance Video Client. Edit Enables the right to edit properties for system monitors in the Management Client. Manage security Enables the right to manage security permissions in the Management Client for all system monitors. Alarms The following settings are only available in Siveillance VMS Video Pro.
Security right Description Enables the right to create new alarm definitions in the Management Client. Create Server Logs The following settings are only available in Siveillance VMS Video Pro. Security right Full control Read system log entries Read audit log entries Read rule-triggered log entries Read log configuration Update log configuration Manage security Description Enables the right to manage all security entries on this part of the system. Enables the right to see system log entries.
Security right Description Enables the right to manage security permissions for all Access Control systems. Manage security MIP plug-ins Through the MIP SDK, a third-party vendor can develop custom plug-ins for your system, for example, integration to external access control systems or similar functionality. Device tab (roles) Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information.
Name Description Playback > Limit playback to Allows playback of recorded video from the selected camera(s) in the clients. Specify a playback limit or apply no restrictions. Read sequences Allows reading the sequence information related to, for example, the Sequence explorer in the clients. Smart search Allows the user to use the Smart search function in the clients. Export Allows the user to export recordings from the clients.
Name Description Allows the client user to: Delete and reduce evidence locks • Remove the camera from existing evidence locks • Delete existing evidence locks • Shorten the expiry time for existing evidence locks • Shorten the protected interval for existing evidence locks Requires user rights to all devices included in the evidence lock. Read evidence locks Allows the client user to search for and read evidence lock details.
Name Description Start manual recording Allows starting manual recording of audio from the selected microphone(s) in the clients. Stop manual recording Allows stopping manual recording of audio from the selected microphone(s) in the clients. Read bookmarks Allows search for and read bookmark details in the clients. Edit bookmarks Allows editing bookmarks in the clients. Create bookmarks Allows adding bookmarks in the clients. Delete bookmarks Allows deleting bookmarks in the clients.
Name Description Read The selected speaker(s) is visible in the clients. Live > Listen Allows listening to live audio from the selected speaker(s) in the clients. For Siveillance Video Client, it requires that the role has been granted the right to view the clients' Live tab. This right is granted as part of the application rights. Specify the time profile or leave the default value. Playback > Within time profile Allows playback of recorded audio from the selected speaker(s) in the clients.
Name Description Allows the client user to: Create and extend evidence locks • Add the speaker to new or existing evidence locks • Extend the expiry time for existing evidence locks • Extend the protected interval for existing evidence locks Requires user rights to all devices included in the evidence lock.
Name Description Playback Enables the right to play back recorded data from metadata devices in the clients. Read sequences Enables the right to use the Sequences feature while browsing recorded data from metadata devices in the clients. Export Enables the right to export recorded audio from metadata devices in the clients. Create and extend evidence locks Enables the right to create and extend the evidence locks on metadata in the clients.
Name Description Read The selected output(s) will be visible in the clients. If visible, the output will be selectable on a list in the clients. Activate The selected output(s) can be activated from the Management Client and the clients. Specify the time profile or leave the default value. PTZ tab (roles) You set up rights for pan-tilt-zoom (PTZ) cameras on the PTZ tab. You can specify the features users/groups can use in the clients.
Name Manage PTZ presets or patrolling profiles Lock/unlock PTZ presets Description Determines the right to add, edit and delete PTZ presets and patrolling profiles on the selected camera in both the Management Client and Siveillance Video Client. To allow this role to use other PTZ functions on the camera, enable the Manual PTZ right. Determines if the role can lock and unlock preset positions for the selected camera. Determines the right to set the selected camera in reserved PTZ session mode.
Name Description When several client users want to talk through the same speaker at the same time, conflicts may occur. Speak priority Solve the problem by specifying a priority for use of the selected speaker(s) by users/groups with the selected role. Specify a priority from Very low to Very high. The role with the highest priority is allowed use the speaker before other roles. Should two users with the same role want to speak at the same time, the first come, first served-principle applies.
Name Playback Description Allows users to play back recorded data from the selected Monitoring Wall in the clients. External Event tab (roles) Specify the following external event rights: Name Description Read Allows users to search for and view the selected external system event in the clients and the Management Client. Edit Allows users to edit the selected external system event in the Management Client. Delete Allows users to delete the selected external system event in the Management Client.
Name Description Delete Enables the right to delete View Groups in the Management Client. Operate Enables the right to use View Groups in Siveillance Video Client, that is to create and delete subgroups and views. Matrix tab (roles) If you have configured Matrix recipients on your system, you may configure Matrix role rights. From a client, you can send video to selected Matrix recipients. Select the users who can receive this on the Matrix tab.
Name Description Receive notifications Enables the right to receive notifications about alarms in Siveillance Video Mobile clients and Siveillance Video Web Client. Access Control tab (roles) When you add or edit basic users, Windows users or groups, specify access control settings: Name Description Use access control Allows the user to use any access control-related features in the clients.
• Windows users are authenticated based on their Windows login and are specific to a machine Create basic users To create a basic user on your system: 1. Expand Security > Basic Users. 2. In the Basic Users pane, right-click and select Create Basic User. 3. Specify a user name and a password, and repeat it to be sure you have specified it correctly. The password must meet the complexity requirements for the Windows operating system on the computer with the Management Server service installed. 4.
System monitor (explained) System monitor provides you with a quick, visual overview of the current state of your system's servers and cameras through colored tiles that represent the system hardware. By default, the system displays tiles that represent all Recording servers, All servers and All cameras. The color of the tiles: Tile color Description Green Normal state. Everything is running normally. Yellow Warning state.
Customize dashboard Add a new camera or server tile: 1. In the System monitor window, click Customize. 2. In the Customize dashboard window that opens, click New under Server tiles or Camera tiles. 3. In the New server tile/New camera tile window, select the cameras or servers to monitor. 4. Under Monitoring parameters, select or clear check boxes for any parameters to add or remove from the relevant tile. 5. Click OK.
The Used space field shows data from other recording servers where this device has recordings if, for example, the device has been located on other recording servers previously. If you click the Details button for the relevant camera/server, you can view system information and create reports regarding: Component Management server Description Shows data from the selected management server Shows data from the selected recording server.
System monitor thresholds (explained) System monitor thresholds allow you to set up and adjust the global thresholds for when tiles on System monitor should visually indicate that your system hardware changes state, for example when the CPU usage of a server changes from a normal state (green) state to a warning state (yellow). The system is set up with default threshold values so that you can start monitoring your system hardware from the moment your system is set up.
Threshold Description Unit NVIDIA memory Thresholds for NVIDIA RAM memory in use on the servers you monitor. % NVIDIA rendering Thresholds for the NVIDIA rendering usage on the servers you monitor. % Camera thresholds Threshold Description Unit Live FPS Thresholds for cameras' FPS in use when live video is shown on cameras you monitor. % Recording FPS Thresholds for cameras' FPS in use when the system is recording video on cameras you monitor.
You can also set up rules (see Rules (explained) on page 293) to perform specific actions or activate alarms (see System dashboard (explained) on page 365) when a threshold changes from one state to another. Set system monitor thresholds 1. In the Site Navigation pane, select System Monitor Thresholds. 2. Select the Enable check box for the relevant hardware if you have not already enabled it. The figure below shows an example. 3.
• Green indicates that things are at a normal state and within your selected threshold values Evidence lock (explained) Available functionality depends on the system you are using. See Product comparison chart on page 37 for more information. With the evidence lock functionality, client operators can protect video sequences, including audio and other data, from deletion if required, for example, while an investigation or trial is ongoing.
When the operator creates an evidence lock, the protected data remains in the recording storage that it was recorded to, and is moved to archiving disks together with non-protected data, but the protected data: • Follows the retention time configured for the evidence lock.
• When the evidence is no longer locked • Where the data is stored • The size of each evidence lock All information shown in Evidence Lock are snapshots. Press F5 to refresh. Current tasks (explained) The Current Tasks node shows an overview of tasks under a selected recording server, their begin time, estimated end time and progress. All information shown in Current Tasks are snapshots. You can refresh these by clicking on the Refresh button in the lower right corner of the Properties pane.
Name Description Front Page Customize the front page of the report. Formatting Format the report. Export Select a save location for the report and create a PDF. Server logs This section describes how to change log settings, filter logs, and create exports. Logs (explained) Logs are a detailed record of user activity, events, actions, and errors in the system. To see logs, in the Site Navigation pane, select Server Logs.
1. In the Site Navigation pane, select Server Logs. By default, the System logs tab appears. To navigate between log types, select a different tab. 2. Under the tabs, select a filter group, for example, Category, Source type, or User. A list of filters appears. 3. Select a filter to apply it. Select the filter again to remove it. Optional: In a list of filters, select Display applied filters only to see only the filters that you applied.
To export a log: 1. Select Export in the upper-right corner. The Export window appears. 2. In the Export window, in the Name field, specify a name for the log file. 3. By default, exported log files are saved in your Log export folder. To specify a different location, select 4. to the right of the Destination field. Select Export to export the log. The contents of your export change depending on the filters that you apply. For information about your export, see Filter logs on page 375.
2. In the Options dialog box, at the bottom of the Server Logs tab, find the Allow 2018 R2 and earlier components to write logs check box. • Select the check box to allow 2018 R2 and earlier components to write logs • Clear the check box to not allow 2018 R2 and earlier components to write logs System logs (properties) Each row in a log represents a log entry. A log entry contains a number of information fields: Name Description Log level Info, warning, or error.
Name Description Source type The type of equipment on which the logged incident occurred, for example, server or device. Source name The name of the equipment on which the logged incident occurred. User The user name of the remote user causing the logged incident. User location The IP address or host name of the computer from which the remote user caused the logged incident. Rule-triggered logs (properties) Each row in a log represents a log entry.
Based on functionality handled in the event server, the alarms feature provides central overview, control and scalability of alarms in any number of installations (including any other Siveillance Video systems) throughout your organization. You can configure it to generate alarms based on either: • Internal system related events For example, motion, server responding/not responding, archiving problems, lack of disk space and more.
5. Alarm data flow You handle and delegate alarms in the alarm list in Siveillance Video Client. You can also integrate alarms with the Siveillance Video Client's map functionality.
Alarm Definitions When your system registers an event on your system, you can configure the system to generate an alarm in Siveillance Video Client. You must define alarms before you can use them, and alarms are defined based on events registered in your system servers. You can also use user-defined events for triggering alarms and use the same event to trigger several different alarms.
Alarm Definitions (properties) The table describes the settings you can make when you create an alarm definition. Alarm definition settings: Name Description Enable By default, the alarm definition is enabled. To disable it, clear the check box. Name Alarm names do not have to be unique, but using unique and descriptive alarm names are advantageous in many situations. Enter a descriptive text about the alarm and how to resolve the issue that caused the alarm.
Name Description If you want the alarm to be based on an event, select this radio button. Once selected, specify the start and stop event. You can select hardware events defined on cameras, video servers and input (see Events overview on page 282). Also global/manual event definitions can be used (see User-defined events (explained) on page 310 Event based Operator action required: Name Description Time limit Select a time limit for when operator action is required. The default value is 1 minute.
Name Description Events triggered by alarm Define an event that the alarm can trigger in Siveillance Video Client. Auto-close alarm If you want a particular event to automatically stop the alarm, select this check box. Not all events can trigger alarms. Clear the check box to disable the new alarm from the beginning. Select the check box to include users with an administrator role in the Assigned to list.
Name Level Description In addition to the default state levels (numbers 1, 4, 9 and 11, which cannot be edited or reused), add new states with level numbers of your choosing. These state levels are only visible in the Siveillance Video Client's Alarm List. Categories Name Description Level Add new categories with level numbers of your choosing. These category levels are used to configure the Initial alarm category setting. Name Enter a name for the entity. You can create as many as you like.
Name Description Sounds Select the sound to be associated with the alarm. The list of sounds contains a number of default Windows sounds. You can also add new sounds (.wav or .mp3). Add Add sounds. Browse the sound file and upload one or several .wav or .mp3 files. Remove Remove a selected sound from the list of manually added sounds. Default sounds cannot be removed. Test Test the sound. In the list, select the sound. The sound plays once.
The components of a Siveillance Video Federated Architecture setup: 1. SQL server 2. Management server 3. Management Client 4. Siveillance Video Client 5. Cameras 6. Recording server 7. Failover recording server 8. to 12.
Hierarchy synchronization A parent site contains an updated list of all its currently attached child sites, child sites' child sites and so on. The federated site hierarchy has a scheduled synchronization between sites, as well as a synchronization every time a site is added or removed by the system administrator. When the system synchronizes the hierarchy, it takes place level by level, each level forwarding and returning communication, until it reaches the server that requests the information.
To start the hierarchy, you can log into the site that you want to work as the central site and add (see Add site to hierarchy on page 392) the first federated site. When the link is established, the two sites automatically create a federated site hierarchy in the Federated Site Hierarchy pane in the Management Client to which you can add more sites to grow the federated hierarchy.
Set up your system to run federated sites To prepare your system for Siveillance Video Federated Architecture, you must make certain choices when you install the management server. Depending on how your IT infrastructure is set up, choose between three different alternatives.
Alternative 2: Connecting sites from different domains To connect to sites across domains, make sure that the domains trust each other. You set up domains to trust each other in the Microsoft Windows Domain configuration. When you have established trust between the different domains on each site in the federated site hierarchy are placed, follow the same description as described in Alternative 1. For more information about how to set up trusted domains, see the Microsoft website (https://docs.microsoft.
5. If you can establish the link to the child site without requesting acceptance from the child site administrator, go to step 7. If not, the child site has the awaiting acceptance has authorize the request. icon until the administrator of the child site 6. Make sure that the administrator of the child site authorizes the link request from the parent site (see Accept inclusion in the hierarchy on page 393). 7.
2. If needed, change the following: General tab (see General tab on page 395) Parent Site tab (see Parent Site tab on page 396) (available on child sites only) Due to synchronization issues, any changes made to remote children might take some time to be reflected in the Site Navigation pane. Refresh site hierarchy Regularly the system automatically synchronizes the hierarchy through all levels of your parent/child setup.
The Management Client for that site opens. 3. Enter login information and click OK. 4. After login is complete, you are ready to do your administrative tasks for that site. Detach a site from the hierarchy When you detach a site from its parent site, the link between the sites are broken. You can detach sites from the central site, from the site itself or its parent site. 1. In the Federated Site Hierarchy pane, right-click the site, and click Detach Site from Hierarchy. 2.
Name Description Time for last synchronization Time and date of the last synchronization of the hierarchy. Status for last synchronization The status of the last synchronization of the hierarchy. It can be either Successful or Failed. Parent Site tab This tab shows information about the parent site of the site that you are currently logged in to. The tab is not visible if your site has no parent site. Name Description Name Shows the name of the parent site.
Siemens recommends Siveillance Video Federated Architecture when: • The network connection between the central and federated sites is stable • The network uses the same domain • There are fewer larger sites • The bandwidth is sufficient for the required use Siemens recommends Siveillance Video Interconnect when: • The network connection between the central and remote sites is unstable • You or your organization want to use another Siveillance Video product on the remote sites • The network uses
1. Siveillance Video Interconnect central Siveillance VMS Video Pro site 2. Siveillance Video Interconnect drivers (handles the connection between the central sites' recording servers and the remote site, must be selected in the list of drivers when adding remote systems via the Add Hardware wizard) 3. Siveillance Video Interconnect connection 4. Siveillance Video Interconnect remote site (the complete remote site with system installation, users, cameras and so on) 5.
On the central site, you can view the system's own status for the interconnected cameras, but not directly the state of the remote site. Instead, to monitor the remote site, you can use the remote site events to trigger alarms or other notifications on the central site (see Configure your central site to respond to events from remote sites on page 403).
If the system detects an automatic retrieval, or request for retrieval from the Siveillance Video Client, outside the time interval that you specified on the Remote Retrieval tab, it is accepted, but not started until the selected time interval is reached. New remote recording retrieval jobs will queue and start when the allowed time interval is reached. You can view pending remote recording retrieval jobs from System Dashboard -> Current Tasks.
7. Specify the IP addresses and port numbers you want to scan. Default is port 80. Click Next. Wait while your system detects the remote sites. A status indicator shows the detection process. In case of a successful detection, a Success message appears in the Status column. If you fail to add, you can click the Failed error message to see why. 8. Choose to enable or disable successfully detected systems. Click Next. 9. Wait while your system detects hardware and collects device specific information.
Requirements The remote desktop connections to the computer you want to remote to must be up and running. 1. On the central site, expand Servers and select Recording Servers. 2. In the Overview pane, expand the required recording server, select the relevant remote system. 3. In the Properties pane, select the Info tab. 4. In the Remote administration area, enter the appropriate Windows user name and password. 5.
3. In the Properties pane, select the Remote Retrieval tab and update the settings (see Remote Retrieval tab on page 177). If the network fails for some reason, the central site misses out on recording sequences. You can configure your system to let the central site automatically retrieve remote recordings to cover the down-period, once the network is reestablished. 1. On the central site, expand Servers and select Recording Servers. 2.
2. In the Overview pane, select the relevant remote server and the Events tab. 3. The list contains the predefined events. Click Add to include user-defined or manual events from the remote site in the list. Use an event on a remote site to trigger an alarm on the central site: 1. On the central site, expand Alarms and select Alarm Definitions. 2. In the Overview pane, right-click Alarm Definitions and click Add New. 3. Enter values as needed. 4.
The remote connect services feature contains the Axis One-click Camera Connection technology developed by Axis Communications. It enables the system to retrieve video (and audio) from external cameras where firewalls and/or router network configuration normally prevents initiating connections to such cameras. The actual communication takes place via secure tunnel servers (ST servers). ST servers use VPN. Only devices that hold a valid key work within a VPN.
2. In the window that opens, fill in the relevant information. 3. If you chose to use credentials when you installed the Axis One-Click Connection Component, select the Use credentials check box and fill in the same user name and password as used for the Axis One-Click Connection Component. 4. Click OK. Register new Axis One-Click camera 1. To register a camera under an ST server, right-click it and select Register Axis One-Click Camera. 2.
Name Description Description Enter/edit a description for the camera. External address Enter/edit the web address of the ST server to which the camera(s) connect. Internal address Enter/edit the web address of the ST server to which the recording server connects. Name If needed, edit the name of the item. Owner authentication key See Camera password. Passwords (for Dispatch Server) Enter password. Must be identical to the one received from your system provider.
Cached smart map files (explained) The files that you use for your geographic background are retrieved from a tile server. The time that the files are stored in the cache folder depends on the value selected in the Removed cached smart map files list in the Options dialog in Siveillance Video Client.
1. Expand the Security node > Roles. 2. In the Roles pane, select the role that your operator is associated with. 3. To give the role editing rights: 4. • Click the Overall Security tab, and select Cameras in the Role Settings pane • In the Allow column, select the Full control or Edit check box Save the changes. The steps above gives the role the right to edit all cameras. To enable editing for individual cameras, go to the Device tab and select the relevant camera.
The Bing Maps and Google Maps options require access to the Internet, and you must purchase a key from Microsoft or Google. • OpenStreetMap - connect to the OpenStreetMap (https://www.openstreetmap.org/) (OSM) open source mapping project. This option requires access to the Internet. The map data for OSM is provided under the organization's Open Database License (https://www.openstreetmap.org/copyright/) • None - this hides the geographic background. However, the geo-reference data is still there.
If you want to use a different key, you can enter it in the Options dialog box in Client. This requires that your system administrator has not locked the key in Management Client, and that the Follow server check box is not selected in Client. The key in Client is associated with your user account, and only you will use it. Steps: 1. In Management Client, on the Site Navigation pane, click Client Profiles. 2. In the Properties pane, select the Client profile, and then click the Smart Map tab: 3.
• In Management Client - you set the tile server address on the Client profiles (see Set an alternative OpenStreetMap tile server on page 412). The server address applies to all Client users assigned to the individual Client profiles • In Siveillance Video Client - you set the tile server address in the Settings window.
6. Save the changes. Set camera position, direction, field of view, and depth (smart map) To ensure that a camera is positioned correctly on the smart map, you can set the GPS coordinates, the direction of the camera, the field of view, and the viewing depth. In doing so, automatically the camera is added to the smart map next time an operator loads it in Siveillance Video Client. Steps: 1. In Management Client, expand the Devices node and select Cameras. 2.
3. On the Info tab, scroll down to Positioning information. 4. Specify the latitude and the longitude in the GPS coordinates field, in that order. Use a period as decimal separator and a comma to separate the values. 5. In the Direction field, enter a value in the range of 0 and 360 degrees. 6. In the Field of view field, enter a value in the range of 0 and 360 degrees. 7. In the Depth field, enter the viewing depth, either in meters or feet. 8. Save the changes.
Setting up smart map with Siveillance Video Federated Architecture When you use smart map in a Siveillance Video Federated Architecture, all the cameras from the connected sites appear on the smart map. The overall steps in this topic describes how to set up smart map in a federated architecture. For general information about Siveillance Video Federated Architecture, see Siveillance Video Federated Architecture (explained) on page 387. 1.
What may cause the error is that the operator is running version 2017 R1 of Siveillance Video Client against an Siveillance VMS Video Pro 2017 R2 installation. Siveillance Video Client looks for the GPS position of the camera on the event server, but in version 2017 R2 or newer of Siveillance VMS Video Pro, the GPS position is stored on the management server. Solution Upgrade Siveillance Video Client to version 2017 R2 or newer.
The Audit log logs the commands that each user performs in the access control system from Siveillance Video Client. Apart from a Siveillance Video Access base license, you need a vendor-specific integration plug-in installed on the event server before you can start an integration (see Configure an integrated access control system on page 417).
1. Add the integrated access control system to your Siveillance Video system. See Wizard for access control system integration on page 418. The wizard takes you through the most basic steps. 2. Specify additional properties for the access control system integration, especially the access control events may require that you map events from the access control system with event categories that Siveillance Video recognizes. See Access control properties on page 419. 3.
The integration plug-in may also define secondary parameters which are not listed in the wizard, but you can change these in General Settings after setting up the integration. The default values for the parameters are supplied by the plug-in or the Siveillance Video system. Connecting to the access control system When the plug-in has been successfully integrated, a summary of the retrieved access control system configuration appears.
Name Description Systems are by default enabled, meaning that they are visible in Siveillance Video Client for users with sufficient rights and that the Siveillance Video system receives access control events. Enable You can disable a system, for example during maintenance, to avoid creating unnecessary alarms. Name The name of the access control integration as it appears in the management application and in the clients. You can overwrite the existing name with a new one.
Name Description Address Enter the address of the server that hosts the integrated access control system. Port Specify the port number on the server to which the access control system is connected. User name Enter the name of the user, as defined in the access control system, who should be administrator of the integrated system in Siveillance Video. Password Specify the password for the user.
Name Description Lists the cameras configured in the Siveillance Video system. Cameras Select a camera from the list, and drag and drop it at the relevant access point to associate the access point with the camera. Access Control Events tab (Access Control) Event categories allow you to group events. The configuration of event categories affects the behavior of access control in the Siveillance Video system and allows you to, for example, define an alarm to trigger a single alarm on multiple event types.
Name Description Assign none, one or more event categories to the access control events. The system automatically maps relevant event categories to the events during integration. This enables a default setup in the Siveillance Video system. You can change the mapping at any time.
Name Name Description Enter a name for the access request notification. Click to add and define access request notifications. Add Access Request Notification Access request notification details To delete a notification, click X on the right side. If a user of Siveillance Video Client logs into a parent site in a Siveillance Video Federated Architecture hierarchy, access request notifications from the child sites also appear in Siveillance Video Client.
Name Description Search cardholder Enter the characters of a cardholder name and it appears in the list, if it exists. Name Lists the names of the cardholders retrieved from the access control system. Lists the type of cardholder, for example: Type • Employee • Guard • Guest If your access control system supports adding/deleting pictures in the Siveillance Video system, you can add pictures to the cardholders.
Requirements: On the roles of the client users, you must enable notifications. To do this, on the role, click the Access Control tab, select Access Control, and then select the Receive notifications check box. Steps: 1. In the Site Navigation pane, select Access Control. 2. On the Access Control Events tab, in the Access Control Event column, locate the event type that you want to edit. 3. To disable access requests for an event type, in the Event Category column, click the Access request check box.
Siveillance Video LPR Siveillance Video LPR system overview Siveillance Video LPR (explained) Siveillance Video LPR offers video-based content analysis (VCA) and recognition of vehicle license plates that interacts with your surveillance system and your Siveillance Video Client. To read the characters on a plate, Siveillance Video LPR uses optical character recognition on images aided by specialized camera settings.
Siveillance Video LPR system architecture Basic data flow: 1. LPR cameras (a) send video to the recording server (b). 2. The recording server sends video to the LPR servers (c) to recognize license plates by comparing them with the license plate characteristics in the installed country modules. 3. LPR servers send recognitions to the event server (d) to match with the license plate match lists. 4. The event server sends events and alarms to Siveillance Video Client (e) when there is a match. 5.
Minimum system requirements For information about the minimum system requirements for the various components of your system, go to the Siemens website (https://intranet.for.siemens.com/cms/041/en/business/products/Pages/siveillance-vms.aspx#tabs-12). Or SIOS: https://support.industry.siemens.com/cs/start?lc=en-WW Siemens recommends that you install the LPR server on a computer especially allocated for this purpose.
This section helps you prepare cameras for license plate recognition, but it also introduces you to important theories about cameras and lenses that are crucial to understand in order to get optimal images. Factors that influence your configuration of LPR: 1. Vehicle 2. Physical surroundings 3.
Unwanted camera features (on page 440) Positioning the camera When you mount cameras for LPR use, it is important to get a good, clear view of the area of interest so the plate can be detected consistently. This ensures the best possible performance and low risk of false detection: • The area should cover only the part of the image where the license plate is visible as the vehicle moves in and out of the image.
Camera angles • Single-line rule: Mount the camera so that you can draw a horizontal line that crosses both the left and right edge of the license plate in the captured images. See the illustrations below for correct and incorrect angles for recognition. • Vertical angle: The recommended vertical view angle of a camera used for LPR is between 15°-30°. • Horizontal angle: The recommended maximum horizontal view angle of a camera used for LPR is between 15°-25°.
Plate width recommendations Mount the camera so that the ideal snapshot of the license plate is captured when the license plate is in the center or lower half of the image: Take a snapshot and make sure that the requirements to stroke width and plate width as described below are fulfilled. Use a standard graphics editor to measure the amount of pixels.
Image resolution Image quality and resolution is important for a successful license plate recognition. On the other hand, if the video resolution is too high, the CPU might be overloaded with the risk of skipped or faulty detections. The lower you can set the acceptable resolution, the better CPU-performance and the higher detection rate you get. In this example we explain how to do a simple image quality calculation and find a suitable resolution for LPR. The calculation is based on the width of a car.
Name Pixels (W×H) SVGA 800×600 XGA 1024×768 720p 1280×1024 Understanding camera exposure Camera exposure determines how light/dark and sharp/blurry an image appears when it has been captured. This is determined by three camera settings: aperture, shutter speed, and ISO speed. Understanding their use and interdependency can help you to set up the camera correctly for LPR. You can use different combinations of the three settings to achieve the same exposure.
Aperture settings The aperture setting controls the amount of light that enters your camera from the lens. It is specified in terms of an f-stop value, which can at times be counterintuitive, because the area of the opening increases as the f-stop decreases. Low f-stop value/wide aperture = shallow depth of field High f-stop value/narrow aperture = large depth of field The example illustrates how the depth of field is affected by the f-stop value. The blue line indicates the focus point.
A low f-stop value reduces the focus area and thereby the area used for recognition, but is suitable for conditions with low light. If it is possible to ensure that vehicles are passing the focus area at a low speed, a low f-stop value is suitable for a consistent recognition. Shutter speed A camera's shutter determines when the camera sensor is open or closed for incoming light from the camera lens. The shutter speed refers to the duration when the shutter is open and light can enter the camera.
• • Little light: Too little light in the surroundings or too little external lighting can lead to underexposure. • • Smear is an effect from overexposure that leads to unwanted light vertical lines in images. It is often caused by slight imperfections in the cameras’ charge-coupled device (CCD) imagers. The CCS imagers are the sensors used to digitally create the images. Underexposure is when images are exposed to too little light, resulting in a dark image with hardly any contrast (on page 439).
• Neutral Density (ND) filters or gray filters basically reduce the amount of light coming into a camera. They work as "sunglasses" for the camera. ND filters affect the exposure of images (see Understanding camera exposure on page 435). • Infrared: If using an infrared light source, focus may change when switching between visible light and infrared light. You can avoid the change in focus by using an infrared compensated lens, or by using an infrared pass filter.
Pixels in an 8-bit grayscale image can have color values ranging from 0 to 255, where grayscale value 0 is absolute black and 255 is absolute white. When you convert your input image to an 8-bit grayscale image, the minimum pixel value difference between a pixel in the text and a pixel in the background should be at least 15.
• At least one LPR server. • The Siveillance Video LPR plug-in on all computers that run the Management Client and the event server. • Make sure that the user selected for running the LPR Server service can access the management server. Siemens recommends that you do not install the LPR server on the same computer as your management server or recording servers. Start installation: 1. Go to the download page on the SIOS: https://support.industry.siemens.com/cs/start?lc=enWW 2.
If you upgrade, some recognition settings are not compatible with those from the previous configuration. To apply the new settings, you must save your configuration. The settings that previously allowed you to flip, rotate and invert the colors of the video have been removed. If you still need these functions, you must change the settings on the cameras themselves. Siveillance Video LPR configuration View LPR server information To check the state of your LPR servers: 1.
Field Description Service up time Shows the up time since the LPR server was last down and the LPR server service started. Computer CPU usage Shows the current CPU usage on the entire computer with the LPR server(s) installed. Memory available Shows how much memory is available on the LPR server. Recognized license plates Shows the number of license plates that the LPR server has recognized in this session.
As a guideline, capture snapshots of vehicles in the real physical surroundings and conditions, in which you want to be able to recognize license plates. The list below illustrates examples of the situations that you should consider when you capture and select snapshots. Not all may be applicable to your surroundings.
• Position in the lane; to define the left and right of the recognition area • Distance to the car; to define the area where LPR analyzes license plates Add LPR camera To configure cameras for LPR, you initially run the Add LPR camera wizard. The wizard takes you through the main configuration steps and automatically optimizes the configuration. To run the wizard: 1. In the Site Navigation pane, expand Servers, expand LPR servers, and select LPR camera. 2. Go to the Overview pane.
The LPR camera appears in the Management Client and based on your selections, the system has optimized the recognition settings for the camera (see Recognition settings tab on page 446). 5. Select the camera you have added and review its settings. You only need to change the configuration if the system does not recognize license plates as well as expected. 6. In the Recognition settings tab, click Validate configuration (on page 453).
Name Description Validate configuration Test that license plates are recognized as expected (see Validate configuration on page 453). Auto-configure Discard manual changes and auto-configure settings (see Autoconfigure on page 453). Snapshots Add or delete snapshots (see Select snapshots on page 452). Recognition area To ensure best performance and avoid false recognitions, Siemens recommends that you select a clearly defined and "well-trimmed" recognition area.
• The sooner you get the results. The overlay in the snapshot displays the currently defined character height setting. The overlay grows and shrinks proportionally to the character height settings to the right. For easy comparison, drag the overlay on top of the real license plate in the snapshot. Zoom with your mouse wheel for a closer look. Name Description Minimum height Set the minimum character height for including license plates in the recognition process.
• takes more time to return results. When the optimal results are met, the recognition process stops and returns the license plate it recognized at that point. Name Description Compensate for interlacing If your LPR camera records interlaced video, and you see a combing effect in the de-interlaced image in LPR, select this check box. This may improve image quality and recognition results.
Name Description Discard recognitions below Discard recognitions with a confidence level below the value you specify. Increase this value to get fewer but possibly more accurate recognitions. Decrease this value to get more but potentially less accurate recognitions. The smaller the difference between Stop recognition above and Discard recognitions below values, the lower the processing time and the CPU load.
Name Description All License plates are matched against all available and future lists. Selected License plates are matched against the selected lists only. Select one or more from the available lists. After changing the settings for your LPR camera, validate your configuration (see Validate configuration on page 453) to check if the system recognizes license plates as well as expected. Country modules tab Here you select the country modules that you want to use with a specific LPR camera.
Name Description Country Module Lists the installed country modules. Country Code Letters that identify a country module. Licensed Shows if a country module is already licensed. You can select a licensed country module for as many cameras as you like. After changing the settings for your LPR camera, validate your configuration (see Validate configuration" on page 453) to check if the system recognizes license plates as well as expected.
Validate configuration You can validate your current configuration to see if you need to change any settings or provide more snapshots. The validation function informs you about how many license plates your system recognizes, and if they are recognized correctly. It can help you decide if your confidence level is set correctly and if your system configuration is optimal. 1. Select the relevant camera. 2. From the Recognition settings tab, click Validate configuration.
Working with license plate match lists License plate match lists (explained) License plate lists are collections of license plates that you want your LPR solution to treat in a special way. License plate recognitions are compared with these lists and if there is a match, the system triggers an LPR event. The events are stored on the event server and can be searched for and viewed on the LPR tab in Siveillance Video Client. By default, events are stored for 24 hours.
5. Instead of defining the match list directly in the Management Client, you can import a file (see Import/export license plate match lists on page 455). 6. If prompted, confirm to save changes. Edit license plate match lists 1. In the Site Navigation pane, select License plate match lists. 2. Go to the Overview pane. Click the relevant list. 3. The License plate match list information window opens. 4. To include new rows to your list, click Add and fill out the fields: • Do not include any spaces.
3. Click Close. 4. You can open and edit the exported file in, for example, Microsoft Excel. License plate match list properties Name Description Name Shows the name of the list. If needed, you can change the name. Custom fields Click to specify which license plate entry columns that you or the client user can add additional information to. See Custom fields (properties) (see Edit custom fields properties on page 457). Search Search the list for specific license plates, numbers, patterns or similar.
Name Description Events triggered by list match Select which event(s) should be triggered by a list match (see Events triggered by LPR on page 457). You can choose between all available types of events defined in your system. Edit custom fields properties You can add columns to your license plate match lists for additional information. You define the name and number of columns as well as the field content.
1. Create the license plate match list (see Add new license plate match lists on page 454) you want to match license plates against. 2. Add and configure your LPR camera(s) (see Add LPR camera on page 445). 3. In the Site Navigation pane, expand Alarms, right-click Alarm Definitions and select to create a new alarm. 4. The Alarm Definition Information window appears. Select the relevant properties (see Alarm Definitions for LPR on page 458). 5. If prompted when done, confirm to save changes. 6.
2. On the Alarm List Configuration tab, select Object, Tag, and Type and click >. 3. If prompted, confirm to save changes. LPR maintenance LPR Server Manager (explained) After installing an LPR server, you can check the status of its services with the Siveillance Video LPR Server Manager. You can, for example, start and stop the LPR Server Service, view status messages, and read log files.
• Service not responding • Not connected to surveillance system • Service not running • Event Server not connected • Unknown error • X of Y LPR cameras running Show LPR server log Log files are a useful tool for monitoring and troubleshooting the status of the LPR Server Service. All entries are time-stamped, with the most recent entries at the bottom. 1. In the notification area, right-click the LPR Server Manager icon. 2. From the menu that appears, select Show LPR server Log File.
Siveillance Video Transact Siveillance Video Transact introduction Siveillance Video Transact (explained) Siveillance Video Transact is an add-on to Siemens's IP video surveillance solutions. Siveillance Video Transact is a tool for observing ongoing transactions and investigating transactions in the past. The transactions are linked with the digital surveillance video monitoring the transactions, for example to help you prove fraud or provide evidence against a perpetrator.
• The blue arrows outline video recordings from the surveillance system The red arrows outline transaction data from the transaction sources By standard, Siveillance Video Transact supports two types of transaction sources: • Serial port clients • TCP server clients Additional types of transaction sources may be supported through custom connectors developed with the MIP software development kit (SDK), for example a connector that retrieves transaction data from an enterprise resource planning (ERP) sy
Transaction events (explained) A transaction event is the occurrence of specific words, numbers, or characters in the stream of transaction data that flows from the transactions sources, for example the cash registers, to the event server. As a system administrator, you need to define what the events are. This allows the operator to track and investigate transaction events in Siveillance Video Client.
Siveillance Video Transact configuration Setting up transactions In this section, you will learn how to add and configure the transaction sources, and how to create the transaction definitions. Add transaction source (wizard) To connect data from a transaction source to Siveillance Video Transact, you need to add the sources of the transactions, for example an automated teller machine. In the wizard, you select a connector, and you can connect one or more cameras.
Name Transaction definition Retention period Description You can select a different transaction definition that defines how to transform the transaction data received into transactions and transaction lines. This includes defining: • when a transaction begins and ends. • how transactions are displayed in Siveillance Video Client. Specify, in days, for how long transaction data is maintained on the event server. The default retention period is 30 days.
in a format that matches real-life receipts. This is necessary, because typically the raw data consists of a single string of data, and it can be difficult to see where the individual transactions begin and end. Steps: 1. In the Site Navigation pane, expand Transact. 2. Select Transaction definitions. 3. Go to the Overview pane. Right-click Transaction definition and select Add new. A number of settings appear in the Properties section. 4.
Name Description Save to file If you want to save the collected raw data to a file, click this button. You can reuse it later. Select the match type to use to search for the start mask and the stop mask in the collected raw data: • Use exact match: The search identifies strings that contain exactly what you have entered in the Start mask and Stop mask fields.
Name Description Filter text Displays the characters currently selected in the Raw data section. If you are aware of characters that you want to be omitted or replaced, but they do not occur in the collected raw data string, you can enter the characters manually in the Character field. If the character is a control character, you need to enter its hexadecimal byte value. Use this format for the byte value: {XX} and {XX,XX,...} if a characters consists of more bytes.
4. In the Properties pane, click Add. A new line is added. 5. Type a name for the event. 6. Select the match type to use to identify a specific string in the transaction data as an event. You can choose between exact match, wildcard symbols, and regular expressions. For more information, see the description of match type in Transaction definitions (properties)(on page 466). 7. In the Match pattern column, specify what you want the system to identify as an event, for example "smartphone". 8.
3. Type a name for the alarm and, in the Description field, possibly also instructions for Siveillance Video Client operator on what action to take. 4. In the Triggering event drop-down menu, select Transaction events. 5. In the drop-down menu below Transaction events, select the specific event. 6. In the Sources field, click the Select... button. A pop-up window appears. 7. Click the Servers tab and select the transaction source. 8. Specify additional settings.
Steps: 1. In the Site Navigation pane, expand Alarms 2. Select Alarm Data Settings and click the Alarm List Configuration tab. 3. In the Available columns section, select the Type field. 4. Add the field to Selected columns. 5. Save the changes. Now, the field is available in Siveillance Video Client. Maintaining transaction setup In this section, you will learn how to edit, disable, and delete transaction sources.
See also Add transaction source (wizard) (on page 464) Disable transaction sources (on page 472) Disable transaction sources You can disable a transaction source, for example if an ATM is temporarily out of order, or a service on a registered cash register is disabled. The flow of transaction data to the event server is disrupted. Steps: 1. In the Site Navigation pane, expand Transact. 2. Select Transaction sources. 3. Go to the Overview pane.Click the transaction source. The properties are displayed. 4.
1. Open Siveillance Video Client and click the Transact tab. 2. Select a transaction source that you know is active and click today appear. . The transaction lines for 3. Click a line to view the associated receipt and video recordings. 3. Verify that transaction events are configured correctly: 1. Define a transaction test event in Management Client, for example an item that is likely to be purchased and registered on a connected transaction source, for example a cash register. 2.
Adding Siveillance Video Mobile ONVIF Bridge This section describes how to install and configure Siveillance Video Mobile ONVIF Bridge. Siveillance Video Mobile ONVIF Bridge (explained) ONVIF is an open, global forum that is working to standardize and secure the way that IP video surveillance products communicate. The goal is to make it easy to exchange video data.
• Request video • Authenticate users • Stream video • Play recorded video ONVIF clients (explained) ONVIF clients are computer appliances or software programs that use ONVIF Webservices. Examples of ONVIF clients are servers, media players, IP-based surveillance systems, or bridges like the Siveillance Video Mobile ONVIF Bridge. The Real Time Streaming Protocol (RTSP) is used to establish and control media sessions between two or more endpoints.
Siemens recommends that you install the ONVIF Bridge server in a demilitarized zone (DMZ). Siveillance Video ONVIF clients 1. An ONVIF client connects to the Siveillance Video via the ONVIF Bridge server through the Internet. To do this, the ONVIF client needs the IP address or domain name (domain/host name) of the server where the Siveillance Video Mobile ONVIF Bridge is installed, and the ONVIF port number. 2.
2. In the Management Client, assign the user to a role that can access cameras, and specify permissions for the ONVIF Bridges security group on the Overall Security tab for the role. 3. Assign the user to the Siveillance Video Mobile ONVIF Bridge during installation, and in the Management Client for each ONVIF client afterward. All users who should be granted access to ONVIF Bridge server, including those who install ONVIF Bridge, must be added in the Onvif Bridge Server Settings in Management Client.
• Registers and starts the Siveillance Video Mobile ONVIF Bridge service and the Siemens RTSP Bridge service • Starts the Siveillance Video Mobile ONVIF Bridge Manager, which is available in the Windows notification area on the server where the ONVIF Bridge Server is installed The actions in the ONVIF Bridge Manager apply to both the Siveillance Video Mobile ONVIF Bridge service and the Siemens RTSP Bridge service.
1. Select the language you want to use, and then click Continue. 2. Read and accept the license agreement, and then click Continue. 3. Select the installation type, as follows: To install the ONVIF Bridge server and plug-in on one computer, and apply default settings, click Typical. 1. Verify that the server URL, user name and password are correct and click Continue. 2. Select the file location and product language, and then click Install.
You are ready for initial configuration (see Configuring the Siveillance Video Mobile ONVIF Bridge on page 480). Configuring the Siveillance Video Mobile ONVIF Bridge After you install the Siveillance Video Mobile ONVIF Bridge, the ONVIF Bridge service is running and the ONVIF Bridge Manager tray icon turns green.
Tips and tricks The configuration created by ONVIF Bridge Manager is stored locally in a file at ProgramData\Siemens\Siveillance Video Mobile ONVIF Bridge. The name of the file is serverconfiguration.xml. If this file is deleted, you must update the configuration in the ONVIF Bridge Manager. To update a configuration, follow the steps described in Change configuration settings for a Siveillance Video Mobile ONVIF Bridge in this document.
Name Description The port number of the ONVIF port. ONVIF clients use this port to connect to the ONVIF Bridge server. ONVIF port The default port number is 580. The port number of the RTSP port. The ONVIF Bridge server sends RTSP video streams through this port to ONVIF clients. RTSP port The default port number is 554. ONVIF user credentials Lists the ONVIF client users that have access to the Siveillance Video system through the ONVIF Bridge server.
Name Description Max days of retention Default value is 30. Frame per seconds Default value is 5. Width Default value is 1920. This corresponds to full HD quality. Height Default value is 1080. This corresponds to full HD quality. Bitrate Kbps Default value is 512. GOP size Default value is 5. Codec Select one of the H.264 codec profiles. The default value is H.264 Baseline Profile. Enable this to use the actual configuration of the cameras instead of the default average values defined above.
Name Description This setting defines the RTSP server playback response, where the client’s time interval for playback is not specified. Prefer absolute time over normalized Select this option if you want your RTSP server to use real time as opposed to scaled or normalized playback. However, if your client application is set to use either relative time intervals or real time intervals (in UTC), the RTSP server replies with those intervals defined in the client.
3. When you start the ONVIF Device Manager, it automatically discovers ONVIF compliant devices on the network. However, it might not discover the Siveillance Video Mobile ONVIF Bridge. • If it does, go to step 6 • If it does not, add the bridge manually. Continue with step 4 4. To add a Siveillance Video Mobile ONVIF Bridge, click ADD. 5.
1. Go to https://www.videolan.org/vlc/, and then download the installer for the VLC media player. 2. Run the installer, and follow the instructions for each step. 3. On the toolbar, click Media, and select Open Network Stream. 4. In the Open media dialog box, enter the following RSTP string. Replace the variables in the square brackets [ONVIF Bridge IP Address] and [Camera GUID] with the correct information: 5.
Create a proxy for the RecordingSearch service using the service endpoint returned by GetServices. Create request and response objects, then call GetRecordingSummary.
_tse__GetRecordingSummary tse__GetRecordingSummary; _tse__GetRecordingSummaryResponse tse__GetRecordingSummaryResponse; result = searchProxy.GetRecordingSummary( searchEndpoint.c_str(), NULL, &tse__GetRecordingSummary, &tse__GetRecordingSummaryResponse ); Search for recordings The Search service method FindRecordings starts an asynchronous search on the camera. FindRecordings returns a token that references the search results.
Playback is initiated by means of the RTSP PLAY method. A range can be specified. If no range is specified, the stream is played from the beginning and plays to the end, or, if the stream is paused, it is resumed at the point it was paused. In this example, “Range: npt=3-20” instructs the RTSP server to start playback from the third second until 20th second. For example: PLAY rtsp://basic:basic@bgws-pvv-04:554/vod/943ffaad-42be-4584-bc2c-c8238ed96373 RTSP/1.
Scale: -1.0 Change speed Speed is controlled by the RTSP Rate-Control header. If "Rate-Control=yes", then the server is in control of the playback speed. The stream is delivered in real time using standard RTP timing mechanisms. If "Rate-Control=no", then the client is in control of the playback speed. Rate-controlled replay will typically only be used by non-ONVIF specific clients because they will not specify “RateControl=no”. To control playback speed in a client, use the provided controllers.
Code What can I achieve with the code?
Code What can I achieve with the code? input-list= Input list You can give a comma-separated list of inputs that will be concatenated together after the normal one Input slave (experimental) input-slave= This allows you to play from several inputs at the same time. This feature is experimental, not all formats are supported.
View logs The ONVIF Bridge Manager saves the log information about the ONVIF Bridge server and the RTSP streams. 1. In the notification area on the computer where the ONVIF Bridge server is installed, right-click the ONVIF Bridge Manager tray icon. 2. Select Show latest ONVIF log or Show latest RTSP log. Change the level of information in your logs The ONVIF Bridge Manager saves the log information about the ONVIF Bridge server and the RTSP streams.
Change configuration settings for the Siveillance Video Mobile ONVIF Bridge If you change the IP address or host name of the surveillance server, or if you have changed the user accounts that have access to the surveillance server service, you must update this information for Siveillance Video Mobile ONVIF Bridge. To change the Video address or login credentials, follow these steps: 1.
You can change this to include sub-sites. However, Siemens recommends that you do so only for systems where sub-sites do not contain large numbers of cameras. The Siveillance Video Mobile ONVIF Bridge aggregates and displays all cameras, including those from sub-sites, in one list. For example, if the system and sub-sites have more than 50 cameras, the list will be difficult to use. If you must include sub-sites, consider installing the Siveillance Video Mobile ONVIF Bridge on each management server.
• Siveillance Video DLNA Server • Siveillance Video DLNA Server 64-bit admin plug-in for the Management Client The following illustration shows a high-level view of the interoperability between a DLNA device and Siveillance Video DLNA Server in the Siveillance Video system. 1. During start up of the Siveillance Video DLNA Server service, the Siveillance Video DLNA Server connects to the management server to authorize itself with the provided credentials.
Before you install Siveillance Video DLNA Server When you install Siveillance Video DLNA Server, you install a server and a plug-in for the Management Client. These components enables you to add DLNA channels and provide video to DLNA devices. You can install and add multiple DLNA servers to your Siveillance Video system. Multiple DLNA devices are able to connect to each DLNA server, so this increases the load on the network, and can impact performance.
• Siveillance Video DLNA Server which includes: • Siveillance Video DLNA Server Manager that is running and accessible from the notification area on the server with Siveillance Video DLNA Server installed • Siveillance Video DLNA Server service Installation also does the following: • Registers and starts the Siveillance Video DLNA Server service • Starts the X Siveillance Video DLNA Server Manager, which is available in the Windows notification area on the server where the Siveillance Video DLNA Ser
2. • The URL or IP address, and the port number, of the management server. The default port is 80. If you omit the port number, the system will use port 80 • Verify that the login as either NETWORK SERVICE or a specified user account with User name and Password is correct • Click Continue Select the file location and product language, and then click Install. When the installation is complete, a list of successfully installed components appears. Click Close. 3.
Configuring Siveillance Video DLNA Server After you installed Siveillance Video DLNA Server, the Siveillance Video DLNA Server service is running and the DLNA Server Manager tray icon in the notification area turns green. The next step is to make cameras available for Siveillance Video DLNA Server. Configure settings for a DLNA server To provide a DLNA device access to your Siveillance Video, follow these steps: 1. Open the Management Client. 2.
• Rule-based: One or multiple cameras per channel. Cameras are set to or removed from the rule-based channel based on events After creating the channel you need to create new rules in Rules to show cameras on this channel (see Add a rule on page 299). To select the cameras available for DLNA devices, follow these steps: 1. Click the Add channels button. 2. Select a channel type. 3. Click the server and camera groups to expand them and select the cameras you want.
• Green: Running • Yellow: Starting or stopping • Red: Stopped If it is stopped, right-click the icon and select Start Siveillance Video DLNA Server. Change surveillance server credentials If you change the IP address, host name, user account or port numbers of the surveillance server, you must update this information for Siveillance Video DLNA Server. Port numbers for the Siveillance Video DLNA Server can also be changed.
2. Specify the new information, and then click OK. The Siveillance Video DLNA Server service restarts and the tray icon turns green. Using DLNA certified device to view video streams To start watching live video from your Siveillance Video system on your public displays or TV, follow these steps: 1. Make sure your device is DLNA certified and connected to the network with Siveillance Video DLNA Server. 2. Scan the network and connect to Siveillance Video DLNA Server when it has been discovered.
Backing up your system configuration can take some time. Backup duration depends on: • Your system configuration • Your hardware • Whether you have installed the SQL server, Event Server service and the Management Client on a single server or several servers Each time you make a backup both manual and scheduled, the SQL Server's transaction log file is flushed. For additional information about how to flush this log file, go to the Microsoft website and search for "SQL Server transaction log.
Backup and restore fail and problem scenarios (explained) If, after your last system configuration backup, you have moved the event server or other registered services such as the log server, you must select which registered service configuration you want for the new system. You can decide to keep the new configuration after the system is restored to the old version. You decide by looking at the host names of the services.
• No logs, including audit logs, are restored • Once restoring has started, you cannot cancel it Restoring: 1. Right-click the notification area's Management Server service icon and select Restore Configuration. 2. Read the important note and click Restore. 3. In the file open dialog box, browse to the location of the configuration backup file, select it, and click Open. The backup file is located on the Management Client computer.
The management server stores your system's configuration in a database. When you back up/restore management server(s), make sure that this database is included in the backup/restore. Requirements for using scheduled backup and restore Microsoft® SQL Server Management Studio, a tool download-able for free from their website (https://www.microsoft.com/downloads/). Apart from managing SQL Server databases, the tool includes some easy-to-use backup and restoration features.
Restore system configuration from a scheduled backup Requirements To prevent configuration changes being made while you restore the system configuration database, stop the: • Management Server service (see Managing server services on page 519) • Event Server service (can be done from Windows Services (search for services.msc on your machine. Within Services, locate Siemens Siveillance VMS Event Server)) • World Wide Web Publishing Service, also known as the Internet Information Service (IIS).
management server also gets access to this database. The system configuration database can be stored in two different ways: • Network SQL Server: If you are storing your system configuration in a database on an existing SQL Server on your network, you can point to the database's location on that SQL Server when installing the management server software on your new management server.
Unavailable management servers (explained) • Recording servers can still record: Any currently working recording servers received a copy of their configuration from the management server, so they can work and store recordings on their own while the management server is down.
2. Replace the recording server ID on the new recording server: 1. Stop the Recording Server service on the old recording server, then in Windows' Services set the service's Startup type to Disabled. It is very important that you do not start two recording servers with identical IDs at the same time. 2. On the new recording server, open an explorer and go to C:\ProgramData\Siemens\Siveillance VMS Recording Server or the path where your recording server is located. 3. Open the file RecorderConfig.xml.
• The system deletes them when the retention time expires. Recordings that someone has protected with Evidence Lock (see Evidence lock (explained) on page 372) is not deleted until the evidence lock's retention time expires. You define the retention time for evidence locks when you create them.
Requirements Before you start the wizard: • Make sure that the new recording server can access the physical camera via the network • Install a recording server on page 70 that you want to move hardware to • Install the same device pack versions (see Device drivers (explained) on page 62) on the new recording server that you run on the existing server To run the wizard: 1. In the Site Navigation pane, select Recording Servers. 2.
Error type The recording server is not connected or in failover mode. Troubleshooting Make sure that the recording server is online. You may need to register it. If the server is in failover mode, wait and try again. The recording server is not the latest version. Update the recording server so it runs the same version as the management server. The recording server could not be found in the configuration. Make sure that the recording server has not been removed.
Error type Troubleshooting You are trying to move hardware to a recording server where one or more recording storages are currently offline. All recording storages on the target recording server must be available. Make sure that all recording storages on the target recording server are online. A recording storage is offline of the disk is offline or otherwise unavailable.
The wizard is prefilled with data from the existing hardware. If you replace it with a similar hardware device, you can reuse some of this data - for example, port and driver information. 5.
Example of the old hardware device having more individual devices than the new one: Click Next. 6. You are presented with a list of hardware to be added, replaced or removed. Click Confirm. 7. Final step is a summary of added, replaced and inherited devices and their settings. Click Copy to Clipboard to copy contents to the Windows clipboard or/and Close to end the wizard. Managing the SQL server This section describes how to make use of a different SQL database than the current one.
You must copy the SQL databases before you proceed. Update the log server's SQL address 1. Go to the computer where your management server is installed and copy the directory %ProgramFiles%\Siemens\Siveillance VMS Management Server\Tools\ChangeSqlAddress\ (with content) to a temporary directory on the event server. 2. Paste the directory that you copied to a temporary place on the computer where the log server is installed and run the included file:VideoOS.Server.ChangeSqlAddress.exe.
6. Wait while the address change takes place. When a confirmation message is presented, click OK. Managing server services On the computer that runs server services, you find server manager tray icons in the notification area. Through these icons, you can get information about the services and perform certain tasks. This includes, for example, checking the state of the services, viewing logs or status messages, and starting and stopping the services.
Management Recording Server Server Manager Manager tray tray icon icon Event Server Manager tray icon Failover Recording Server Manager tray icon Description Starting Appears when a server service is in the process of starting. Under normal circumstances, the tray icon changes after a short while to Running. Stopping Appears when a server service is in the process of stopping. Under normal circumstances, the tray icon changes after a short while to Stopped.
Management Recording Server Server Manager Manager tray tray icon icon Event Server Manager tray icon Failover Recording Server Manager tray icon Description Must be authorized by administrator Appears when the Recording Server service is loaded for the first time. Administrators authorize the recording server through the Management Client: Expand the Servers list, select the Recording Server node and in the Overview pane, right-click the relevant recording server and select Authorize Recording Server.
For more information about the tray icons, see Server manager tray icons (explained) on page 519. See also Start, stop, or restart the Event Server service on page 523 Start or stop the Recording Server service on page 522 Start or stop the Recording Server service The Recording Server Manager tray icon indicates the state of the Recording Server service, for example Running. Through this icon, you can start or stop the Recording Server service.
2. Select Show Status Messages. Depending on the server type, either the Management Server Status Messages or Recording Server Status Messages window appears, listing time-stamped status messages: Start, stop, or restart the Event Server service The Event Server Manager tray icon indicates the state of the Event Server service, for example Running. Through this icon, you can start, stop, or restart the Event Server service.
Stopping the Event Server service on page 524 Stopping the Event Server service When installing MIP plug-ins in the Event Server, first you must stop the Event Server service and then, afterward, restart it. However, while the service is stopped, many areas of the Video system will not function: • No events or alarms are stored in the Event Server.
3. 1. To view the log file, click Open log file. 2. To open the log folder, click Open log folder. To view the 100 most recent lines in the MIP log, go back to the context-menu and click Show MIP logs. A log viewer is displayed. If someone removes the log files from the log directory, the menu items are grayed out. To open the log viewer, first you need to copy the log files back into one of these folders: C:\ProgramData\Siemens\Siveillance VMS Event Server\logs or C:\ProgramData\Siemens\Siveillance V
Add and edit registered services 1. In the Add/Remove Registered Services window, click Add or Edit, depending on your needs. 2. In the Add Registered Service or Edit Registered Service window (depending on your earlier selection), specify or edit settings. 3. Click OK. Manage network configuration With the network configuration settings, you can specify the management server's server LAN and WAN addresses so the management server and the trusted servers can communicate. 1.
Component Requirement Click Add to add the IP address or hostname of the registered service. If specifying a hostname as part of a URL, the host must exist and be available on the network. URLs must begin with http:// or https:// and must not contain any of the following characters: < > & ' " * ? | [ ] ". URLs Example of a typical URL format: http://ipaddress:port/directory (where port and directory are optional). You can add more than one URL if required.
Remove a recording server If you remove a recording server, all configuration specified in the Management Client is removed for the recording server, including all of the recording server's associated hardware (cameras, input devices, and so on). 1. Right-click the recording server you want to remove in the Overview pane. 2. Select Remove Recording Server. 3. If you are sure, click Yes. 4. The recording server and all of its associated hardware are removed.
5. In the Internet Information Services (IIS) window, verify whether the SMTP Service check box is selected. If so, SMTP Service is installed. If SMTP Service is installed, select one of the following solutions: Solution 1: Disable SMTP Service, or set it to manual startup This solution lets you start the recording server without having to stop the SMTP Service every time: 1. From Windows' Start menu, select Control Panel. 2. In the Control Panel, double-click Administrative Tools. 3.
• In C:\ProgramData\Siemens\Siveillance VMS Management Server\ServerConfig.xml: http://ClusterRoleAddress/IDP • In C:\Program Files\Siemens\Siveillance VMS Management Server\IIS\IDP\appsettings.json: "Authority": "http://ClusterRoleAddress/IDP" On the Recording Servers, verify that the authorizationserveraddress is also set to the cluster role address: In C:\ProgramData\Siemens\Siveillance VMS Recording Server\RecorderConfig.
without the security patch, will cause the recording servers to fail. The instructions for installing the security patch on your recording servers are available on our website https://www.siemens.com/siveillance-vms/. When all recording servers in your system are upgraded to version 2019 R2 or later, Siemens recommends that you set UseRemoting to False in the management server configuration file. For more information, see the Hardening guide.
• If you plan to enable encryption during installation, you need to have the proper certificates installed and trusted on relevant computers. For more information, see Secure communication (explained) on page 52. You can also enable encryption after installation from the server tray icon in the notification areas of the relevant servers. When you are ready to start the upgrade, follow the procedures in Upgrade best practices on page 532.
If you enable encryption on the management server, the recording servers are offline until they are upgraded, and you have enabled encryption to the management server (see Management server encryption (explained) on page 53). 2. Upgrade failover recording servers. From your management server's download web page (controlled by the Download Manager), install Recording Server.
1. On the recording server, create a local Windows user. 2. From the Windows Control Panel, find the Siemens Siveillance Video Data Collector service. Right-click it, select Properties, and select the Log on tab. Set the Data Collector service to run as the local windows user you just created on the recording server. 3. On the management server, create the same local Windows user (with the same user name and password). 4.
Adaptive Streaming Introduction The Adaptive Streaming provides the ability to determine the size of a camera view item and use the above-mentioned interface extension to send a message to the Siveillance Video Client to switch stream on the camera view item. Solution overview The Adaptive Streaming in the Siveillance Video Client monitors which camera view items are currently shown and whether size of the camera view items is changed.
Issued by Cyber security disclaimer Siemens Schweiz AG Smart Infrastructure International Headquarters Gubelstrasse 22 CH-6301 Zug, Switzerland 6301 Zug - Switzerland Tel. +41 41 724 24 24 Siemens provides a portfolio of products, solutions, systems and services that includes security functions that support the secure operation of plants, systems, machines and networks.
