1. Manuals
  2. Brands
  3. OnSSI Manuals
  4. Recording Equipment
  5. RC-E
  6. User manual

OnSSI RC-E User Manual

Recording component
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
RC-E User Manual
Recording Component (RC-E)

User Manual

© 2012 On-Net Surveillance Systems Inc.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the RC-E and is the answer not in the manual?

Questions and answers

Related Manuals for OnSSI RC-E

Summary of Contents for OnSSI RC-E

  • Page 1: User Manual

    RC-E User Manual Recording Component (RC-E) User Manual © 2012 On-Net Surveillance Systems Inc.
  • Page 2 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.

  • Page 3: Table Of Contents

    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.........................
  • Page 4 Issue: Insufficient Continuous Virtual Memory Fails Installation................33 Issue: Multi-domain Environments; One-way Trusts not Working ................33 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................................
  • Page 5 Manage Local IP Address Ranges ........................171 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 ....................
  • 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...........................

  • Page 7: Introductions

    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.

  • Page 8: The Rc-E Recording Server

    Where? Typically installed on the surveillance 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.

  • Page 9: System Requirements

    Manage Users and Groups in place before you 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.

  • Page 10: Computer Running Management Client

    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.

  • Page 11: Navigating The Built-In Help System

    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. To do this, simply use the help window's three tabs: Contents, Search, and Glossary, or use the links inside the help topics.

  • Page 12: Installation And Removal

    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, network, and storage system.

  • Page 13: Install Management Server

    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"...

  • Page 14: Step 1: Internet Information Services

    Verify or change the location (drive and directory) to place the installation file and click Next. Once the files are extracted, you will see a screen with checkboxes to Install RC-E Event Proxy and RC-E Recorder.

  • Page 15: Step 2: Rc-E Management Server Database

    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.
  • 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 management server component.

  • Page 17: What's Next

    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"...

  • Page 18: Part Ii-Installing The Component

    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. Specify recording server setup parameters (see "Specify Recording Server Setup Parameters" on page 21).
  • 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. Select required installation folder, then click Next. When asked which type of server to install, click the Standard recording server [...] icon. This lets you install a regular recording server.

  • Page 20: Failover Servers

    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.

  • Page 21: Management Client

    Launch RC-E Management Client. This will start the Management Client (RC-E Manager) right away. 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. ...

  • Page 22: Installing Log Server

    Next. 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 page 150).

  • Page 23: Important Port Numbers

    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.

  • Page 24: Multiple Management Servers (Clustering)

    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.

  • Page 25: Prerequisites For Installing Onssi 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. 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).

  • Page 26: Upgrading Rc-E In A Cluster

    No registry settings should be replicated, click Next. Verify that the cluster service is configured according to your needs, then click Next. 10. The RC-E management server has now been configured as a generic service in the failover cluster. Click Finish to exit the wizard.

  • Page 27: Installing Multiple Recording Server Instances

    View status messages for each instance individually, grouped on tabs. 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: In Windows' Start menu, select Control Panel, and then...

  • Page 28: Removing Management Client

    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 any version, you will only be able to install a version for which your license file is valid.

  • Page 29: Upgrading The Management Server

    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 the three installation steps for the management server, you will be asked to address step 3 (OnSSI RC-E management server).

  • Page 30: Upgrading A Management Client

    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.

  • Page 31: Issue: Recording Server Startup Fails Due To Port Conflict

    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.
  • Page 32 From Windows' Start menu, select Control Panel. In the Control Panel, double-click Administrative Tools. In the Administrative Tools window, double-click Services. In the Services window, repeat steps a-c for these items: OnSSI ImageImportService, OnSSI ImageServer, OnSSI LogCheckService, OnSSI Recording Server. Double-click the item.

  • Page 33: Issue: Changes To Sql Server Location Prevents Database Access

    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.

  • Page 34: Management Client (Rc-E Manager)

    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 pane). The Management Client's features are grouped into the following categories: ...

  • Page 35: Menu Bar

    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.

  • Page 36: Panes Overview

    RC-E User Manual Management Client (RC-E Manager) To free up memory, refresh the Management Client: Click OK to exit the dialog, then press F5 on your keyboard or select Refresh from the Action menu. Panes Overview The Management Client window may contain up to four panes.

  • Page 37: Site Navigation Pane And Federated Hierarchy Pane

    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.
  • Page 38 What 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.

  • Page 39: Log In To The Management Client

    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.

  • Page 40: Management Client Menu Overview

    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.

  • Page 41: Customize The Management Client's Layout

    RC-E User Manual Management Client (RC-E Manager)  Search... 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.
  • 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.

  • Page 43: Activate Licenses

    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. To register with the OnSSI Licensing Portal, open a browser and go to the following URL: https://rclicensing.onssi.com/CustomerRegistration...
  • Page 44 On the OnSSI Licensing screen, enter your email address. This will become your user name for the OnSSI Licensing Portal. 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.

  • Page 45: Manage Licenses

    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.

  • Page 46: Remote Connect Services

    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 cameras can deliver data to RC-E.
  • 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 environment.

  • Page 48: Axis One-Click Camera Connection Properties

    RC-E User Manual Management Client (RC-E Manager) Removing Secure Tunnel Servers To remove an ST server, right-click it, select Remove Axis Secure Tunnel Server... Click Yes. Registering a new Axis One-click Camera To register a camera under an ST server, right-click it, select Register Axis One-click Camera...

  • Page 49: Servers

    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.
  • Page 50 When ready, click Next. 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.
  • Page 51 RC-E User Manual Management Client (RC-E Manager) Start address: First IP address in required range. End address: Last IP address in required range. The start and end IP address may be identical, allowing you to only scan for a single hardware device if needed.
  • Page 52 When ready, click Next. 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.

  • Page 53: Manage Hardware

    RC-E User Manual Management Client (RC-E Manager) 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.
  • 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 permanently. In the overview pane (see "Panes Overview" on page 36), expand the required recording server, right-click the no longer needed hardware device.
  • 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. 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.

  • Page 56: About Storage And Archiving

    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 organizations' needs.
  • Page 57 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 takes place.

  • Page 58: Viewing Archived Recordings

    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.
  • Page 59 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.

  • Page 60: Manage Recording Servers

    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.
  • 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.
  • Page 62 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.
  • Page 63 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).
  • 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).
  • Page 65 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.
  • Page 66 RC-E User Manual Management Client (RC-E Manager) Recording and archiving configuration list content: Database name Maximum size of the database (and usage; also represented graphically by a proportional filling of the database) Database location 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.
  • 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.
  • Page 68 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.
  • Page 69 RC-E User Manual Management Client (RC-E Manager) Deleting an Archive from within an Existing Storage To delete an archive, select the wanted archive from the Recording and archiving configuration list by clicking it. A selected archive is marked by a dark frame.

  • Page 70: Manage Multicasting

    About Upgrading 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.
  • 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.

  • Page 72: Manage Public Addresses

    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.

  • Page 73: Servers And Clients Require Time-Synchronization

    (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.
  • 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)

  • Page 75: Devices

     Outputs : (see "Manage Output" on page 91) 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. 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).
  • Page 76 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 network or on individual clients, RC-E will revert to unicasting (sending of separate data packets to separates recipients).
  • Page 77 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.
  • Page 78 RC-E User Manual Management Client (RC-E Manager) The selected motion level is indicated by the black vertical line in the motion indication bar above the sliders. 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.
  • Page 79 RC-E User Manual Management Client (RC-E Manager) Select between 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 regions.
  • Page 80 RC-E User Manual Management Client (RC-E Manager) When you enable privacy masking, the preview image is divided into selectable sections by a grid. To define privacy mask regions, drag the mouse pointer over the required areas in the preview image. Pressing down left mouse button selects a grid section;...
  • Page 81 RC-E User Manual Management Client (RC-E Manager) example, you may create a rule specifying that one patrolling profile should be used during daytime opening hours, 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.
  • Page 82 Customizing speed for transitions is only supported if your camera supports PTZ scanning 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.
  • Page 83 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.
  • Page 84 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.
  • Page 85 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.
  • Page 86 "Manage Rules" on page 133) which ensures that audio feeds from all connected microphones and speakers are automatically fed to the RC-E system. Like other rules, the default rule can be deactivated and/or modified as required. You have two entry points for managing microphones: ...
  • Page 87 "Manage Rules" on page 133) which ensures that audio feeds from all connected microphones and speakers are automatically fed to the RC-E system. Like other rules, the default rule can be deactivated and/or modified as required. You have two entry points for managing speakers: ...
  • Page 88 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.
  • Page 89 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.
  • Page 90 RC-E User Manual Management Client (RC-E Manager) To specify a description, type the description and click Save in the toolbar (see "Management Client Overview" on page 34).  Hardware 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.
  • Page 91 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.
  • Page 92 RC-E User Manual Management Client (RC-E Manager) In the Site Navigation pane (see "Panes Overview" on page 36), expand Servers and select Recording Servers. 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.
  • Page 93 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.
  • 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.
  • Page 95 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: ...
  • Page 96 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.
  • Page 97 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)).
  • Page 98 RC-E. Such events must obviously be configured on the hardware before they can be used in RC-E , therefore they are called hardware configurable events. Read more about hardware configurable events for cameras (see "Manage Cameras" on page 75), inputs (see "Manage Input"...
  • Page 99 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.
  • Page 100 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.
  • Page 101 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.
  • Page 102 It is highly recommended that you use a unique camera shortcut number for each camera. Tip: Find more information about keyboard shortcuts from a Ocularis Client user's perspective in the separate Ocularis Client documentation available on the OnSSI RC-E software DVD as well as from www.onssi.com (http://www.onssi.com)
  • Page 103 RC-E User Manual Management Client (RC-E Manager) Not all video encoders support the use of PTZ cameras. Even video encoders which support the use of PTZ cameras may require configuration, such as installation of additional drivers (typically through accessing a browser-based configuration interface on the device's IP address) before PTZ cameras can be used.
  • Page 104 RC-E anyway. When prebuffering is enabled for a camera or a microphone, RC-E continuously records video or audio from the camera's or microphones stream and provisionally stores it in the database for a specified number of seconds before automatically deleting it—...
  • Page 105 RC-E User Manual Management Client (RC-E Manager) The number of seconds you specify in the Prebuffer size box must be sufficiently large to accommodate your requirements. Example: If, like in this rule example, you plan to be able to save video from five seconds prior to detected motion, the prebuffer size must be at least five seconds.
  • Page 106 RC-E User Manual Management Client (RC-E Manager) Enabling and Disabling Edge Recording—Camera Only The Edge recording area will only be enabled if the selected camera supports edge recording. If disabled, select the Use edge recording if device is unavailable check box to enable edge recording.
  • Page 107 RC-E User Manual Management Client (RC-E Manager) 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 types of cameras selected. Tip: Some cameras may support more than one type of stream, for example MPEG4 and MJPEG. In that case, you...

  • Page 108: Client

    By default, each role you define in the Management Client is also created as a view group: when you add a role in RC-E Manager, the role will by default appear as a view group for use in Ocularis Client Limited Mode.

  • Page 109: Rules And Events

    RC-E User Manual Management Client (RC-E Manager) rename or remove each of your view groups if required. This is no matter whether the view groups were created automatically when adding a role or whether you added them manually. Adding a View Group In the Management Client's Site Navigation pane (see "Panes Overview"...

  • Page 110: Actions And Stop Actions Overview

    Some hardware is capable of creating events 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 hardware configurable events.
  • Page 111 RC-E User Manual Management Client (RC-E Manager) Each type of action is described (additional actions may, however, be available if your RC-E installation uses add-on products, special plug-ins, etc.). For each type of action, stop action information is listed as well:...
  • Page 112 Specify a priority from 1 to 32.000, where 1 is the lowest priority. Default PTZ priority is 3000. If your system is upgraded from an older version of RC-E , the old values (Very Low, Low, Medium, High and Very High) have been translated as follows: ...
  • Page 113 Only one preset position on one camera can be selected; it is not possible to select several preset positions. If your system is upgraded to RC-E 4.0 (or future versions), rule priority settings is a new feature. Existing rules (created without priority) automatically get priority 1. It is strongly recommended to reconsider this lowest possible priority for all affected rules.
  • Page 114 RC-E User Manual Management Client (RC-E Manager) Action Description strongly recommended to reconsider this lowest possible priority for all affected rules. This type of action requires that the devices to which the action will be linked are PTZ (Pan/Tilt/Zoom) devices, and that default preset positions have been defined for those devices.
  • Page 115 RC-E User Manual Management Client (RC-E Manager) Action Description an event or after a period of time. Start plug-in on Starts one or more plug-ins. When selecting this type of action, Manage Rule will <devices> prompt you to select required plug-ins, and on which devices to start the plug-ins.

  • Page 116: Create Typical Rules

     Use Higher Live Frame Rate on Motion: Ensures that when motion is detected on a specific camera, RC-E will use a higher than default live frame rate for the camera, and return to using the camera's default live frame rate when motion is no longer detected.
  • Page 117 Overview" on page 106) instead. Motion is normally detected by RC-E when video received from cameras is analyzed. This is the type of motion detection dealt with in this example. However, some cameras are— depending on configuration of the camera hardware—...
  • Page 118 RC-E User Manual Management Client (RC-E Manager) Devices/recording server/management server link: When you have selected the required event, clicking the devices/recording server/management server link opens the Select Group Members window, which lets you specify the devices on which device the event should occur in order for the rule to apply.
  • Page 119 RC-E User Manual Management Client (RC-E Manager) Click Finish. This will add your new rule to the list of rules. Use Specific PTZ Patrolling Profile During Specific Part of Day Tip: When patrolling stops, you can—if needed—get the PTZ camera to...
  • Page 120 RC-E User Manual Management Client (RC-E Manager) On the wizard's next step, specify which time conditions should be met in order for the rule to apply. In this example... we want the rule to apply between 1:00 and 8:00 on Saturdays, so two time conditions are required: one which specifies use of a start time and end time, and one which specifies use on a particular day of the week.
  • Page 121 RC-E User Manual Management Client (RC-E Manager) Note that the stop criterion No actions performed on rule end is not available: a stop criterion must be defined for this type of rule. We still need to define exactly which kind of stop action should take place when the time period ends.
  • Page 122 RC-E User Manual Management Client (RC-E Manager) overview pane (see "Panes Overview" on page 36). Select the required PTZ camera from the list, and select the Presets tab in the properties pane (see "Panes Overview" on page 36). For details of how to define preset positions on the Presets tab, see Preset Positions (see "PTZ Presets Tab (Camera Properties)"...
  • Page 123 RC-E User Manual Management Client (RC-E Manager) Finally, click the priority link to set the priority (see "Actions and Stop Actions Overview" on page 110) of the patrolling profile. The rule description now reflects our selection: Click Next to move to step 4 of the wizard.
  • Page 124 In this example, we assume that patrolling has already been set up for the PTZ camera, and that the external input unit is a door sensor connected to an input port on a device on the RC-E system: When the door sensor is activated, the PTZ camera will pause patrolling, move to a preset position covering the door area, remain at the preset position for 15 seconds, then resume patrolling.
  • Page 125 In this example...we want the event to be activated input. Input comes from— and is configured on— separate hardware rather than on RC-E itself, so we go to the Hardware Configurable group, select the event Input Activated, and click OK:...

  • Page 126: Default Rules

    IMPORTANT: Like other rules, default rules can be deactivated and/or modified as required. The fact that default rules are present does therefore not in itself guarantee that your RC-E system will work. Nor does it guarantee that video feeds or audio feeds will automatically be fed to the RC-E system, as the default rules may subsequently have been deactivated or modified.
  • Page 127 Perform an action when time interval ends stop feed immediately Default Start Audio Feed Rule Ensures that audio feeds from all connected microphones and speakers are automatically fed to the RC-E system. IMPORTANT: While the default rule enables access to connected microphones' and speakers' audio feeds immediately upon installing the system, it does not guarantee that audio will be recorded (see "Record Tab Overview"...

  • Page 128: Events Overview

    RC-E User Manual Management Client (RC-E Manager) Events Overview When creating an event-based rule in the Manage Rule wizard (see Manage Rules (on page 133)), you are able to select between a number of different events. In order for you to get a good overview, selectable events are listed in groups according to whether they are:...
  • Page 129 Motion Started (HW) Occurs when a camera detects motion in its video stream. In addition to RC-E's motion detection, some cameras are— depending on configuration of the camera hardware— themselves able to detect motion. Such camera-detected motion detection can also be used in RC-E rules.
  • Page 130 Motion Started Occurs when RC-E detects motion in video received from cameras. This type of event requires that RC-E's motion detection is enabled for the cameras to which the event will be linked. Exactly what constitutes motion depends on the motion detection settings specified for individual cameras in RC-E.
  • Page 131 RC-E User Manual Management Client (RC-E Manager) Event Description This type of event requires that at least one device on your system has an external input unit connected to an output port. Output Deactivated Occurs when an external output unit connected to an output port on a device is deactivated.
  • Page 132 Database Repair Occurs if a database becomes corrupted, in which case RC-E will automatically attempt two different database repair methods: a fast repair and a thorough repair.

  • Page 133: Manage Rules

    (see "Manage Failover Servers" on page 192). Manage Rules are a central element in RC-E. The behavior of an RC-E surveillance 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.
  • Page 134 How is stopping the feed from a device different from manually disabling the device? Stopping a device means that video will no longer be transferred from the device to RC-E, in which case neither live viewing nor recording will be possible. However, a device on which the feed has been stopped will still be able to communicate with the recording server, and the feed from device can be started automatically through a rule, as opposed to when the device is manually disabled in the Management Client.
  • Page 135 Default Rules OnSSI RC-E comes with a number of default rules, ensuring that basic features work without any user intervention being required. See Default Rules (on page 126).
  • Page 136 RC-E User Manual Management Client (RC-E Manager) Event: Clicking the event link lets you select the event which must occur in order for the rule to apply (for example Motion Started). Devices/recording server/management server: When you have selected the required event, clicking the devices/recording server/management server link lets you specify the devices on which the event should occur in order for the rule to apply.
  • Page 137 Deactivating and Activating a Rule A rule is by default active, meaning that RC-E will apply the rule as soon as the rule's conditions apply. If you do not want a rule to be active, you can deactivate the rule. When the rule is deactivated, RC-E will not apply the rule, even if the rule's conditions apply.

  • Page 138: Manage Time Profiles

    Always. This means that members of roles with this default time profile attached has no time-based limits to their user rights in the RC-E system. An alternative time profile can easily be assigned to a role. Time profiles are highly flexible: they can be based on one or more single periods of time, on one or more recurring periods of time, or a combination of single and recurring times.
  • Page 139 RC-E User Manual Management Client (RC-E Manager) Specifying a Time Profile In the Time Profiles list, right-click Time Profiles, and select Add Time Profile...: Tip: Instead of right-clicking to select Add Time Profile..., you can press CTRL+N on your keyboard.

  • Page 140: Manage Day Length Time Profiles

    To overcome this, Day Length Time profiles can be created and defined in RC-E according to the sunrise and sunset in a specified geographical area. Via GPS coordinates, the system, on a daily basis, calculates the sunrise and sunset time, even incorporating daylight saving time.

  • Page 141: Manage Notification Profiles

    RC-E User Manual Management Client (RC-E Manager)  Time zone: Time zone indicating the physical location of the camera(s). Manage Notification Profiles With notification profiles you can set up ready-made e-mail notifications, which can automatically be triggered by a rule (see "Manage Rules" on page 133), for example when a particular event occurs. You are even able to include still images and AVI video clips in the e-mail notifications.
  • Page 142 RC-E User Manual Management Client (RC-E Manager) If you want to include AVI video clips in e-mail notifications under the notification profile, select Include images, and specify time before and after event and frame rate. Click Finish. IMPORTANT: Pre-alarm images functionality cannot coexist with edge recording, see Enabling and Disabling Edge Recording—Camera Only (on page 106).

  • Page 143: Manage User-Defined Events

    In this case, user-defined events make it possible for end users to manually trigger events while viewing live video in the Ocularis Client. Thus, when a user-defined event occurs because it is manually triggered by an Ocularis Client user, a rule can trigger that one or more actions should take place on the OnSSI RC-E system.
  • Page 144 When an access control device is activated, a user-defined event is triggered in RC-E. This user-defined event is used in a rule to start recording on a camera associated with the activated access control device. It is defined in the meta-data which camera is associated with what rule. This way the company does not need to have 35 user-defined events and 35 rules triggered by the user-defined events;...

  • Page 145: Security

    You define roles first, then you add users/groups and a time profile (see "Manage Time Profiles" on page 138) to each role. One role is predefined in RC-E , and cannot be deleted: the Administrators role. In addition to the Administrators role, you are able to add as many roles as required in your organization.
  • Page 146 (i.e. it contains three users). Groups can contain any number of users. By adding a group to RC-E, you add all of its members in one step. Once the group has been added to RC-E, any changes subsequently made to the group in Active Directory (such as new members added or old members removed) will immediately be reflected in RC-E.

  • Page 147: Manage Roles

    You are now able to assign users/groups to the role, and to specify which of RC-E’s features they should be able to access. See Assign and Remove Users & Groups to/from a Role (see "Assign and Remove Users and Groups to/from Roles"...
  • Page 148 RC-E User Manual Management Client (RC-E Manager) Copying a Role If you have a role with complicated settings and/or rights and need a similar—or almost similar—role, it might be easier to copy the already existing role and make minor adjustments to the copy than to creating a new role from scratch.
  • Page 149 RC-E User Manual Management Client (RC-E Manager) Click OK. Viewing Effective Roles With the Effective Roles feature, you are able to view all roles (see "About Roles" on page 145) of a selected user or group (see "Manage Users and Groups" on page 145). This ability is especially convenient if you are using groups; in fact it is the only way of viewing the roles of individual group members.
  • Page 150 RC-E User Manual Management Client (RC-E Manager) Removing Users and Groups from a Role Tip: To find out which roles user, groups, or individual group members have, use the Effective Roles (see "Manage Roles" on page 147) feature. Keep in mind that a user may also have roles through group memberships. When that is the case, you cannot remove the individual user from the role.
  • Page 151 RC-E User Manual Management Client (RC-E Manager) Get sequences: ...the Sequences feature can be used when browsing recorded video from the selected camera(s) in access clients. Playback Video:...playing back of recorded video from the selected camera(s) will be possible in access clients.
  • Page 152 Security Manager will win the ability to control the camera. If your system is upgraded from an older version of RC-E, the old values (Very Low, Low, Medium, High and...
  • Page 153 Application Rights The Application tab lets you specify which applications in your RC-E system users/groups with the selected role should be able to use. Users must be a member of the Administrator role to have access to the Management Client.

  • Page 154: Manage View Groups

    162). NetMatrix Rights Specifying role rights on the NetMatrix tab is only relevant if you have configured NetMatrix recipients on your RC-E system. From the Ocularis Client it is possible to send video to selected NetMatrix recipients. The NetMatrix tab lets you specify which NetMatrix recipients should be selectable for this purpose in the Ocularis Client.
  • Page 155 RC-E User Manual Management Client (RC-E Manager)  In addition to the view groups that are created when roles are added, you are able to create as many other view groups as you require. You can also delete view groups which you do not want to use, including those automatically created when adding roles.

  • Page 156: System Dashboard

     Configuration Report: (see "About Configuration Report" on page 157) From here you can decide what to include in, and print, RC-E system configuration reports. About System Monitor From the Site Navigation pane (see "Panes Overview" on page 36), expand System Dashboard, and click System Monitor.

  • Page 157: About Current Task

    About Configuration Report When creating RC-E pdf configuration reports, you can include any possible elements of your RC-E system which you want to see in the report. Examples of what can be included ranges from licenses over device to alarm configuration, and much more.

  • Page 158: Server Logs

    System Log records system-related information. OnSSI RC-E has a number of default settings related to the different logs, see Handling Log Settings (on page 161). Furthermore, you are able to view logs in a number of different languages, export them, and save the exported logs as tab delimited text (.txt) files at a location of your choice;...
  • Page 159 Management Client (RC-E Manager) Rule Log only: Type of equipment on which the logged incident occurred. Since log entries are administrator-defined and relate to incidents on the OnSSI RC-E system, source type will normally be System. Event and System Logs only: Type of equipment on which the logged incident occurred, for example Management Server or Device.
  • Page 160 RC-E User Manual Management Client (RC-E Manager) Navigating Log If a log contains more than one page of information, you are able to navigate between the log's pages by clicking the buttons in the bottom right corner of the log pane.
  • Page 161 Click Export to export the required log content to the required location. Handling Log Settings OnSSI RC-E has a number of default settings related to its logs. To verify or change these settings, do the following: Go to the Management Client's menu bar, and select Tools > Options...

  • Page 162: Rc-C

    RC-E’s Management Client to define roles with access to RC-C servers. Note that user names and passwords are case sensitive. You can also create a new user in RC-C, and assign the required user rights in RC-C, so they match the RC-E role. See the RC-C documentation for more information about creating new users in RC-C.
  • Page 163 Select the RC-C server to which you want to assign the role. Select a user with the RC-C user rights that represent the correct user rights for the RC-E role you are assigning it to. You can do this in two ways: In the Basic Authentication section, enter the user name and password for a user which is defined as basic authenticated user in RC-C.
  • Page 164 Remember to define the network configuration settings, so the RC-E management server will be able to handle the token authentication of clients for added RC-C servers. In the RC-E Management Client, you must add all RC-C servers you would like to receive data from. The RC-C system's internal master/slave setup cannot be reused by RC-E.

  • Page 165: Registered Services

    If all involved servers (both the OnSSI RC-E management server and the trusted servers or the required OnSSI RC-C) are on your local network, you can simply specify the LAN address. If one or more involved servers access the system through an internet connection, you must also specify the WAN address.

  • Page 166: Important Prerequisites When Running Federated Sites

    Important Prerequisites When Running Federated Sites The easiest way to make federated architecture work correctly is to prepare your RC-E system for this feature during installation. There are certain important prerequisites that you must ensure already at the time of installing your management server.
  • Page 167 Select to install the Management Server service using a common administrator account. Finish the installation. Repeat steps 1-4 to install any other RC-E systems you want to connect. They must all be installed using a common administrator account. See Adding a Site to the Hierarchy (see "Manage OnSSI Federated Architecture" on page 177) for details on how to proceed.

  • Page 168: Options

    RC-E User Manual Management Client (RC-E Manager) It is not possible to mix domain(s) and workgroup(s), i.e. connect sites from a domain to sites from a workgroup and vice versa. Options Options The Management Client's Options dialog lets you specify a number of settings related to the appearance of the application, to logging, to mail server configuration, etc.
  • Page 169 See Manage Logs (on page 158) for more information. Mail Server The Mail Server tab lets you specify settings for the outgoing SMTP mail server you are going to use with your RC-E system. See Outgoing SMTP Mail Server Settings (on page 171) for more information.

  • Page 170: Avi Compression Settings

    RC-E User Manual Management Client (RC-E Manager) User Settings The User Settings tab lets you specify settings for user preference, such as whether a message should be shown when edge recording is enabled. See Record tab Overview (on page 103) for more information.

  • Page 171: Outgoing Smtp Mail Server Settings

    Outgoing SMTP Mail Server Settings You are able to specify settings for the outgoing SMTP mail server you are going to use with your RC-E system. Specifying these settings is a prerequisite for using rule-triggered notification profiles (see "Manage Notification Profiles"...
  • Page 172 RC-E User Manual Management Client (RC-E Manager) In the Management Client's menu bar, select Tools > Options. This will open the Options dialog (see "Options" on page 168). Tip: You can also access the Options dialog from the Network tab; this can be handy if you are also configuring the public IP address of a recording server.

  • Page 173: Onssi Federated Architecture

    It is only relevant to speak of a parent/child setup for management servers—not for recording servers (see "The RC-E Server (Management Server)" on page 7). However, due to their relations to management servers, recording servers will automatically become part of the parent/child setup.

  • Page 174: Basic Rules Of Federated Sites

    In general, you must be an administrator to work with federated architecture. However, by requesting the adding of children to a top-site (to which you have administrator rights), you can (without administrator rights to the other sites) create the overall initial infrastructure of a federation. But, as described in Manage OnSSI On-Net Surveillance Systems, Inc.

  • Page 175: Possibilities And Constrains Of Federated Sites

    Frequently Asked Questions to Federated Sites What is a federated site? A federated site is basically just an individual RC-E system, complete with management server, SQL server, one or more recording server(s), failover server(s) and cameras. To make use of OnSSI Federated Architecture, you must connect at least two individual RC-E systems.
  • Page 176 Can I include RC-C slave(s) in my federated hierarchy? Yes, that is possible, but only as slave(s) to an RC-E management server. In this case, the relationship with the RC-C server will work as described in Manage RC-C Servers.

  • Page 177: Federated Sites Example Scenario-Limestone City

    OnSSI Federated Architecture Federated Sites Example Scenario—Limestone City The following is an example of how several RC-E systems can be integrated into a federated architecture-in this case in a City Surveillance scenario. Many surveillance integrators want to integrate several independent surveillance entities into a large scale system, where each site can still be used and managed locally and users and administrators can be given access to the entire large scale installation.

  • Page 178: Expand/Collapse

    The management server is installed as a Network Service: Before a parent/child link can be established without the acceptance from the administrator of the child, both computers involved (parent and child) must be added as a user to the other's RC-E administrator role. See Assign and Remove Users and Groups to/from Roles (on page 149).

  • Page 179: Accepting Inclusion In The Hierarchy

    If the management server is installed as a Network Service: Computers involved must not be added as users to each other's RC-E administrator role, but should be added as another RC-E non-administrator role. See Assign and Remove Users and Groups to/from Roles (on page 149).

  • Page 180: Connecting To Another Site In The Hierarchy

     The management server is installed as a Network Service: Both computers involved must be added as users to each other's RC-E administrator role. See Assign and Remove Users and Groups to/from Roles (on page 149).  The management server is installed as a user account: This user account must be a member of the administrator group of the server being linked to.

  • Page 181: Refreshing The Site Hierarchy

    RC-E User Manual OnSSI Federated Architecture Your home-site must be the child of another site, i.e. have a parent. To Detach Home-site from a Parent Hierarchy 1. In the Management Client window, in the Federated Sites Hierarchy pane (see "Panes Overview" on page 36), right-click the home-site, and click Detach Site from Hierarchy.
  • Page 182 RC-E User Manual OnSSI Federated Architecture In the Management Client, in the Federated Sites Hierarchy pane (see "Panes Overview" on page 36), select the relevant site, right-click, and select Properties. If needed, change the following: General Tab Information related to the site you are currently connected to: ...

  • Page 183: Backup, Restore And Move System Configuration

    Flushing the SQL Server Transaction Log What Is the SQL Server Transaction Log and Why Does It Need to Be Flushed? Each time a change in the RC-E data occurs, the SQL Server will log this change in its transaction log - regardless whether it is a SQL Server on your network or a SQL Server Express edition.

  • Page 184: Backing Up Log Server Database

    Handle the SurveillanceLogServer database using the same method as when handling system configuration described earlier in this topic. The SurveillanceLogServer database (name may be different if you renamed the system configuration database) contains all your OnSSI RC-E system logs, including errors reported by recording servers and cameras.

  • Page 185: Manual Backup & Restore Of System Configuration

    The type of backup described in this topic is best suited if you have a smaller RC-E setup and wish to do a one-time, non-scheduled backup. Besides manual backups, it is strongly recommended to also configure regular, scheduled system backups (see "Scheduled Backup &...

  • Page 186: Restoring System Configuration (From Manual Back Up)

    Backup, Restore and Move System Configuration Backing up: All relevant RC-E configuration files will be combined into one single .cnf file, which is saved at a specified location. From the Management Client's menu bar, select File, Backup Configuration..Next, you are presented with an important note. Read the contents of the note. Click Backup.
  • Page 187  Your initial license (.lic) file, i.e. the one you used when initially installing RC-E , not the .lic file which is the result of your license activation (see "Activate Licenses" on page 43). License activation is, among other things, based on the specific hardware on which the activation took place;...

  • Page 188: Copying System Configuration From Old Server (Step 1)

    Since first part of a copy is in reality identical to a scheduled backup, see Scheduled Back Up of RC-E System Configuration section (see "Scheduled Backup & Restore of System Configuration" on page 183), steps 1-3.

  • Page 189: Installing New Management Server On New Server (Step 2)

    This should all be done to the new management server. Since second part of a copy is in reality identical to a restore, see Restoring RC-E System Configuration (From Scheduled Back Up) (see "Restoring System Configuration (From Manual Back Up)" on page 186), steps 1-2 and rest of the topic for details.

  • Page 190: Device Drivers

    Manage and Remove Video Device Drivers Video device drivers are small programs used for controlling/communicating with the camera devices connected to a recording server. The video device drivers should therefore be installed on each recording server on your RC-E system.

  • Page 191: Failover Servers

    Changing the Management Server Address The failover server must be able to communicate with your RC-E system's management server. You therefore specify the IP address/hostname of the management server during the installation of the failover server. Should you later need to change the address of the management server, you do it the following way: In order to be able to change the management server address, the Failover Server service must be stopped.

  • Page 192: Viewing Version Information

    During installation of the failover server, you specified a user account under which the Failover Server Service should run. For the failover server to work, it is important that the user account in question has access to your OnSSI RC-E system with administrator rights.

  • Page 193: Installing Failover Servers

    Tip: If a failover server does not become visible in the Management Client, verify that the failover server has been configured with the correct IP address/hostname of the management server. Also verify that the user account under which the Failover Server Service runs has access to your RC-E system with administrator rights. Failover Servers Are Grouped Failover servers are always grouped;...

  • Page 194: Enabling Failover Servers

    RC-E User Manual Failover Servers Tip: Alternatively, drag and drop failover servers between the two boxes. When ready, click OK. The required failover servers now belong to the group. A failover server can only be a member of one group at a time.

  • Page 195: Assigning Failover Servers To Recording Servers

    RC-E User Manual Failover Servers On the Network tab, you are able to define the failover server's public IP address, etc. This is relevant especially if using NAT (Network Address Translation) and port forwarding. See the description of a regular recording server's Network tab (see "Manage Public Addresses"...

  • Page 196: Failover-Related Events

    Failover-Related Events OnSSI RC-E features two failover-related events, Failover Started and Failover Stopped, which you can use when creating rules (see "Manage Rules" on page 133). The two events are further described in the Events Overview (on page 128).

  • Page 197: Database Corruption

    RC-E User Manual Database Corruption Database Corruption Protect Databases from Corruption If a recording server's databases become corrupted, the recording server is in many cases able to repair the corrupt databases. While the ability to repair corrupt databases is highly valuable, it is of course even better to take steps to...

  • Page 198: Services Administration

    While the recording server service is stopped, RC-E will not be able to interact with devices connected to the recording server. Consequently, no live viewing or recording will be possible. While the management server service is stopped, you will not be able to use the RC-E Management Client at all. See Accessing the Server Service (on page 198).

  • Page 199: Changing Recording Server Settings

    In order to be able to change settings, the Recording Server Service must be stopped. While the Recording Server Service is stopped, RC-E will not be able to interact with devices connected to the recording server. Consequently, no live viewing or recording will be possible.

  • Page 200: Virus Scanning

    RC-E User Manual Virus Scanning Virus Scanning Virus Scanning Information Virus scanning should in some cases be avoided—if allowed in your organization. If you use virus scanning software on:  recording data in databases on recording servers  data being archived in archiving (see "About Storage and Archiving" on page 56) locations it will most likely use a considerable amount of system resources on scanning.

  • Page 201: Snmp

    OnSSI RC-E will act as an SNMP agent, which can generate an SNMP trap as a result of a triggered rule. A third party SNMP management console can then receive information about the rule-triggering event, and operators of the SNMP management console can configure their system for further action as required.

  • Page 202: Daylight Saving Time

    OnSSI RC-E uses Coordinated Universal Time (UTC), which is the official world reference for time. UTC is not adjusted to reflect switches either to or from DST. Since RC-E uses UTC, no RC-E recordings are ever stored with the same timestamp twice, not even during the DST change hour.

  • Page 203: Contact Information

    RC-E User Manual Contact Information Contact Information On-Net Surveillance Systems (OnSSI) One Blue Plaza 7th Floor P.O. Box 1555 Pearl River, NY 10965 Website: www.onssi.com General: info@onssi.com 845.732.7900 Fax: 845.732.7999 Sales Support: sales@onssi.com 845.732.7900 x 1 PreSales Support salesengineering@onssi.com 845.732.7900 x 2 Technical Support: support@onssi.com...

Table of Contents