How it Works
OnSSI
Loading...
RC-E
User Manual
203 pgs1.49 Mb0

OnSSI RC-E User Manual

Download
Page 1
RC-E User Manual
Recording Component (RC-E)
User Manual
© 2012 On-Net Surveillance Systems Inc.
Page 2
RC-E User Manual
00081512-0945-RC-5_5.0-OC3.5.0.77_v01 00081512-0945-RC-5_5.0-OC3.5.0.77_v01
On-Net Surveillance Systems, Inc. On-Net Surveillance Systems, Inc.
One Blue Hill Plaza, 7th Floor, PO Box 1555
One Blue Hill Plaza, 7th Floor, PO Box 1555
Pearl River, NY 10965
Pearl River, NY 10965
Phone: (845) 732-7900 | Fax: (845) 732-7999 Phone: (845) 732-7900 | Fax: (845) 732-7999
Web: www.onssi.com Web: www.onssi.com
Legal Notice
This product manual is intended for general information purposes only, and due care has been taken in its preparation. Any risk arising from the use of this information rests with the recipient, and nothing herein should be construed as constituting any
kind of warranty. © 2002-2012 On-Net Surveillance Systems, Inc. All rights reserved. OnSSI and the ‘Eye’ logo are registered trademarks of On-Net
Surveillance Systems, Inc. Ocularis, Ocularis Client, Ocularis Client Lite, Ocularis Video Synopsis, NetEVS, NetDVMS, NetDVR, ProSight, NetGuard, NetGuard-EVS, NetSwitcher, NetMatrix, NetCentral, NetTransact, NetPDA and NetCell are trademarks of On-Net Surveillance Systems, Inc. All other trademarks are property of their respective owners.
On-Net Surveillance Systems, Inc. reserves the right to change product specifications without prior notice. Patents Applied For in the U.S. and Abroad
Page 3
RC-E User Manual
Contents
Contents
Introductions................................................................................................................................................ 7
Product Overview, RC-E .............................................................................................................................................7
About Updates .........................................................................................................................................................7
The RC-E Server (Management Server)..................................................................................................................7
The RC-E Recording Server ....................................................................................................................................8
The Management Client (RC-E Manager)................................................................................................................8
The Download Manager...........................................................................................................................................8
System Requirements.................................................................................................................................................9
Computer Running Management Server..................................................................................................................9
Computer Running Recording Server or Failover Server.........................................................................................9
Computer Running Management Client................................................................................................................10
Computer Running Log Server..............................................................................................................................10
Active Directory......................................................................................................................................................10
Navigating the Built-in Help System ..........................................................................................................................11
Installation and Removal.......................................................................................................................... 12
Installation Overview .................................................................................................................................................12
Installing RC-E on Virtual Servers..........................................................................................................................12
Install Management Server........................................................................................................................................13
Step 1: Internet Information Services.....................................................................................................................14
Step 2: RC-E Management Server Database ........................................................................................................15
Step 3: RC-E Management Server.........................................................................................................................15
What's Next?..........................................................................................................................................................17
Install System Components.......................................................................................................................................17
Part I—Downloading the Installer...........................................................................................................................17
Part II—Installing the Component ..........................................................................................................................18
Recording Servers..................................................................................................................................................18
Failover Servers.....................................................................................................................................................20
Management Client................................................................................................................................................21
Specify Recording Server Setup Parameters.........................................................................................................21
Install Log Server (Custom).......................................................................................................................................21
Installing Log Server...............................................................................................................................................22
Important Port Numbers............................................................................................................................................23
List of Ports Used by RC-E ....................................................................................................................................23
Multiple Management Servers (Clustering) ...............................................................................................................24
Prerequisites for Installing OnSSI RC-E in a Cluster.............................................................................................. 25
Installing RC-E in a Cluster....................................................................................................................................25
Upgrading RC-E in a Cluster..................................................................................................................................26
Multiple Recording Server Instances.........................................................................................................................26
Installing Multiple Recording Server Instances.......................................................................................................27
Remove System Components ...................................................................................................................................27
Removing Management Server..............................................................................................................................27
Removing Download Manager and Log Server......................................................................................................27
Removing Management Client...............................................................................................................................28
Removing Recording Server..................................................................................................................................28
Upgrade from Previous Version ................................................................................................................................28
Prerequisites ..........................................................................................................................................................28
Upgrading the Management Server .......................................................................................................................29
Upgrading Recording Servers................................................................................................................................29
Upgrading a Management Client............................................................................................................................30
Upgrading Video Device Drivers ............................................................................................................................30
Installation Troubleshooting.......................................................................................................................................30
On-Net Survei
llance Systems, Inc. iii
Page 4
RC-E User Manual
Contents
Issue: Automatic IIS Installation for Mgmt.
Issue: Recording Server Startup Fails due to Port Conflict ....................................................................................31
Issue: Changes to SQL Server Location Prevents Database Access ....................................................................33
Issue: Insufficient Continuous Virtual Memory Fails Installation............................................................................. 33
Issue: Multi-domain Environments; One-way Trusts not Working.......................................................................... 33
.............................................................................................................30
Management Client (RC-E Manager) ....................................................................................................... 34
Management Client (RC-E Manager) Overview........................................................................................................34
Management Client's Elements .............................................................................................................................. 34
Site Navigation Pane and Federated Hierarchy Pane............................................................................................34
Menu Bar................................................................................................................................................................35
Toolbar...................................................................................................................................................................35
Memory Indicator ...................................................................................................................................................35
Panes Overview........................................................................................................................................................36
Menu and Tool Bars...............................................................................................................................................36
Overview Pane.......................................................................................................................................................36
Preview Pane.........................................................................................................................................................36
Properties Pane .....................................................................................................................................................36
Site Navigation Pane and Federated Hierarchy Pane............................................................................................37
Basics........................................................................................................................................................................37
Get Started.............................................................................................................................................................37
Log in to the Management Client ...........................................................................................................................39
Management Client Menu Overview ......................................................................................................................40
Customize the Management Client's Layout..........................................................................................................41
Activate Licenses ...................................................................................................................................................43
Manage Licenses...................................................................................................................................................45
Remote Connect Services.........................................................................................................................................46
About Remote Connect Services ...........................................................................................................................46
Axis One-Click Camera Connection Properties......................................................................................................48
Servers......................................................................................................................................................................49
Add Hardware (Cameras, etc.)...............................................................................................................................49
Manage Hardware..................................................................................................................................................53
About Storage and Archiving..................................................................................................................................56
Manage Recording Servers....................................................................................................................................60
Manage Multicasting ..............................................................................................................................................70
Manage Public Addresses......................................................................................................................................72
Servers and Clients Require Time-Synchronization...............................................................................................73
Devices......................................................................................................................................................................75
About Devices........................................................................................................................................................75
Client.......................................................................................................................................................................108
About Clients........................................................................................................................................................108
Manage View Groups........................................................................................................................................... 108
Rules and Events....................................................................................................................................................109
About Rules and Events.......................................................................................................................................109
Actions and Stop Actions Overview......................................................................................................................110
Create Typical Rules............................................................................................................................................116
Default Rules........................................................................................................................................................126
Events Overview ..................................................................................................................................................128
Manage Rules......................................................................................................................................................133
Manage Time Profiles ..........................................................................................................................................138
Manage Day Length Time Profiles.......................................................................................................................140
Manage Notification Profiles.................................................................................................................................141
Manage User-defined Events...............................................................................................................................143
Security ...................................................................................................................................................................145
About Security......................................................................................................................................................145
About Roles..........................................................................................................................................................145
Manage Roles......................................................................................................................................................147
On-Net Survei
llance Systems, Inc. iv
Page 5
RC-E User Manual
Contents
Manage Vie
System Dashboard..................................................................................................................................................156
About System Dashboard .................................................................................................................................... 156
About System Monitor..........................................................................................................................................156
About Current Task..............................................................................................................................................157
About Configuration Report..................................................................................................................................157
Server Logs.............................................................................................................................................................158
Manage Logs .......................................................................................................................................................158
RC-C .......................................................................................................................................................................162
Manage RC-C Servers.........................................................................................................................................162
Registered Services ................................................................................................................................................165
Manage Network Configuration............................................................................................................................165
Manage Registered Services ...............................................................................................................................165
Important Prerequisites When Running Federated Sites ........................................................................................ 166
Options....................................................................................................................................................................168
Options................................................................................................................................................................. 168
AVI Compression Settings ...................................................................................................................................170
Outgoing SMTP Mail Server Settings................................................................................................................... 171
Manage Local IP Address Ranges.......................................................................................................................171
w Groups...........................................................................................................................................154
OnSSI Federated Architecture............................................................................................................... 173
OnSSI Federated Architecture Overview.................................................................................................................173
Licensing of OnSSI Federated Architecture.........................................................................................................173
Basic Rules of Federated Sites............................................................................................................................ 174
Principles for Setting Up Federated Sites.............................................................................................................174
The Administrator Role and Federated Sites .......................................................................................................174
Possibilities and Constrains of Federated Sites ...................................................................................................175
Frequently Asked Questions to Federated Sites..................................................................................................175
Federated Sites Example Scenario—Limestone City........................................................................................... 177
Manage OnSSI Federated Architecture ..................................................................................................................177
Expand/Collapse..................................................................................................................................................178
Site Navigation Pane............................................................................................................................................178
Right-clicking is not Selecting!..............................................................................................................................178
Context Menu.......................................................................................................................................................178
Adding a Site to the Hierarchy..............................................................................................................................178
Accepting Inclusion in the Hierarchy ....................................................................................................................179
Connecting to Another Site in the Hierarchy ........................................................................................................180
Detaching a Site from the Hierarchy.....................................................................................................................180
Refreshing the Site Hierarchy .............................................................................................................................. 181
Renaming a Site...................................................................................................................................................181
Setting the Site Properties....................................................................................................................................181
Backup, Restore and Move System Configuration.............................................................................. 183
Scheduled Backup & Restore of System Configuration ..........................................................................................183
Flushing the SQL Server Transaction Log ...........................................................................................................183
Prerequisites ........................................................................................................................................................183
Scheduled Back Up of System Configuration.......................................................................................................183
Backing Up Log Server Database........................................................................................................................ 184
Restoring System Configuration (From Scheduled Back Up)...............................................................................184
Manual Backup & Restore of System Configuration................................................................................................185
Select Shared Backup Folder...............................................................................................................................185
Manual Back Up of System Configuration............................................................................................................185
Restoring System Configuration (From Manual Back Up).................................................................................... 186
Move System Configuration to New Management Server.......................................................................................186
Copying System Configuration from Old Server (Step 1).....................................................................................188
What Happens while the Management Server Is Unavailable?............................................................................188
Copying Log Server Database.............................................................................................................................188
Installing New Management Server on New Server (Step 2)...............................................................................189
On-Net Survei
llance Systems, Inc. v
Page 6
RC-E User Manual
Contents
Copying/Restoring System Configuration to New Server (Step 3).......................................................................189
Device Drivers.......................................................................................................................................... 190
Manage and Remove Video Device Drivers............................................................................................................190
Making New Video Device Driver Versions Available for Installation ...................................................................190
Installing Video Device Drivers.............................................................................................................................190
Removing Video Device Drivers...........................................................................................................................190
Failover Servers....................................................................................................................................... 191
Failover Server Service Administration ................................................................................................................... 191
Starting and Stopping the Failover Server Service...............................................................................................191
Changing the Management Server Address ........................................................................................................191
Viewing Status Messages....................................................................................................................................191
Viewing Version Information.................................................................................................................................192
Manage Failover Servers ........................................................................................................................................192
Installing Failover Servers....................................................................................................................................193
Adding and Grouping Failover Servers ................................................................................................................193
Enabling Failover Servers....................................................................................................................................194
Editing Failover Server Properties........................................................................................................................194
Assigning Failover Servers to Recording Servers................................................................................................195
Frequently Asked Questions................................................................................................................................195
Failover-Related Events.......................................................................................................................................196
Database Corruption............................................................................................................................... 197
Protect Databases from Corruption......................................................................................................................... 197
Power Outages: Use a UPS ................................................................................................................................. 197
Windows Task Manager: Be Careful when Ending Processes.............................................................................197
Hard Disk Failure: Protect Your Drives.................................................................................................................197
Services Administration ......................................................................................................................... 198
Management Server Service and Recording Server Service ..................................................................................198
Accessing the Server Service .............................................................................................................................. 198
Starting the Server Service ..................................................................................................................................198
Stopping the Server Service.................................................................................................................................198
Changing Recording Server Settings...................................................................................................................199
Viewing Status Messages....................................................................................................................................199
Viewing Version Information.................................................................................................................................199
Work with Recording Server Settings in details....................................................................................................199
Virus Scanning ........................................................................................................................................200
Virus Scanning Information .....................................................................................................................................200
SNMP ........................................................................................................................................................ 201
SNMP Support ........................................................................................................................................................201
Installing the SNMP Service.................................................................................................................................201
Configuring the SNMP Service.............................................................................................................................201
Daylight Saving Time.............................................................................................................................. 202
Daylight Saving Time .............................................................................................................................................. 202
Spring: Switch from Standard Time to DST..........................................................................................................202
Fall: Switch from DST to Standard Time..............................................................................................................202
Contact Information ................................................................................................................................ 203
On-Net Surveillance Systems, Inc. vi
Page 7
RC-E User Manual Introductions
Introductions
Product Overview, RC-E
The RC-E recorder, part of Ocularis ES, is a fully distributed solution, designed for large multi-site and multiple server installations requiring 24/7 surveillance, with support for devices from different vendors. The solution offers centralized management of all devices, servers, and users, and empowers an extremely flexible rule system driven by schedules and events.
While Ocularis contains multiple components, RC-E also contains its own components. RC-E consists of the following main elements:
 The management server - the center of your installation (RC-E Server) One or more recording servers (RC-E Recorder)  One or more Management Clients (RC-Manager),which are unlicensed and can be downloaded and installed for
free (as many times as needed).
A Download Manager Finally, RC-E handles an unlimited number of cameras, servers, and users—across multiple sit es if req uire d.
About Updates
OnSSI regularly release service updates for our products, offering improved functionality and support for new devices. If you are an RC-E system administrator, it is recommended that you check the OnSSI website for updates at regular
intervals in order to make sure you are using the most recent version of RC-E.
The RC-E Server (Management Server)
What? Stores the surveillance system's configuration in a relational database, either on the management server
computer itself or on a separate SQL Server on the network. Also handles user authentication, user rights, etc. To enhance system performance, several management servers can be run under OnSSI Federated Archite cture (see "OnSSI Federated Architecture Overview" on page 173).
W
here? Runs as a service, and is typically installed on a dedicated serve r .
What is provided with the management server? When installing the management server if you select Typical
Management Server Installation (see "Typical" on page 16), you will also install:
T
he log server
o What? Provides the necessary functionality for logging information from your RC-E installation. o Where? Usually installed on the same server as the management server and runs as a service.
On-Net Survei
llance Systems, Inc. 7
Page 8
RC-E User Manual Introductions
The RC-E Recording Server
What? Used for recording video and for communicating with cameras and other devices. In large installations, more
than one recording server is often used on the surveillance system. Failover servers can be set up to take over if a recording server becomes temporarily unavailable.
Where? Recording servers as well as failover servers run as services, and are typically installe d on separate servers rather than on the management server itself.
The Management Client (RC-E Manager)
What? Feature-rich administration client for configuration and day-to-day management of the system. Available in
several languages.
Where? Typically installed on the surveillanc e system administrator's workstation or similar.
The Download Manager
What? Lets surveillance system administrators manage which RC-E -related components your organization's users
will be able to access from a targeted web page generated by the management server. Where? Automatically installed on the management server during RC-E i nstall ation process.
On-Net Surveillance Systems, Inc. 8
Page 9
RC-E User Manual Introductions
System Requirements
IMPORTANT: RC-E no longer supports Microsoft® Windows® XP (however, clients can still be run/accessed from computers with Windows XP Professional).
It is recommended to have the Microsoft Active Directory install RC-E. If you add the management server to the Active Directory after installing RC-E, you must re-install the management server, and replace users with new users defined in the Active Directory.
The following are minimum requirements for the computers used in an RC-E solution:
Computer Running Management Server
CPU: Intel® Xeon® , minimum 2.0 GHz (Dual Core recommended)  RAM: Minimum 1 GB (2 GB or more recommended)  Network: Ethernet (1 Gbit recommended)  Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024 x 768, 16-bit color
(see "
Manage Users and Groups
" on page 145)®
in place before you
Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)  Hard Disk Space: Minimum 50 GB free (depends on number of servers, cameras, rules, and logging settings)  Operating System: Microsoft
®
Windows® Server 2008 R2 (64 bit), Microsoft® Windows® Server 2008 (32 or 64
bit), Microsoft® Windows® Server 2003 (32 or 64 bit).
®
Furthermore, to run clustering/failover servers, a Microsoft
Windows® Server 2003/2008 Enterprise or Data
Center edition is needed.
Software: Microsoft .NET 3.5 SP1 and .NET 4.0 and Internet Information Services (IIS) 5.1 or newer.
Computer Running Recording Server or Failover Server
CPU: Dual Core Intel Xeon, minimum 2.0 GHz (Quad Core recommended)  RAM: Minimum 1 GB (2 GB or more recommended)  Network: Ethernet (1 Gbit recommended)  Graphics Adapter: Onboard GFX, AGP, or PCI-Express, minimum 1024 x 768, 16-bit color  Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)  Hard Disk Space: Minimum 100 GB free (depends on number of cameras and recording settings)  Operating System: Microsoft
64 bit), Microsoft Microsoft Windows Windows
® ® ®
®
Windows® 7 Professional (32 bit or 64 bit), Microsoft® Windows® Server 2008 R2 (64 bit), Windows® Server 2008 (32 or 64 bit), Microsoft® Windows® Vista® Business (32 or 64 bit), Microsoft® Vista Enterprise (32 or 64 bit), Microsoft® Windows® Vista Ultimate (32 or 64 bit) or Microsoft® Server 2003 (32 or 64 bit).
®
Windows® 7 Ultimate (32 bit or 64 bit), Microsoft® Windows® 7 Enterprise (32 bit or
Software: Microsoft .NET 4.0 Framework.
On-Net Survei
llance Systems, Inc. 9
Page 10
RC-E User Manual Introductions
IMPORTANT: When formatting the hard disk of a recording/failover server device, it is important to change its
Allocation unit size setting from 4 to 64 kilobytes. This is to significantly improve recording performance of the hard disk. You can read more about allocating unit sizes and find help at http://support.microsoft.com/kb/140365/en-us (see http://support.microsoft.com/kb/140365/en-us - http://support.microsoft.com/kb/140365/en-us).
Computer Running Management Client
CPU: Intel Core2TMTM Duo, minimum 2.0 GHz  RAM: Minimum 1 GB  Network: Ethernet (100 Mbit or higher recommended)  Graphics Adapter: AGP or PCI-Express, minimum 1024 x 768 (1280 x 1024 recommended), 16-bit color  Hard Disk Space: Minimum 100 MB free  Operating System: Microsoft
bit or 64 bit*), Microsoft bit*), Microsoft bit*), Microsoft Microsoft
®
Windows® Vista Enterprise (32 bit or 64 bit*), Microsoft® Windows® Vista Business (32 bit or 64
®
Windows® Server 2008 (32 bit or 64 bit*), Microsoft® Windows® Server 2008 R2 (64 bit) or
®
Windows® Server 2003 (32 bit or 64 bit*).
* Running as a 32 bit service/application
®
®
Windows® 7 Professional (32 bit or 64 bit*), Microsoft® Windows® 7 Enterprise (32
Windows® 7 Ultimate (32 bit or 64 bit*), Microsoft® Windows® Vista Ultimate (32 bit or 64
Software: Microsoft .NET 4.0 Framework, DirectX 9.0 or newer, and Windows Help (WinHlp32.exe) which you
can download from http:// www.microsoft.com/downloads/ (see http://www.microsoft.com/downloads/ - http://www.microsoft.com/downloads/).
Computer Running Log Server
CPU: Intel® Xeon® , minimum 2.0 GHz (Dual Core recommended)  RAM: Minimum 1 GB (2 GB or more recommended)  Network: Ethernet (1 Gbit recommended)  Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024 x 768, 16-bit color  Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)  Hard Disk Space: Minimum 10 GB free (depends on number of servers, cameras, rules, and logging settings)  Operating System: Microsoft
®
Windows® Server 2008 R2 (64 bit), Microsoft® Windows® Server 2008 (32 or 64
bit), Microsoft® Windows® Server 2003 (32 or 64 bit)
Software: Microsoft .NET 4.0 and Internet Information Services (IIS) 5.1 or newer.
Active Directory
OnSSI RC-E users are normally added from Active Directory, although users can also be added without Active Directory.
Active Directory is a distributed directory service included with several Windows Server operating systems; it identifies resources on a network in order for users or applications to access them.
On-Net Survei
llance Systems, Inc. 10
Page 11
RC-E User Manual Introductions
If wishing to add users through the Active Directory service, a server with Active Directory installed, and acting as domain controller, must be available on your network.
Navigating the Built-in Help System
You are always able to freely navigate between the help system's contents. T o do this, simply use the help window's three tabs: Contents, Search, and Glossary, or use the links inside the help topics.
Contents Tab: Lets you navigate the help system based on a tree structure. Many users will be familiar with this
type of navigation from, for example, Windows Explorer. To go straight to the help system's Contents tab, click Contents... button in the Management Client's toolbar.
Search Tab: Lets you search for help topics containing particular terms of interest. For example, you can search
for the term zoom a nd every help topic containing the term zoom will be listed in the search results. Clicking a help topic title in the search results list will open the required topic. To go straight to the help system's Search tab, click the Search... button in the Management Client's toolbar.
The actual content of each help topic is displayed in the right pane of the help window. Help topic texts may contain various types of links, notably so-called expanding drop-down links.
Clicking an expanding drop-down link will display detailed information. The detailed information will be displa yed immediately below the link itself; the content on the page simply expands. Expanding drop-down links thus help save space.
To print a help topic, navigate to the required topic and click the browser's Print button.
Tip: When printing a selected help topic, the topic will be printed as you see it on your screen. Therefore, if a topic
contains expanding drop-down links, click each required drop-down link to display the text in order for it to be included in your printout.
On-Net Surveillance Systems, Inc. 11
Page 12
RC-E User Manual Installation and Removal
Installation and Removal
Installation Overview
If upgrading from a previous version of RC-E , make sure you read the upgrade information (see "Upgrade from Previous Version" on page 28).
If you plan to run OnSSI Federated Architecture (on page 173), make sure to read about important prerequisites. Your RC-E installation process begins with the installation of the management server software.
The management server is the center of your RC-E installation. It is typically installed on a dedicated server.
See Management Server Installation (see "Install Management Server" on page 13).
Once the man The recording server, which is used for recording video feeds, and for communicating with cameras an d other
devices. The recording server is typically installe d on o ne or more separate computers, rather than on the management server itself. See Install System Components (on page 17).
agement server is installed, you are able to install key components required by the management serve r :
T
he management client, also known as the RC-E Manager, which is used for configuration and day-to-day management of the system. The Management Client is typically installed on the system administrator's workstation or similar. See Management Client Installation (see "Management Client" on page 21).
Tip: Video devi
ng the initial installation of your RC-E system. However, new versions of the drivers are released from regularly
duri
ce drivers (see "Manage and Remove Video Device Drivers" on page 190) are installed automatically
and may be found on the OnSSI website.
As well on traditional servers, installation can also take place on virtualized servers.
Installing RC-E on Virtual Servers
As mentioned, it is possible to run all RC-E components on virtualized Windows® servers, such as - for example ­VMware
Tip: Virtualization is often preferred to better utilize hardware resources. Normally, virtual servers running on the hardware host server do not load the virtual server to a great extent, and often not at the same time. However, RC-E recording servers record all cameras and streaming video. This puts high load on CPU, memory, net work, and storage system. Thus when run on a virtual server, the normal gain of virtualization disappears to a large extent, since
- in many cases - it will use all available resources. If run in a virtual environment, it is important that the hardware host has the same amount of physical memory as
allocated for the virtual servers and that the virtual server running the recording server is alloc ated enough CPU and memory - which it is not by default. Typically, the recording server needs 2-4 GB depending on configuration. Another bottleneck is network adapter allocation and hard disk performance. Consider allocati ng a physical network adapter on the host server of the virtual server running the recording server. This makes it easier to ensure that the network adapter is not overloaded 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 amount of images.
®
and Microsoft Hyper-V®. Contact your IT department for more information.
On-Net Survei
llance Systems, Inc. 12
Page 13
RC-E User Manual Installation and Removal
Install Management Server
If upgrading from a previous version of RC-E, make sure you read the upgrade information (see "Upgrade from Previous Version" on page 28).
If you plan to run OnSSI Federated Architecture, make sure to read about important prerequisites for running OnSSI Federated Architecture (see "OnSSI Federated Architecture Overview" on page 173).
Read the End User License Agreement on the Product License Sheet (enclosed with the software DVD) before installing any part of RC-E.
Your RC-E installation process begins with the installation of the RC-E management server software. The management server is the center of your OnSSI RC-E installation.
Prerequisites
Windows Installer 4.5 - only on Windows Server 2003
Before installing RC-E, it is important that you install Windows Installer 4.5. You can download the Windows Installer 4.5 (see http://www.microsoft.com/downloads - http://www.microsoft.com/do http://www.microsoft.com/downloads (see http://www.microsoft.com/downloads/ - http://www.microsoft.com/downloads/).
wnloads) from this link:
SQL Serv
er
The management server requires access to a relational database. Later in this install atio n process you must choose between using an existing SQL Server on the network (Administrator rights on the SQL Server are required) or setting up a SQL Server Express Edition (a lightweight, yet powerful, version of a full SQL server) on the management server computer itself.
Whichever SQL solution you choose, make sure to have Microsoft .NET Framework 3.5 Service Pack 1 installed on the management server computer running the SQL Server Express Edition (even though Microsoft .NET Framework 4.0 is already installed) or the separate server running the existing SQL Server. See also System Requirements (on page 9).
Which SQL Server type is right for our organization? The SQL Server Express Edition is easy to install and prepare for use, and will often suffice for systems with less than 500 cameras. However, if you plan to perform frequent/regular backups of your database, using an existing SQL Server on the network is recommended (Administrator rights on the SQL Server are required). For large installations, such as installations with 500 cameras or more, using an existing SQL Server on the network is always recommended.
Windows Server 2003 Fix
If you use Windows Server 2003 it is recommended to install this supported fix (see http://support.microsoft.com/kb/925336 - http://support.microsoft.com/kb/925336) for Windows Server 2003 before starting:
http://support.microsoft.com/kb/925336 (see http://support.microsoft.com/kb/925336 ­http://support.microsoft.com/kb/925336). Otherwise, the installation of your management server might fail due to Microsoft Windows Installer process having insufficient contiguous virtual memory to verify that the .msi package or the .msp package is correctly signed.
The following steps assume that Ocularis Base has already been installed and licensed and the Base Component Installation web page is accessible from the machine where the RC-E Manageme nt Server is to be installed.
On-Net Survei
llance Systems, Inc. 13
Page 14
RC-E User Manual Installation and Removal
Installing
1. Shut down any OnSSI software running. If upgrading, it is highly recommended that you remove any previous versions of the management server before upgrading. Note, however, that you may not want to remove the management server database, as it contains your RC-E configuration.
2. From the Base Component install page, (http://<IP Address of Base machine>/OcularisService/InstallerWebsite/sysadmin.html), click the link for the RC-E Event Proxy and Recorder bundle.
3. Choose to 'Run' the executable.
4. When the download and security scan is complete, an 'Installation Wrapper' wizard screen appears. This wizard prompts you for a location to extract the installation files only. Verify or change the location (drive and directory) to place the installation file and click Next.
5. Once the files are extracted, you will see a screen with checkboxes to Install RC-E Event Proxy and RC-E Recorder.
You may elect to install one, the other or both. In new and upgrade installations it is recommended to always install the Event Proxy. This installation will check the system for an existing proxy and, if found, will walk you through the process of uninstalling the old proxy and installing the new one. For the Recorder, this refers to the RC-E recorder components as a whole. For new installations, this box should be checked. For upgra de installations, see the Release Notes for special upgrade instructions.
6. Click Finish.
7. Follow the wizard prompts for the Event Proxy installation (if that checkbox was marked).
8. After the Event Proxy is installed, the RC-E Management Server files are extracted and a screen appears listing the steps involved in the installation:
9. Complete the steps outlined in the window.
Tip: Depending on what is already installed on the computer which is goi ng to act as management server, you may not need to complete all of the window's three steps. The step that currently requires your attention will be highlighted.
Tip: When the management server software is installed, you are able to check the state of the management server by looking at the management server icon in the management server computer's notification area.
See Management Server Service and Recording Server Service (on page 198) for more information.
Step 1: Internet Information Services
The RC-E Management Server Installation automatically detects if Internet Information Services (IIS) is already installed. If this step is not available, it is simply because IIS is already installed.
Internet Information Services includes a range of administrative features for managing web servers and web applications, and is required in order to run an OnSSI RC-E management server.
If installing on a server running Windows 2008 Server, IIS is automatically installed once you click the Internet Information Services step (should automatic installation fail, it is possible to do installation troubleshooting (on pag e
30)).
1.
On Windows Server 2003, clicking the Internet Information Services step opens Windows' built-in Windows Components wizard:
2. In the wizard's Components list, select Application Server.
On-Net Survei
llance Systems, Inc. 14
Page 15
RC-E User Manual Installation and Removal
Click Deta
ils... and select Internet Information Services (IIS).
3. Click Details... and verify that all IIS subcomponents are selected. Click OK to return to the Windows Components wizard.
4. In the Windows Components wizard, click Next and follow the wizard.
Tip: It is a good idea to have your Windows installation DVD ready; it may be required during the process.
When IIS is installed, you will be returned to the RC-E Management Server Installation window for the next step of the installation.
Step 2: RC-E Management Server Database
Before completing this step, click the View Microsoft SQL Server 2008 Express End-user License Agreement link to read the license agreement for the software.
This step opens the Database Setup wizard, which will guide you through the process of preparing a database for use with the management server.
In the Database Setup wizard you will get the choice of using an existing SQL Server on the network or setting up a SQL Server Express Edition (a lightweight, yet powerful, version of a full SQL server) on the management server computer itself.
Follow the wizard's steps by clicking Next. IMPORTANT: We recommend that you install the database on a dedicated hard disk drive that is not used for
anything else but the database. Installing the database on its own drive will prevent low disk performance. IMPORTANT: During the database preparation process, you will be asked whether you want to create a new
database, use an existing database, or overwrite an existing database. For a new installation, you would typically select the default option Create new database. However, if you are installing the database as part of upgrading to a newer version of RC-E, and you want to use your existing database, make sure you select Use existing database .
When you have prepared the database, you will be returned to the OnSSI RC-E Management Server Installation window for the last step in the management server installation.
Step 3: RC-E Management Server
This step opens a wizard, which will guide you through the process of installing th e management server software itself.
Follow the wizard's steps by clicking Next.
Tip: The wizard will ask you to specify the location of your temporary license (.lic) file. The system will verify your license file before you are able to continue. Therefore, have your license file ready.
On one of the wizard's steps, you will be asked to select between two installation options:
Typical (on page 16)
-or­Custom (on p
You ma
y install the log server as part of the management server installation. But if required you can just as well install
this on another server in your surveillance system: Installing the log server (see "Install Log Server (Custom)" on page 21) provides the necessary functionality for
ging information from your RC-E installation.
log
On-Net Survei
llance Systems, Inc. 15
age 16)
Page 16
RC-E User Manual Installation and Removal
Typical
If you select Typical installation, the wizard will install all the management server components at their default location and with other default settings. A Typical installation is recommended for most users.
Custom
If you select Custom installation, you get the option to select where to install each individual managem ent server component. A Custom installation is recommended for advanced users.
Only relevant if selecting Custom installation: On one of the wizard's steps you will be asked to select an IIS (Internet Information Services) web site for the
Management Server service. Select one of the listed web sites, and make sure the selected web site is started, then click Next. If the selected web
site is not started, Next is disabled.
Tip: You may find that only a single IIS web site—the Default Web Site—is listed. In that case simply make sure that the web site is started, then click Next.
Towards the end of the wizard, in the Service Log On Setup window, you will be asked to select a user account under which the Management Server service will run:
You will be able to select either a: predefined Network Service account (see "Select a Predefined Account; Network Service" on page 16) (in which
case the servic
e will run whenever the computer acting as management server is running).
- or -
particular user account (see "Select a Particular User Account" on page 16) (in which case the service will use
the specified user account to log in to the computer acting as management server).
Tip: If the computer acting as management server is a member of a domain, you should either select Network Service, or make sure that you specify a user account which belongs to the domain in qu estion.
Select a Predefined Account; Network Service
1. Select This predefined account.
2. Select Network Service.
3. Click OK.
Select a Particular User Account
1. Select This account.
2. Click Browse.... This will open the Select User window.
3. In the Select User window, verify that the required domain is specified in the From this location field. If not, click Locations... to browse for the required domain.
4. In the Enter the object names to select box, type the required user name.
Tip: Typing part of a name is often enough. Use the Check Names feature to verify that the name you have entered is recognized.
5. Click OK.
On-Net Survei
llance Systems, Inc. 16
Page 17
RC-E User Manual Installation and Removal
Specify the password for the user account in the Password field, and confirm the password in the Confirm
6. password field.
The password fields must not be empty; the password for the account must contain one or more characters and/or digits.
7. Click OK.
What's Next?
Upon installation of the management server software, the management server's built-in web page automatically opens in a browser. The web page lets you install key components required by the management server, among these:
One or more recording servers (for recording video feeds and for communicating with cameras and other
devices)
A Management Client (for configuration and day-to-day management of the system) Even though the web page opens automatically on the management server computer, you will in most cas es want to
install the key components on other computers than the management server itself. This is no problem since installation takes place through the web page, which can easily be accessed from other computers. See Install System Components (on page 17) for further information.
Install System Components
If upgrading from a previous version of RC-E, make sure you read the upgrade information (see "Upgrade from Previous Version" on page 28).
Installation of the following components is not covered in this section: log server (see "Install Log Server (Custom)" on page 21) and management server (see "Install Management Server" on page 13). See installation details for each.
Read the End User License Agreement on the Product License Sheet before installing any part of OnSSI RC-E. IMPORTANT: As a prerequisite make sure of the following: During the installation process you will be asked to
specify a user account under which the Failover Server service will run. For the failover solution to work, the failover server has to use the same user account as the recording server. Furthermore, the user account you specify must have access to your RC-E system with administrator rights. Do the following to make sure of this...
To verify whether the user account has administrator access to your OnSSI RC-E system, do the following:
1. In the Management Client's Site Navigation pane, expand Security and select Roles. In the overview pane's roles list, select the Administrators role.
2. In the properties pane's role settings list, verify that the required user is listed.
3. If the user is not listed, add the required user (see "Assign and Remove Users and Groups to/from Roles" on e 149) to the Administrators role b
pag
Part I—Downloading the Installer
y clicking Add... below the role settings list.
The following describes the installation process. The process is more or less similar for the component types mentioned, so replace the component wit h the OnSSI RC-E recording server, failover server or the Management Client, depending on your needs.
On-Net Survei
llance Systems, Inc. 17
Page 18
RC-E User Manual Installation and Removal
On the computer on which you will install the component, shut down any OnSSI software running. If
1. upgrading, it is highly recommended that you remove (see "Remove System Components" on page 27) any previous versions of the component before upgrading.
2. With a web browser, connect to the RC-E management server at the following address: http://[management server address]:[port]/installation/admin/ where [management server address] is the IP address or host name of the management server, and [port] is
the port number which IIS has been set up to use on the management server. This will open the management server's built-in web page. If not accessing the web page on the management
server itself, log in with an account which has administrator rights on the management server.
3. On the web page find the relevant component's installer section, and then click the English link under the required recording server version (often, only one version will be available).
Depending on your security settings, one or more Windows security warnings ma y appear after you click the link. If such security warnings appear, accept security warnings by clicking Run or similar (exact button text depends on your browser version).
Part II—Installing the Component
Select the relevant component for a description of the process (if required, repeat the process on other computers where the component should be installed):
Recording Servers
1. This will open the RC-E Recording Server Setup wizard, which will guide you through the install ation. On the first step of the wizard, click Next.
2. Select installation method: Typical (see "Recording servers (Typical)" on page 18)
- or - Custom (see "Recording servers (Custom)" on page 19)
3. Click Install.
4. On the last step of the wizard, click Finish. The recording server is now installed. The recording server has no user interface as such; it is accessed and managed through the Management Client.
Tip: When the recording server software is installed, you are able to check its state.
See Management Server Service and Recording Server Service (on page 198) for more information.
Recording servers (Typical)
The Typical option installs the RC-E recording server with default settings. A Typical installation is recommended for most users.
1. Specify recording server setup parameters (see "Specify Recording Server Setup Parameters" on page 21).
2. Click Next.
On-Net Survei
llance Systems, Inc. 18
Page 19
RC-E User Manual Installation and Removal
Recording servers (Custom)
The Custom option lets you select where to install the RC-E recording server components. A Custom installation is recommended for advanced users.
1. Select required installation folder, then click Next.
2. When asked which type of server to install, click the Standard recording server [...] icon. This lets you install a regular recording server.
3. Specify recording server setup parameters.
4. Click Next.
5. The wizard will ask you to select a user account under which the Recording Server service will run. You must select between: o a predefined system account (see "Select a Predefined System Account" on page 19)
- or ­a particular user account (see "Select a Particular User Account" on page 20) (in which case the service
o
will use the specified user account to log in to the computer acting as recording server).
Tip: If the computer acting as recording server is a member of a domain, select the predefined account Local System or make sure you specify a user account which belongs to the domain in questio n.
If using network drives, you should always specify a particular user account (which has access to the network drives in question), as the Recording Server service will not be able handle the network drives otherwise.
6. Click Next.
7. In some cases it can be advantageous to install more than one instance of the recording server on the same physical server (see "Multiple Recording Server Instances" on page 26). Specify the required num ber of
es (default is 1), then click Next.
instanc o Only relevant if installing more than one instance of the recording server on the same physical server:
For each instance, specify the IP address to use for the instance in question. IMPORTANT: Note that the IP addresses you specify must be assigned to the physical server in
question. Furthermore, even though your organization will not use IPv6 addresses, make sure to assign both IPv6 and IPv4 on the server as these are needed by the software.
Tip: Provided enough IP addresses are assigned to the server, the fields will be pre-filled.
8. Click Next.
Select a Predefined System Account
1. Select This predefined account.
2. Select Local System, Local Service, or Network Service as applicable.
3. Click OK.
On-Net Survei
llance Systems, Inc. 19
Page 20
RC-E User Manual Installation and Removal
Select a Particular User Account
1. Select This account.
2. Click Browse.... This will open the Select User window.
3. In the Select User window, verify that the required domain is specified in the From this location field. If not, click Locations... to browse for the required domain.
4. In the Enter the object names to select box, type the required user name.
Tip: Typing part of a name is often enough. Use the Check Names feature to verify that the name you have entered is recognized.
5. Click OK.
6. Specify the password for the user account in the Password field, and confirm the password in the Confirm password field.
The password must contain one or more characters and/or digits.
7. Click OK.
Failover Servers
1. This will open the RC-E Recording Server Setup wizard, which will guide you through the i nstallation On the first step of the wizard, click Next.
2. Select installation method Custom.
3. Select required installation folder, and then click Next.
4. When asked which type of server to install, click the Failover recording server for temporary [...] icon.
5. Specify failover server setup parameters (see "Specify Recording Server Setup Param eters" on page 21).
6. Click Next. A failover server has two services:
7.
o A Failover Server service, which handles the processes of taking over from the regular recording server. o A Recording Server service, which enables the failover server to act as a recording server while the
regular recording server is unavailable.
The wizard will ask you to select a particular user account under which the services will run. Make your selection.
See Select a Particular User Account... (see "Select a Particular User Account" on page 20) for how to select. For the failover solution to work, the user account you specify must have access to your RC-E system with
administrator rights. If the computer acting as failover server is a member of a domain, make sure you specify a user account which belongs to the domain in question. If using network drives, always specify a user account which has access to the network drives in question.
8. Click Install.
9. On the last step of the wizard, click Finish. The failover server is now installed. The failover server has no user interface as such; it is accessed and managed through the Management Client.
On-Net Survei
llance Systems, Inc. 20
Page 21
RC-E User Manual Installation and Removal
Tip:
When the failover server software is installed, you are able to check its state. See Management Server Service
and Recording Server Service (on page 198) for more information.
Management Client
1. In the Select installer language drop down box, select language to use during the installation. In this example, we assume that you prefer English.
2. Next to appear is the RC-E Management Client Setup wizard, which will guide you through the installation process. On the first step of the wizard, click Next.
3. Select required installation folder, then click Next.
4. Click Install to begin installation; wait while the required components are installed.
5. When ready, click Finish.
6. To get an overview of the Management Client (see "Management Client Overview" on page 34), select
nch RC-E Management Client. This will start the Management Client (RC-E Manager) right away.
Lau
Specify Recording Server Setup Parameters
Name: A name for the server in question. If required, you can later change the name through the RC-E
Management Client.
RC-E management server: The IP address (example: 123.123.123.123) or host name (example: ourserver) of
the management server to which the server in question should be connected. If required, you can later change the management server IP address/host name as part of the basic administration on the Recording or Failover Server service.
MediaDB: The path to the server in question's media database. The media database is the recording server's
default storage area, i.e. the default location in which recordings from connected cameras are stored in individual camera databases. If required, you can later change the path, and/or add paths to more storage area locations, from the RC-E Management Client.
When should I choose a particular user account instead of a predefined? If using network drives you should always specify a particular user account (with access to the network drives in questi on). Otherwise the service in question is unable to handle the required network drives.
Install Log Server (Custom)
If upgrading from a previous version of RC-E , make sure you read the upgrade information (see "Upgrade from Previous Version" on page 28).
Installation of the following components are not covered in this section: recording servers, failover servers, Management Client (see "Install System Components" on page 17), and management server (see "Install Management Server" on page 13). See installation details for each.
Read the End User License Agreement on the Product License Sheet (enclosed with the software DVD) before installing any part of RC-E.
Normally, the log server is installed as part of the Management Server Installation (see "Install Management Server" on pa
ge 13), when installed with the Typical
log server , when these are not installed as part of the Typical management server installation. The log server can be installed either on the management server or on any other computer.
option. The following describes how to make a custom installation of the
On-Net Survei
llance Systems, Inc. 21
Page 22
RC-E User Manual Installation and Removal
Make sure that
user rights are set up correctly in the operating system. You can read about user rights in the operating system on Microsoft's web site_(http://technet.microsoft.com/en-us/library/cc794944(WS.10).aspx (see http://technet.microsoft.com/en-us/library/cc794944(WS.10).aspx - http://technet.microsoft.com/en­us/libr
ary/cc794944(WS.10).aspx).
Installing Log Server
The following describes the installation process (custom Installation).
1. On the computer on which you will install the log server, shut down any OnSSI software running. If upgrading, it is highly recommended that you remove (see "Remove System Components" on page 27) any previous versions of the server before upgrading.
2. Download the log server's installer from the management server's built-in web page at the address http://[management server address]:[port]/installation/admin/ where [management server address] is the IP address or host name of the management server, and
[port] is the port number which IIS has been set up to use on the management server. On the web page find the log servers' installer section, and then click the English link. Note that
depending on your security settings, one or more Windows security warnings ma y appear after you click the link. If such security warnings appear, accept security warnings by clicking Run or similar (exact button text depends on your browser version).
3. Run the installation file, either directly or from the location you saved it to. Follow the on-screen installation
guide.
4. Verify/specify the required installation path and click Next.
5. Log Server:
o Select the database to be used by the log server and click Next. o Select the web site on which you want to install and click Next. o Specify the URL address of the RC-E management server (example: http://123.123.123.123). If installing
the server on the management server itself, simply specify localhost and click Next.
6. Specify a user account under which the log server's service will run. The specified user is automatically
granted administrator rights in RC-E, see Specify the Rights of a Role (see "Specify Rights of a Role" on
e 150).
pag You must sele
ct between:
o a predefined Network Service account (see "Select a Predefined Network Service Account" on pa ge
23)(in which case the service will run whenever the comput
er acting as management server is running).
-or -
o a particular user account (see "Select a Particular User Account" on page 23) (in which case the service
will use the specified user account to log in to the computer acting as recording server).
When should I choose a particular user account instead of a predefined? If using network drives you should always specify a particular user account (with access to the network drives in que s tion). Otherwise the service in question is unable to handle the required network drives.
7. Click Install. When installation is complete, click Finish.
On-Net Survei
llance Systems, Inc. 22
Page 23
RC-E User Manual Installation and Removal
Select a Predefined Network Service Account
1. The Network Service account is selected by default.
2. Click OK.
The Network Service account must be added as a Windows user on the relevant recording server computers in your surveillance system in order to retrieve status information from these recording servers.
Select a Particular User Account
1. Select This account.
2. Click Browse.... This will open the Select User window.
3. In the Select User window, verify that the required domain is specified in the From this location field. If not,
click Locations... to browse for the required domain.
4. In the Enter the object names to select box, type the required user name.
Tip: Typing part of a name is often enough. Use the Check Names feature to verify that the name you have entered is recognized.
5. Click OK.
6. Specify the password for the user account in the Password field, and confirm the password in the Confirm
password field. The password must contain one or more characters and/or digits.
7. Click OK.
Important Port Numbers
OnSSI RC-E uses particular ports when communicating with other computers, cameras, etc.
What is a port? A port is a logical endpoint for data traffic. Networks use different ports for different types of data traffic. Therefore it is sometimes, but not always, necessary to specify which port to use for particular data communication. Most ports are used automatically based on the types of data included in the communication. On TCP/IP networks, port numbers range from 0 to 65536, but only ports 0 to 1024 are reserved for particular purposes. For example, port 80 is used for HTTP traffic which is used when viewing web pages.
When using RC-E, you must therefore make sure that certain ports are open for data traffic on your network. The port numbers can be changed. Different port numbers may therefore be used in your organization. See
Management Server Service and Recording Server Service (on page 198) for information about changing the recording server-related port numbers.
Tip: Consult the administrator of your organization's firewall if in doubt about how to open ports for traffic.
List of Ports Used by RC-E
Port 20 and 21 (inbound and outbound): Used by recording servers to listen for FTP information; some devices
use FTP for sending event messages. FTP (File Transfer Protocol) is a sta ndard for exchanging files across networks.
On-Net Survei
llance Systems, Inc. 23
Page 24
RC-E User Manual Installation and Removal
Port 2
5 (inbound and outbound): Used by recording servers to listen for SMTP information. Also, some devices
use SMTP (e-mail) for sending event messages and /or for sending images to the surveillance system server via e­mail. SMTP (Simple Mail Transfer Protocol) is a standard for sending e-mail messages between servers.
Port 80 (inbound and outbound): While not directly used by RC-E , but by management servers, port 80 is typically used by the IIS (Internet Information Services) Default Web Site for running the RC-E Management Server service.
Port 554 (inbound and outbound): Used by recording servers for RTSP traffic in connection with H.264 video streaming.
Port 1024 and above (outbound only (except ports listed in the following)): Used by recording servers for HTTP traffic between cameras and servers.
Port 5210 (inbound and outbound): Used for communication between recording servers and failover servers when databases are merged after a failover server has been running.
Port 5432 (inbound and outbound): Used by recording servers to listen for TCP information; some devices use TCP for sending event messages.
Port 7563 (inbound and outbound): Used by recording servers and Ocularis Client for handling PTZ camera control commands and for communicating.
Port 8080 (inbound and outbound):Used for internal system communication. Port 8844 (inbound and outbound): Used for communication between failover servers. Port 9993 (inbound and outbound): Used for communication between recording servers and management
servers. Port 11000 (inbound and outbound): Used by failover se rvers for polling (i.e. regularly checking) the state of
recording servers. Port 65101(inbound and outbound): Used by recording servers for communication between recording servers and
drivers (internally, used for example when SMTP events are received). Any other port numbers you may have selected to use. Examples: If you have changed the IIS Default Web Site
port from its default port number (80) to another port number, or if you have integrated RC-C servers into your RC-E system, in which case a port must be allocated for use by RC-C's Image Server service.
Multiple Management Servers (Clustering)
The RC-E management server can be installed on multiple servers within a cluster of servers. T his ensu res that RC-E has very little down-time: if a server in the cluster fails, another server in the cluster will automatically take over the failed server's job running the RC-E management server. The automatic process of switching over the RC-E server service to run on another server in the cluster only takes a very short time (up to 30 seconds).
Note that the allowed number of failovers is limited to two within a six hour period. If exceeded, Management Server services are not automatically started by the clustering service. The number of allowed failovers can be changed to better fit your needs. See Microsoft's homepage http://technet.microsoft.com/en­us/library/cc787861%28WS.10%29.aspx (see http://technet.microsoft.com/en-us/library/cc787861(WS.10).aspx ­http://technet.microsoft.com/en-us/library/cc787861(WS.10).aspx) for details on how to do this.
Is clustering the same as federated architecture? No, clustering is not the same as federated architecture (see "OnSSI Federated Architecture Overview" on page 173). Clustering is a method to obtain failover support for a management server on a site. With clustering, it is only possible to have one active management server per surveillance setup, but other management servers may be set up to take over in case of failure. On the other hand, federated architecture, is a method to combine multiple independent corporate sites into one large setup, offering flexibility and unlimited possibilities.
On-Net Survei
llance Systems, Inc. 24
Page 25
RC-E User Manual Installation and Removal
Prerequisites for Installing OnSSI RC-E in a Cluster
Two or more servers installed in a cluster.
Tip: You can find information about failover clusters on Microsoft's web site.
-Regarding clusters in Windows 2003, see Deploying Exchange Server 200 3 in a Cluster (see http://technet.microsoft.com/en-us/library/bb123612(EXCHG.65).aspx - http://technet.microsoft.com/en-
ary/bb123612(EXCHG.65).aspx). http://technet.microsoft.com/en-
us/libr
us/libr
ary/bb123612(EXCHG.65).aspx)
-Regarding clusters in Windows 2008, see Failover Clusters (see http://technet.microsoft.com/en­us/library/cc732488(WS.10).aspx - http://technet.microsoft.com/en-
ary/cc732488(WS.10).aspx).(http://technet.microsoft.com/en-us/libr
us/libr
ary/cc732488(WS.10).aspx)
Either an external SQL database installed outside the server cluster or an internal SQL service within the
server cluster.
A Microsoft® Windows® Server 2003/2008 Enterprise or Data Center edition.
Installing RC-E in a Cluster
The section is based on Windows 2008. So, if you are using Windows 2003, descriptions and illustrations might differ from what your see on your screen.
1. Install the RC-E management server and all its subcomponents on the first server in the cluster by following the procedures described in Install Management Server (on page 13).
The management server must be installed with a specific user and not as a Network Service. This requires that you use the Custom install option, see Install Management Server, step 3 (see "Install Management Server" on page 13), for details. Furthermore, the specific user must have access to the shared network drive and preferably a non-expiry password.
The service channel and the IIS should both be installed normally with the exact same user, and not as cluster services.
2. After you have installed the management server and the Management Client on the first server in the clu s ter, open the Management Client, then from the Tools menu select Registered Services...
a) In the Add/Remove Registered Services window, select the Log Service in the list, then click Edit... b) In the Edit Registered Service window, change the URL address of the log service to the URL address of the
cluster.
c) Repeat steps a and b for all services listed in the Add/Remove Registered Services win d ow. d) In the Add/Remove Registered Services window, click Network... e) In the Network Configuration window, change the URL address of the server to the URL address of the
cluster. (This step only applies to the first server in the cluster.) Click OK.
3. Click Close in the Add/Remove Registered Services window, then exit the Management Client.
4. Stop the management server service (see "Management Server Service and Recording Server Service" on pag
e 198) and the Internet Information Service (IIS). You can rea
d about how to stop the IIS at Microsoft's homepage: http://technet.microsoft.com/en-us/library/cc732317(WS.10).aspx (see http://technet.microsoft.com/en-us/library/cc732317(WS.10).aspx - http://technet.microsoft.com/en-
ary/cc732317(WS.10).aspx).
us/libr
On-Net Survei
llance Systems, Inc. 25
Page 26
RC-E User Manual Installation and Removal
Repeat steps 1-4 for all subsequent servers in the cluster, this time pointing to the existing SQL database, but
5. for the last server in the cluster you install the management server on, do not stop the management server service.
The management server service must be configured as a generic service in the failover cluster in order to take effect:
1. On the last server you have installed the management server on, open Windows' Failover Cluster Management, found under Administrative Tools in the Start menu.
2. In the Failover Cluster Management window, expand your cluster, right-click Services and Applications, then select Configure a Service or Application...
3. On the first page of the High Availability wizard click Next, then on the second page of the wizard select Generic Service in the list, and click Next.
4. Do not specify anything on the third page of the wizard, click Next.
5. Select the OnSSI RC-E management server service from the list, then click Next.
6. Specify the name (host name of the cluster), that clients will use when accessing the service, then click Next.
7. No storage is required for the service, click Next.
8. No registry settings should be replicated, click Next.
9. Verify that the cluster service is configured according to your needs, then click Next.
10. The RC-E management server has now been configure d as a generic service in the failover cluster. Click Finish to exit the wizard.
Upgrading RC-E in a Cluster
Prerequisite
Make sure to have a backup of the database in question before updating the cluster. How To Update...
1. Stop Management Server services (see "Management Server Service and Recording Server Service" on pag
e 198) on all management servers in the cluster.
2.
Uninstall the management server on all servers in the cluster. See Remove System Components (on page
27).
3.
Use the procedure for installing multiple management servers in a cluster as described in Installing RC-E in a Cluster (on page 25).
IMPORTANT: When installing, make sure to reuse the existing SQL configuration database (which will automatically be upgraded from the old existing database version to the new one).
Multiple Recording Server Instances
It is only recommended to install multiple instances of the Recording Server service on the same server under the following conditions.
If you: are upgrading from RC-E 4.1 or older
On-Net Survei
llance Systems, Inc. 26
Page 27
RC-E User Manual Installation and Removal
—and—
are already running more 32-bit Recording Server service instances on the same server.
Since it is not possible to move devices/cameras from one recording server to another, setups running more than one 32-bit Recording Server service instances on the same server, will need to maintain this structure.
For all other setups, the newer 64-bit recording server eliminates the need for running more 32-bit instances on the same server.
Installing Multiple Recording Server Instances
During the recording server installation (see "Install System Components" on page 17), you simply select the requir ed number of instances. A maximum of 99 recording server instances is allowed on a single server.
Using multiple recording server instances does not require addition al licenses. In the Management Client, each recording server instance will be displayed separ ately, allowing you to configure each
instance separately. When managing the Recording Server service (see "Management Server Service and Recording Server Service" on
pag
e 198) by right-clicking its icon in the notification ar
Stop and start each instance individually  View status messages for each instance individually, grouped on tabs.
ea on the server itself, you can:
Remove System Components
If you are not an RC-E system administrator, do not attempt to remove the management software. The following procedure describes standard system component removal in recent Windows versions; the procedure
may be slightly different in older Windows versions:
1. In Windows' Start menu, select Control Panel, and then...
o If using Category view, find the Programs category, and click Uninstall a program. o If using Small icons or Large icons view, select Programs and Features.
2. In the list of currently installed programs, right-click the required program or service, select Uninstall, and
Removing Management Server
OnSSI RC-E management servers are most likely installed on a dedicated server.
To remove, follow the general removal procedure (see "Remove System Components" on page 27).
Removing Download Manager and Log Server
The Download Manager and log server, which are all installed on the management server, are removed separately from the management server software.
To remove, follow the general removal procedure (see "Remove System Components" on page 27).
follow the removal instructions.
On-Net Survei
llance Systems, Inc. 27
Page 28
RC-E User Manual Installation and Removal
Removing Management Client
OnSSI RC-E Management Client are all removed at the computer on which the program or service is installed.
To remove, follow the general removal procedure (see "Remove System Components" on page 27).
Removing Recording Server
To remove an RC-E recording server, use the following procedure on the computer on which the recordin g server is installed:
What happens to the recording server's recordings? During the removal process, you will be asked whether you want to keep the recording server's recordings.
1. Stop the recording server service by right-clicking the recording server icon in the computer's notificatio n area (also known as the system tray), then selecting Stop Recording Server Service.
2. To remove, follow the general removal procedure (see "Remove System Components" on page 27). Right­click the RC-E
Recording Server in step 2 of the process.
Upgrade from Previous Version
This information is only relevant if you are upgrading a previous installation of RC-E. IMPORTANT: RC-E no longer supports Microsoft® Windows® XP. See System Requirements (on page 9).
The process of upgrading RC-E involves removing all of its components except the Database Server. The Database Server is one of the management server's components, it contains the entire system configuration (recording server configurations, camera configurations, rules, etc.). As long as you do not remove the Database Server, you will not need to reconfigure your surveillance system configuration in any way (although you may of course want to configure some of the new features in the new version).
Backward compatibility with recording servers from RC-E versions older than 3.0 is limited. You can still access recordings on such older recording servers; but in order for you to be able to change their configuration, they must be of version 3.0 or later. It is thus highly recommended that you upgrade all recording servers in your RC-E system.
When doing an update which includes updating your rec ording servers, you automatically update your Video Device Drivers as well. In this case, after restarting your system, it might take several minutes for your hardware devices to make contact with the new Video Device Drivers, so have patience. This is due to several internal checks being performed on the newly installed drivers.
Prerequisites
Have your temporary license (.lic) file ready. The license file will change when your SLC changes, so you are
likely to have received a new license file when purchasing the new version. When you install the management server, the wizard will ask you to specify the location of your license (.lic) file, which the system will verify before you will be able to continue.
If you do not have your license file, contact your OnSSI vendor.
Have your new RC-E version ready. If you have not purchased the software on a DVD, you can download it from
www.onssi.com (http://www.onssi.com). Note that although you can download a to install a version for which your license file is valid.
On-Net Survei
llance Systems, Inc. 28
ny version, you will only be able
Page 29
RC-E User Manual Installation and Removal
The management server stores your RC-E system's configuration in a database. The system configur ation database can be stored in two different ways: 1) In a SQL Server Express Edition database on the management server itself, or 2) in a database on an existing SQL Server on your network. If using 2), Administrator rights on the SQL Server are required whenever you need to create, move or upgrade the management server's system configuration database on the SQL Server. Once you are done creating, moving or updating, being database owner of the management server's system configuration database on the SQL Server will suffice.
Upgrading the Management Server
The management server has several components. This describes removing old components—except the Database Server—and installing the new ones:
1. First remove the management server itself. See Remove System Components (on page 27).
2. Next, remove the RC-E Windows components.
3. If the RC-E Management Client is installed on the management server itself, remove the Management Client too. See Remove System Components (on page 27).
Run the installation for the new version of RC-E. After a short while, the installation window will open. Out of
4. the three installation steps for the management server, you will be asked to address step 3 (OnSSI RC-E management server).
5. Click the installation window's step 3, and complete the RC-E management server installation. During this process you will be asked to specify the path to your license (.lic) file.
6. When the management server is installed, the management server's web page will appear in a browser. If you want to install the Management Client software on the management server itself, you can do it from the management server's web page.
Upgrading Recording Servers
Once the new management server is installed, you can remove the old recording server version, and install the ne w one:
What happens to the recording server's recordings? During the removal process, you will be asked whether you want to keep the recording server's recordings.
1. See Remove System Components (on page 27) for how to remove a recording server.
2.
When the recording server has been removed, open a browser and connect to the management server's web page at the following address:
http://[management server address]:[port]/installation/admin/ where [management server address] is the IP address or host name of the management server, and [port] is
the port number which IIS has been set up to use on the management server. If not accessing the web page on the management server itself, log in with an account which has
administrator rights on the management server.
3. From the web page, install the new version of the recording server software.
4. Repeat for each recording server on your RC-E system.
When updating your recording servers, you automatically update your Vide o Device Drivers as well. After restarting your recording servers, it might take several minutes for your hardware devices to make contact with the new Video
On-Net Survei
llance Systems, Inc. 29
Page 30
RC-E User Manual Installation and Removal
Device Drivers, so have patience. This is due to several internal checks being performed on the newly installed drivers.
Upgrading a Management Client
If the Management Client is installed on separate computers, such as the surveillance system administrator's workstation or similar, you should now remove the old version and install the new one:
1. See Remove System Components (on page 27) for details on removing a Management Client.
2. When the Management Client has been removed, open a browser and connect to the management server's web page at the following address:
http://[management server address]:[port]/installation/admin/ where [management server address] is the IP address or host name of the management server, and [port] is
the port number which IIS has been set up to use on the management server. If not accessing the web page on the management server itself, log in with an account which has
administrator rights on the management server.
3. From the web page, install the new version of the Management Client.
Upgrading Video Device Drivers
Before upgrading Video Device Drivers, you must remove old Video Device Drives. For information on how to remove/upgrade/install Video Device Drivers, see Manage and Remove Video Device
Drivers (on page 190).
Installation Troubleshooting
The following issues may occasionally occur during or upon installation of the RC-E management server or recording servers. For each issue, one or more solutions are available.
Issue: Automatic IIS Installation for Mgmt.
If installing the management server on a server running Windows 2008 Server, Internet Information Services (IIS) is under normal circumstances automatically installed.
For the management server, this happens when you click the Internet Information Services step in the RC-E
Management Server Installation window.
If the automatic installation fails, you can install IIS manually.
Solution: Install IIS Manually
1. If automatic IIS installation fails, you will see an error message asking you to install IIS manually. In the error message box, click Install IIS Manually.
2. You will now see the Server Manager window. In the left side of the window, select Roles, then the Roles Summary.
3. Now select Add Roles to start a wizard.
On-Net Survei
llance Systems, Inc. 30
Page 31
RC-E User Manual Installation and Removal
In the wizard, click Next, select Web Server (IIS), and follow the wizard's steps.
4.
5. When you reach the wizard's Select Role Services step, you will see that some role services are selected by default. However, you should select some additional role services:
Under Security, select Basic Authentication and Windows authentication. Under Management Tools, select IIS 6 Management Console, expand it, and select IIS 6 Metabase
Compatibility, IIS 6 WMI Compatibility, IIS 6 Scripting Tools, and IIS 6 Management Console.
6. Complete the wizard by following the remaining steps.
Issue: Recording Server Startup Fails due to Port Conflict
This is an issue if either the Simple Mail Transfer Protocol (SMTP) Service or an existing installation of RC-C is running.
Both use port 25. If port 25 is already in use, it may not be possible to start the RC-E Recording Server service. It is important that port number 25 is available for the recording server's SMTP service since many cameras are only capable of communicating via this port.
SMTP Service: Verification and Solutions
To verify whether SMTP Service is installed, do the following:
1. From Windows' Start menu, select Control Panel.
2. In the Control Panel, double-click Add or Remove Programs.
3. In the left side of the Add or Remove Programs window, click Add/Remove Windows Components.
4. In the Windows Components wizard, select the Internet Information Services (IIS) item, and click Details....
5. In the Internet Information Services (IIS) window, verify whether the SMTP Service check box is selected. If it is, 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 the Administrative Tools win d o w, d o u b l e- click Services.
4. In the Services window, double-click the Simple Mail Transfer Protocol (SMTP) item.
5. In the SMTP Properties window, click Stop, then set Startup type to either Manual or Disabled.
Tip: When set to Manual, the SMTP Service can be started manually from the Services window, or from a command prompt using the command net start SMTPSVC.
6. Click OK.
Solution 2: Remove SMTP Service Note that removing the SMTP Service may affect other applications using the SMTP Service.
On-Net Survei
llance Systems, Inc. 31
Page 32
RC-E User Manual Installation and Removal
rom Windows' Start menu, select Control Panel.
1. F
2. In the Control Panel, double-click Add or Remove Programs.
3. In the left side of the Add or Remove Programs window, click Add/Remove Windows Components.
4. In the Windows Components wizard, select the Internet Information Services (IIS) item, and click
Details....
5. In the Internet Information Services (IIS) window, clear the SMTP Service check box.
6. Click OK, Next, and Finish.
OnSSI RC-C: Verification and Solutions
To verify whether RC-C is installed, do the following:
1. From Windows' Start menu, select Control Panel.
2. In the Control Panel, double-click Add or Remove Programs.
3. In the Add or Remove Programs window, verify whether RC-C appears in the list. If it does, RC-C is installed.
If RC-C is installed, select one of the following solutions: Solution 1: Remove RC-C
1. From Windows' Start menu, select Control Panel.
2. In the Control Panel, double-click Add or Remove Programs.
3. In the Add or Remove Programs window, select RC-C, click Uninstall/Change, and then OK.
Solution 2: Set RC-C Services to manual startup This solution lets you start the recording server without having to stop the RC-C Services every time:
1. From Windows' Start menu, select Control Panel.
2. In the Control Panel, double-click Administrative Tools.
3. In the Administrative Tools window, doub l e - c l i c k Services.
4. In the Services window, repeat steps a-c for these items: OnSSI ImageImportService, OnSSI ImageServer, OnSSI LogCheckService, OnSSI Recording Server.
5. Double-click the item.
6. In the <item> Properties window, click Stop, then set Startup type to Manual.
7. Click Close.
Tip: With the startup type Manual, you can start and stop the RC-C Services from a command file:
To start the RC-C Services from a command file, create a file named e.g. startx.cmd with the following content:
net start "OnSSI ImageImportService" net start "OnSSI ImageServer" net start "OnSSI LogCheckService" net start "RecordingServer"
To stop the RC-C Services from a command file create a file named e.g. stopx.cmd with the following content:
On-Net Survei
llance Systems, Inc. 32
Page 33
RC-E User Manual Installation and Removal
net stop "OnSSI ImageImportService" net stop "OnSSI ImageServer" net stop "OnSSI LogCheckService" net stop "RecordingServer"
Issue: Changes to SQL Server Location Prevents Database Access
This is an issue if using an MS SQL Server database as the RC-E management server database: If the location of the SQL Server is changed, for example by changing the host name of the computer running the SQL Server, access to the database will be lost.
Solution: Run Management Server Database Installation Step Again See Management Server Installation (see "Install Management Server" on page 13). When running the database
ation, you will - during the database preparation process - be asked whether you want to create a new
install database, use an existing database, or overwrite an existing database: Pointing to the new location of the SQL Server, select to use an existing database. This will update the SQL connection string used by the management server, and it will again be possible to access the database.
Issue: Insufficient Continuous Virtual Memory Fails Installation
The following is only relevant if you use Windows Server 2003. If you try to install a large Windows Installer package or patch package in Windows Server 2003, this problem might
occur if the Windows Installer process has insufficient continuous virtual memory to verify that the .msi package or the .msp package is correctly signed.
Solution: A supported fix (see http://support.microsoft.com/kb/925336 - http://support.microsoft.com/kb/925336) is
vailable for Windows Server 2003. See http://support.microsoft.com/kb/925336 (see
a
http://support.microsoft.com/kb/925336 - http://support.microsoft.com/kb/925336).
Issue: Multi-domain Environments; One-way Trusts not Working
See Multi-domain Environments, One-way Trust.
On-Net Surveillance Systems, Inc. 33
Page 34
RC-E User Manual Management Client (RC-E Manager)
Management Client (RC-E Manager)
Management Client (RC-E Manager) Overview
The Management Client, also known as the RC-E Manager, is the feature-rich administration client used for configuration and day-to-day administration of your RC-E system. The Management Cl ient software is typically installed (see "Install System Components" on page 17) on the surveillance system administrator's workstation or similar. The term 'Management Client' is a generic name used for the 'RC-E Manager'.
Management Client's Elements
The Management Client window is divided into a number of panes. T he number of panes will change depending on your task:
The following illustrations outline the Management Client window's default la yout; the window layout can be customized (see "Customize the Management Client's Layout" on page 41), and may therefore be different on your computer.
When working with recording servers and devices (cameras, inputs, outputs), the Management Client window
contains a menu bar (on page 35) and four panes (see "Panes Overview" on page 36):
When working with rules, time and notification profiles, users, roles, etc., the Management Client window typically contains a menu bar (on page 35) and three panes (see "Panes Overview" on page 36):
When viewing logs, the Management Client window typically contains only the menu bar, (see "Menu Bar" on pag
e 35) the Site Navigation and Federated Sites Hierarchy Pane (see "Site Navigation Pane and Federated
Hierarc
hy Pane" on page 34) and an overview area (marked in gray):
Site Navigation Pane and Federated Hierarchy Pane
The Management Client is the feature-rich administration client used for configuration and day-to-day administration of your RC-E system. The Management Client software is typically installed on the surveillance system administrator's workstation or similar. The term 'Management Client' is a generic name used for the 'RC-E Manager'.
Site Navigation Pane
This is your main navigation element in the Management Client. Name, settings and configurations of the site you are logged into are reflected (see "Manage OnSSI Federated Architecture" on page 177) here (site-name is visible at the top of the pan
Basics: General information, for example about licenses in your RC-E system  Servers: Management of recording servers and failover servers (spare recording servers) connected to your RC-
E system
Devices: Management of cameras, microphones, speakers, input, and output
e). The Management Client's features are grouped into the following categories:
Client: Management of view groups
On-Net Survei
llance Systems, Inc. 34
Page 35
RC-E User Manual Management Client (RC-E Manager)
Ru
les and Events: Management of rules, time profiles, notification profiles, events and events settings.
Security: Management of users, groups, and roles  System Dashboard: System reporting functionality and overview of recording servers' databases and archives  Server Logs: Access to the various logs of your RC-E system
Tip: Right-clicking items in the Site Navigation pane gives you quick access to management features.
Federated Site Hierarchy Pane
Your navigation element dedicated to displaying OnSSI Federated Architecture (see "OnSSI F ederated Architecture Overview" on page 173) sites and their parent/child links.
T
he parent server you are logged in to, a.k.a your home site, will always be at top, and adopting its point of view, you
can view all its linked children and downwards in the parent/child hierarchy.
What if I only have one server and don't run OnSSI Federated Architecture? Your user interface looks the same, but you will only see the one server in your setup.
Menu Bar
The Management Client's menu bar features the following menus (see "Management Client Menu Overview" on page
40): File Menu, Edit Menu, View Menu, Action M
enu, Tools Menu and Help Menu.
Toolbar
The Management Client's toolbar features the following options:
Save: Save changes to your settings.
Undo: Undo your latest change. Help...: Access a help topic relevant to your task Contents...: Access the help system's table of contents. Search...: Access the help system's search feature.
Tip: Read more about the Management Client's built-in help system in Use the Built-in Help System (see "Navigating
the Built-i
n Help System" on page 11).
Memory Indicator
The memory indicator located in the lower left corner of the Management Client states how much memory is available for working with the Management Client.
When you expand items in the Site Navigation pane the Management Client uses memory to treat data stored in the individual items. Expanded items keep processing even when you expand other items in the Site Navigation pane, thus letting you access already-expanded items faster.
When available memory drops to 300 MB the memory indicator numbers turn red. When the memory indicator drops to 0 MB, meaning there is no more memory available for the Management Client,
you cannot expand any more items.
On-Net Survei
llance Systems, Inc. 35
Page 36
RC-E User Manual Management Client (RC-E Manager)
o free up memory, refresh the Management Client: Click OK to exit the dialog, then press F5 on your keyboard or
T select Refresh from the Action menu.
Panes Overview
The Management Client window may contain up to four panes.
1. Site Navigation Pane and Federated Sites Hierarchy Pane (see "Site Navigation Pane a nd Federated hy Pane" on page 34)
Hierarc
Overview Pane (on page 36)
2.
3.
Properties Pane (on page 36) Preview Pane (on page 36)
4.
The illustration outlines the Management Client window's default layout; the window layout can be customized (see "Customize the Management Client's Layout" on page 41), and may therefore be different on your computer.
Menu and Tool Bars
Provide quick access to often-used features.
Overview Pane
Provides an overview of the item you have selected in the navigation pane, typically in the form of a detailed list. Selecting a particular item in the overview pane will typically display the item's properties in the prop erties pane.
Right-clicking items in the overview pane gives you access to management features.
Preview Pane
Displays preview images from selected cameras or state information from selected microphones, speakers, inputs and outputs. The example to the left shows a camera preview image with information about the resolution and data rate of the camera's live stream.
Tip: By default, information shown with camera preview images will concern live streams (shown in green text). If you want recording stream information instead (shown in red text), select View > Show Recording Streams from the Management Client's menu.
You will see the preview pane when you deal with recording servers and devices. You can toggle the preview pane on and off in the View menu. To resize the preview pane, drag its borders. The larger the preview pane, the larger preview images and state information will appear.
Tip: Performance can be affected if the preview pane displays preview images from many cameras at a high frame rate. To control the number of preview images, and their frame rate, select Options > General from the Tools menu.
Properties Pane
Displays properties of the item selected in the overview pane. In many cases, properties are displayed across a number of tabs:
On-Net Survei
llance Systems, Inc. 36
Page 37
RC-E User Manual Management Client (RC-E Manager)
Site Navigation Pane and Federated Hierarchy Pane
The Management Client is the feature-rich administration client used for configuration and day-to-day administration of your RC-E system. The Management Client software is typically installed on the surveillance system administrator's workstation or similar. The term 'Management Client' is a generic name used for the 'RC-E Manager'.
Site Navigation Pane
This is your main navigation element in the Management Client. Name, settings and configurations of the site you are logged into are reflected (see "Manage OnSSI Federated Architecture" on page 177) here (site-name is visible at the top of the pan
Basics: General information, for example about licenses in your RC-E system  Servers: Management of recording servers and failover servers (spare recording servers) connected to your RC-
E system
Devices: Management of cameras, microphones, speakers, input, and output  Client: Management of view groups  Rules and Events: Management of rules, time profiles, notification profiles, events and events settings.  Security: Management of users, groups, and roles
e). The Management Client's features are grouped into the following categories:
System Dashboard: System reporting functionality and overview of recording servers' databases and archives  Server Logs: Access to the various logs of your RC-E system
Tip: Right-clicking items in the Site Navigation pane gives you quick access to management features.
Federated Site Hierarchy Pane
Your navigation element dedicated to displaying OnSSI Federated Architecture (see "OnSSI F ederated Architecture Overview" on page 173) sites and their parent/child links.
he parent server you are logged in to, a.k.a your home site, will always be at top, and adopting its point of view, you
T can view all its linked children and downwards in the parent/child hierarchy.
What if I only have one server and don't run OnSSI Federated Architecture? Your user interface looks the same, but you will only see the one server in your setup.
Basics
Get Started
The tasks typically involved in setting up an RC-E system are listed below. Note that although information is presented as a checklist, a completed checklist does not in itself guarantee that the
RC-E system will match the exact requirements of your organization. To make the system match the needs of your organization, it is highly recommended that you monitor and adjust the system once it is running.
For example, it is often a good idea to spend time on testing and adjusting the motion detection sensitivity settings of individual cameras under different physical conditions (day/night, windy calm weather, etc.) once the system is
On-Net Survei
llance Systems, Inc. 37
Page 38
RC-E User Manual Management Client (RC-E Manager)
ing. The setup of rules, which determine most of the actions performed by the RC-E system (including when to
runn record video), is another example of configuration which to a very large extent depends on your organization' s needs.
The following steps should be completed after the installation and licensing of Ocularis Base.
Install the various components of your RC-E system. See Installation Overview (on page 12).  Log in to the Management Client. See Log in to the Management Client (on page 39).
Authorize use of your RC-E system's recording servers. See Manage Recording Servers (on page 60).
Why must I authorize recording servers? By authorizing recording servers before th ey can be used, surveillance system administrators have full control over which recording servers are able to send information to their RC-E management server.
Detect the hardware devices (i.e. cameras and video encoders) which should be added to each rec ording
server. See the wizard Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49).
W
hat is the Add Hardware wizard?Add Hardware helps you detect IP hardware devices, such as cameras and
video encoders, on your network and add them to your RC-E system. The wizard offers you two ways of detecting and adding hardware devices: With automatic hardware detection, RC-E automatically scans for available hardware within one or more specified IP address ranges. With assisted hardware detection, you manually specify the IP address of each required device. Both options offer the possibility of automatically detecting the correct hardware drivers.
Verify that each recording server's storage areas will meet your needs. See About Storage and Archiving (on
page 56).
What is a storage area? A storage area is a directory in which the databases containing r ecordings from the cameras connected to the recording server are stored— each individual camera database by default h as a ma ximum size of 5 GB. A default storage area is automatically created for each recording server when the recording server is installed on the system. Connected cameras’ databases are stored in the recording server's default storage are a unless you specifically define that another storage area should be used for storing the databases of particular cameras. If required, a wizard lets you add further storage areas (on the recording server computer itself, or at another location, for example on a network drive), edit which storage area should be the default area, etc.
Verify that each recording server's archiving settings will meet your needs. See About Storage and Archiving
(on page 56).
hat is archiving? Archiving is the automatic transfer of recordings from a camera's default database to another
W
location. This way, the amount of recordings you are able to store will not be limited by the size of the camera's default database. Archiving also makes it possible to back up your recordings on backup media of your choice. Archiving is configured on a per-recording server basis. Once you have configured the archiving settings for a recording server (where to store archives, how often to transfer recordings to the archives, etc.), you can enable archiving for individual cameras. When archiving is enabled for a camera, the contents of the camera's database will automatically be moved to an archive at regular intervals.
Configure any required failover servers. A failover server is a spare recording server which can take over if a
regular recording server becomes unavailable. See About Failover Servers (see "Manage Failov er Servers " on pa
ge 192).
Configure each recording server's individual cameras. See Manage Camera s (on page 75).
Tip: You are able to gro
up cameras, and configure common properties for all cameras within a group in one step.
Tip: Motion detection, a vital setting on most IP surveillance systems, is enabled by default. However, you may want to fine-tune motion detection settings, or disable motion detection for particular cameras.
Enable and configure microphones— if any. See Manage Microphones (on page 85).
Enable and configure speakers— if any. See Manage Speakers (on page 87).
Enable and configure input— if any. See Manage Inputs (see "Manage Input" on page 88).
Enable and configure output— if any. See Manage Outputs (see "Manage Output" on page 91).
On-Net Survei
llance Systems, Inc. 38
Page 39
RC-E User Manual Management Client (RC-E Manager)
Create rules. See Manage Rules (on page 133).
What is a rule? Rules are a central element in RC-E. The behavior of an RC-E system is to a very large extent determined by rules. Rules determine highly important settings, such as when cameras should record, when PTZ (Pan/Tilt/Zoom) cameras should patrol, when notifications should be sent, etc.
Tip: When creating rules, you may also want to use time profiles (see "Manage Time Profiles" on page 138) (for
y making rules apply within or outside predefined periods of time) or notification profiles (see "Manage
quickl
Notification Profiles" on page 141) (for quickly making rules send pre-configured e-mails— with video clips, if
requ
ired— to selected recipients).
Add roles. See About Roles (on page 145).
What is a role? Roles determine which RC-E features users and groups are able to use. In other words, roles determine rights.
Add users and/or groups of users. See About Users and Groups (see "Manage Users and Groups" on pa ge
145).
Tip: If you have a server with Active Directory installed, and acting as domain controller on your network, RC-E lets you quickly add users and/or groups from Active Directory.
Activate licenses. See About Licensing (see "Manage Licenses" on page 45).
hy must licenses be activated? When installing the system, you used a single temporary license. The temporary
W
license is only valid for a certain number of days. After this initial period ends, all recording servers and cameras on your system will require activation of their individual licenses. You must therefore activate your licenses before the initial period ends, since all recording servers and cameras for which no licenses have been activated will otherwise stop sending data to the surveillance system.
Use the Download Manager to make additional components available to u sers—if required. See Use the
Download Manager.
What is the Download Manager? An application which lets surveillance system admini strators manage which system-related components (e.g. particular language versions of clients) surveillance system users will be able to access from a targeted web page generated by the management server.
Log in to the Management Client
Access to the RC-E Management Client requires certain user rights. Consult your surveillance system administrator if in doubt.
1. Click the RC-E Management Client desktop icon or—in Windows' Start menu—select All Programs > RC-E >
Management Client. This will make the login window appear:
2. The login window's Server type field will in many cases appear dimmed and pre-filled with the required information. If not, select RC-E.
3. In the Server address field, type the IP address or host name of the computer running the RC-E management server.
Tip: If you have logged in before, you can select previously used server IP addresses or host names from the list.
4. By default, you will log in to the management server with your active Windows account. This means that if you are currently logged in as, for example, JohnSmith, you will by defau lt log in to the management server as JohnSmith as well.
o If you wish to log in to the management server with your active Windows account (this is the default login
option), select Windows Authentication (current user) in the Authentication field.
On-Net Survei
llance Systems, Inc. 39
Page 40
RC-E User Manual Management Client (RC-E Manager)
If you wish to log in to the management server with a different Windows account, select Windows
o
Authentication in the Authentication field, then type the required user name and password in the User name and Password fields respectively.
Tip: If you have logged in with Windows Authentication before, you can select previously entered user names from the list.
Tip: When using Windows Authentication, you have the option of selecting Remember password, in which case you will not have to type the password at subsequent logins.
5. Click Connect to open Management Client.
Management Client Menu Overview
Action Menu Items
(Depending on context)
Refresh is always available and reloads the requested information from the management server.  Expand (or Collapse) is available when working with Federated architecture, Servers, Devices, Client, Rules and
Events and System Dashboard.
A number of context specific items. Be aware of the following when working with the Action menu concerning OnSSI Federated Architecture (see "OnSSI
Federated Architecture Overview" on page 173): To be able to delete a site without being connected to it, right- clicking a site does not select it, but offers a context menu. Because of this, some context menu items may be disabled if you are not connected to the site and some are only available on the home-site, i.e. the site you are logged in to. For more details see Manage OnSSI Federated Architecture (see "OnSSI Federated Architecture Overview" on page 173).
Edit Menu Items
Undo lets you cancel your latest action.
Tip: As an alternative to selecting Edit > Undo, press CTRL+Z on your keyboard.
File Menu Items
Save: Lets you save your current configuration.
Tip: As an alternative to selecting File > Save, press CTRL+S on your keyboard.
Logoff...: Lets you log out of the Management Client, and log in with another user account if necessary.  Exit: Lets you close down and exit the Management Client.
Help Menu Items
Help... lets you access a help topic relevant to your task.  Contents... lets you access the help system's table of contents.
On-Net Survei
llance Systems, Inc. 40
Page 41
RC-E User Manual Management Client (RC-E Manager)
Sear
ch... lets you access the help system's search feature.
About... opens a dialog displaying information about the version of your Management Client.
Tools Menu Items
Registered Services... lets you add trusted servers. See Manage Trusted Servers for details.  RC-C Servers... lets you add RC-C servers specifically. See Manage RC-C Servers (on page 162) for details.  Effective Roles... lets you view all roles of a selected user or group (see "Manage Users and Groups" on page
145). For more informatio
n, see Manage Roles (on page 147).
Options... opens the Options dialog (see "Options" on page 168), which lets you define and edit several global
RC-E settings.
View Menu Items
(Depending on context) Reset Application Layout: Lets you reset the layout of the different panes in the Management Client to their
default settings. See Customize the Management Client's Layout (see "Customize the Management Client's
yout" on page 41)t for details.
La
Preview W
w
orking with recording servers and devices.
indow: Lets you toggle the preview pane (see "Panes Overview" on page 36) on and off when
Tip: If the preview pane displays images from many cameras at a high frame rate, it may slow down performance. To specify the number of preview images you want in your previe w pane, a s well as their frame rate, select Options > General from the Tools menu.
Show Recording Streams: By default, the information shown with preview images in the preview pane will
concern cameras' live streams (shown in green text). If you want information about recording streams i nstead, select Show Recording Streams. Recording stream information will be shown in red text.
Federated Site Hierarchy: By default, the is enabled, and this command lets you toggle it on and off.  Site Navigation: By default, the Site Navigation pane (see "Panes Overview" on page 36) is enabled, and this
command lets y
ou toggle it on and off.
Customize the Management Client's Layout
You can rearrange panes in the Management Client, and thus customize its look to suit your needs. If you rearrange the panes, you can always reset the entire layout to the Management Client's default layo ut.
Resizing Panes
You can resize panes by dragging the borders of the panes:
1. Place your mouse pointer over a border.
2. When the pointer becomes a double-headed arrow, drag the border in the required direction.
The size of the content inside the panes stays the same regardless of the size of the panes, with one exception: the larger the preview pane is, the larger preview images and state information will appear.
On-Net Survei
llance Systems, Inc. 41
Page 42
RC-E User Manual Management Client (RC-E Manager)
Moving Panes
You can move a pane to a different position either as a floating pane or to a docked position, by clicking on a pane's title bar and dragging it with the mouse.
The position and whether the pane becomes a floating pane or docked depend on where you release the mouse button. See the following topics for more information.
The Management Client offers some layout elements that help you control the new position of the pane. The layout elements are available when you drag a pane. For more information about how you use the layout elements when moving panes see these topics: Floating Panes To move a pane to a floating pane, drag the pane to its new position without using one of the layout elements. Moving a Pane to a Docked Outer Position If you move a pane to a docked outer position, it fills the area with a horizontal or vertical split that goes from top to
bottom or left to right.
1. Drag the pane to one of the outer layout elements.
Tip: Before you release the mouse, the pane's new position is indicated by a gray area.
2. Release the mouse to dock the pane at its current position. Moving a Pane to a Docked Inner Position If you drag the pane to one of the inner layout elements, the pane will be positioned along one side of one of the other
panes.
1. Drag the pane to one of the inner layout elements.
Tip: Before you release the mouse, the pane's new position is indicated by a gray area.
2. Release the mouse to dock the pane at its current position. Moving a Pane to a Shared Position You can move a pane into another pane's position so two or more panes share the same position:
1. Drag the pane to the center layout element of the pane which position you want to share.
Tip: Before you release the mouse, the pane's new position is indicated by a gray area.
2. Release the mouse to dock the pane at its current position.
Tip: To view the content of the panes, click the tabs on the bottom of the shared position.
Splitting Shared Positions
If you do not want a pane to share a position with another pane, do this:
1. Click the tab of the relevant pane and drag it to a new position. The pane's new position can be a docked position or a floating pane.
2. Release the mouse to place the pane at its current position.
On-Net Survei
llance Systems, Inc. 42
Page 43
RC-E User Manual Management Client (RC-E Manager)
Using Auto-Hide
You can auto-hide panes. An auto-hidden pane is available as a tab to the right or left of the previous position of the pane. When you place your mouse pointer over the tab, the content of the pane slides out. As soon the cursor is positioned outside the pane, it slides back.
To auto-hide a pane click the Auto Hide pushpin in the title bar of the pane you want to auto-hide. Do the following to show and open an auto-hidden pane again:
1. Place your mouse pointer over the tab of the auto-hidden pane to show the pane.
2. Click the Auto Hide pushpin in the title bar of the pane to dock the pane.
Resetting to Default Layout
If you have moved, resized and auto-hidden panes and now want to reset the entire layout of the panes in the Management Client to their default settings, do the following:
1. From the Management Client's View menu, select Reset Application Layout.
2. Restart the application.
Toggling Preview Pane On and Off
You can close the preview pane when working with recorders and devices b y clicking Close in the right side of the Preview pane's title bar.
To reopen the Preview pane (see "Panes Overview" on page 36) select Preview Client's View menu.
Window from the Management
Tip: If the preview pane displays images from many cameras at a high frame rate, it may slow down performance. To specify the number of preview images you want in your pr eview pane, as well as their frame rate, select Options > General from the Tools menu.
Tip: When the preview pane is closed, it uses no resources and improves therefore the computer's performance.
Activate Licenses
You cannot activate more licenses than you have purchased. To view your total number of licenses, expand Basics in the Management Client's Site Navigation pane, and select License Information. If you have added more cameras than you have licenses for, you must get additional licenses before you can activate them.
Activate Licenses Online (on page 44)  Activate Licenses Offline (on page 44) 
Activating Licenses after the Grace Day Period (on page 44)
Activate OnSSI License Portal Account
Before you can use the online license function, you must obtain an OnSSI License Portal account. This step need only be done once.
1. To register with the OnSSI Licensing Portal, open a browser and go to the following URL:
https://rclicensing.onssi.com/CustomerRegistration
On-Net Survei
llance Systems, Inc. 43
Page 44
RC-E User Manual Management Client (RC-E Manager)
On the OnSSI Licensing screen, enter your email address. This will become your user name for the OnSSI
2.
Licensing Portal.
3. Enter the SLC for RC-E. This is the alphanumeric value found on the license file. For instance, the code
should have 11 characters and be in the form similar to: 750-XXXX-XXXX.
4. Click Submit.
5. You will receive an email with your OnSSI Licensing Portal user name and password. Use these creden tials
when activating licenses online.
Activate Licenses Online
1. In the Management Client (RC-E Manager's) Site Navigation pane, expand Basics, right-click License
Information, and select Activate License Online.
2. Enter your OnSSI License Portal username and password.
3. Click OK.
Activate Licenses Offline
1. In the Management Client's Site Navigation pane, expand Basics, right-click License Information, and select
Activate License Offline > Export License for Activation.
This will open a Save Request File dialog box. A default filename is display. You may keep this filenam e or change it. The file that will be created is a license request file with .lrq filename extension. Save the file to a location that is easily accessible.
2. Click Save to create and save the file.
3. Send the license request file by e-mail to [email protected]. Your license request will be verified and activated and an updated license file will be sent back to you via e-
mail. This process typically takes less than 24 hours. However, during busy peak periods or during weekends or holidays, the process may take 48 hours or more. Please plan ahead.
4. When you have received the updated license file (.lic), save it to a location easily accessible from the Management Client (RC-E Manager).
5. In the RC-E Manager's site navigation pane, expand Basics.
6. Right-click License Information, select Activate License Offline > Import Activated License and select the .lic file to import it.
7. Click Open to import the file and complete the activation process.
Activating Licenses after the Grace Day Period
If the grace day period is reached before activation, all cameras which are not activated within the given period will become unavailable, and will not be able to send data to the surveillance system.
If you exceed the grace day period before you activate a licens e, the license is not lost. You can activate the license as usual using either of the above steps (Activating Licenses Online or Offline).
Configuration, added cameras, defined recording servers, and other settings will not be removed from the Management Client if a license is activated too late.
On-Net Survei
llance Systems, Inc. 44
Page 45
RC-E User Manual Management Client (RC-E Manager)
Manage Licenses
When you purchase RC-E, you also purchase a certain number of licenses for device channels. Device channels are typically cameras but could also be dedicated input/output bo xes.
At first, when you have installed the various RC-E components, configured the system, and added recording servers and cameras through the Management Client, the surveillance system runs on temporary licenses which need to be activated before a certain period ends. This is called the 'grace day period'.
When the new surveillance system is working, we recommend that you activate your licenses before you make the final adjustments. The reason is that you must activate your licenses before the grace day period expires, since all recording servers and cameras for which no licenses have been activated will not be able to send data to the surveillance system if the grace day period is expired.
Which Devices Require a License?
You need licenses for the number of device channels - typically cameras but it could also be dedicated input/out boxes - you want to run on the RC-E system. One device channel license enables you to run one camera or one dedicated input/output box. You can use and define an unlimited number of recording servers, microphones, speakers, inputs and outputs.
You can always get more licenses as your surveillance system grows. See Getting Additional Licenses (on page 46).
What to Know When Replacing Cameras?
You can replace a camera licensed in the RC-E system with a new camera, and have the new camera activated and licensed instead.
The total number of purchased device channels corresponds to the total number of cameras that are able to run on the surveillance system simultaneously. If you remove a camera from a recording server, you also free a license.
If you replace a camera with a similar camera (manufacturer, brand, and model), and give the new camera the same IP address as the old one, you will maintain full access to all the camera's databases. In this case, you simply move the network cable from the old camera to the new one without changing any settings in the Management Client, and then activate the license.
If replacing a camera with a different model, you must use the Management Client's Replace Hardware wizard to map all relevant databases of cameras, microphones, inputs, outputs, etc. When done, remember to activate the license. For details on the Replace Hardware wizard, see Replacing Hardware (on page 54).
There is no limit to the number of cameras you can replace.
What to Know about Licenses and OnSSI Federated Architecture?
Refer to OnSSI Federated Architecture Overview (on page 173)
Viewing Your License Information
A comprehensive overview of the licenses in your RC-E recorder is available if you expand Basics in the RC-E Manager's Site Navigation pane (see "Panes Overview" on page 36), and then select Lic bring up the License Information page, on which you can see:
ense Information. This will
Your software license code  The total number of available device channels (typically cameras but it could a lso b e ded icated input/output
boxes) you are licensed to run
On-Net Survei
llance Systems, Inc. 45
Page 46
RC-E User Manual Management Client (RC-E Manager)
How many licenses you have used, both the number of activated licenses and the number of temporary (not
activated) licenses
Whether you need to get additional licenses in order to have enough licenses for all of you r cameras Any expiry dates listed on the page are in the management server's local time. Since you are not necessarily located
in the same time zone as the management server, the management server's current local time is displayed in the bottom right corner of the page.
You can activate licenses online or offline, by expanding Basics in the Site Navigation pane, and right-clicking License Information.
The cameras (or dedicated input/output boxes) for which you do not have a license will not send data to the surveillance system. Cameras added after all available licenses are used are unav ailable. Cameras without licenses will be identified by an exclamation mark symbol when listed in the Management Client' s overview pane (see "Panes Overview" on page 36).
Tip: In the short period until you have obtained additional licenses, you can disa ble some less important cameras to allow some of the new cameras to run instead. See Manage Hardware (on page 53) for more information.
Where I Can See How Many Grace Days I Have Left? This information is also available from the License Information page where you can see if you need to get more licenses so all added c ameras can deliver data to RC-E.
When you add a new camera for which you have a license, you are granted a new full grace day period for the camera in question from the date you added the camera. Therefore the end date of the grace day period displayed on the License information page is for the first added but not activated camera. The duration of the full grace day period can be found in a readme file which is available from Windows' Start menu, by selecting All Programs > RC-E > Read Me.
Getting Additional Licenses
What if you want to add - or if you already have added - more device channels (cameras or dedicated input/output boxes) than you currently have licenses for? In that case, you must buy additional licenses before the cameras will be able to send data to your RC-E system.
To get additional licenses for RC-E, contact your OnSSI vendor, or visit www.onssi.com (http://www.onssi.com). W
hen you have received an updated license file (.lic) with the new licenses, you can activate your licenses.
Tip: In the short period until you get the additional licenses, you can disable some less important cameras to allow some of the new cameras to run instead. To disable or enable a camera, expand Recording Servers in Management Client's Site Navigation pane (see "Panes Overview" on page 36), then select the required recording server, right-click the requ
ired camera, and select Enable.
Remote Connect Services
About Remote Connect Services
The Remote Connect Services feature contains the Axis One-click Camera Connection technology developed by Axis Communications. It enables RC-E 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 a Virtual Private Network (VPN). Only devices holding a valid key can operate within a VPN. This offers a secure tunnel where data can be exchanged between public networks in a safe way.
Remote Connect Services allows you to... Edit credentials within the Axis Dispatch Service
On-Net Surveillance Systems, Inc. 46
Page 47
RC-E User Manual Management Client (RC-E Manager)
Add, edit, and remove ST servers
Register/Unregister and edit Axis One-click cameras  Go to the hardware related to the Axis One-Click camera.
Before you can use Axis One-click Camera Connection, you must first install a suitable ST server environ men t.
Installing an STS Environment for One-click Camera Connection
1. Contact your system provider to obtain the needed user name and password for Axis Dispatch Services
2. Make sure your camera(s) support Axis Video Hosting System, http://www.axis.com/products/avhs/ (http://www.axis.com/products/avhs/).
3. If needed, update your Axis cameras with the newest firmware, http://www.axis.com/techsup/firmware.php (http://www.axis.com/techsup/firmware.php)
4. On each camera's homepage, go to Basic Setup, TCP/IP, and select Enable AVHS and Always
5. From your management server's built-in download web page, install the Axis One-Click Connectio n Component to setup a suitable Axis secure tunnel framework
6. Start the Axis One-Click service from Services(search for services.msc on your machine).
Working with Axis One-click Camera
Editing the Axis Dispatch Service Properties
1. The Properties pane displays relevant dispatch information on the Axis Dispatch Service tab.
2. Edit properties (see "Axis One-Click Camera Connection Properties" on page 48). In the toolbar (see "Management Client Overview" on page 34), click Save.
3.
Adding or Editing Secure Tunnel Servers
1. Do one of the following:
a) To add an ST server, right-click the Axis Secure Tunnel Servers node, select Add Axis Secure Tunnel
Server...
or
b) To edit an ST server, right-click it, select Edit Axis Secure Tunnel Server...
2. In the window that opens, fill in the relevant information (see "Axis One-Click Camera Connection Properties"
ge 48).
on pa
3.
If you chose to use credentials when you installed the Axis One-Click Connectio n Component, make sure to select the Use credentials check box and fill in exactly the same user name and password as used for the Axis One-Click Connection Component.
4. Click OK.
On-Net Survei
llance Systems, Inc. 47
Page 48
RC-E User Manual Management Client (RC-E Manager)
Removing Secure Tunnel Servers
1. To remove an ST server, right-click it, select Remove Axis Secure Tunnel Server...
2. Click Yes.
Registering a new Axis One-click Camera
1. To register a camera under an ST server, right-click it, select Register Axis One-click Camera...
2. In the window that opens, fill in the relevant information (see "Axis One-Click Camera Connection Properties" on pa
ge 48).
3. Click OK. The camera will now appear under the relevant ST server.
4.
The color coding of the camera is either:
Red: Initial state—registered, but not connected to the ST server  Yellow: Registered—connected to the ST server, but not added as hardware  Green: Added as hardware—may or may not be connected to the ST server.
When added, status will always be green. The connection status (see "Read Server Service State Icons" on page
199) is then—as normal—reflected by Devic In the overview pane, you may group your cameras for an easier overview. If you choose not to register your camera at the Axis dispatch service at this point, you can do so later from the right-
click menu (select Edit Axis One-click Camera...).
es on Recording Servers in the overview pane.
Unregistering an Axis One-click Camera
1. To unregister a camera under an ST server, right-click it, select Unregister Axis One-click Camera.
2. In the dialog that appears, make sure the check mark is selected and click Yes.
3. The camera will disappear from under the relevant ST server.
Axis One-Click Camera Connection Properties
Camera password: Enter/Edit. Provided with your camera at purchase. For further details, see your camera's
manual or www.axis.com (http://www.axis.com).
Cam Description: Enter/Edit a description of the item. Not required.  External address: Enter/Edit the http address of the ST server where the camera(s) connect.  Internal address: Enter/Edit the http address of the ST server where the recording server connects.
Name: If needed, edit the name of the item.
On-Net Survei
era user: See details for Camera password.
Tip: Remember http:// in front of both the external and internal address.
llance Systems, Inc. 48
Page 49
RC-E User Manual Management Client (RC-E Manager)
Owner authentication key: See Camera password. Passwords (for Dispatch Server): Enter password. Must be identical to the one received from OnSSI.  Passwords (for ST server): Enter password. Must be identical to the one entered when the Axis One-Click
Connection Component was installed.
Register/Unregister at the Axis Dispatch Service: Indicate whether you wish to register your Axis camera with
the Axis dispatch service. Can be done at time of setup or later.
Serial number: Same as the MAC address. See Camera password. Use credentials: If it was decided—during installation of the ST server—to use credentials, select the check box.  User name (for Dispatch Server): Enter user name. Must be identical to the one received from OnSSI.  User name (for ST server): Enter user name. Must be identical to the one entered when the Axis One-Click
Connection Component was installed.
Servers
Add Hardware (Cameras, etc.)
The Add Hardware wizard helps you detect IP hardware devices, such as cameras and video encoders, on your network and add them to recording servers on your RC-E system.
To access Add Hardware, expand the Servers folder in the Management Client's Site Navigation pane (see "Panes Overvie page 36) right-click the required recording server and select Add Hardware...
T scanning, Manual and Remote connect hardware. With the Express option, RC-E automatically scans for available hardware on the recording server's local network. With Address range scanning, RC-E scans defined network IP address ranges and detects hardware models. With Manual, you manually specify the IP address and port for each device. With Remote connect hardware, you can add hardware connected via a remotely connected server. All options offer the possibility of automatically detecting the correct hardware drivers.
Tip: If you are new to RC-E: use the Express hardware detection as it will guide you through each of the steps involved in detecting and adding your IP devices.
It is strongly advised that you only add a physical hardware device to one recording server at the time.
w" on page 36) and select the Recor
he wizard offers you four ways of detecting and adding hardware devices: Express (recommended), Address range
ding Server node, then in the overview pane (see "Panes Overview" on
Express
The Express (recommended) option automatically discovers hardware models on the recording server's local network.
1. Select Express (recommended) and click Next.
2. Specify user names and passwords if your hardware devices are not using the factory default user name and password. You can add as many user names and passwords as required by clicking Add. Remember to select the Include check box for each required device.
When ready, click Next.
3. Wait while the hardware is detected. A status indicator will show the detection process.
On-Net Surveillance Systems, Inc. 49
Page 50
RC-E User Manual Management Client (RC-E Manager)
Tip: Select the Show
hardware running on other recording servers check box to see if detected har dware is
running on other recording servers.
Once detection is complete, click Next.
4. Wait while device-specific information is collected for each hardware device. A status indicator will show the detection process. If collecting hardware information for a device is unsuccessful, click the Failed error message to see why. Once collection is complete, click Next.
Choose to enable or disable successfully detected hardware and cameras. Detected hardware, such as hardware device, camera, microphone and speaker is listed individuall y, al lowing you to, for example, add a hardware device's camera without enabling its speaker if needed.
You can change the name of the hardware by clicking Hardware name and choosing between:
o [Hardware model] [address] o [Hardware model]
Additionally, you can change name of the device by clicking Device name and choosing between:
o [Hardware name] - [Device type] [number] o [Device type] [number] on [hardware name] o [Address] - [Device type] [number]
A change of name for hardware and/or device will be applied to all available hardware/devices and will take effect immediately.
Tip: You can disable the hardware, but enable its devices if necessary.
When ready, click Next.
5. Select a default group for all device types, or group the devices individuall y. The devices are listed according to type, for example, camera, microphone, speaker. Click Finish.
Address Range Scanning
The Address Range Scanning option scans your network for relevant hardware devices based on your specifications regarding required IP ranges, drivers, and device user names and passwords.
1. Select Address Range Scanning and click Next.
2. Specify user names and passwords if your hardware devices are not using the factory default user name and password. You can add as many user names and passwords as required by clicking Add . Remember to select the Include check box for each required device. You must add and include at least one user name and password in order for the wizard to proceed.
When ready, click Next.
3. Select which drivers to use when scanning. By default, RC-E will use all known drivers. If your organization only uses certain hardware devices and/or models, you can achieve faster scanning by selecting only the drivers required for those hardware devices. Click Next.
Tip: The list of drivers is typically very long, and by default all drivers are selected. With Select All and Clear All, you can avoid having to select/clear all check boxes manually.
4. Specify the IP address network ranges you want to scan for hardware.
On-Net Survei
llance Systems, Inc. 50
Page 51
RC-E User Manual Management Client (RC-E Manager)
o Start ad
dress: First IP address in required range.
o End address: Last IP address in required range. The start and end IP address may be identical, allo wing
you to only scan for a single hardware device if needed.
o Port: Port number(s) on which to scan. Default is port 80. If your hardware devices are located behind a
NAT-enabled router or a firewall, you may need to specify a different port number. When this is the case, also remember to configure the router/firewall so it maps the port and IP addresses used by the hardware devices.
You can add as many network ranges as needed by clicking Add to add another row. You can add any network address between 0.0.0.1 and 255.255.255.255. At least one network range must be selected before you can continue.
Remember to select the Include check box for each required range. You can only specify IPv4 addresses when using Address Range Scanning. Wait while the hardware is detected. A status indicator will show the detection process. If you successfully detect hardware on a specified network range, a Success message will appear in the
Status column. If you fail to add a network range, you can click the Failed error message to see why.
Tip: Select the Show hardware running on other recording servers check box to see if detected hardware is running on other recording servers.
Once detection is complete, click Next.
5. Wait while device-specific information is collected for each hardware device. A status indicator will show the detection process. If collecting hardware information for a device is unsuccessful, click the Failed error message to see why the collection of information has failed. Once collection is complete, click Next.
6. Choose to enable or disable successfully detected hardware and cameras. Detected hardware, such as hardware device, camera, microphone and speaker is listed individuall y, al lowing you to, for example, add a hardware device's camera without enabling its speaker if needed.
You can change the name of the hardware by clicking Hardware name and choosing between:
o [Hardware model] [address] o [Hardware model]
Additionally, you can change name of the device by clicking Device name and choosing between:
o [Hardware name] - [Device type] [number] o [Device type] [number] on [hardware name] o [Address] - [Device type] [number]
A change of name for hardware and/or device will be applied to all available hardware/devices and will take effect immediately.
Tip: You can disable the hardware, but enable its devices if necessary.
When ready, click Next.
7. Select a default group for all device types. The devices are listed according to type, for example, camer a, microphone, speaker. Click Finish.
On-Net Survei
llance Systems, Inc. 51
Page 52
RC-E User Manual Management Client (RC-E Manager)
Manual
The Manual option lets you specify details about each hardware device separately. This can be a good choice if you only want to add a few hardware devices, and you know their IP addresses, required user names and passwords, etc.
1. Select Manual and click Next.
2. Specify user names and passwords if your hardware devices are not using the factory default user name and password. You can add as many user names and passwords as required by clicking Add. Remember to select the Include check box for each required device. You must choose to add and include at least one user name and password in order for the wizard to proceed.
When ready, click Next.
3. Now select which drivers to use when scanning. By default, RC-E will use all known drivers. If your organization only uses certain hardware devices and/or models, you can achieve faster scanning by selecting only the drivers required for those hardware devices.
Tip: The list of drivers is typically very long, and by default all drivers are selected. With Select All and Clear All , you can avoid having to select/clear all check boxes manually.
When ready, click Next.
4. Specify information for the hardware you want to add. You can also option ally select the type of driver you want to add to speed up hardware detection.
o Address: Specify the IP address of the hardware, you want to add. o Port: Specify the port number to which the camera is added. o Hardware driver: Select the driver of the hardware you want to add. Or select Auto-detect to let the
wizard detect which driver to install.
5. Wait while the hardware is detected. A status indicator will show the detection process. Select or clear the network ranges to use in the detection process.
If you successfully detect hardware, a Success message will appear in the Status column. If you fail to add a network range, click the Failed error message to see why.
Tip: Select the Show hardware running on other recording servers check box to see if detected hardware is running on other recording servers.
Once detection is complete, click Next.
6. Choose to enable or disable successfully detected hardware and cameras. Detected hardware, such as hardware device, camera, microphone and speaker is listed individuall y, al lowing you to, for example, add a hardware device's camera without enabling its speaker if needed.
You can change the name of the hardware by clicking Hardware name and choosing between:
o [Hardware model] [address] o [Hardware model]
Additionally, you can change name of the device by clicking Device name and choosing between:
o [Hardware name] - [Device type] [number] o [Device type] [nu o [Address] - [Device type] [number]
On-Net Survei
llance Systems, Inc. 52
mber] on [hardware name]
Page 53
RC-E User Manual Management Client (RC-E Manager)
A chang
e of name for hardware and/or device will be applied to all available hardware/devices and will take
effect immediately.
Tip: You can disable the hardware, but enable its devices if necessary.
When ready, click Next.
7. Select a default group for all device types or group the devices individuall y . The devices are listed according to type, for example, camera, microphone, speaker. Click Finish.
Remote Connect Hardware
Remote connect hardware automatically scans for hardware connected via a remotely connected server.
1. Select Remote connect hardware and click Next.
2. Wait while the hardware is detected. A status indicator will show you how far you are in the detection process.
3. Once detection has completed, select which hardware you want to add and click Next.
Manage Hardware
For each recording server on your system, you have several options for managing ad ded IP hardware. Most configuration and management of individual camera settings (such as a camera's recording settings), input
settings, and output settings takes place on a more detailed level; see Manage Cameras (on page 75), Manage Inputs (see "Manage Input" on page 88), and Manage Outputs (see "Manage Output" on page 91).
Editing Basic Hardware Settings (IP, etc.)
You are able to edit basic settings, such as IP address/host name, for added hardware:
1. In the overview pane (see "Panes Overview" on page 36), expand the required recording server, right-click the hard
2. From the menu that appears, select Edit IP Hardware...: This opens the Edit Hardware window, in which you can edit the following: o Name: The name of the hardware in the Management Client's lists, etc.
Tip: You can also quickly change the name of a hardware device by selecting Rename IP Hardware... from the menu.
o Description: (Optional) A description or other information about the hardware device. It will, among other
o Hardware URL: URL, IP address, or host name of the hardware device. o User name: Required to access and use the hardware device. o Password: Required to access and use the hardware device. o Type: Non-editable field indicating the hardware driver used for the hardware device.
3. Click OK.
ware device you wish to edit.
places, appear when you pause your mouse pointer over the hardware device in the overview pane.
On-Net Survei
llance Systems, Inc. 53
Page 54
RC-E User Manual Management Client (RC-E Manager)
Deleting Individual Hardware
IMPORTANT: When deleting a hardware device, all its recordings are deleted permanent ly.
1. In the overview pane (see "Panes Overview" on page 36), expand the required recording server, right-click the no lo
nger needed hardware device.
2. From the menu that appears, select Delete IP Hardware.
Tip: As an alternative, press DELETE on your keyboard.
3. Confirm that you want to delete the hardware device.
4. The hardware device is removed from the recording server's listings in the Management Client.
Tip: If you ever need to add the hardware device to a recording server again, select the required recording server and use the Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49) wizard.
Replacing Hardware
When you replace a physical camera (hardware device) on your network with another hardware device, you must know the IP address, port, user name and password of the new hardware device.
Furthermore, when replacing hardware devices, note that your system might be affected by license limitations (see "Manage Licenses" on page 45). Using the Activate Online (see "Activate Licenses" on page 43)wizard, you must reactivate your licenses after replacing hardware devices. Also note, that if the new number of cameras, microphones, inputs, outputs, etc. exceeds the old number of cameras, microphones, inputs, outputs, etc. you might also have to buy new licenses (see "Manage Licenses" on page 45). See your License Information (see "Manage Licenses" on page 45).
1. In the Overview pane (see "Panes Overview" on page 36), expand the required recording server, right-click the hard
ware device you wish to replace.
2. From the menu that appears, select Replace Hardware.
3. The Replace Hardware wizard appears. Click Next.
4. In the wizard, in the Address field (marked by red arrow in the image), enter the IP address of the new hardware. If known, select relevant hardware device driver from the Hardware Driver drop-down list (marked by red arrow in the image). Otherwise select Auto Detect. If port, user name or/and password data is different for the new device, also correct this before starting the auto detect process (if needed).
Tip: The wizard is pre-filled with data from the existing hardware device. If you replace it with a similar hardware device, you can reuse some of this data - for example, port and driver information.
5. Do one of the following:
o If you selected the required hardware device driver directly from the list, click Next. o If you selected Auto Detect in the list, click Auto Detect, wait for this process to be successful, click Next.
This step is designed to help you map devices and their databases, depending on the n umber of individual cameras, microphones, inputs, outputs, etc., attached to the old hardware device and the new respectively.
It is important to consider how to map databases from the old hardware device to databases of the new hardware device. You do the actual mapping of individual cameras, microphones, inputs, outputs, etc. by selecting a corresponding camera, microphone, input, output or None in the right-side column.
IMPORTANT: Make sure to map all cameras, microphones, inputs, outputs, etc. Contents stored in databases belonging to cameras, microphones, inputs, outputs, etc. mapped to None, will be lost.
On-Net Survei
llance Systems, Inc. 54
Page 55
RC-E User Manual Management Client (RC-E Manager)
Click Next. You are presented with a list of hardware to be added, replaced or removed. Click Confirm.
6.
7. Final step is a summary of added, replaced and inherited devices and their settings. Click Copy to Clipboard to copy contents to an external source (for, for example, reporting purposes) or/and Close to end the wizard.
Renaming Hardware
1. In the overview pane (see "Panes Overview" on page 36), expand the required recording server, right-click the hardware device you wish to rename.
2. From the menu that appears, select Rename IP Hardware.
Tip: As an alternative, press F2 on your keyboard.
3. Overwrite the name of the hardware.
Disabling/Enabling Hardware
Added hardware is by default enabled. In the overview pane (see "Panes Overview" on page 36), under the required recording server, enabled/disabled
ware devices are indicated.
hard
Disabling
Disable added hardware, for example, for licensing or performance purposes:
1. In the overview pane (see "Panes Overview" on page 36), expand the required recording server, right-click the hard
ware device you wish to disable.
2. From the menu that appears, select Enabled to clear it.
Deleting All Hardware on a Recording Server
IMPORTANT: When deleting hardware devices, all recordings from the hardware devices in question will be deleted permanently.
1. In the overview pane (see "Panes Overview" on page 36), right-click the required recording server where you w
ant to delete all hardware.
2. From the menu that appears, select Delete All Hardware.
3. Confirm that you want to delete all hardware on the selected recording server.
Renaming Individual Devices
1. In the overview pane (see "Panes Overview" on page 36), expand the required recording server and the required hardware device. Right-click the camera, input, or output you wish to rename.
2. From the menu that appears, select Rename Device.
Tip: As an alternative, press F2 on your keyboard.
3. Overwrite the name of the selected device.
On-Net Survei
llance Systems, Inc. 55
Page 56
RC-E User Manual Management Client (RC-E Manager)
Enabling/Disabling Individual Devices
Cameras are by default enabled. Microphones, speakers, inputs and outputs are by default disabled. This means that microphones, speakers, inputs and outputs must be individually enabled before they can be used on
the RC-E system. The reason for this is that surveillance systems inherently rely on cameras, whereas the use of microphones, etc. is highly individual depending on organi z ations' needs.
In the overview pane (see "Panes Overview" on page 36), under the required server, enabled/disabled devices are indicated:
The same method for enabling/disabling is used for cameras, microphones, speakers, inputs, and outputs.
Enabling
1. In the overview pane (see "Panes Overview" on page 36), expand the required recording server and the required hardware device. Right-click the camera, input, or output you wish to enable.
2. From the menu that appears, select Enabled.
About Storage and Archiving
When a camera or device records video and/or audio, all specified recordings are per default stored in the storage area defined for the device. More precisely in the storage area's default rec ording database named Recording. A storage area has no default archive(s), but these can easily be created.
Depending on recording settings, the storage areas's recording database will most likely run full at some point and its contents need to be archived in order to be saved. It is therefore possible to create archives within the default storage area and start an archiving process. Furthermore, it is possible to create alternative storage area(s) and configure that selected video/audio recordings must be stored/archived here.
Archiving is the automatic transfer of recordings from a camera's or device's default database to another location. This way, the amount of recordings you are able to store will not be limited by the size of the device's recording database. Archiving also makes it possible to back up your recordings on backup media of your choice.
Storage and archiving is configured on a per-recording server basis. To ease explanations, the following mostly mentions cameras and video, but al is true about speakers and
microphones and audio and sound as well. IMPORTANT: We recommend that you use a dedicated hard disk drive for the recording server database. Using a
dedicated hard disk drive for the database will prevent low disk performance. Furthermore, when formatting the hard disk, it is important to change its Allocation unit size setting from 4 to 64 kilobytes. This is to significantly improve recording performance of the hard disk. You can read more about allocating unit sizes and find help at http://support.microsoft.com/kb/140365/en-us (see http://support.microsoft.com/kb/140365/en-us ­http://support.microsoft.com/kb/140365/en-us).
IMPORTANT: The oldest data in a database will always be auto-archived (or deleted if no next arch ive is defined) when less than 5GB of space is free. If less than 1GB space is free, data will be deleted. A database always requires 250MB of free space; if this limit is reached (if data is not deleted fast enough), no more data will be written to the database until enough space has been freed. The actual maximum size of your database will thus be the amount of gigabytes you specify, minus 5GB.
Attaching Devices to a Recording Server
Once you have configured the storage area and archiving settings for a recording server (where to store recordings, archives, how often to transfer recordings to archives, etc.), you can enable storage and archiving for individu al
On-Net Survei
llance Systems, Inc. 56
Page 57
RC-E User Manual Management Client (RC-E Manager)
cameras or a g
roup of cameras. This is done from the individual devices or from the device group, see Attaching
Individual Devices or a Group of Devices to a Storage Area (on page 58).
Effective Archiving
When archiving is enabled for a camera or a group of cameras, the contents of the camera(s)' database will automatically be moved to an archive at regular intervals.
Depending on your requirements, you are able to configure one or more archives for each of your databases. Archives can be located either on the recording server computer itself, or at another location which can be reached by RC-E , for example on a network drive.
By setting up your archiving in an effective way, you can prune and groom your database storage area usage significantly if needed. Often, it is desired 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 and sound quality a bit. Effective pruning and grooming can help ensure this and can be handled from the Storage tab (see " Storage Tab (Recording Server Properti
Recording database retention  Recording database size  Archive retention  Archive size  Archive schedule  Encryption
es)" on page 65) of a recording server by adjusting s
everal interdependent settings such as:
Frames Per Second (FPS). The size fields define the size of the camera's database, exemplified by the cylinder, and its archive(s) respectivel y: By means of retention time and size setting for the recording database, exemplified by the white area in the cylinder,
you define how old recordings must be before they are archived. In our illustrated example, recordings are archived when they have "sifted" down into the green area of the database cylinder, or in other words: when they are old enough to be archived.
The retention time and size setting for archives define how long the recordings remain in the archive; recordings remain in the archive for the time specified, or until the archive has reached the specified size limit. When these settings are met, RC-E begins to overwrite old recordings in the archive.
The archiving schedule defines how often and at what times archiving take s place. Encryption and FPS determine the size of the data in the databases. To have recordings archived, all these parameters must be set up in accordance with each other. This means that the
retention period of a next coming archive must always be longer than the retention period of a current archive or recording database. This is due to the fact that the number of retention days stated for an archive includes all retention stated earlier in the process. Furthermore, archiving must always take place more frequently than the retention period is set to, otherwise you risk losing data. If you have a retention time of 24 hours, any data older than 24 hours will be deleted. Therefore, to get your data safely moved to the next archive, it is important to run archiving more often than every 24 hours.
Example: These storage areas (image to the left) has a retention time of 4 days and the following archive (image to the right) a retention time of 10 days. Furthermore, archiving is set to occur every day at 10:30, ensuring a much more frequent archiving than retention time is set to.
Tip: You can also control archiving by use of rules and events. See About Rules and Events (see "About Events" on pag
e 97) and Events Overview (on page 128).
On-Net Survei
llance Systems, Inc. 57
Page 58
RC-E User Manual Management Client (RC-E Manager)
Attaching Individual Devices or a Group of Devices to a Storage Area
Once a storage area is configured for a recording server, you can enable it for individual devices (cameras, microphones or speakers) or a group of devices. You can also select which of a recording server's storage areas should be used for the individual device or the group.
1. In the Site Navigation pane (see "Panes Overview" on page 36), expand Devices a
nd select either Cameras,
Microphones or Speakers as required.
2. In the Overview pane (see "Panes Overview" on page 36), select the required device or a device group.
3. In the Properties pane, select the Record tab.
4. In the Storage area, select Select...
5. In the dialog that appears, select the wanted database, click OK.
6. In the toolbar (see "Management Client Overview" on page 34), click Save.
Viewing Archived Recordings
Archived recordings may be viewed in the Ocularis Client. As long as the archived recordings are stored locall y or on accessible network drives, you can use the Ocularis Client's many features (kinetic timeline, motion slicing, evidence export, etc.) when browsing archived recordings; just like you would with recordings stored in a cameras' regular databases. The fact that you are viewing archived recordings will be completely transparent.
Remember that individual user rights may prevent particular users from viewing recordings from particular cameras ­just as is the case when browsing recordings from cameras' regular databases.
Backing Up Archived Recordings
Many organizations want to back up their recordings, using tape drives or similar. Exactly how you do this is highly individual, depending 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. Creating backups based on the content of individual camera databases may cause sharing violations or other malfunctions.
When scheduling a backup, make sure the backup job does not overlap with your specified archiving times.
Tip: You are able to view each recording server's archiving schedule in each of a recording server's archives, on the
Storage tab (see "Storage Tab (Recording Server Properties)" on page 65).
Knowing Archive Structure Lets You Target Backups
When recordings are archived, they are stored in a certain sub-directory structure within the archive. During all regular use of your RC-E system, the sub-directory structure will be completely transparent to the system's
users, as they browse all recordings with the Ocularis Client regardless of whether the recordings are archived or not. Knowing the sub-directory structure is thus primarily interesting if you want to back up your archived recordings (see "Archive Structure" on page 59).
Using the Ocularis Client to View Archived Video
You can use the Ocularis Client to view archived video. See the Ocularis Client documentation for details.
On-Net Survei
llance Systems, Inc. 58
Page 59
RC-E User Manual Management Client (RC-E Manager)
Archive Structure
When recordings are archived, they are stored in a certain sub-directory structure within the archive. During all regular use of your RC-E system, the sub-directory structure will be completely transparent to the system's
users, as they browse all recordings with the Ocularis Client regardless of whether the recordings are archived or not. Knowing the sub-directory structure is thus primarily interesting if you want to back up your archived recordings.
In each of the recording server's archive directories, separate sub-directories are automatically created. These sub­directories are named after the name of the device and the name of the archive database.
Since you are able to store recordings from different cameras in the same archive, and since archiving for each camera is likely to be performed at regular intervals, further sub-directories are also automatically added.
These sub-directories each represent approximately an hour' s worth of recordings. The one-hour split makes it possible to remove only relatively small parts of an archive's data if the maximum allowed size of the archive is reached.
The sub-directories are named after the device, followed by an indication of whether recordings come from an edge camera or via SMTP (if relevant), plus the date and time of the most recent database record contained in the sub­directory.
Naming structure:
...[Storage Path]\[Storage name]\[device-name] - plus date and time of most recent recording]\
If from edge camera:
...[Storage Path]\[Storage name]\[device-name] (Edge) - plus date and time of most recent recording]\
If from SMTP:
...[Storage Path]\[Storage name]\[device-name] (SMTP) - plus date and time of most recent recording]\
Real life example: ...F:\OurArchive\Archive1\Camera 1 on Axis Q7404 Video Server(10.100.50.137) -
2011-10-05T11:23:47+02:00\
Even further sub-directories are automatically added. The amount and nat ure of these sub-directories depend on the nature of the actual recordings. For example, several different such sub-directories will be added if the r ecord ings are technically divided into sequences; something which is often the case if motion detection has been used to trigger recordings.
If you want to back up your archives, knowing the basics of the sub-directory structure enables you to target your backups.
Examples: If wishing to back up the content of an entire archive, back up the required archive directory and all of its content; for
example everything under:
...F:\OurArchive\
If wishing to only back up the recordings from a particular camera from a particular period of time, back up the contents of the relevant sub-directories only; for example everything under:
...F:\OurArchive\Archive1\Camera 1 on Axis Q7404 Video Server(10.100.50.137) ­2011-10-05T11:23:47+02:00\
On-Net Survei
llance Systems, Inc. 59
Page 60
RC-E User Manual Management Client (RC-E Manager)
Archiving and Virus Scanning
If you are using virus scanning software on the computer on which the camera databases you want to archive ar e located, or on a computer to which data is archived, it is likely that the virus scanning will use a considerable amount of system resources on scanning all the data which is being archived.
This may affect system performance negatively. Also, virus scanning software may temporarily lock each file it scans, which may further impact system performance negatively.
If possible, you should therefore disable any virus scanning of camera databases and archiving locations.
Frequently Asked Questions about Archiving
What happens if a storage area becomes unavailable? If a storage area becomes unavailable-for example if the storage area is located on a network drive, and the connection to the drive is lost— it will not be possible to store recordings in the storage area. RC-E registers the availability of its recording servers' storage areas. This means that when a storage area becomes available again, it will again be possible to save recordings in the storage area. However, any recordings from the period in which the storage area was unavailable will be lost. When creating rules (see "Manage Rules" on page 133), you can use the events Database Storage Area Unavailable and Database Storage Area Available to trigger actions, such as the automatic sending of e-mail to relevant people in your organization (see Events Overview (on page 128) for more information). Furthermore, info area becoming unavailable/available will be logged (see "Manage Logs" on page 158).
Ho
w do I ensure that archiving is set up correctly? Archives are set up by adjusting several interdepende nt
parameters correctly as described previously. Can I create an archive on a network drive? Archives can be located either on the rec ording server computer itself,
or at another location which can be reached by RC-E, for example on a network drive. What happens when the maximum size of an archive is reached? When you create archives from the Storage tab
(see "Storage Tab (Recording Server Properties)" on page 65), you specify a maximum size limit for the days and gigabytes. When either of the two maximum limits is reached, recordings in excess of the specified number of days/gigabytes will be removed. However, in order not to remove more recordings than necessary, excess recordings will be removed in chunks of approximately one hour's worth of recordings.
What happens if a scheduled archiving fails? If a scheduled archiving fails, for example because the archive is located on a network drive which is temporarily unavailable, RC-E will retry archiving after an hour. If that fails, another retry will take place after yet another hour, and so forth.
If the time of the next scheduled archiving is reached between two retries, an archiving attempt will be made at the scheduled time; if that attempt fails, OnSSI RC-E will retry archiving after an hour, and so forth.
What happens if archiving is not finished before the next scheduled archiving? Your RC-E system inserts a compulsory period of archiving-free time after each finished archiving job. This ensures that archiving jobs do not overlap in time.
rmation about a storage
archive, in
Manage Recording Servers
OnSSI RC-E recording servers are used for recording video feeds, and for communicating with cameras and other devices. An RC-E surveillance system will typically contain several recording servers, although only a single recording server is required for the system to work.
Recording servers on your system— i.e. computers with the RC-E recording server software installed, an d configured to communicate with an RC-E management server— will be listed in the Management Client's overview pane (see "Panes Overview" on page 36) when you expand the Servers folder in the Overview" on page 36) and then select the Recording S
Backward compatibility with recording servers from RC-E versions older than 3.0 is limited. You can still access recordings on such older recording servers; but in order for you to be able to change their configuration, they must be
On-Net Survei
llance Systems, Inc. 60
Site Navigation pane (see "Panes
ervers node.
Page 61
RC-E User Manual Management Client (RC-E Manager)
of version 3.0 or later. It is thus highly recommended that all recording servers in your RC-E system are upgraded (see "Upgrade from Previous Version" on page 28) to the latest possible version.
IMPORTANT: When the Recording Server Service is running, it is very important that neither Windows Explorer nor other programs are accessing Media Database files or folders associated with your OnSSI RC-E surveillance setup. Otherwise, the recording server might not be able to rename or move relevant media files. Unfortunately, this might bring the recording server to a halt. If this situation has already occurred, stop the Recording Server Service, close the program accessing the media file(s) or folder(s) in question, and simply restart the Recording Server Service.
Authorizing a Recording Server
When first using the system, or when new recording servers have been added to the system, you must authorize the new recording servers.
Why must I authorize recording servers? In an RC-E system, recording servers point to management servers, not the other way round. In theory, recording servers which you do not want to include in your surveillance system could thus be configured to connect to your management servers. By authorizing recording servers before they can be used, surveillance system administrators have full control over which recording servers are able to send information to which management servers.
1. Expand the Servers folder in the Management Client's Site Navigation pane and select the Recording Servers node.
2. Right-click the required recording server in the overview pane.
3. From the menu that appears, select Authorize Recording Server: After a short moment, the recording server will be authorized and ready for further configuration.
Viewing/Editing a Recording Server's Properties
When a recording server is authorized, you are able to view/edit the recording server's properties, including its database storage area settings:
When you select the required recording server in the Management Client's overview pane, the recordin g server's properties are displayed in the properties pane (see "Panes Overview" on page 36). Expand the required recording server to see
which devices are connected to the recording server. While the Management Client loads information
about the recording server, the text (... expanding) is displayed next to that recording server:
Adding Hardware (Cameras, etc.) to a Recording Server
You add IP hardware, such as cameras, video encoders, etc., to recording servers on your RC-E system through the Add Hardware wizard. The wizard helps you scan your network for relevant hardware. See the wizard Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49) for more information.
Managing Hardware on a Recording Server
You have several options for managing IP hardware, such as cameras, video encoders, etc., on recording servers on your RC-E system. See Manage IP Hardware (see "Manage Hardware" on page 53).
Renaming a Recording Server
1. Expand the Servers folder in the Management Client's Site Navigation pane and select the Recording Servers node.
On-Net Survei
llance Systems, Inc. 61
Page 62
RC-E User Manual Management Client (RC-E Manager)
Right-click the required recording server listed in the overview pane.
2.
3. From the menu that appears, select Rename Recording Server.
Tip: As an alternative to using the menu, press the F2 key on your keyboard.
4. You are now able to overwrite the name of the recording server in the overview pane.
Removing a Recording Server
IMPORTANT: Removing a recording server will remove all configuration specified for the recording server through the Management Client, including all of the recording server's associated hardware (cameras, input devices, etc.).
1. Expand the Servers folder in the Management Client's Site Navigation pane and select the Recording Servers node.
2. Right-click the no longer required recording server in the overview pane.
3. From the menu that appears, select Remove Recording Server.
4. You will be asked to confirm that you want to remove the recording server and all of its associated hardware from the RC-E system. If you are sure, click Yes.
5. The recording server and all of its associated hardware will be removed.
Replacing a Recording Server
If a recording server is malfunctioning and you want to replace it with a new server, while letting the ne w server inherit the settings of the old, malfunctioning recording server, do the following:
1. Retrieve the recording server ID from the old recording server;
a) In the Management Client's Site Navigation pane select Recording Servers, in the Overview pane select the
old, required recording server.
b) In the Management Client's Properties pane, select the Storage tab. c) Press and hold down the CTRL key on your keyboard while selecting the Info tab. d) Copy the recording server ID found in the lower part of the Info tab. Do not copy ID = but only the ID itself.
IMPORTANT: Stop the Recording Server service (see "Management Server Service and Recording Server Service" on page 198) on the old recording server, then in Windows' Services set the service's Startup type to Disabled.
2. Replace recording server ID on the new recording server:
a) Make sure that the Recording Server service is stopped (see "Management Server Service and Recording
Server Servic
It is very important that you do not start two recording servers with identical IDs at the same time.
b) On the new recording server, open an explorer and go to C:\ProgramData\OnSSI\OnSSI RC-E Recording
Server or the path where your recording server is located.
e" on page 198) and disabled on the old recording server.
c) Open the file RecorderConfig.xml. d) Delete the ID stated in between the tags <id> and </id>.
On-Net Survei
llance Systems, Inc. 62
Page 63
RC-E User Manual Management Client (RC-E Manager)
Paste the copied recording server ID in between the tags <id> and </id>. Save the RecorderConfig.xml file.
e) f) Restart the recording server service. When the new Recording Server service starts up, the recording server
has inherited all settings on the old recording server.
Tip: This procedure also applies if you re-install Windows on the computer running the recording server, even if you do not replace the computer running the recording server.
Troubleshooting: Missing Recording Servers
If you have installed several recording servers on your surveillance system, the recording servers should automatically be listed in the Management Client.
If your Management Client does not list all the recording servers you have installed, the most likely reason is that the missing recording servers have not been correctly configured to connect to a management server (in an RC-E system, recording servers point to management servers, not the other way round).
The configuration normally takes place during one of the steps in the recording server installation process. Here, you specified recording server setup parameters, among these the IP address or host name of the management server to which the recording server should be connected:
Fortunately, you do not have to re-install recording servers in order to specify which management servers they should connect to. Once a recording server is installed, you can verify/change its basic configuration the following way:
How to Verify/Change which Management Server a Recording Server Connects to:
In order to verify/change a recording server's basic configuration, the recording server servi ce must be stopped. This means that recording and live viewing will not be possible while you verify/change the recording server's basic configuration.
1. On the computer running the recording server, right-click the recording server icon in the notification area:
Tip: The notification area is occasionally also known as the system tray, it is located at the far right of the recording server computer's Windows taskbar.
2. From the menu that appears, select Stop Recording Server Service:
3. Right-click the notification area's Recording Server icon again.
4. From the menu that appears, select Change Settings...: The Recording Server Settings window appears. Verify/change the following settings: o Management server hostname/IP address: Lets you specify the IP address (example:
123.123.123.123) or host name (example: ourserver) of the management server to which the recording server should be connected. This information is necessary in order for the recording server to be able to communicate with the management server.
o Management server port: Lets you specify the port number to be used when communicating with the
management server. Default is port 9993, although you are able to change this if required.
5. Click OK.
6. To start the Recording Server service again, right-click the notification area's Recording Server icon, and select Start Recording Server Service:
On-Net Survei
llance Systems, Inc. 63
Page 64
RC-E User Manual Management Client (RC-E Manager)
Failover Tab (Recording Server Properties)
A failover server is a spare recording server which can take over if a regular recording server becomes unavailable; see also About Failover Servers (see "Manage Failover Servers" on page 192).
our organization uses failover servers, use the Failover tab to select which groups of failover servers should take
If y over from a regular recording server if the recording server in question becomes unavailable.
To access the Failover tab, select the required recording server in the overview pane (see "Panes Overview" on page
36), then select the Failover tab in the
Selecting Required Failover Groups
Benefits of Using Failover Groups
Grouping has a clear benefit: When you specify which failover servers should be able to take over from a recording server, you do not select a particular failover server; rather you select a failover grou p. If the selected group contains more than one failover server, this gives you the security of being able to have more than just one failover server ready to take over if the recording server becomes unavailable. For information about configuring failover groups, see Manage Failover Servers (on page 192).
properties pane (see "Panes Overview" on page 36).
Prima
ry and Secondary Failover Group
For each recording server, you are able to select a primary and an optional secondary failover group. If the recording server becomes unavailable, a failover server from the primary failover group will take over. If you have also selected a secondary failover group, a failover server from the secondary group will take over in case all failover servers in the primary failover group are busy. This way, you only risk not having a failover solution in the rare case when all failover servers in the primary as well as in the secondary failover group are busy.
How to Select Required Failover Groups
1. Select the required failover group from the Primary failover group list.
2. If you also want a secondary failover group for the recording server, repeat the process in the Secondary
failover group list.
You cannot select the same failover group for use as both primary and secondary failover group.
Failover Service Communication Port
By default, TCP port 11000 is used for communication between recording servers and failover servers. Such communication is primarily about the configuration of the recording server from which the failover server should take over.
If required, you can change the port number. Note that if you change the port number, you must restart the Recording Server service (see "Management Server Service and Recording Server Service" on page 198) on the recording server in q
uestion.
Info Tab (Recording Server Properties)
You are able to verify or edit the name and description of a selected recording server on the Info tab. To access the Info tab, select the required recording server in the overview pane (see "Panes Overview" on page 36), then select the Info tab in the
On-Net Survei
properties pane (see "Panes Overview" on page 36).
llance Systems, Inc. 64
Page 65
RC-E User Manual Management Client (RC-E Manager)
Info Tab's Fields
Name: Name of the recording server. The name will be used whenever the recording server is listed in RC-E and
Ocularis Administrator. A name is not compulsory, but highly recommended. The name does not have to be unique.
To change the name, simply overwrite the existing name and click Save in the toolbar (see "Management Clie
nt Overview" on page 34).
Tip:
If you change the name, it will be updated throughout RC-E. This means that if the name is used in, for
example, a rule, the name will automatically change in the rule as well.
Description: Description of the recording server. The description will appear in a number of listings within RC-E.
For example, the description will appear when pausing the mouse pointer over the recording server's name in the overview pane (see "Panes Overview" on page 36). A description is not compulsory.
T
o specify a description, simply type the description and click Save in the toolbar (see "Management Client
Overvie
w" on page 34).
Host name: Non-e
ditable field, displaying the recording server's host name.
Web server URL: Non-editable field, displaying the URL of the recording server's web server. The web server is
used, for example, for handling PTZ camera control commands, and for handling browse and live requests from the Ocularis Client. The URL will include the port number used for web server communication (typically port
7563).
Time zone: Non-editable field, displaying the time zone in which the recording server is located.
Storage Tab (Recording Server Properties)
On the Storage tab, you are able to setup, manage and view storage areas for selected recording servers. For a more general introduction to storing and archiving, see About Storage and Archiving (on page 56).
W
hat is a storage area? A storage area is a directory in which database content— primarily recordings from the
cameras connected to the recording server— is stored in at least a recording database and possibly archived in a number of archiving databases. A default storage area with a default recording database is automatically created for each recording server when the recording server is installed on the system. Unless you specifically define that another storage area should be used for particular cameras, recordings from connected cameras are stored in individual camera databases in the recording server's default storage area. Archives can be added to a storage area at any time convenient.
To access the Storage tab, select the required recording server on the Overview pane (see "Panes Overview" on
e 36), then select the Stor
pag It is not possible to add databases or edit a storage area if the recording server is offline.
Storage Tab's Elements
age tab in the Properties pane (see "Panes Overview" on page 36).
Storage configuration list contents:
Name: Indicates the name of the storage area. Click it to edit it.  Device Usage: Indicates how many devises use the storage. Click the number link to see device details: Default: Indicates the default storage, i.e. the storage area in which database content is automatically stored
unless you specifically define other storage areas for particular cameras. Only one storage at the time can be default.
On-Net Survei
llance Systems, Inc. 65
Page 66
RC-E User Manual Management Client (RC-E Manager)
Recording and archiving configuration list content:
1. Database name
2. Maximum size of the database (and usage; also represented graphically by a proportional filling of the database)
3. Database location
4. Archiving schedule for archiving to the next archive in the list. Note that the number of retention days stated for an archive includes all retention stated earlier in the process.
Creating a New Storage Area
A storage area is always created with at predefined recording database named Recording, which cannot be renamed. Besides a recording database, a storage area can contain a number of archives, see Creating an Archive within an Existing Storage Area (on page 67).
1. To add an extra storage area to a selected recording server, click the button located below the Storage configuration list.
2. This opens the Storage and Recording Settings dialog where you must specify the following:
o Name: Rename the storage area if needed; use a descriptive and unique name. o Path: Type or use the browser link next to the field to specify the path to the directory in which to save
the storage area. The storage area does not necessarily have to be located on the recording serv er computer itself.
Tip: If the directory you plan to use does not already exist, you can create it using the bro wser dialog. Network drives must be specified using UNC (Universal Naming C onvention) format, example: \\server\volume\directory\.
o Retention time: Select a number of units and select either Days or Hours to specify how long recordings
should stay in the recording database before being deleted or archived (depending on archive settings). This is useful if you do not want your most recent recordings to be archived (or deleted) straight away even though archiving may be scheduled to take place before the specified number of hours.
Tip: Pausing the mouse pointer over a database will show detailed database information.
Who determines the schedule? You do. You must specify the intervals with which the archiving
process will start.
Example: If you specify 24 hours, recordings must be at least a day old before they will be archived. If archiving is scheduled to take place before the 24 hours have passed, only recordings older than 2 4 hours will be archived. Bear in mind that the archive's scheduling may mean that recordings will be older than the specified number of hours before they are archived. This may especially be the ca se if you specify an archiving schedule with long time spans between archiving.
Archiving is set up by adjusting several interdependent settings, see About Storage and Archiving (on page 56)for more information.
o Maximum size: Select the maximum number of gigabytes of recording data to save in the recording
database. Example: If you want to store up to 100 gigabytes of recording data in the database, select 100.
Recording data in excess of the specified number of gigabytes will be auto-moved to the first archive in the list - if any is specified - or deleted.
On-Net Survei
llance Systems, Inc. 66
Page 67
RC-E User Manual Management Client (RC-E Manager)
IMPORTANT: This is one of two maximum size settings for the recording database. The Retention Time setting specified earlier may mean that recordings are removed from the recording database before the specified number of gigabytes is reached.
IMPORTANT: The oldest data in a database will always be auto-archived (or deleted if no next arch ive is defined) when less than 5GB of space is free. If less than 1GB space is free, data will be deleted. A database always requires 250MB of free space. If this limit is reached (if data is not deleted fast enough), no more data will be written to the database until enough space has been freed. The actual maximum size of your database will thus be the amount of gigabytes you specify, minus 5GB.
o Signing: Check this box if you want to write a digital signature to database files containing recorded
data. This allows the Ocularis Client to verify that the contents of imported and opened databases have not been tampered with and that no database files have been removed.
Note that signing is turned off per default as it may affect system performance.
o Encryption: Select the appropriate level of encryption for the recording database by selecting either
None, Light or Strong. Note that the stronger the encryption, the more CPU usage it will cause.
o Password: (mandatory only if you selected Light or Strong in the Encryption field mentioned earlier):
Click Set... to set a password.
3. Click OK.
If needed, you are now ready to create archive(s) within your new storage area, see Creating an Archive within an Existing Storage Area (on page 67).
Creating an Archive within an Existing Storage Area
A storage area has no default archive when it is created.
1. To create an archive, select the wanted storage area by clicking it in the Recording and archiving configuration list.
2. Next, click the button located below the Recording and archiving configuration list.
3. This opens the Archive Settings dialog where you must specify the following:
o Name: Rename if needed; use a descriptive and unique name. o Path: Type or use the browser link next to the field to specify the path to the directory in which to save
the archive. The archive does not necessarily have to be located on the recording server computer itself.
Tip: If the directory you plan to use does not already exist, you can create it using the browser dialog. Network drives must be specified using UNC (Universal Naming C onvention) format, example: \\server\volume\directory\.
o Retention time: Select a number of units and select either Days or Hours to specify how long recordings
should stay in the archive before being moved to another archive or deleted (depending on archive settings). The retention time must always be longer than the retention time of the last archive or the recording database. This is due to the fact that the number of retention days stated for an archive includes all retention stated earlier in the process.
Who determines the schedule? You do. You must specify the intervals with which the archiving process will start.
Example: If you specify 24 hours, recordings must be at least a day old before they will be archived. If archiving is scheduled to take place before the 24 hours have passed, only recordings older than 2 4
On-Net Survei
llance Systems, Inc. 67
Page 68
RC-E User Manual Management Client (RC-E Manager)
will be archived. Bear in mind that the archive's scheduling may mean that recordings will be older
hours than the specified number of hours before they are archived. This may especially be the ca se if you specify an archiving schedule with long time spans between archiving.
Archiving is set up by adjusting several interdependent settings, see About Storage and Archiving (on page 56)for more information.
o Maximum size: Select the maximum number of gigabytes of recording data to save in the archive.
Example: If you want to store up to 100 gigabytes of recording data in the archive, select 100. Recording data in excess of the specified number of gigabytes will be auto-moved to the next archive in the list - if any is specified - or deleted.
IMPORTANT: This is one of two maximum size settings for the storage area. The Retention Time setting specified earlier may mean that recordings are removed from the archive before the specified number of gigabytes is reached.
IMPORTANT: The oldest data in a database will always be auto-archived (or deleted if no next arch ive is defined) when less than 5GB of space is free. If less than 1GB space is free, data will be deleted. A database always requires 250MB of free space. If this limit is reached (if data is not deleted fast enough), no more data will be written to the database until enough space has been freed. The actual maximum size of your database will thus be the amount of gigabytes you specify, minus 5GB.
o Schedule: Click the Schedule icon next to the Schedule field to specify an archiving schedule, i.e. the
intervals with which the archiving process should start. If required, you are able to make archiving take place very frequently (in principle every minute all year round), or very infrequently (for example, every first Monday of every 36 months).
4. Click OK.
What is the ideal interval? The ideal interval to use between each archiving process depends entirely upon your organization's needs. Consider your system's recordi ng settings, make an estimate of the amount of data you expect to record within, for example, a day, a week, or a month, then decide on a suitable interval. Bear in mind that your organization's needs may change over time; it is thus a good idea to regularly monitor your archiving settings, and adjust them if required.
In this example, we have selected that archiving should take place twice every week: at three o'clock in the morning on Wednesdays and Sundays. Note that regional settings on your computer may mean that dates and times appear differently in your version of RC-E.
Tip: The effect of your selections is summed up in the lower part of the dialog. Use the summary to verify that your selections reflect your intentions.
Tip: If required, you can always adjust the archive's settings—including its scheduling—once the arch ive has been created.
o Reduce frame rate: Select the Reduce frame rate check box and set a frame per second (FPS) in order
to reduce FPS when archiving. Reducing frame rates by a selected number of FPS's will make your recordings take up less space in the
archive. On the other hand, it also reduces quality since a number of frames are erased, leaving only FPS corresponding to the number of FPS selected in the dialog. MPEG/H.264 will be reduced to minimum key-frames.
Tip: It is possible to reduce frame rates to less than 1 FPS, for example as low as 0.1 FPS which means 1 frame every 10 seconds.
On-Net Survei
llance Systems, Inc. 68
Page 69
RC-E User Manual Management Client (RC-E Manager)
Deleting an Archive from within an Existing Storage
1. To delete an archive, select the wanted archive from the Recording and archiving configur ation list by clicking it. A selected archive is marked by a dark frame.
It is only possible to delete the last archive in the list. The archive does not have to empty.
2. Click the button located below the Recording and archiving configuration list.
3. Click Yes.
Deleting an Entire Storage Area
Prerequisites
The storage area you want to delete must not be set as default storage area. Furthermore, it cannot be used by any devices to hold recordings. This means that you must possibly move devices and their not yet archived recordings to another storage area before you are allowed to delete the storage area, see Moving Non-archived Recordings from One Storage Area to Another (see "Moving Non-archived Recordings from One Storage to Another" on page 69).
To Delete an Entire Storage Area
1. To delete a storage area, select the wanted storage area by clicking it.
2. Click the button located below the Storage configuration list.
3. Click Yes.
Editing Settings for a Selected Storage Area or Archive
1. In the Recording and archiving configuration list, to edit a storage area, select its recording database. To edit an archive, select the archive database.
Tip: A selected database is marked by a dark frame.
2. Click the button located below the Recording and archiving configuration list.
3. For editing a recording database, see Creating a New Storage Area (on page 66) and for editing an archive, see Creating a New Archive within an Existing Storage Area (see "Creating an Archive within an Existing Storage Are
a" on page 67).
If you change the maximum size of a database, recordings that exceed the new limit are auto-archived to the next archive or deleted - depending on archiving settings.
Moving Non-archived Recordings from One Storage to Another
1. Moving of contents from one recording database to another is done from the Record tab of the device in question.
2. In the Management Client's Site Navigation pane (see "Panes Overview" on page 36), expand Devices, select the wanted device type. In the Overview pane, select the wanted device.
3. In the Properties pane, click the Record tab. In the upper part of the Storage area, click Select... .
4. In the Select Storage dialog that follows, select the wanted database.
On-Net Survei
llance Systems, Inc. 69
Page 70
RC-E User Manual Management Client (RC-E Manager)
5. Click OK.
the Recordings Action dialog that follows, select whether already existing - but non-archived -recordings
6. In should be moved along to the new storage or deleted.
7. After selecting, click OK.
About Upgrading
See also Record Tab Overview (on page 103).
If you upgrade your RC-E system to version 4.0 (or later), you might discover that you end up with a lot more storages than before the upgrade. This is due to the fact that from RC-E 4.0 and forward, the database structure is different than it used to be and during the update process, the system creates a number of extra databases. However, since your original naming-convention is respected, you are able to reconstruct your former database structure with only little modification of devices and deletion of obsolete storages or databases.
Manage Multicasting
OnSSI RC-E supports multicasting of live streams from recording servers. In cases when many Ocularis Client users want to view live video from the same camera, multicasting can help save considerable system resources.
Multicasting is only possible for live streams; not for recorded video/audio. If a recording server has more than one network interface card, it is only possible to multicast on one of them.
Through the Management Client you are able to specify which one to use. The successful implementation of multicasting also requires that your network equipment (switches, etc.) has been
set up to relay multicast data packets to the required group of recipients only. If not; multicasting may not be different from broadcasting, which can significantly slow down network communication.
What Is Multicasting?
In regular network communication, each data packet is sent from a single sender to a single recipient - a process known as unicasting. With multicasting, however, it is possible to send a single data packet (from a server) to multiple recipients (clients) within a group. Multicasting can thus help save bandwidth.
When using unicasting, the source must transmit one data stream for each recipient. When using multicasting, only a single data stream is required on each network segment.
Multicasting is therefore an interesting option for streaming live video from recording servers to Ocularis Client s since video streams will not be duplicated on each network segment.
Multicasting as described here is not streaming of video from camera to servers. With multicasting, you work with a clearly defined group of recipients, based on options such as IP address ranges,
the ability to enable/disable multicast for individual cameras, the ability to define largest acceptable data packet size (MTU), the maximum number of routers a data packet must be forwarded between (TTL), etc. Thus, multicasting should not be confused with the much more primitive method broadcasting, which would send data to everyone connected to the network, even if the data is perhaps not relevant for everyone:
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; broadcasting can thus significantly slow
down network communication.
On-Net Survei
llance Systems, Inc. 70
Page 71
RC-E User Manual Management Client (RC-E Manager)
What Are the Requirements?
In order to use multicasting, your network infrastructure must support IGMP (Internet Group Management Protocol, an IP multicasting standard).
Furthermore, multicasting must be configured through the Management Client.
Enabling Multicasting
On the Multicast tab, select the Live multicast check box. If the entire IP address range for multicast is already in use on one or more other recording servers, you cannot
enable multicasting on further recording servers without freeing up some multicasting IP addresses first.
Assigning IP Address Range
In this section you specify the range from which you want to assign addresses for multica st streams from the selected recording server. Clients will connect to these addresses when viewing multicast video from the recording server i n question.
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. For more info, see the following.
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.
Source IP address for all multicast streams: If a recording server has more than one network interface card, it
is only possible to multicast on one of them. This field is therefore relevant if your recording server has more than one network interface card—or if it has a network interface card with more than one IP address.
To use the recording server's default interface, leave the value 0.0.0.0 (IPv4) or :: (IPv6) in the field. If you want to use another network interface card, or a different IP address on the same network interface card, specify the IP address of the required interface.
Specifying Datagram Options
In this section you specify settings for data packets (datagrams) transmitted through multicasting. MTU: Maximum Transmission Unit, the largest allowed physical data packet size (measured in bytes). Messages
larger than the specified MTU will be split into smaller packets before being sent. Default value is 1500, which is also the default on most Windows computers and Ethernet networks.
TTL: Time To Live, the largest allowed number of hops a data packet should be able to travel before it is
discarded or returned. A hop is a point between two network devices, typically a router. Default value is 128.
Enabling Multicasting for Individual Cameras
Even when you have specified multicasting settings for the selected recording server, multicasti ng will not work until you enable it for required cameras:
Select the required recording server in the Management Client's Site Navigation pane (see "Panes Overview" on page
36), select the required camera in the overview pane (see "Panes Overview" on page 36), then select Liv on the Client tab (see "Client Tab (Camera Properties)" on page 76) in the properties pane (see "Panes Overview" on
e 36). Repeat for all required cameras under the recording server in question.
pag
e multicast
On-Net Survei
llance Systems, Inc. 71
Page 72
RC-E User Manual Management Client (RC-E Manager)
Specify IP Address Range
To specify the range from which you want to assign addresses for multicast streams from the selected recording server do the following:
For each multicast camera feed, the IP address/port combination (IPv4 example: 232.0.1.0:6000) must be unique. You can thus either use one IP address and many ports, or many IP addresses and fewer ports. By default, RC-E suggests a single IP address and a range of 1000 ports, but you can change this as required.
Example: If you want multicast for 1000 cameras, you would need either:
o 1 IP address and a range of 1000 different ports, OR o a range of two IP addresses and a range of 500 different ports (or any matching combination), OR o a range of 1000 IP addresses and a single port
When specifying the 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.
Tip: If required, a range may include only one IP address (IPv4 example: 232.0.1.0-232.0.1.0) Tip: IP addresses for multicasting must be within a special range set aside for dynamic host allocation by IANA (the
authority overseeing global IP address allocation). If using IPv4, you can read more about the range, which goes from
232.0.1.0 to 232.255.255.255, at www.iana.org/assignments/multicast-addresses (www.iana.org/assignments/ipv6-
multicast-a
(www.iana.org/assignments/ip
ddresses). If using IPv6, the range is different; see w
v6-multicast-addresses).
ww.iana.org/assignments/ipv6-multicast-addresses
Manage Public Addresses
You define a recording server's public IP address on the Network tab. To access the Network tab, select the required recording server in the overview pane (see "Panes Overview" on page 36), then select the Netw properties pane (see "Panes Overview" on page 36).
This description is also valid for failover servers (see "Manage Failover Servers" on page 192).
Why Use a Public Address?
When the Ocularis Client connects to a surveillance system, an amount of initial data communication, includi ng the exchange of contact addresses goes on in the background. This happens automatically, and is completely transparent to users.
Ocularis Client users may connect from the local network as well as from the internet, and in each case the surveillance system should be able to provide suitable addresses so the clients can get access to live and recorded video from the recording servers:
When clients connect locally, the surveillance system should reply with local addresses and port numbers. See
also Manage Local IP Address Ranges (on page 171).
When clients connect from the internet, the surveillance system should reply with the recording server's public address, i.e. the address of the firewall or NAT (Network Address Translation) router, and often also a different port number (which is then forwarded to recording servers).
To provide access to the surveillance system from outside a NAT (Network Address Translation) firewall, RC­E lets you use public addresses and port forwarding. This will allow clients from outside the firewall to connect to recording servers without using VPN (Virtual Private Network). Each recording server (and failover server) can be mapped to a specific port and the port can be forwarded through the firewall to the server's internal address.
ork tab in the
On-Net Survei
llance Systems, Inc. 72
Page 73
RC-E User Manual Management Client (RC-E Manager)
Enabling Public Access
To enable public access, select the Network tab's Enable public access box.
Defining Public Address and Port
When public access is enabled, you are able to define the recording server's publ ic address and public port number in the Public address and Public port fields respectively.
As public address, use the address of the firewall or NAT router which clients accessing the surveillance system from the internet must go through in order to reach recording servers.
Specifying a public port number is compulsory; it is always a good idea that port numbers used on th e firewall or NAT router are different from the ones used locally.
When using public access, the firewall or NAT router used must be configured so requests sent to the public addr ess and port are forwarded to the local address and port of relevant recording servers.
Local IP Ranges
There are cases when the recording server's public address should not be used: When cl ients connect from the local network, the surveillance system should reply with local addresses and port numbers. The surveillance system must therefore be able to determine whether a client belongs on a local IP range or on the internet.
For this purpose, you are able to define a list of IP ranges which the surveillance system should recognize as coming from a local network. You do this by clicking Configure... on the Network tab. See Manage Local IP Address Ranges (on page 171) for more information.
Servers and Clients Require Time-Synchronization
Part of the security surrounding the use of remote clients with RC-E is based on time-based tokens.
Why Servers Require Time-Synchronization
When a client logs in to the surveillance system, the client receives a token from the management server. The token contains important security-related time information.
The management server also sends a similar token to the required recording server(s). This is partly due to the fact that recording servers may be located all around the world; each recording server thus uses the token to validate the client's token against the local time in the recording server's own time zone.
The validity of a token expires after a while. It is therefore important that time on your management server and all of your organization's recording servers is synchronized (minute and second- wise; ho urs may of course be different in different locations around the world). If time on the servers is not synchronized, you may experience that a recording server is ahead of the management server's time.
When a recording server is ahead of the management server's time, it may result in a client's token expiring on the recording server earlier than intended by the management server. Under unfortunate circumstances you might even experience that a recording server claims that a client's token has already expired when it receives it; effectively preventing the client from viewing recordings from the recording server.
How to synchronize time on your organization's servers depends on your network configuration, internet access, use of domain controllers, etc. Often, servers on a domain are already time-synchronized against the domain controller. If so, you should be fine as long as all required servers belong to the domain in question.
If your servers are not already time-synchronized, it will be necessary to synchronize the servers' time against a time server, preferably the same time server.
On-Net Survei
llance Systems, Inc. 73
Page 74
RC-E User Manual Management Client (RC-E Manager)
The following articles from Microsoft describe what to do in different situations: How to configure an authoritative time server in Windows Server 2003 (see
http://support.microsoft.com/kb/816042/en-us - http://support.microsoft.com/kb/816042/en-us)
Registry entries for the W32Time service (see http://support.microsoft.com/kb/223184/en-us -
http://support.microsoft.com/kb/223184/en-us)
If these links do not http://www.microsoft.com/) for time server, time service, s
work for you, try searching www.microsoft.com (see http://www.microsoft.com/ -
ynchronize servers or similar.
It is also very important that Ocularis Client s are time-synchronized with the management server.
Why Clients Require Time-synchronization
Because configuration communication is facilitated by the Ocularis Base, Ocularis Client machines should also be time-synchronized with the management server and the Ocularis Base machine. A time difference of up to five minutes between Ocularis Client machines and servers is tolerated.
On-Net Surveillance Systems, Inc. 74
Page 75
RC-E User Manual Management Client (RC-E Manager)
Devices
About Devices
To add cameras, go to Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49). To replace cameras, go to Manage Hardware (on page 53).
In the Mana follo
wing under Devices:
gement Client's Site Navigation pane (see "Panes Overview" on page 36), you are able to work with the
Cameras: (see "Manage Cameras" on page 75) Lets you handle the majority of camer
management. Microphones: (see "Manage Microphones" on page 85) On many devices you are able to attach
ernal microphones; some devices even have built-in microphones.
ext
Speakers : (see "Manage Speakers" on page 87) On many devices you are able to attach ex
loudspeakers; some devices even have built-in speakers.
Inputs : (see "Manage Input" on page 88) On many devices you are able to attach external units, typically
ext
ernal sensors, to input ports on the device. Input from such external input units can be used for many
purposes in RC-E.
Outputs : (see "Manage Output" on page 91) On many devices you are able to attach external units to output
ports on the d
evice. This allows you to activate/deactivate lights, sirens, etc. through RC-E.
a configuration and
ternal
Manage Cameras
To add cameras, go to Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49). To replace cameras, go to Manage Hardware (on page 53).
Enab
ling/disabling as well as renaming of individual cameras takes place on the recording server hardware
management level; see Managing Hardware (see "Manage Hardware" on page 53). F
or all other configuration and management of cameras, expand Devices in the Management Client's Site Navigation
pane (see "Panes Overview" on page 36), then select Cameras. In the overview pane (see "Panes Overview" on page
36), you group your cameras for an easy overview of your c properties for all cameras within a group in one step. See Using Device Groups (see "About Device Groups" on page
95) for information about creating groups as well as adding cameras to your groups. you have placed your cameras in groups, configuration can begin.
Once
ameras. Grouping also lets you specify common
Configuring Individual Cameras
You configure individual cameras by selecting the required camera in the li st, then specifying the camera's required settings on the tabs in the Properties pane:
The Info tab (see "Info Tab Overview" on page 101) for managing the selected camera's name, etc.
The Settings tab (see "Settings Tab Overview" on page 106) for managing the selected camera's general
settings.
The Streams tab (see "About Multi-streaming" on page 98) for managing the selected camera's video streams.
The Record tab (see "Record Tab Overview" on page 103) for managing th e selected cam
database and archiving storage settings.
On-Net Survei
llance Systems, Inc. 75
era's recording,
Page 76
RC-E User Manual Management Client (RC-E Manager)
The Presets tab (see "PTZ Tab (Hardware Properties)" on page 102) for managing the selected camera's preset positions (only available if the selected camera is a PTZ camera).
The Patrolling tab (see "PTZ Patrolling Tab (Camera Properties)" on page 80) for managing the selected
camera'
s patrolling profiles (only available if the selected camera is a PTZ camera).
The Events tab (see "Events Tab Overview" on page 99) for managing hardware configura ble events.
The Client tab (see "Client Tab (Camera Properties)" on page 76) lets you specify information which will affect
client'
s use of the selected camera.
The Privacy Mask tab (see "Privacy Mask Tab (Camera Properties)" on page 79) lets you enable and configure
privac
y masking for the selected camera.
The Motion tab (see "Motion Tab (Camera Properties)" on page 77) for managing the selected camera's motion
detection settings.
Client Tab (Camera Properties)
The Client tab lets you specify information which will affect clients' use of the selected camera. To access the Client tab, select the required camera in the overview pane (see "Panes Overview" on page 36), then select the Clie the properties pane (see "Panes Overview" on page 36).
Client Settings
nt tab in
Live multicast: RC-E supports multicasting (see "Manage Multicasting" on page 70) (sending of single data
packets to multiple recipients within a group, thereby saving bandwidth and system resources) of live streams from recording servers to Ocularis Client s. To enable multicasting of live streams from the selected camera, select the check box.
Remember that for the feature to work, multicasting must also be configured for the recording server; see Manage Multicasting (on page 70). If multicasting is not possible, for example due to restrictions on the net
work or on individual clients, RC-E will revert to unicasting (sending of separate data packets to separates
recipients).
Default microphone: By defining a default microphone, you can determine from which microphone Ocularis
Client users should by default hear recordings when they select the camera in question in their Ocularis Client s. The users can subsequently select another microphone if they require so.
Bear in mind that although you have defined a default microphone for a camera, it cannot be guaranteed that all Ocularis Client users will hear audio from the microphone in question: Some users may not have speakers attached, some users may not have the rights required to listen to audio, etc.
Default Speaker: By defining a default speaker, you can determine through which microphone Ocularis Client
users should by default be able to speak when they select the camera in question in their Ocularis Client s. The users can subsequently select another speaker if they require so.
Bear in mind that although you have defined a default speaker for a camera, it cannot be guaranteed that all Ocularis Client users will be able to talk through the speaker in question: Some users may not have a microphone attached, some users may not have the rights required to talk through speakers, etc.
Shortcut: Users of the Ocularis Client can take advantage of a range of keyboard shortcuts, some of which let
the users toggle between viewing different cameras. Such shortcuts include numbers, which are used to ide ntify each camera. In the Management Client, each camera's shortcut number is specified in the Shortcut field.
A camera shortcut number must not contain any letters or special characters, and cannot be longer than four digits. Examples of correct camera shortcut numbers: 3, 1234. Examples of incorrect camera shortcut numbers: A*3, 12345. Always use a unique camera shortcut number for each camera.
On-Net Survei
llance Systems, Inc. 76
Page 77
RC-E User Manual Management Client (RC-E Manager)
Tip:
Find more information about audio and keyboard shortcuts from a Ocularis Client user's perspective in the
separate Ocularis Client documentation available from www.onssi.com.
Motion Tab (Camera Properties)
The Motion tab lets you enable and configure motion detection for the selected camera. Motion detection configuration is a key element in your RC-E surveillance solution: Your motion detection configuration may determine when video is recorded, when events are generated, when external output (such as lights or sirens) is triggered, etc.
Time spent on finding the best possible motion detection configuration for each camera may therefore help you later avoid unnecessary alarms, etc. Depending on the physical location of the camera, it may be a very good idea to test motion detection settings under different physical conditions (day/night, windy/calm weather, etc.).
Before you configure motion detection for a camera, it is highly recommended that you have configur ed the camera's image quality settings, such as resolution, compression, etc., on the Settings tab (see "Settings Tab Overview" on page 106). If you later change image quality settings, you should always test any motion detectio n configuration afterwards.
Tip: You can configure motion detection for all cameras in a device group (see Manage Cameras (on page 75)) in one step. N the case with exclude regions (areas in which not to use motion detection), as these are very likely to vary from camera to camera.
Enabling and Disabling Motion Detection
Motion detection is enabled by default. To enable/disable motion detection for a camera, select/clear the Motion tab's Motion detection check box.
ote, however, that some motion detection settings must be configured individually for each camera. This is
When motion detection is disabled for a camera, any motion detection-related rules (see "Manage Rules" on page
133) for the camera will not work.
Motion Detection Settings
You are able to specify settings relating to the amount of change required in a camera's video in order for the change to be regarded as motion. You are also able to specify intervals between motion detection analyses, any areas of an image in which motion should be ignored, etc.
Sensitivity Slider: The Sensitivity slider determines how much each pixel in the camera's images must change before it is regarded as
motion. 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 will be allowed in each pixel before it is regarded as motion. The lower the sensitivity level, the more change in each pixel will be allowed before it is regarded as motion. This way
you are able to allow insignificant changes, which should not be regarde d as motion. Pixels in which motion is detected are highlighted in green in the previe w image. Select a slider position in which only
detections you consider motion are highlighted.
Tip: Your exact sensitivity slider setting is indicated by a number from 0-300 in the right side of the slider. This way you are able to compare the exact sensitivity slider setting between cameras.
Tip: If you find the concept of motion detection sensitivity difficult to grasp, try dragging the slider to the left towards the highest possible sensitivity (0) position: The more you drag the slider towards the highest possible sensitivity position, the more of the preview image becomes highlighted in green. This is because with a very high sensitivity level even the slightest change in each pixel will be regarded as motion.
Motion Slider: The Motion slider determines how many pixels in the camera's images image must change before it is regarded as
motion.
On-Net Survei
llance Systems, Inc. 77
Page 78
RC-E User Manual Management Client (RC-E Manager)
he selected motion level is indicated by the black vertical line in the motion indication bar above the sliders.
T The black vertical line in the motion indication serves as a threshold: When detected motion is above the selected
sensitivity level, the bar changes color from green to red, indicating a positive detection.
Tip: Your exact motion slider setting is indicated by a number from 0-10.000 in the right side of the slider. This way you are able to compare the exact motion slider setting between cameras.
Keyframes Settings: 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 will contain the entire view of the camera. Image Processing Interval: You are able to select how often motion detection analysis should be carried out on video from the camer a. From the Process image every (msec): list, select the required interval: every 100 milliseconds (i.e. once every tenth
of a second), every 250 milliseconds, every 500 milliseconds, every 750 milliseconds, or every 1000 milliseconds (i.e. once every second). Default is every 500 milliseconds.
The interval is applied regardless of the camera's frame rate settings. Detection Method: You are able to optimize motion detection performance by analyzing only a selected percentage of the image, for
example 25%. By analyzing 25%, only every fourth pixel in the image is analyzed instead of all pixels. Using optimized detection will reduce the amount of processing power used to carry out the analysis, but will also
mean a less accurate motion detection. In the Detection method drop down-box, select the wanted detection method. Ignoring Motion Detection in Parts of Images: The Exclude Regions settings in the lower part of the Motion tab lets you disable motion detection i n specific areas of
a camera's images. Parts of images in which motion should be ignored this way are called exclude regions. Disabling motion detection in specific areas may help you avoid detection of irrelevant motion, for exam ple if the
camera covers an area where a tree is swaying in the wind or where cars regularly pass by in the background. When exclude regions are used with PTZ cameras and you pan/tilt/zoom the camera, the exclud ed area will not move
accordingly. This might mean that objects originally excluded will be included. This is due to the fact that the exclude region is locked according to the camera's view, not the excluded region. Consequently, it is not recommended to use exclude regions with PTZ cameras.
To use exclude regions, select the Use exclude regions check box.
Defining Exclude Regions:
When you select the Use Exclude regions check box, the preview image will be divided into selectable sections by a grid.
To define exclude regions, drag the mouse pointer over the required areas in the preview image. Pressing down the left mouse button selects a grid section; right mouse button clears a grid section.
You are able to define as many exclude regions as you require. Excluded regions are shown in blue. The blue exclude area indications will only appear in the preview image on the Motion tab, not in an y other preview
images in the Management Client or access clients. Grid Size
The value selected in the Grid size list determines the density of the grid, regardless whether the grid is shown or not.
On-Net Survei
llance Systems, Inc. 78
Page 79
RC-E User Manual Management Client (RC-E Manager)
Select bet
ween the values 8×8 (i.e. a grid dividing the image into eight sections along the X-axis and eight
sections along the Y-axis), 16×16, 32×32 or 64×64. With a grid of 8×8, the image will be divided into relatively few sections for you to select for exclude regi ons.
Each section will be relatively large; you will not be able to define very detailed exclude regions. With a grid size of 64×64, the image will be divided into relatively many sections for you to select for exclude regions. Each section will be relatively small, enabling you to define more detailed exclude regions.
Show Grid
The grid may be visible or hidden, depending on whether the Show grid check box is sel ected or not.
When the Show grid check box is selected (default), the preview image will feature a grid indicating the division of the preview image into selectable sections. The grid may help you when selecting exclude regions in the preview image.
The density of the grid is determined by the value selected in the Grid size list. Showing the grid is not a requirement for selecting exclude regions; even without the grid you are able to
select exclude regions as described earlier. Hiding the grid may provide a less obscured view of the preview image.
Show Regions
When the Show regions check box is selected (default), exclude regions will be highlighted in blue in the preview image.
Hiding exclude regions may provide a less obscured view of the preview image. However, under normal circumstances it is highly recommended that you keep the Show regions box selected; otherwise exclude regions may exist without you or your colleagues being aware of it.
The blue exclude area indications will only appear in the preview image on the Motion tab, not in any other preview images in the Management Client or access clients.
Pen size
Use the Pen size slider to indicate the size of the selections you wish to make when clicking and dragging the grid to select regions for privacy masking. Default is set to small, which is equivalent to one square in the grid.
Privacy Mask Tab (Camera Properties)
The Privacy Mask tab lets you enable and configure privacy masking for the selected camera. Among other things, you can define if and how selected areas of a camera's view should be masked before distribution. For example, if a surveillance camera films a street, in order to protect residents privacy, you can mask certain areas of a building (could be windows and doors) with privacy masking. This is required in some cou ntries to comply with national legislation.
As Administrator you are also able to see through privacy masked areas, and can turn showing of privacy masked areas on and off. When viewed via Ocularis Client, privacy masked areas will be represented as black areas and it is impossible to see behind the privacy masking or in any way remove it.
When privacy masks are used with PTZ cameras and you pan/tilt/zoom the camera, the selected area masked for privacy will not move accordingly. This might mean that objects masked for privacy become visible. This is due to the fact that the masked area is locked according to the camera's view, not the masked object. Consequently, it is not recommended to use privacy masking with PTZ cameras.
Enabling and Disabling Privacy Masking
The privacy masking feature is enabled by default. To enable/disable the privacy masking feature for a camera, select/clear the Privacy Mask tab's Privacy masking check box.
Privacy Masking Settings
On-Net Survei
llance Systems, Inc. 79
Page 80
RC-E User Manual Management Client (RC-E Manager)
hen you enable privacy masking, the preview image is divided into selectable sections by a grid.
W To define privacy mask regions, drag the mouse pointer over the required areas in the preview image. Pressin g down
left mouse button selects a grid section; right mouse button clears a grid section. You are able to define as many privacy mask regions as you require. Privacy mask regions are shown in r ed.
The red privacy mask indications will also appear in the previe w image on the Motion tab. Grid Size
The value selected in the Grid size list determines the density of the grid, regardless whether the grid is shown or not.
Select between the values 8×8 (i.e. a grid dividing the image into eight sections along the X-axis an d eight sections along the Y-axis), 16×16, 32×32 or 64×64.
With a grid of 8×8, the image will be divided into relatively few sections for you to select for privacy mask regions. Each section will be relatively large; you will not be able to define ver y detailed privacy mask regions. With a grid size of 64×64, the image will be divided into relatively many sections for you to select for privacy mask regions. Each section will be relatively small, enabling you to define more detailed privacy mask regions.
Show Grid
The grid may be visible or hidden, depending on whether the Show grid check box is sel ected or not. When the Show grid check box is selected (default), the preview image will feature a grid indicating the
division of the preview image into selectable sections. The grid may help you when selecting privacy mask regions in the preview image.
Showing the grid is not a requirement for selecting privacy mask regions; even without the grid you are able to select privacy mask regions as described above. Hiding the grid may provide a less obscured view of the preview image.
Show Privacy Masks
When the Show privacy masks check box is selected (default), privacy mask regions will be highlighted in red in the preview image.
Hiding privacy mask regions may provide a less obscured view of the preview image. However, under normal circumstances it is highly recommended that you keep the Show privacy masks box
selected; otherwise exclude privacy mask regions may exist without you or your colleagues bein g aware of it.
Pen size
Use the Pen size slider to indicate the size of the selections you wish to make when clicking and dragging the grid to select regions for privacy masking. Default is set to small, which is equivalent to one square in the grid.
PTZ Patrolling Tab (Camera Properties)
The Patrolling tab lets you create patrolling profiles, the automatic movement of a PT Z (Pan/Tilt/Zoom) camera between a number of preset positions (see "PTZ Presets Tab (Camera Properties)" on page 83). Before you are able to
work with patrolling, you must have specified at least two preset positions for the camera. You manage patrolling on the Patrolling tab, which is available only when the selected camera is a PTZ camera. Patrolling profiles are the definitions of how patrolling should take place. This includes the order in which the camera
should move between preset positions, how long it should remain at each position for, etc. You are able to create an unlimited number of such patrolling profiles and use them in your rules (see "Manage Rules" on page 133). For
On-Net Survei
llance Systems, Inc. 80
Page 81
RC-E User Manual Management Client (RC-E Manager)
le, you may create a rule specifying that one patrolling profile should be used during daytime opening hours,
examp and another during nights.
In order to use PTZ cameras' features, including the ability to pan, tilt, and zoom, operators must have a role which gives them the necessary rights. See About Roles (on page 145) for more information, including step-by-step
ptions of how to assign users to roles and how to specify the rights of roles.
descri
Adding a New Patrolling Profile
1. Click New. This will open the Add Profile dialog.
2. In the Add Profile dialog, specify a name for the patrolling profile:
Tip: Use a descriptive name; the name of the patrolling profile may later be used in situations where you will not have access to details about the patrolling profile, e.g. when using the patrolling profile in a rule (see "Manage Rules" on page 133).
3. Click OK.
The new patrolling profile will be added to the Patrolling tab's Profile list. You are now able to
specify required preset positions and other settings for the patrolling profile.
Specifying Preset Positions for Use in a Patrolling Profile
1. Select the required patrolling profile in the Profile list:
2. Click Add . This will open the Select Preset dialog.
3. In the Select Preset dialog, select the preset positions required for your patrolling profile:
4. Click OK. The selected preset positions are added to the list of preset positions for the patrolling profile:
5. The preset position at the top of the list will be used as the first stop when the camera patrols according to the patrolling profile, the preset position in second position from the top will be the second stop, and so forth.
If required, change the sequence by selecting the required preset position and using the up/do wn buttons:
Tip: If required, you can easily add more preset positions to the list by clicking Add , or remove unwanted preset positions from the list by selecting the unwanted preset position, then clicking Remove.
Specifying How Long to Stay at Each Preset Position
When patrolling, the PTZ camera will by default remain for 5 seconds at each preset position specified in the patrolling profile before it moves on to the next preset position. To change the number of seconds for which the PTZ camera will remain at a specific preset position, do the following:
1. Select the required patrolling profile in the Profile list.
2. In the list of preset positions for the selected patrolling profile, select the preset position for which you want to change the time:
3. Specify the required time (in number of seconds) in the Wait time (secs.) field:
4. If required, repeat for other preset positions.
Customizing Transitions
By default, the time required for moving the camera from one preset position to another, known as transition, is estimated to be 3 seconds. During this time, motion detection is by default disabled on the camera, as irrelevant motion is otherwise likely to be detected while the camera moves between the preset positions. Transitions are also known as PTZ scanning.
On-Net Survei
llance Systems, Inc. 81
Page 82
RC-E User Manual Management Client (RC-E Manager)
Customizing speed for transitions is only supported if your camera supports PTZ scannin g and is of the type where preset positions are configured and stored on the RC-E server (type 1 PTZ camera). Otherwise the Speed slider is grayed out.
You can customize the transitions between each of the preset positions in a patrollin g profile. You are able to customize the following:
The estimated transition time  The speed with which the camera will move during a transition  Which plug-ins to disable during transition.
To customize transitions between preset positions in a patrolling profile, do the following:
1. Select the required patrolling profile in the Profile list.
2. Select the Customize transitions check box: This will add transition indications to the list of preset positions for the selected patrolling profile.
3. In the list, select the required transition:
4. Specify the estimated transition time (in number of seconds) in the Expected time (secs.) field:
5. Use the Speed slider to specify the required transition speed. When the slider is in its right most position, the camera will move with its default speed. The more you move the slider to the left, the slower the camera will move during the selected transition.
Tip: A number indicating the exact speed is displayed near the top right corner of the slider. When required, the number (from 0.0001 (very slow) to 1.0000 (default speed)) allows you to define exactly the same custom speed across transitions.
6. In the Plug-ins to disable list, specify any plug-ins you want to disable during the selected transiti on. By default, the plug-in used for motion detection on the camera (MotionDetectionPlugin) is disabled in order to avoid irrelevant motion being detected during transition.
To add a plug-in to the list, click Add..., and select the required plug-in. This requires that one or more other plug-ins are available, and that they can be disabled.
To remove a plug-in from the list, for example if you do not want motion detection to be disabled during the transition, select the plug-in and click remove.
7. Repeat as required for other transitions.
Specifying an End Position
You are able to specify that the camera should move to a specific preset position when patrolling according to the selected patrolling profile ends.
1. Select the required patrolling profile in the Profile list.
2. Select the Go to specific preset on finish check box: This will open the Select Preset dialog.
3. In the Select Preset dialog, select the required end position, and click OK.
Tip: You can select any of the camera's preset positions as the end position, you are not limited to the preset positions used in the patrolling profile.
On-Net Survei
llance Systems, Inc. 82
Page 83
RC-E User Manual Management Client (RC-E Manager)
The selected end position is added to the list of preset positions for the selected patrolling profile. When
4. patrolling according to the selected patrolling profile ends, the camera will go to the specified end position.
Renaming an Existing Patrolling Profile
1. Select the required patrolling profile in the Profile list.
2. Click Rename. This will open the Rename Profile dialog.
3. In the Rename Profile dialog, type a new name for the patrolling profile.
Tip: Use a descriptive name; the name of the patrolling profile may later be used in situations where you will not have access to details about the patrolling profile, e.g. when using the patrolling profile in a rule (see "Manage Rules" on page 133).
4. Click OK.
Specifying Manual PTZ Session Timeout
Patrolling of PTZ cameras may be interrupted manually by Ocularis Client users with the necessary user rights. You are able to specify how much time should pass before regular patrolling is resumed after a manual interruption:
1. In the Management Client's menu bar, select Tools > Options. This will open the Options wind ow.
2. On the Options window's General tab, select the required amount of time in the PTZ manual session timeout list (default is 15 seconds).
The setting will apply for all PTZ cameras on your RC-E system.
PTZ Presets Tab (Camera Properties)
The Presets tab lets you create preset positions to be used, for example, in rules (see "Manage Rules" o n page 133) for making a PTZ (Pan/Tilt/Zoom) camera move to a specific preset position when an event occurs, as well as in patrolling (see "PTZ Patrolling Tab (Camera Properties)" on page 80), the automatic movement of a PTZ camera between a number of preset positions.
You manage preset positions on the Presets tab, which is available only when the selecte d camera is a PTZ (Pan/Tilt/Zoom) camera. The Presets tab will not be available if the selected PTZ camera does not support preset positions.
In order to use PTZ cameras' features, including the ability to pan, tilt, and zoom, operators must have a role which gives them the necessary rights. See About Roles (on page 145) for more information, including step-by-step descri
ptions of how to assign users to roles and how to specify the rights of roles.
Adding a Preset Position
As an alternative to defining preset positions in RC-E, preset positions may for some PTZ cameras also be defined on the camera device itself (typically by accessing a device-specific configuration web page) and imported into RC-E by selecting Use presets from device.
To add a preset position for the camera in RC-E, do the following:
1. Click Add.... This will open the Add Preset window:
2. The Add Preset window displays a preview image from the camera; use the navigati on buttons and/or sliders to move the camera to the required preset position. While you do this, you are able to verify the position of the camera through the preview image.
3. Specify a name or number for the preset position in the Name field.
On-Net Survei
llance Systems, Inc. 83
Page 84
RC-E User Manual Management Client (RC-E Manager)
Tip:
If typing a name, use a descriptive name; the name of the preset position may later be used in situations where you will not have access to a preview image from the preset position, e.g. when using the preset in a
rule (see "Manage Rules" on page 133).
4.
Optionally, type a description of the preset position in the Description field.
5. Click OK. This will close the Add Preset window, and add the preset position to the Presets tab's list of available preset positions for the camera.
How to Use the Axes Navigation Sliders The navigation sliders let you to move the camera along each of its axes. Click inside the sliders to move the sliders'
red handles to the required positions. The slider for the X-axis (allowing you to pan left/right) is located immediately below the preview image. The slider for the Y-axis (allowing you to tilt the camera up/down) is located immediately to the left of the preview
image. The slider for the Z-axis (allowing you to zoom in and out) is located immediately above the preview image. The
camera will zoom in when you move the slider towards Tele, and zoom out when you move the slider towards Wide. How to Use the Iris Slider
Iris settings are only available for some cameras. Iris settings control the amount of light in images. The higher the iris setting, the lighter images will appear. Click inside the slider to move the slider's red handle to the required position. How to Use the Focus Slider
Focus settings are only available for some cameras. Click inside the slider to move the slider's red handle to the required position.
Using Preset Positions from Device
As an alternative to specifying preset positions in RC-E, preset positions may for some PTZ cameras also be defined on the camera device itself (typically by accessing a device-specific configuration web page.
Such device-defined presets can subsequently be imported into RC-E by selecting Use presets from device. If importing presets from the camera device, any presets you have previously defined for the camera in RC-E will be
removed; this will affect any patrolling profiles in which these presets are used, as well as any rules in which the affected patrolling profiles are used.
If you later wish to edit such device-defined presets, editing should take place on the camera device.
Assigning a Default Preset Position
If required, you are able to assign one of a PTZ camera's preset positions at the camera's default preset position. Having a default preset position can be useful because it allows you to define rules (see "Manage Rules" on page
133) specifying that the PTZ camera shoul
d go to the default preset position under particular circumstances, for
example after the PTZ camera has been operated manually. To assign a preset position as the default, select the required preset in your list of defined preset positions, then select
the default preset box below the list. Only one preset position can be the default preset position.
Editing a Preset Position
To edit an existing preset position defined in RC-E (presets imported from a device should be edited on the device itself), do the following:
On-Net Survei
llance Systems, Inc. 84
Page 85
RC-E User Manual Management Client (RC-E Manager)
Select the required preset position in the Presets tab's list of available preset positions for the camera.
1.
2. Click Edit.... This will open the Edit Preset window:
3. The Edit Preset window displays a preview image from the preset position in qu estion; 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 as required.
Tip: If using a name, make sure it is descriptive; the name of the preset position may later be used in situations where you will not have access to a preview image from the preset position, e.g. when using the preset in a rule (see "Manage Rules" on page 133).
5. Click OK.
Testing a Preset Position
1. Select the required preset position in the Presets tab's list of available preset positions for the camera.
2. Click Test.
3. The Presets tab's preview image will move to the selected preset position.
Tip: If the preview image does not appear to move to the selected preset position when you click Test, verify that preview image does not already show the selected preset position. In that case, try testing another preset position first.
360 Degree Lens Tab (Camera Properties)
Use of 360° technology requires a dedicated ImmerVision 360° lens mounted. In this way, 360° technology enables panomorph technology through an advanced lens. The 360° Lens tab lets you enable and configure panomorph support for the selected camera.
Enabling and Disabling Panomorph Support
The panomorph feature is disabled by default. To enable/disable it, select/clear the 360° Lens tab's Enable panomorph support check box.
Panomorph Settings
When enabling the panomorph support functionality, you m ust also select a Registered Panomorph Lens (RPL) number from the ImmerVision Enables
®
panomorph RPL number list. This is to ensure identification and correct configuration of the lens used with the camera in question. The RPL number is usually found on the lens itself or on the box it came in. For details of ImmerVison, panomorph lenses, and RPLs, see http://www.immervision.com/en/home/index.php (see http://www.immervision.com/en/home/index.php - http://www.immervision.com/en/home/index.php).
You must also
indicate the physical position/orientation of the camera in question. This is done by selecting its
position from the Camera position/orientation list.
Manage Microphones
On many devices you are able to attach external microphones; some devices even have built-in microphones. Devices' microphones are automatically detected when you add the devices to your RC-E system through the
Management Client's Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49) wizard, regardless of which of the
wizard's detection options you use.
On-Net Survei
llance Systems, Inc. 85
Page 86
RC-E User Manual Management Client (RC-E Manager)
Microph
ones do not require separate licenses; you can use as many microphones as required on your system. You can use microphones completely independently of cameras.
Who is able to listen to audio recorded by microphones? Users of the Ocularis Client can—provided microphones are available, and the users have the rights to use them—listen to audio from microphones. Roles (see "About Roles" on pa
ge 145) determine users' right to listen to microphones. You cann
ot listen to microphones from the Management
Client.
Tip: RC-E comes with a default rule (see "Manage Rules" on page 133) which ensures that audio feeds from all
ected microphones and speakers are automatically fed to the RC-E system. Like other rules, the default rul e can
conn be deactivated and/or modified as required.
You have two entry points for managing microphones:
In the Management Client's Site Navigation pane (see "Panes Overview" on page 36), expand Devic
es, select
Microphones, expand the required device group, and select the required microphone. If no device groups are
available, you must first group your microphones: See Using Device Groups (see "About Device Groups" on page
95) for information about creating groups as well as adding microphones to your groups.
In the Management Client's Site Navigation pane, expand Servers and select Recording Servers, then in the overview pane (see "Panes Overview" on page 36) expand the required recording server, expand the required
e and select the required microphone.
devic
Check the RC-E release notes to verify that microphones are supported for the devices and firmware used.
Enabling Microphones
When microphones are detected with the wizard Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49) they are by default disabled. You can enable microphones when needed. If a device has several microphones you can enable one, some, or all of them as required.
1. In the Site Navigation pane (see "Panes Overview" on page 36), expand Se
rvers and select Recording
Servers.
2. In the Overview pane (see "Panes Overview" on page 36), expand the relevant recording server, and find the device on which the microphone is placed.
3. Right-click the required microphone, and select Enabled.
On some devices, a microphone can also be enabled/disabled on the device itself, typically through the device's own configuration web page. If a microphone does not work after enabling it in the Management Client, you should thus verify whether the problem may be due to the microphone being disabled on the device itself.
Configuring Individual Microphones
You configure individual microphones by selecting the required microphone in the list, then specifying the microphone's required settings on the tabs in the Properties pane (see "Panes Overvie w" on page 36):
T
he Info tab (see "Info Tab Overview" on page 101) for managing the selected microphone's name, etc.
T
he Settings tab (see "Settings Tab Overview" on page 106) for managing the selected microphone's general
settings.
he Record tab (see "Record Tab Overview" on page 103) for managing the selected microphone's recording,
T
ase and archiving storage settings.
datab
The Events tab (see "Events Tab Overview" on page 99) for managing hardware configurable events.
On-Net Survei
llance Systems, Inc. 86
Page 87
RC-E User Manual Management Client (RC-E Manager)
Viewing Current State of a Microphone
When you have selected a microphone in the Management Client, information about the current status of the selected microphone is presented in the preview pane (see "Panes Overview" on page 36).
Manage Speakers
On many devices you are able to attach external loudspeakers; some devices even have built-in speakers. Devices' speakers are automatically detected when you add the devices to your RC-E system through the
Management Client's Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49) wizard, regardless of which of
wizard's detection options you use. Speakers do not require separate li cens es; you can use as many speakers as
the required on your system.
You can use speakers completely independently of cameras.
Who is able to talk through speakers? Users of the Ocularis Client can—provided speakers are available, and the users have the rights to use them—click a button to talk through speakers. Roles (see "Manage Roles" on page 147) determi
What happens if two users want to speak at the same time? Roles determine users' right to talk through speakers. As part of the roles definition, you are able to specify a speaker priority from very high to very low. If two users want to speak at the same time, the user whose role has the highest priority will win the ability to speak. If two users with the same role want to speak at the same time, the first-come first-served principle applies.
Tip: RC-E comes with a default rule (see "Manage Rules" on page 133) which ensures that audio feeds from all conn be deactivated and/or modified as required.
You have two entry points for managing speakers:
ne users' right to talk through speakers. You cannot talk through speakers from the Management Client.
ected microphones and speakers are automatically fed to the RC-E system. Like other rules, the default rul e can
In the Management Client's Site Navigation pane (see "Panes Overview" on page 36), expand Devic
es, select
Speakers, expand the required device group, and select the required speaker. If no device groups are available,
you must first group your speakers: See About Device Groups (on page 95) for information about creating groups as well as adding speakers to your groups.
In the Management Client's Site Navigation pane, expand Servers and select Recording Servers. In the overview
pane (see "Panes Overview" on page 36), expand the required recording server an
d select the required speaker.
Check the RC-E release notes to verify that speakers are supported for the devices and firmware used.
Enabling Speakers
When speakers are detected with the wizard Add Hardware, they are by default disabled. You can enable speakers when needed. If a device has several speakers you can enable one, some, or all of them as required.
1. In the Site Navigation pane (see "Panes Overview" on page 36), expand Se Servers.
2. In the Overview pane (see "Panes Overview" on page 36), expand the relevant recording server, and find the device on which the speaker is placed.
3. Right-click the required speaker, and select Enabled.
On some devices, a speaker can also be enabled/disabled on the device itself, typically through the device's own configuration web page. If a speaker does not work after enabling it in the Management Client, you should thus verify whether the problem may be due to the speaker being disabled on the device itself.
rvers and select Recording
On-Net Survei
llance Systems, Inc. 87
Page 88
RC-E User Manual Management Client (RC-E Manager)
Configuring a Speaker
You configure individual speakers by selecting the required speaker in the list, then specifying the speaker's required settings on the tabs in the Properties pane:
1. The Info tab (see "Info Tab Overview" on page 101) for managing the selected speaker's name, etc.
2. The Settings tab (see "Settings Tab Overview" on page 106) for managing the selected speaker's general settings.
3. T
he Record tab (see "Record Tab Overview" on page 103) for managing the selected speaker's recording,
database and archiving storage settings.
Viewing Current State of a Speaker
When you have selected a speaker in the Management Client, information about the current status of the selected speaker is presented in the preview pane.
Manage Input
On many devices you are able to attach external units to input ports on the device. Input units are typically external sensors. Such external sensors may, for example, be used for detecting if doors, windows, or gates are opened. Input from such external input units is treated as events by RC-E.
Such events can be used in rules (see "Manage Rules" on page 133). For example, you could create a rule specifying that a camera deactivated.
Devices' input ports are automatically detected when you add the devices to your RC-E system through the Management Client's Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49) wizard, regardless of which of
wizard's detection options you use.
the You have two entry points for managing input:
should begin recording when an input is activated, and stop recording 30 seconds after the input is
In the Management Client's Site Navigation pane (see "Panes Overview" on page 36), expand Devic
es, select
Inputs, expand the required device group, and select the required input. If no device groups are available, you
must first group your input: See About Device Groups (on page 95) for information about creating groups as well as adding input to your groups.
In the Management Client's Site Navigation pane, expand Servers and select the Recording Server node, then
expand the required recording server in the overview pane (see "Panes Overview" on page 36) and select the
ired input.
requ
Before you specify use of external input and output units on a device, verify that sensor operation is recognized by the device. Most devices are capable of showing this in their configuration interfaces, or via CGI script commands. Also check the RC-E release notes to verify that input- and output-controlled operations are supported for the devices and firmware used.
Enabling Input
When inputs are detected with the Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49) process, they are by default disabled. You can activate inputs when needed. If a device has several inputs you can enable one, some, or all of them as required.
1. In the Site Navigation pane (see "Panes Overview" on page 36), expand Se Servers.
2. In the Overview pane (see "Panes Overview" on page 36) expand the relevant recording server, and find the devic
e on which the input is placed.
On-Net Survei
llance Systems, Inc. 88
rvers and select Recording
Page 89
RC-E User Manual Management Client (RC-E Manager)
Right-click the required input, and select Enabled.
3.
Specifying Input Properties
Each input typically has several properties. You can access these properties in two ways:
In the Management Client's Site Navigation pane (see "Panes Overview" on page 36), expand D
evices, and
select Inputs. In the Overview pane expand the required inputs folder and select the required input.
- or -
In the Overview pane (see "Panes Overview" on page 36), select a device group to define settings for all inputs in
the grou
p, or expand a device group, and select the required input.
The properties of the selected input, or the common properties for all inputs in a selected device group, will be displayed on the following tabs: Settings, Info, and Events.
To learn more about the properties of the selected input, or the common properties for all inputs in a selected device group, see:
Viewing the Current State of an Input
The change of an input's state is regarded as an event by RC-E. Events can be used in rules and hereby trigger actions when the state of an input is changed.
See Define Input- and Output-Related Rules (on page 94) for more information about how to include an input event i n a rule.
T
o view the current state of an input in the Management Client, do the following:
1. In the Site Navigation pane (see "Panes Overview" on page 36), expand Devices, and select Inputs.
2. In the Overview pane (see "Panes Overview" on page 36), expand the required inputs folder and select the
ired input.
requ
Tip: You may select a group of inputs to view the current status of all inputs in the group.
3. Information about the current status of the selected input is presented in the preview pane. When an input is deactivated, it is shown by a gray indicator: When the input is activated, the indicator lights up green:
Fill in Properties on the Info Tab
Lets you view and edit basic information about an input. Contains the following fields: Name: Name of the input. Not compulsory, but highly recommended. Used whenever the input is liste d in RC-E
and clients. Does not have to be unique.
To change the name, overwrite the existing name and click Save in the toolbar (see "Management Client Overvie
Tip: example, a rule, the name will automatically change in the rule as well.
Description: Description of the input. Not compulsory. Will appear in a number of listings within RC-E. For
example, the description will appear when pausing the mouse pointer over the item's name in the Overview pane (see "Panes Overview" on page 36):
On-Net Survei
w" on page 34).
If you change the name, it will be updated throughout RC-E. This means that if the name is used in, for
llance Systems, Inc. 89
Page 90
RC-E User Manual Management Client (RC-E Manager)
o specify a description, type the description and click Save in the toolbar (see "Management Cli ent
T Overvie
w" on page 34).
Hardwar
e name: Name of the hardware with which the input unit is connected. The field is non-editable from
here, but can be changed by clicking Go To next to it. This takes you to hardware information, where the name is editable.
Unit number: Non-editable field, displaying the unit on which the input can be found on the hardware. For
hardware capable of having more than one input unit attached, the unit number will typically indicate the number of the input port to which the input is attached. For hardware with, for example, four input ports, the numbers will typically range from 0 to 3.
Fill in Properties on the Settings Tab
Lets you verify or edit key input settings, for a selected input, or for all inputs within a selected device group. If the selected device group contains 400 or more inputs, the Settings tab will be unavail able for viewing and editing because changing settings for so many devices in one step takes too long time.
The content of the Settings tab is determined entirely by the devices in question, and is thus likely to vary depending on the input selected.
Content may vary, but you will typically see the following property:
Input rises on: Lets you define whether the input signal should be considered rising on Circuit closed or Circuit
open. The value of this setting is used on the input's Events tab, where you define properties for input events: Input Rising event, Input Falling event, and Input Changed event. See also the description of the properties of the Events tab (see "Fill in Properties on the Events Tab" on page 90).
T
he content of the Settings tab is displayed in a table, in which the first column lists the available settings, and the
second column lists the value of each setting. You are typically able to change the values:
1. Select the row with the property you want to change
2. Click the button to the right of the properties column.
3. Change the value of the property.
4. In the toolbar (see "Management Client Overview" on page 34), click Save.
When you have changed a setting to a non-default value, the value will appe ar in bold. When a val ue must be within a certain range, for example between 0 and 100, the allowed range will be displayed in the gray information box below the settings table.
Fill in Properties on the Events Tab
Lets you define events based on changes of the input's state, from circuit opened to circuit closed or the reverse order. The events you define can subsequently be used in rules.
You can define events for a selected input, but not for all inputs in a device group.
1. In the Site Navigation pane (see "Panes Overview" on page 36), expand Devices, and select Inputs.
2.
In the Overview pane (see "Panes Overview" on page 36), select the required input.
3. Select
4. In the Select Driver Event dialog, select the appropriate option (Input Rising event, Input Falling event, or
the Events tab, and click Add....
Input Changed event).
On-Net Survei
llance Systems, Inc. 90
Page 91
RC-E User Manual Management Client (RC-E Manager)
5. Click OK. Your
selected type of input event will now appear in the Events tab's Configured events list.
To the right of the list, settings for the selected input event are displayed in a table. The table's first column lists available settings, the second column lists the value of each setting.
The settings on the Events tab is determined entirely by the devices in question, and is thus likely to vary depending on the input selected.
Content may vary, but you will typically see the following property: Enabled: Select between True (enabled), or False (disabled).
You are typically able to change the values:
1. Select the row with the property you want to change.
2. Click the button to the right of the properties column.
3. Change the value of the property.
4. In the toolbar (see "Management Client Overview" on page 34), click Save.
When you have changed a setting to a non-default value, the value will appe ar in bold. When a val ue must be within a certain range, for example between 0 and 100, the allowed range will be displayed in the grey information box below the settings table.
Manage Output
On many devices you are able to attach external units to output ports on the device. This allows you to activate/deactivate lights, sirens, etc. through RC-E.
Output may be used when creating rules (see "Manage Rules" on page 133). You can create rules that automatically activate or de
Output can also be triggered manually from the Management Client and the Ocularis Client. Devices' output ports are automatically detected when you add the devices to RC-E through the Management Client's
Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49) wizard, regardless of which of the wizard's detection optio
ns you use. By default, output are disabled. You can enable output when needed.
You have two entry points for managing outputs:
activate outputs, and rules that trigger actions when the state of an output is changed.
In the Management Client's Site Navigation pane (see "Panes Overview" on page 36), expand Devic
Outputs, expand the required device group, and select the required output. If no device groups ar e available, you
must first group your output: See About Device Groups (on page 95) for information about creating groups as well as add
ing output to your groups.
In the Management Client's Site Navigation pane, expand Servers and select Recording Servers, then in the
overview pan (see "Panes Overview" on page 36)e expand the required recording server output.
Before you specify use of external input and output units on a device, verify that sensor operation is recognized by the device. Most devices are capable of showing this in their configuration interfaces, or via CGI script commands. Also check the RC-E release notes to verify that input- and output-controlled operations are supported for the devices and firmware used.
Enabling Output
When outputs are detected with the Add Hardware (see "Add Hardware (Cameras, etc.)" on page 49) process, they are by default disabled. You can activate outputs when needed.
If a device has several outputs you can enable one, some, or all of them as required.
On-Net Survei
llance Systems, Inc. 91
es, select
and select the required
Page 92
RC-E User Manual Management Client (RC-E Manager)
In the Site Navigation pane (see "Panes Overview" on page 36), expand Se
1.
rvers and select Recording
Servers.
2. In the Overview pane (see "Panes Overview" on page 36) select the relevant recording server, and find the device on which the output is placed.
3. Right-click the required output, and select Enabled.
Specifying Output Properties
Each output has several properties which can be found on the output's Settings and Info tabs. You can access these tabs in two ways:
In the Site Navigation pane (see "Panes Overview" on page 36), expand Devices and select Outputs, th
en in the
Overview pane expand the required outputs folder and select the required output.
- or ­ In the Overview pane (see "Panes Overview" on page 36), select a device group to change the settings for all
outputs in th
is group, or expand a device group and select the required output.
The properties of the selected output, or the common properties for all outputs in a selected device group, will be displayed on the following tabs: Settings and Info.
To learn more about the properties of the selected output, or the common properties for all outputs in a selected device group, see:
Automatic and Manual Activation of Output
Output can be activated automatically or manually: Automatic Activation of Output
With the Management Client's rules (see "Manage Rules" on page 133) feature, you are able to create r
ules that
automatically activate or deactivate output, and rules that trigger actions when the state of an output is changed.
For example, you may create a rule specifying that a siren should sound if motion is detected on a particular
camera, or you may create a rule specifying that a camera should start recording if a siren sounds. See Define Input- and Output-Related Rules (on page 94) for more information.
Ma
nual Activation of Output
Output may be activated manually from the Management Client and the Ocularis Client:
1. In the Site Navigation pane (see "Panes Overview" on page 36), expand Devices and select Outputs.
2.
In the Overview pane (see "Panes Overview" on page 36), expand the required outputs folder and select the requ
ired output.
Tip: You may select a group of outputs, for example All Outputs, to manually activate all outputs in the group.
The availability of features for manually activating an output depends entirely on the device in question, and may thus vary.
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. When an output is activated, the indicator lights up green:
Alternatively, click the rectangular button to activate the output for the duration defined in the Output Trigger Time setting on the Settings tab (this feature/setting may not be available for all outputs). After the defined duration, the output is automatically deactivated.
On-Net Survei
llance Systems, Inc. 92
Page 93
RC-E User Manual Management Client (RC-E Manager)
Fill in Properties on the Info Tab
Lets you view and edit basic information about an output: Name: Name of the output. Not compulsory, but highly recommended. Used whenever the output is listed in RC-
E and clients. Does not have to be unique.
To change the name, overwrite the existing name and click Save in the toolbar (see "Management Client
Overview" on page 34).
Tip:
If you change the name, it will be updated throughout RC-E. This means that if the name is used in, for
example, a rule, the name will automatically change in the rule as well.
Description: Description of the output. Not compulsory. Will appear in a number of listings within RC-E. For
example, the description will appear when pausing the mouse pointer over the item's name in the Overview pane (see "Panes Overview" on page 36):
o specify a description, type the description and click Save in the toolbar (see "Management Cli ent
T Overvie
w" on page 34).
Hardwar
e name: Name of the hardware with which the output unit is connected. The field is non-editable from
here, but can be changed by clicking Go To next to it. This takes you to hardware information, where the name is editable.
Unit number: Non-editable field, displaying the unit on which the output can be found on the hardware. F or
hardware capable of having more than one output unit attached, the unit number will typically indicate the number of the output port to which the output is attached. For hardware with, for example, four output ports, the numbers will typically range from 0 to 3.
Fill in Properties on the Settings Tab
Lets you verify or edit key output settings, such as active output state, output trigger time, etc., for a selected output, or for all outputs within a selected device group. However, if the device group contains 400 cameras or more the Settings tab will not be available for viewing and editing because changing settings for so many devices in one step takes too long time.
The content of the Settings tab is determined entirely by the drivers for the cameras in question, and is thus likely to vary depending on the output selected.
Some devices are only able to apply outputs for a relatively short time, for example max. 5 seconds. Refer to the documentation for the device in question for exact information.
Content is displayed in a table, in which the first column lists the available settings, and the second column lists the value of each setting.
You are typically able to change the values:
1. Select the row with the property you want to change
2. Click the button to the right of the properties column.
3. Change the value of the property.
4. In the toolbar (see "Management Client Overview" on page 34), click Save.
When you have changed a setting to a non-default value, the value will appe ar in bold. When a val ue must be within a certain range, for example between 0 and 100, the allowed range will be displayed in the grey information box below the settings table.
On-Net Survei
llance Systems, Inc. 93
Page 94
RC-E User Manual Management Client (RC-E Manager)
Define Input- and Output-Related Rules
To be able to automatically
activate an output or trigger an event activated by an output, you must, after you have enabled an output,  trigger an action activated by an input, you must, after you have enabled the input and created an event based on
the input, include it in a rule. See Manage Output (on page 91) or Manage Input (on page 88) for more information. For example, you may create a rule specifying that:
a siren should sound if motion is detected on a particular camera, or you may create a rule specifying th at a
camera should start recording if a siren sounds (output). a camera should record if a particular input is activated (input).
For the following examples to be useful you should have general knowledge about manag ing rules (see "Manage Rules" on page 133). See also Create Typical Rules (on page 116) for other step-by-step descriptions of how to create rul
Tip: When you create a rule based on an in- or output event, the actions you specify in the rule do n ot ha ve to relate to the device on which the external in- or output was activated; you can easily specify that the actions should take place on one or more different devices— even across recording servers.
es.
Defining a Rule that Activates/Deactivates an Output
1. Start the Manage Rule and in step 1 select a rule type and, if necessary, a condition in step 2.
2. In Manage Rule's step 3 (Step 3: Actions) select the Set device output to <state> action.
3. If you like the output to be activated/deactivated immediately, skip this step. If you do not want to activate or deactivate the output immediately after the event, click the immediately link in the initial rule description, and select an interval between the event and the activation/deactivation of the output. Click OK to confirm your selection.
4. Click the state link in the initial rule description, and select whether you want to activate or deactivate the output. Click OK to confirm your selection.
5. Click the devices link in the initial rule description, and select which output you want to activate or deactivate. Click OK to confirm your selection.
6. If wanted you can select more actions in the Manage Rule's step 3 (Step 3: Actions). Do so or simply click Next to continue to the next step.
7. In Manage Rule's step 4 (Step 4: Stop criteria) select one of the stop actions, for instance to deactivate the output after a certain time or event.
8. Click Finish to save the rule.
Defining a Rule where an Output Triggers an Action
In the Rules feature, all registered external output (activation, deactivation or change) is treated as an event. Based on an event, you are able to specify a wide variety of actions to take.
To define a rule where an output activates an action, do the following:
1. Start the Manage Rule.
2. In Manage Rule's step 1 (Step 1: Type of rule) select the Perform an action on <event > option.
On-Net Survei
llance Systems, Inc. 94
Page 95
RC-E User Manual Management Client (RC-E Manager)
3. Click
the event link in the initial rule description.
4. In the Select an Event dialog's Built-in group, select the appropriate option for your rule: Output Activated, Output Changed or Output Deactivated. Click OK to confirm your selection.
5. Click the devices/recorders/servers link in the initial rule description.
6. In the Select Devices and Groups dialog select the required output. Click OK to confirm your selection.
7. Click Next to continue to the Manage Rule's step 2 (Step 2: Conditions) and select, if necessary, a condit ion.
8. Continue to step 3 (Step 3:Actions) and select one or more actions.
9. If you do not want to define a stop action, skip this step. If you want to define a stop action— for instance to deactivate the output again— click Next to continue to step 4 (Step 4: Stop criteria), and select a stop action.
10. Click Finish to save the rule.
Defining a Rule where an Input Triggers an Action
In the Rules feature, all registered external input (activation, deactivation, or change) is treated as an event. Based on an event, you are able to specify a wide variety of actions to take.
To define a rule specifying that an input should result in one or more actions (for example the starting of recording on a certain camera), do the following:
1. Start Managing Rules.
2. In Managing Rules step 1 (Step 1: Type of rule) select the Perform an action on <event > option.
3. Click the event link in the initial rule description.
4. In the Select an Event dialog's Hardware Configurable group, select the appropriate option for your rule: Input Activated, Input Changed, or Input Deactivated. Click OK to confirm your selection.
5. Click the devices/recording servers/management servers link in the initial rule description.
6. In the Select Devices and Groups dialog select the required input. Click OK to confirm your selection.
7. Click Next to continue to Managing Rules step 2 (Step 2: Conditions) and select, if necessary, a condition.
8. Continue to step 3 (Step 3:Actions) and select one or more actions.
9. Click Next to continue to step 4 (Step 4: Stop criteria), and select a stop criteria. Click Next to continue to step 5 (Step 5: Stop actions), and select a stop action.
10. Click Finish to save the rule.
About Device Groups
You are able to group different types of devices (cameras, microphones, speakers, inputs, outputs) on your RC-E system by using device groups. The use of device groups has several benefits:
Device groups help you maintain an intuitive overview of devices on your system  You are able to specify common properties for all devices within a device group in one step  When dealing with roles (see "About Roles" on page 145), you are able to specify common security settings for
all d
evices within a device group in one step
On-Net Survei
llance Systems, Inc. 95
Page 96
RC-E User Manual Management Client (RC-E Manager)
When dealing with rules (see "Manage Rules" on page 133), you are able to apply a rule for all devices within a device group in one step
You can add as many device groups as required; you are completely free to decide which devices to include. The only restriction is that you cannot mix different types of devices (for example cameras and speakers) in a device group.
If a device group contains 400 devices or more, the Settings tab is unavailable for viewing and editing. For camera groups, the Streams tab is also unavailable for editing and viewing if the group contains 400 cameras or more. When you click the plus sign next to the device folder, your RC-E system will load the contents of the device folder, which may take a few seconds. While expanding, the text (expanding...) is displayed next to the folder name.
The following examples are based on grouping cameras into device groups, but the principle applies for microphones, speakers, inputs and outputs as well.
Adding a Device Group
1. In the overview pane (see "Panes Overview" on page 36), right-click the item under which you wish to create the new device group.
2. Select Add Device Group:
Tip: You may also simply press CTRL+N on your keyboard.
The Add Device Group dialog will appear.
3. In the Add Device Group dialog, specify a name and description of the new device group: The description will later appear when pausing the mouse pointer over the device group in the device list.
4. Click OK. A folder representing the new device group is added to the list. You are now able to specify which devices should belong in the device group.
Tip: If required, you are able to add device groups as subgroups under other device groups, as illustrated here:
Specifying Which Devices to Include in a Device Group
1. In the Overview pane (see "Panes Overview" on page 36)'s device list, right-click the required device group folder.
2. Select Edit Device Group Members. The Select Group Members window will appear.
3. In the Select Group Members window, select either: o The Device Groups tab, which lists devices based on existing device groups.
Tip: A device can be a member of more than one device group.
o The Recording Servers tab, which lists devices based on which recording servers the devices belong on.
4. Select the devices you wish to include, and click Add . This will copy the selected devices to the Selected box:
Tip: You may also double-click a device to copy it from one box to the other, or you may simply drag devices between the two boxes.
Tip: To select several devices in one step, press the CTRL key on your keyboard while selecting.
5. Click OK. The selected devices will be added to your device group on the device list.
On-Net Survei
llance Systems, Inc. 96
Page 97
RC-E User Manual Management Client (RC-E Manager)
Specifying Common Settings for All Devices in a Device Group
When using device groups, you are able to quickly specify common properties for all devices within a given device group:
1. In the overview pane (see "Panes Overview" on page 36)'s device list, click the required device group. In the properties pane (see "Panes Overview" on page 36), all properties w
hich are available on all of the
device group's devices will be listed, grouped on tabs.
2. Specify the required common properties. Properties not available on all of the devices in the device group will not be listed; such properties must still
be configured individually for each device. If the device group contains 400 or more devices the Settings tab is unavailable for viewing and editing. For
camera groups the Streams tab is also unavailable for viewing and editing if the group contains 400 cameras or more.
Tip: The Settings tab (see "Enabling and Disabling Edge Recording— Camera Only" on page 106) has
nient functionality for quickly switching between settings for the device group and se ttings for individual
conve devices.
Deleting a Device Group
1. In the overview pane (see "Panes Overview" on page 36)'s device list, right-click the unwanted device group folder.
2. Select Delete Group.
Tip: You may also simply press DELETE on your keyboard.
3. You will be asked to confirm that you want to delete the device group. Verify that you are deleting the correct device group, then click Yes.
Remember that you have only deleted the device group itself. If you wish to delete IP hardware - such as a camera ­from your RC-E system, do so on a recording server level (see Managing Hardware (see "Manage Hardware" on page 53)).
About Events
Events are primarily used for triggering actions. Actions are configurable through rules (see "Ma na ge Rules " on page
133).
Examp
le: You create a rule which specifies that in the event of detected motion, the surveillance system
should take the action of starting recording of video from a particular camera.
In the Management Client's Site Navigation pane (see "Panes Overview" on page 36), you are able to work with the following under Rules and Events:
Rules (see "Manage Rules" on page 133): R
surveillance system is to a very large extent determined by rules.
Time profiles (see "Manage Time Profiles" on page 138): T
Management Client. They can be used when creating rules in the Management Client; for example, to create a rule which specifies that a certain action should take place within a certain time profile.
On-Net Survei
llance Systems, Inc. 97
ules are a central element in RC-E. The behavior of your
ime profiles are periods of time defined in the
Page 98
RC-E User Manual Management Client (RC-E Manager)
Notific
ation Profiles (see "Manage Notification Profiles" on page 141): With notification profiles you can set up
ready-made e-mail notifications, which can automatically be triggered by a rule, for example when a particular event occurs.
User-defined Events (see "Manage User-defined Events" on page 143): User-defi
ned events are custom made
events making it possible for users to manually trigger events in the system or react to inputs from the system.
Hardware Configurable Events: (see "Hardware Configurable Events" on page 110)Some hardware is capable
of creating ev
ents themselves. For example, some cameras are themselves able to detect motion or static/moving objects, and their detections can be used as events in RC-E. Such events must obviously be configured on the hardware before they can be used in RC-E , therefore they are called hard ware config urable events. Read more about hardware configurable events for cameras (see "Manage Cam eras" on page 75), inputs (see "Manage Input" on page 88) and microphones (see "Manage Microphones" on page 85) respectively.
See Events Overvie
w (on page 128) for a list of events.
About Multi-streaming
Viewing of live video and playing back of recorded video does not necessarily require the same settings to achieve the best result. To handle this, RC-E and some cameras support multi-streaming, with which you can establish two independent streams to the recording server. Either one stream for live viewing and another stream for playback purposes or two separate live streams—with different resolution, encoding, and frame rate.
Example 1, live and recorded video:
For viewing live video, your organization may prefer MPEG4 at a high frame rate. For playing back recorded video, your organization may prefer MJPEG at a lo wer frame rate because this will
help preserve disk space.
Example 2, two live videos: For viewing live video from a local operating point, your organization may prefer MPEG4 at a high frame rate
to have the highest quality of video available.
For viewing live video from a remotely connected operating point, your organization may prefer MJPEG at a
lower frame rate and quality in order to preserve network bandwidth.
Even when cameras support multi-streaming, individual multi-streaming capabilities may vary considerably between different cameras. Refer to camera's documentation for exact information. To see if a camera offers different types of streams, see the Settings tab (see "Settings Tab Overview" on page 106).
You manage multi-streaming on the Streams tab. The tab is only available when the selected camera or device group supports multi-streaming.
If you select a device group with 400 or more cameras, the Streams tab will not be available for viewing and editing because changing settings for so many devices in one step takes too long time.
To access the Streams tab, expand Devices in the Management Client's Site navigation pane (see "Panes Overview" on pa
ge 36), expand the relevant camera folder in the Overview pane (see "Panes Overview" on page 36), select the
requ
ired camera and then select the Streams tab in the Properties pane (see "Panes Overview" on page 36).
he tab will by default list a single stream—the selected camera's default stream, used for live video as well as for
T video which is being recorded for playback purposes.
Note that while it is possible to set up and use two live streams, only one of the enabled live streams is able to record video at a time. To change which stream to use for recording, use the Record box.
On-Net Survei
llance Systems, Inc. 98
Page 99
RC-E User Manual Management Client (RC-E Manager)
Adding a New Stream
1. On the Streams tab, click Add. This will add a second stream to the list (you cannot have more than two
streams).
2. In the Stream column, select the required type of stream.
3. If you want to use the stream for live video, select the check box in the Live column. Leave the check box cleared if you only want to use the stream for video which will be recorded.
You can use the same stream for both live and recorded video if required. You cannot use two different streams for the same purpose, for example for live video.
4. If you want to use the stream for recorded video, select the check box in the Record column. Leave the check box cleared if you only want to use the stream for live video.
Note how the selection in the Plug-ins column always follows the stream you have selected for recorded video. This is because the integrated plug-in which RC-E uses for motion detection is always applied on the video stream which will be recorded.
The Edge Recording column indicates whether the selected stream supports edge recording (see "Record T
ab Overview" on page 103) or not.
5. Click Sav
e.
Events Tab Overview
For items (cameras or microphones) supporting events, you are able to manage the hardware configurable events on the Events tab. To access the Events tab, select the required item in the overview pane (see "Panes Overview" on pag
e 36), then select the Events tab in the p
The Events tab will only be available if the selected item supports hardware configurabl e events. Even when an item supports hardware configurable events, it is always your decision whether you want to use such
events on your RC-E system. Therefore, you simply add each hardware configurable event you want to be able to use on each item.
About the Event Tab for Camera
In addition to RC-E's motion detection, some cameras can themselves be configured to detect motion. If a camera is capable of such detection, the camera's detections can be used as events. Such events can in turn be used when creating event-based rules (see "Events Overview" on page 128). Events from cameras are called hardware
urable events as they technically occur on the actual camera hardware rather than on the surveillance system.
config Even though events based on signals from input and/or output units connected to camera devices are technically also
hardware configurable events, they are managed elsewhere. See Manage Inputs (see "Manage Input" on page 88) and Manage Outputs (see "Manage Output" on page 91).
About the Event Tab for Microphone
Some devices are capable of creating events themselves. Such events can in be used when creating event-based rules (see "Events Overview" on page 128) in RC-E. Events from such devices are called hardware configurable events, as the
y technically occur on the actual camera hardware rather than on the surveillance system.
roperties pane (see "Panes Overview" on page 36).
Adding a Hardware Configurable Event
1. On the Events Tab, click Add.... This opens the Select Driver Event window.
On-Net Survei
llance Systems, Inc. 99
Page 100
RC-E User Manual Management Client (RC-E Manager)
Select the required hardware configurable event:
2. You can only select one hardware configurable event at a time.
3. Click OK. The selected event will be added to the Events tab's list of configured events.
4. In the toolbar (see "Management Client Overview" on page 34), click Save.
Using Several Instances of a Hardware Configurable Event
To be able to specify different properties for different instances of an event, you are able to add a hardware configurable event more than once (see also Specifying Hardware Configurable Event Properties (see "Specify
ware Configurable Event Properties" on page 100)).
Hard The following example is specific to cameras.
Example: The camera in question has been configured with two motion windo ws, called A1, and A2. Yo u have added two instances of the Motion Started (HW) event. In the properties of one instance, you have specified use of motion window A1; in the properties of the other instance, you have specified use of motion window A2.
When you use the hardware configurable event in a rule, you are able to specify that the event should be based on motion detected in a specific motion window in order for the rule to be triggered:
Deleting a Hardware Configurable Event
Bear in mind that deleting a hardware configurable event will affect any rules in which the event is used.
1. In the Events tab's Configured Events list, select the no longer required event.
Tip: If there are several instances of the same event, use the properties list in the right side of the tab to verify that you have selected the correct event.
2. Click Delete. The selected event will be deleted without further warning.
3. In the toolbar (see "Management Client Overview" on page 34), click Save.
Specify Hardware Configurable Event Properties
For each hardware configurable event you have added, you are able to specify properties. The number of properties depends on the item in question. In order to work as intended, some or all of the properties must be specified identically on the item as well as on RC-E.
Even though the following list is not exhaustive, you may often be able to specify the following properties :
Enabled: Determines whether use of the hardware configurable event is enabled. Select True to enable; select
False to disable.
Enabled is the only property you will always see for microphones.
Include Images: Determines whether video should be sent from the camera to RC-E when the event occurs.
Select True if video is required; select False if video is not required.
Motion Window: Many cameras capable of detecting motion can be configured with different motion d etection
settings for different parts the camera's images. For example, if a camera covers a 2-lane road, different motion detection settings may have been defined for the right lane and left lane area of the camera's images. Such areas are generally known as motion windows.
On-Net Survei
llance Systems, Inc. 100
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use