P2000 DVR/VMS Integration Manual€¦ · 02/10/2002 · 7.0 6.14 7.0 N/A Aimetis Symphony™ 6.13 6.14 7.0 6.14 7.0 Version 6.x only: Do not install the Aimetis client on the same

24-10832-62 Revision EDecember 2017

DVR/VMS integration

P2000Security Management System

version 3.14 SP5

Copyright 2017Johnson Controls

All Rights Reserved

No part of this document may be reproduced without the prior permission of Johnson Controls.

If this document is translated from the original English version by Johnson Controls, all reasonable endeavors will be used to ensure the accuracy of translation. Johnson Controls shall not be liable for any translation errors contained herein or for incidental or consequential damages in connection with the furnishing or use of this translated material.

Due to continuous development of our products, the information in this document is subject to change without notice. Johnson Controls shall not be liable for errors contained herein or for incidental or consequential damages in connection with furnishing or use of this material. Contents of this publication may be preliminary and/or may be changed at any time without any obligation to notify anyone of such revision or change, and shall not be regarded as a warranty.

Other Manufacturer’s Documentation

Johnson Controls does not duplicate documentation of other equipment manufacturers. When necessary, Johnson Controls provides documentation that supplements that of other manufacturers. When unpacking your equipment, keep all original manufacturer documentation for reference.

Technical Support

For factory technical support, Johnson Controls authorized field technicians or authorized dealer representatives can contact Global Security Solutions Technical Support by phone at (866) 893-0423 or (414) 524-1214, or by email at [email protected]. They can also call the Field Support Center at (800) 524-1330 or (414) 524-5000 and use options 6, 1, 7.

End users and customers should contact their local Johnson Controls branch or authorized dealer for any of their support needs (technical support, maintenance contracts, on-site field support, P2000 Software Service Agreements, Service Partnerships, and so on). Visit http://www.johnsoncontrols.com/location-finder to find your local Johnson Controls office.

For material returns contact the branch if the material was purchased through a Johnson Controls branch or through the Product Sales Operations Team, if ordered through the Advanced Order Management System (AOMS) and follow the RMA process; or contact the authorized dealer representative where the material was purchased directly.

Acknowledgment

Metasys® and Johnson Controls® are trademarks of Johnson Controls. All other company and product names are trademarks or registered trademarks of their respective owners.

mailto:[email protected]

http://www.johnsoncontrols.com/location-finder

DVR/VMS Integration Table of Contents

TABLE OF CONTENTS

24-10832-62 Rev. E

Chapter 1: Introduction

About This Guide 1-1

Guide Summary 1-2

Note on Other Manufacturers’ Documentation 1-2

Manual Conventions 1-2

Important Installation Notes 1-3

Hardware Requirements 1-3

Supported Protocols 1-4

Digital Video Integration Components 1-5

Defining System Hardware for the Digital Video Integration 1-6

Namespace and Database 1-6

Relationship Between the Namespace and Database 1-7

Naming Conventions 1-7

Naming Items for the AV Server Namespace 1-7

Defining the Number of Namespace Items 1-9

Chapter 2: Protocol Integration Details

Johnson Controls P2000 VMS 2-2

Supported Features 2-2

P2000 VMS Client Download and Installation 2-3

P2000 VMS Version 7.x Configuration Notes 2-10

P2000 VMS Version 6.x Configuration Notes 2-14

Aimetis Symphony 2-19


Aimetis Client Download and Installation 2-20

Aimetis Version 7.x Configuration Notes 2-20

Aimetis Version 6.x Configuration Notes 2-25

Avigilon Control Center 2-30


Configuration Notes 2-31

i

DVR/VMS Integration Table of Contents24-10832-62 Rev. E

Genetec Omnicast 2-33



Genetec Security Center 2-43



Milestone 2-66



Chapter 3: DVR/VMS Configuration

Configuration Overview 3-1

Using the CCTV/AV Configuration Window 3-2

Configuring DVR/VMS Components 3-3

General Configuration Notes 3-3

CCTV Server 3-4

AV Switches 3-6

Cameras 3-15

Camera Presets 3-22

Monitors 3-24

Dry Contact 3-26

Alarm Options for DVR/VMS Integration Components 3-30

Chapter 4: DVR/VMS Operation

Using the P2000 Software Functions 4-1

DVR/VMS Event Actions 4-2

Displaying DVR/VMS Items in the Real Time Map 4-5

Associating Cameras to Input Points or Terminals 4-8

Launching the AV Player 4-10

Launching the AV Player from the Real Time List 4-11

Launching the AV Player from the Real Time Map 4-12

Launching the AV Player from the Alarm Monitor 4-13

Launching the AV Player from the Options Menu 4-14

ii


AV Player Components and Functions 4-14

Main Menu 4-15

Video Player 4-16

AV Player Functions 4-17

Viewing Modes 4-18

Live Video Monitoring 4-19

Monitor Selection 4-20

Video Search and Retrieval 4-21

PTZ and Presets Control 4-22

Troubleshooting P2000 AV Player 4-24

Appendix A: Namespace Definitions

Flags A-1

DVR/VMS Namespace Tags A-2

DVR/VMS Channel Namespace Tags A-5

iii


iv

DVR/VMS Integration Introduction24-10832-62 Rev. E

1. INTRODUCTION

The P2000 software provides seamless integration with approved Digital Video Recorders (DVRs) or Video Management Systems (VMS). The integration allows authorized users to manage camera functions from a single P2000 workstation, and to tie an event generated in the P2000 system to a live audio-visual (AV) recording. Depending on the digital video equipment used at the site, the P2000 software also enables users to search, retrieve, and download real-time or archived AV recordings from any transaction or surveillance camera from any place and at any time.

You can recall audio-visual files by a variety of query options, including date and time, alarm events, camera ID, or DVR ID. Live video and audio playback options are available from the Alarm Monitor, Real Time List, and Real Time Map.

The digital video system communicates with the P2000 server through a TCP/IP connection. The P2000 CCTV Server, a software component installed automatically with the Digital Video option, provides communication.

Additionally, you can configure the digital video integration feature with a CCTV Switch for added control of the CCTV cameras and monitors.

NOTE: For information specific to the P2000 VMS integration with P2000 Web UI, refer to the documentation provided with the P2000 Web UI.

ABOUT THIS GUIDE

This guide covers the P2000 Security Management System (SMS) integration with supported digital video systems. Use this guide as a supplement to the P2000 documentation. For the most up-to-date version of this guide, refer to the QuickLIT website at:

http://cgproducts.johnsoncontrols.com/default.aspx?topframe.aspx&0

1-1

http://cgproducts.johnsoncontrols.com/default.aspx?topframe.aspx&0


GUIDE SUMMARY

This guide covers the following information:

• Chapter 1: Introduction defines the conventions used throughout the manual, lists the hardware requirements and supported protocols, and describes the digital video system components.

• Chapter 2: Protocol Integration Details offers protocol-specific lists of supported features as well as configuration and operation details.

• Chapter 3: DVR/VMS Configuration describes common steps required to define the components of the digital video integration in the P2000 system.

• Chapter 4: DVR/VMS Operation provides information on using the DVN/VMS integration, including detailed information about the Audio/Visual (AV) Player.

• Appendix A: Namespace Definitions contains information about the namespace tags and flags used in the digital video system.

NOTE: Depending on the software version you are using, the screen captures in this manual may differ slightly.

NOTE ON OTHER MANUFACTURERS’ DOCUMENTATION

Johnson Controls® does not duplicate documentation of other equipment manufacturers. When necessary, as in some installation procedures, we provide documentation that supplements other manufacturer’s documentation. When unpacking the equipment, keep all original manufacturer documentation for future reference.

MANUAL CONVENTIONS

The following items used throughout this manual indicate special circumstances, exceptions, important points regarding the equipment or personal safety, or emphasize a particular point.

NOTE: Notes indicate important points or exceptions to the information provided in the main text.

1-2

DVR/VMS Integration Introduction
24-10832-62 Rev. E
IMPORTANT: Important messages remind you that certain actions, if not performed exactly as stated, may cause damage to equipment or make your system non-operational.

IMPORTANT INSTALLATION NOTES

Do not install the third-party vendor’s workstation or server software on the P2000 server. In addition, we recommend that you do not install the third-party digital video client software and the P2000 workstation software on the same machine unless required.

The Export file and Snap shot features require time synchronization between the digital video system and the P2000 workstation running the AV Player. In addition to that, on P2000 workstations using Windows Server 2008 or Windows 7 you must manually create an AVData directory at the following location:

\Program Files (x86)\Johnson Controls\P2000\AVData

The user running the AV Player must have full permissions for this folder. Refer to the Windows documentation for instructions on setting user permissions.

HARDWARE REQUIREMENTS

To operate the digital video feature in the P2000 system, both the P2000 server and the P2000 workstation require video cards compliant with Microsoft® DirectX® 9.0. The following chip sets and boards are certified:

• Intel® 82845 G/GL/GV

• NVIDIA® (all chip sets)

• ATI® Radeon™

If a graphic card is not compliant with DirectX 9.0, then the CCTV Service and AV Player does not function properly.

Consult with the digital video system vendor for other detailed hardware requirements.

NOTE: You cannot use virtual machines for AV players.

1-3


SUPPORTED PROTOCOLS

The P2000 digital video integration supports the following protocols, original equipment manufacturer (OEM) software versions, and software development kits (SDKs).

You may only use one version of each protocol within a P2000 system.

Table 1-1: Supported Digital Video Protocols

Vendor/Protocol*OEM Software Version

SDK Version

Notes

Johnson Controls® P2000 VMS

6.136.147.0

6.14

7.0

N/A

Aimetis Symphony™ 6.136.147.0

6.14

7.0

Version 6.x only: Do not install the Aimetis client on the same machine as the P2000 Server or P2000 Workstation.

Avigilon Control Center™ Enterprise Edition and Standard Edition

5.0 5.0 N/A

Genetec™ Omnicast™

4.8 4.8 N/A

Genetec Security Center

5.4 5.4 Supported server operating systems: Windows Server 2012 R2.

Supported workstation operating systems: Windows 7 (64 bit), Windows 8.1.

.Net framework 4.5.1, must be installed on the P2000 server machine. It is not required on the P2000 workstations.

Milestone XProtect® 2014 Corporate

7.0d MIP 10.02.02

N/A

Milestone XProtect 2014 Enterprise

8.6d MIP 10.02.02

N/A

Milestone XProtect 2014 Professional

8.6d MIP 10.02.02

N/A

Milestone XProtect 2016 R3 Corporate

10.2b MIP 10.02.02

N/A

1-4


* The P2000 software contains software produced and copyrighted by the following third-party manufacturers: Genetec, and Milestone.

Feature availability in the P2000 system depends on the set of features provided by the manufacturer’s integration software. See Chapter 2: Protocol Integration Details.

DIGITAL VIDEO INTEGRATION COMPONENTS

Components that operate within the DVR/VMS integration include the following:

• CCTV Server – A component that provides communication with the DVR/VMS hardware. CCTV Server is responsible for sending commands from the P2000 system to the DVR/VMS system using the P2000 event action functions.

• AV Server – A component that provides communication with the DVR/VMS hardware and is responsible for receiving alarms from the DVR/VMS system, as well as automatically forwarding P2000 alarms to the digital video system (provided you have configured the Input to Camera or Terminal to Camera mapping).

• AV Switch – A component that defines general system information about the DVR/VMS hardware, and about the monitors and cameras connected to it. You must define at least one AV Switch for each configured CCTV Server.

• Monitors – A component defined for a particular AV Switch.

• Cameras – A component defined for a particular AV Switch. You may also configure the presets that are available for a particular camera.

• Dry Contacts – Two-state (open/closed) input points defined for a particular AV Switch.

Milestone XProtect 2016 R3 Expert

10.2b MIP 10.02.02

N/A

Milestone XProtect 2016 R3 Professional

10.2a MIP 10.02.02

N/A

Vendor/Protocol*OEM Software Version

SDK Version

Notes

1-5


NOTE: Matrix operations, such as presets and monitors, may require additional components (such as a compatible video matrix switch) controlled by the P2000 system’s CCTV feature.

DEFINING SYSTEM HARDWARE FOR THE DIGITAL VIDEO INTEGRATION

Once you have configured the CCTV Server and the AV Switch, and the cameras, monitors, and dry contacts are connected to the configured addresses, you do not need to configure any other equipment. The AV Switch configuration contains the necessary global configuration information for the hardware components connected to it.

However, you may want to specifically define the operation of a piece of equipment. For example, you may have one fixed camera, so you do not want to enable the move functions for the operator when running AV Player. In this case, set up and configure a named camera. Any functions expressly defined for the named camera override the global camera information in the AV Switch configuration.

Similarly, the camera configuration defines global information about the camera presets, including the number of presets to be generated in the namespace. For example, if the camera definition generates 20 presets, then the 20 presets exist in the namespace tagged with the namespace name. However, to specify a name for the presets, you must specifically set up and define each preset in the CCTV/AV Configuration window.

Namespace and Database

When you define the CCTV Server, AV Switch, and other items in the CCTV/AV Configuration window (except for Dry Contacts), the software creates a database table for each item, and also creates a valid entry for the AV Switch in the AV Server namespace. If the system uses the default settings for the digital video protocol, it adds as many entries to the namespace as there are default items, but does not create database tables for these items until one of the them has been specifically created, configured, and saved. For example, if you specifically create a preset, the system creates a record that contains information about the named preset. When you create the preset, you allocate it a number that the software uses to create the namespace name (OPC name) for the preset. The system updates the namespace entry from any information in the database the next time the CCTV Server is started.

1-6


Relationship Between the Namespace and Database

The following figure summarizes how the various system activities relate to the namespace and database.

Naming Conventions

When a digital video system has a large number of components, we recommend naming them with a consistent naming convention. For example, you can assign name to a camera and include the AV Switch name (OfficeCam1), camera location (Floor 4), or the area of its view (West Car Park). The P2000 system adds these names to the database. Using meaningful names helps the system operators.

The system automatically assigns AV Server namespace names using the number assigned to the item when manually or automatically configured.

Naming Items for the AV Server Namespace

Each of the items that you define specifically in the CCTV/AV Configuration window (except for dry contacts) is automatically allocated an identifying name that the CCTV Server recognizes. The name comprises the number of the item and a fixed description. In the case of cameras and monitors, the number is the physical address to which the equipment is wired at the AV Switch; in the case of other AV Switch elements, the address is a logical address that the CCTV Server can recognize. The digital video system’s software automatically assigns a fixed description when the item number is added to the CCTV/AV Configuration window.

Digital VideoConfiguration

AV PlayerConfiguration

EventActions

DVR/VMS Equipment

NamespaceDatabase

1-7


NOTE: The system initializes the AV Server namespace for the CCTV Server from the P2000 database each time the CCTV Server is started. If the CCTV Server cannot find the P2000 database, then the namespace is initialized from a local copy. However, the local copy was created when the P2000 database was last read, so it may not be up to date.

The system automatically tags the item name with an inherent name. For example, a preset is recognized by its AV Switch, Camera, and Preset name; presets created for different cameras can have the same number, but have a different namespace name.

When you create records in the CCTV/AV Configuration window, you need to enter a number for the address of the item that you are adding. Each number is prefixed by one or two letters. The following table shows the prefix letters and the range of numbers permitted for each item.

Table 1-2: Permitted Prefix Letters and Number Ranges

The DVR/VMS system determines the number of items. In addition, if the system is configured with the CCTV advanced feature and a CCTV switch, the capacity of the switch determines the number of cameras and monitors.

The CCTV/AV Configuration window automatically inserts the prefix letters for the item.

The user selects the number. Follow these rules:

• AV switches must be numbered consecutively starting from AV0001.

• In certain video management systems, the number for cameras and monitors must match the hardware address at the AV switch. Other video management systems (for example, Milestone MIP) may require the name to match. The system does not automatically check

Namespace Item Parent Item Prefix Range

Switch Server AV 1 to 9999

Monitor Switch M 1 to 9999

Camera Switch C 1 to 9999

Camera Presets SwitchCamera Pr 1 to 9999

1-8


whether the number is correct. Where a large number of monitors and cameras is installed, we recommend that the installing engineer develop a plan for the addressing process, so that the correct numbers can be entered into the CCTV/AV Configuration window.

Additional recommendations are as follows:

• Connect cameras and monitors to the low-numbered addresses at the AV switch in order to keep the number of AV Server namespace entries as small as possible.

• For easier operations, define the most frequently used equipment with numbers that appear in the AV Player window; at is: AV0001 to AV0006 for AV switches, M0001 to M0020 for monitors, and C0001 to C0040 for cameras.

NOTE: The CCTV Server system uses intrinsic addressing, so we recommend that you do not change the address of the items once they have been configured. If you do, you may find that actions that use intrinsic addressing (for example, OPCWrite event actions) refer to a different item.

Defining the Number of Namespace Items

When you create and configure items for the CCTV Server, you must assign a number to each item in the namespace. The range of numbers permitted is dependent on the number of items configured for the namespace.

A feature of the software allows the namespace items to be configured automatically. You can decide whether the total number of items in the namespace is based on the default number of names defined by the digital video system you are using, or whether it is based on a specific user-defined number.

Automatic configuration of the namespace items is useful for the initial software setup, allowing you to have a working system after just configuring a CCTV server and an AV switch with the digital video system defaults, and connecting the cameras and monitors to a valid address at the AV switch.

1-9


1-10

DVR/VMS Integration Protocol Integration Details24-10832-62 Rev. E

2. PROTOCOL INTEGRATION DETAILS

This chapter provides information specific to integration with particular video protocols. It contains only some of the protocol-specific information, as available at the time of this publication. Refer to the DVR’s or VMS’s manufacturer documentation for further documentation and guidance.

Each section is divided into “Supported Features” and “Configuration Notes.” You should review the “Configuration Notes” section for your protocol prior to installing the integration components on the P2000 system.

• Johnson Controls P2000 VMS on page 2-2

• Aimetis Symphony on page 2-19

• Avigilon Control Center on page 2-30

• Genetec Omnicast on page 2-33

• Genetec Security Center on page 2-43

• Milestone on page 2-66

The following information applies to all DVR/VMS integrations:

• After making any changes to the configuration of the DVR/VMS, you should stop and restart the AV Service and the CCTV Server using the P2000 Service Control tool.

• At times, you may have to manually stop and restart the P2000 service for a particular video protocol. In such cases, cycle the P2000 AV Service immediately afterwards to ensure that alarms are monitored.

• The DVR/VMS-related messages are sent to the Real Time List only when the P2000 AV Service is running.

2-1

DVR/VMS Integration Protocol Integration Details: P2000 VMS24-10832-62 Rev. E

JOHNSON CONTROLS P2000 VMS

Supported Features

FeatureSupport

Version 6.x Version 7.x

AV Actions for P2000 Events

Camera Complete Alarm

Camera Complete Alarm Associated Input

Camera Complete Alarm Associated Terminal

Camera Preset Yes Yes

Camera Recording Quality

Camera Send Alarm

Camera Send Alarm Associated Input

Camera Send Alarm Associated Terminal

Camera Start Recording Yes Yes

Camera Start Recording and Archiving

Camera Start Recording Associated Input Yes Yes

Camera Start Recording Associated Terminal Yes Yes

Camera Stop Recording Yes Yes

Camera Stop Recording Associated Input Yes Yes

Camera Stop Recording Associated Terminal Yes Yes

Launch AV Player Yes* Yes**

Monitor Camera

AV Alarm Subscriptions

Motion Alarm Yes Yes

Behavior alarm

Dry contact alarm

DVR system alarms

Video loss alarm Yes Yes

AV Player Actions

Call up live video Yes Yes

Retrieve video Yes Yes

PTZ control Yes Yes

Capture video Yes

Capture image Yes Yes

2-2


* Version 6.x uses a P2000 VMS Viewer instead of the AV Player. See P2000 VMS Version 6.x Configuration Notes on page 2-14 for more information.

** Version 7.x uses the Video Viewer provided by the P2000 VMS 7.0 Client. See P2000 VMS Version 7.x Configuration Notes on page 2-10 for more information.

P2000 VMS Client Download and Installation

All DVR/VMS integrations with P2000 SMS require appropriate codecs, which are installed on the P2000 server and workstations during the P2000 software installation. The P2000 VMS integrations, however, require an additional component, called the P2000 VMS Client to be installed after the P2000 software and codecs installations are complete.

This client software may be delivered to the computer during the P2000 software installation, or may be available as a download. See the following sections for instructions on how to obtain and install the P2000 VMS Client software.

NOTE: For the P2000 Web UI, there are additional requirements. If you are using the P2000 Web UI, install the P2000 VMS Client on the P2000 server and on the P2000 workstations, and then refer to the P2000 Web UI Installation Guide for instructions.

P2000 VMS Version 7.x

The P2000 VMS Version 7.x Client software is available for download from:

http://xnet.johnsoncontrols.com

You will need login credentials to access the file. To obtain Username and Password, contact your Johnson Controls representative.

P2000 VMS Version 6.x

The P2000 VMS Version 6.x Client software is available for download from:


You will need login credentials to access the file. To obtain Username and Password, contact your Johnson Controls representative.

2-3




Download Instructions

Download instructions are very similar for both client versions; use the steps below for general guidance.

To download the latest P2000 VMS Client:

1. Go to http://xnet.johnsoncontrols.com.

2. Enter your credentials and click Log In.

3. The window opens with the Account Management tab active.

4. Click the Downloads tab and then Downloads on the left window pane.

2-4

http://xnet.johnsoncontrols.com/Xnet/Login.aspx


5. A list of available downloads is displayed. Locate and download the client installer.

The same P2000 VMS Client installer is used on the P2000 server and workstations.

Installation Instructions

Installation instructions are very similar for both client versions; use the steps below for general guidance.

To install P2000 VMS Client:

1. Launch the P2000 VMS Client installer.

2. The Install Shield opens. Select the installation language and click OK.

2-5


3. The installer checks what prerequisites are present. Missing prerequisites are identified and listed. Click Install to proceed.

4. Click Yes to reboot.

5. After the restart, select the installation language and click OK.

2-6


6. Accept the license agreement and click Next.

2-7


7. In the Install Johnson Controls Remote Support Tool window accept the default selection by clicking Next.

8. In the Destination Folder window accept the default selection by clicking Next.

2-8


9. In the Ready to Install the Program window click Install.

10. In the InstallShield Wizard completed window, clear Launch the program check box and click Finish.

2-9


P2000 VMS Version 7.x Configuration Notes

The following notes apply to the P2000 system integration with P2000 VMS Version7.x:

• The P2000 VMS integration requires Enterprise camera licenses.

• For the P2000 VMS integration to function properly, the P2000 VMS Client must be installed on the P2000 server as well as on the P2000 workstations. You also must log in to the P2000 VMS Client at least once.

• The P2000 VMS Client must be running in order to display live or recorded video.

• P2000 VMS Version 7.x uses the P2000 Aimetis 7 Interface Service.

• Integration with this protocol supports (but does not require) Active Directory (AD) authentication. For Active Directory instructions with AD authentication, see P2000 VMS Version 7.x Active Directory (AD) Authentication on page 2-10.

• Camera video requests from the P2000 core and Web UI for live or recorded video are displayed in a video viewer application which is part of the P2000 VMS 7.0x Client. See P2000 VMS Version 7.x Video Viewer Application on page 2-13 for details.

• Motion Alarms and Video Loss alarms require configuration of motion tracking rules. This configuration is done from the P2000 VMS server; for detailed information refer to the documentation provided with the server.

• For P2000 Web UI, there are additional requirements. If you are using the P2000 Web UI, refer to the P2000 Web UI Installation Guide for information.

NOTE: After making changes to the P2000 VMS configuration, follow this sequence: stop the P2000 AV Service, then stop and restart the P2000 Aimetis 7 Interface Service, and then start the P2000 AV Service.

P2000 VMS Version 7.x Active Directory (AD) Authentication

Integration with P2000 VMS Version 7.x protocol allows Active Directory authentication to be used when the P2000 server connects to the P2000 VMS server. (Connection without Active Directory authentication is also supported.)

2-10


To use Active Directory authentication, you must configure it at the P2000 VMS server side as well as at the P2000 server:

• Configure P2000 VMS User Account for Active Directory Authentication on page 2-11

• Configure the P2000 Server Components for Active Directory Authentication on page 2-12.

NOTE: Use the following instructions as general guidelines; for detailed information refer to the manufacturer’s documentation.

Configure P2000 VMS User Account for Active Directory Authentication

To enable Active Directory Integration at the P2000 VMS Server:

1. Launch the Setup wizard.

2. Select Active Directory Integration under Security Mode section.

3. Provide the LDAP URL (a string encapsulating the address and port of a directory server).

4. Enter the P2000 VMS System administrator credentials and click Verify to verify the details provided.

5. Click on Apply to save the changes.

Next, the P2000 users who request live and recorded video need to be added to the P2000 VMS server using Security User Task in the Server Configuration Tool.

To add a new user to the Active Directory in the Aimetis system:

1. Open the Server Configuration Tool.

2. Enter the administrator login credentials.

3. Under the Security tab, select Users and click Add.

4. Enter the Username for Active Directory.

5. Fill out remaining fields and make selections as needed for your system.

2-11


6. Click on Check Active Directory to authenticate the user.

7. Click Save.

Configure the P2000 Server Components for Active Directory Authentication

For Active Directory authentication, start the P2000 Aimetis V7 Interface Service with the Active Directory account log on credentials. These credentials are used to connect the P2000 server to the P2000 VMS 7.x server through Active Directory authentication.

If you change Active Directory account, you must also update the log on credential for the P2000 Aimetis V7 Interface Service or you will not be able to run the service under PegasysServices account.

Use Active Directory log on credentials

2-12


To enable Active Directory authentication, in the Edit AV Switch widow, Audio-Visual tab, check Use AD Authentication (the Username field becomes disabled).

P2000 VMS Version 7.x Video Viewer Application

Camera video requests from the P2000 core and Web UI for live or recorded video are displayed in a video viewer application which is part of the P2000 VMS 7.0 Client.

NOTE: The P2000 VMS Version 7.x video viewer application is not installed by the P2000 software installer; it is part of the P2000 VMS Version 7.x Client. See P2000 VMS Client Download and Installation on page 2-3.

Video Viewer Operation

For all P2000 AV Player commands, a request to see camera video is sent automatically from the P2000 SMS to the P2000 VMS Version 7.x Client, and the video is displayed in the first tile of the video viewer where you are logged on. For every request made from the P2000 system, the P2000 VMS Version 7.x Client opens a new window for that camera.

Active Directory (AD) authentication

2-13


Note the following important rules:

• As the P2000 user, you have to manually start and log on to the P2000 VMS Version 7.x Client. The P2000 system will not start the client and video viewer automatically.

• The login user name for the P2000 VMS Version 7.x Client must be that same as the login user name for the P2000 SMS.

Integration with P2000 Core

P2000 Core application is able to request live or recorded video display from the P2000 VMS Version 7.x Client. Video can be requested from one camera at a time.

All video, live or recorded, requested from the P2000 Core user interface, displays in the first tile of the video viewer.

Integration with Web UI

P2000 Web UI is able to request video display from the P2000 VMS Version 7.x Client. P2000 Web UI can request P2000 VMS Version 7.x integration for both live and recorded video from multiple cameras.

For multiple camera requests from the Web UI, video display starts with Tile 1. Each additional camera is added to the next tile. If both live and recorded video are requested, the live video tile displays immediately before the recorded video tile for each requested camera.

P2000 VMS Version 6.x Configuration Notes

The following notes apply to the P2000 system integration with P2000 VMS:

• For the P2000 VMS integration to function properly, the P2000 VMS Client must be installed on the P2000 server as well as on the P2000 workstations.

• It is not required for the P2000 VMS Client to actually be running on the P2000 server or workstations.

• P2000 VMS uses the P2000 Aimetis Interface Service.

• If you use the auto-discovery feature, in order for alarms to be displayed correctly you must manually restart the AV Service and the P2000 Aimetis Interface Service after the P2000 system has auto-discovered all cameras and monitors.

• Auto-discovery of presets and dry contacts is not supported.

2-14


• Re-naming a camera in the P2000 VMS system does not change the name of that camera in the P2000 system; instead, it adds a new camera with that name. For proper functioning, when re-naming cameras, change the name both in P2000 VMS and in the P2000 system before any subsequent synchronization.

• Integration with this protocol uses a proprietary viewer application instead of the AV Player. That application does not provide an interface to start or stop recording, or to capture and export video.

• Motion Alarms require configuration of motion tracking area for each camera, and configuration of motion tracking rules. The motion tracking rules can be applied to multiple cameras.

• For the P2000 Web UI, there are additional requirements. If you are using the P2000 Web UI, refer to the P2000 Web UI Installation Guide for information.

• Video streaming is not supported on systems using Windows 10.

NOTE: After making changes to the P2000 VMS configuration, follow this sequence: stop the P2000 AV Service, then stop and restart the P2000 Aimetis Interface Service, and then start the P2000 AV Service.

Motion Tracking

Use the following instructions as general guidelines; for detailed information refer to the manufacturer’s documentation.

To define the motion tracking area:

1. In the Server Configuration window, select the camera you want to configure.

2. Under Analytics Engines, enable [Number] - Zero Configuration Motion Detection.

2-15


3. Under Analytics Configuration, draw the area for motion detection. Click OK.

To define motion tracking rules:

1. In the Server Configuration window, select Rules and click New.

Selected camera Analytics Engines tab

Motion tracking option

Analytics Configuration tab Draw tool

2-16


2. The Rule Wizard opens with steps 1–5 for creating rules. Under Instructions, click Next.

3. Under Event:

• Enter a name in Sub Events.

• Select the check boxes for the cameras that use this rule.

• Select [Number] - Zero Configuration Motion Detection from the video engines running on the camera.

• Draw the area for motion detection.

• Click Next.

Rules for motion tracking

Defining New rule

2-17


4. Under Action, select Raise Alarm and click Next.

5. Under Schedule, create or select a schedule, and click Next.

6. Under Summary, click Save.

Enable alarms to be raised

Example of a 24/7 rule enforcement

2-18

DVR/VMS Integration Protocol Integration Details: Aimetis Symphony24-10832-62 Rev. E

AIMETIS SYMPHONY

Supported Features

Feature

Support

Version 6.x Version 7.x







Camera Send Alarm










Launch AV Player Yes* Yes**

Monitor Camera


Motion Alarm Yes Yes

Behavior alarm

Dry contact alarm

DVR system alarms

Video loss alarm Yes Yes

AV Player Actions

Call up live video Yes Yes

Retrieve video Yes Yes

PTZ control Yes Yes

Capture video Yes


2-19


* Version 6.x uses a proprietary viewer application instead of the AV Player. See Aimetis Version 6.x Configuration Notes on page 2-25 for more information.

** Version 7.x uses Video Viewer provided by Aimetis. See Aimetis Version 7.x Configuration Notes on page 2-20 for more information.

Aimetis Client Download and Installation

All DVR/VMS integrations with P2000 SMS require appropriate codecs, which are installed on the P2000 server and workstations during the P2000 software installation. The Aimetis Version 7.x integration, however, requires an additional component, called the Aimetis Symphony 7.0 Client to be installed after the P2000 software and codecs installations are complete.

IMPORTANT: This component is not required by Aimetis Version 6.x.

The Aimetis Symphony Client software available for download from the manufacturer at the following location:

http://xnet.aimetis.com

To obtain Username and Password, contact your Johnson Controls representative.

For detailed download and installation instructions refer to the manufacturer’s documentation. The installation process is very similar to P2000 VMS client installation as described in Installation Instructions on page 2-5.

NOTE: For the P2000 Web UI, there are additional requirements. If you are using the P2000 Web UI, install the Aimetis Symphony Client on the P2000 server and on the P2000 workstations, and then refer to the P2000 Web UI Installation Guide for instructions.

Aimetis Version 7.x Configuration Notes

The following notes apply to the P2000 system integration with Aimetis:

• The Aimetis integration requires Enterprise camera licenses.

2-20


• For the Aimetis integration to function properly, the Aimetis Symphony Client must be installed on the P2000 server as well as on the P2000 workstations. You also must log in to the Aimetis Symphony Client at least once.

• It is not required for the Aimetis Symphony Client to actually be running on the P2000 server or workstations.

• Integration with Aimetis Version 7.x uses the P2000 Aimetis V7 Interface Service.

• Integration with this protocol supports (but does not require) Active Directory (AD) authentication. For Active Directory instructions with AD authentication, see Aimetis Version 7.x Active Directory (AD) Authentication on page 2-21.

• Camera video requests from the P2000 core and Web UI for live or recorded video are displayed in the Aimetis Video Viewer application. See Aimetis Version 7.x Video Viewer Application on page 2-24.

• Motion Alarms and Video Loss alarms require configuration of motion tracking rules. This configuration is done from the Aimetis Symphony server; for detailed information refer to the documentation provided with the server.

• Motion Alarms and Video Loss alarms require configuration of motion tracking rules. This configuration is done from the Aimetis Symphony server; for detailed information refer to the documentation provided with the server.

• For the P2000 Web UI, there are additional requirements. If you are using the P2000 Web UI, refer to the P2000 Web UI Installation Guide for information.

NOTE: After making changes to the Aimetis configuration, follow this sequence: stop the P2000 AV Service, then stop and restart the P2000 Aimetis 7 Interface Service, and then start the P2000 AV Service.

Aimetis Version 7.x Active Directory (AD) Authentication

This integration allows Active Directory authentication to be used when the P2000 server connects to the Aimetis Symphony server. (Connection without Active Directory authentication is also supported.)

2-21


To use Active Directory authentication, you must configure it at the Aimetis Symphony server side as well as at the P2000 server:

• Configure Aimetis User Account for Active Directory Authentication on page 2-22

• Configure the P2000 Server Components for Active Directory Authentication on page 2-23

NOTE: Use the following instructions as general guidelines; for detailed information refer to the manufacturer’s documentation.

Configure Aimetis User Account for Active Directory Authentication

To enable Active Directory Integration at the Aimetis Symphony server:

1. Open the Setup wizard.

2. Select Active Directory Integration under Security Mode section.

3. Provide the LDAP URL (a string encapsulating the address and port of a directory server).

4. Enter the Aimetis System administrator credentials and click Verify to verify the details provided .

5. Click on Apply to save the changes.

Next, the P2000 users who request live and recorded video need to be added to the Aimetis Symphony server using Security User Task in the Server Configuration Tool.

To add a new user to the Active Directory in the Aimetis system:

1. Open the Server Configuration Tool.

2. Enter the administrator login credentials.

3. Under the Security tab, select Users and click Add.

4. Enter the Username for Active Directory.

2-22


5. Fill out remaining fields and make selections as needed for your system.

6. Click on Check Active Directory to authenticate the user.

7. If the information is correct click Save.

Configure the P2000 Server Components for Active Directory Authentication

For Active Directory authentication, start the P2000 Aimetis V7 Interface Service with the Active Directory account log on credentials. These credentials are used to connect the P2000 server to the Aimetis Symphony server through Active Directory authentication.

If you change Active Directory account, you must also update the log on credential for the P2000 Aimetis V7 Interface Service or you will not be able to run the service under PegasysServices account.

Use Active Directory log on credentials

2-23


To enable Active Directory authentication, in the Edit AV Switch widow, Audio-Visual tab, check Use AD Authentication (the Username field becomes disabled).

Aimetis Version 7.x Video Viewer Application

Camera video requests from the P2000 core and Web UI for live or recorded video are displayed in a video viewer application which is part of the Aimetis Version 7.x Client.

NOTE: Aimetis Version 7.x video viewer application is not installed by the P2000 software installer; it is part of the Aimetis Version 7.x Client. See Aimetis Client Download and Installation on page 2-20.

Active Directory (AD) authentication

2-24



For all P2000 AV Player commands, a request to see camera video is sent automatically from the P2000 SMS to the Aimetis Version 7.x Client, and the video is displayed in the first tile of the video viewer where you are logged on. For every request made from the P2000 system, the Aimetis Version 7.x Client opens a new window for that camera.


• As the P2000 user, you have to manually start and log on to the Aimetis Version 7.x Client. The P2000 system will not start the client and video viewer automatically.

• The login user name for the Aimetis Version 7.x Client must be that same as the login user name for the P2000 SMS.


P2000 Core application is able to request live or recorded video display from the Aimetis Version 7.x Client. Video can be requested from one camera at a time.

All video, live or recorded, requested from the P2000 Core user interface, displays in the first tile of the video viewer.


P2000 Web UI is able to request video display from the Aimetis Version 7.x Client. P2000 Web UI can request Aimetis Version 7.x integration for both live and recorded video from multiple cameras.


Aimetis Version 6.x Configuration Notes

The following notes apply to the P2000 system integration with Aimetis:

• The Aimetis client cannot be installed on the same machine as a P2000 Server or a P2000 Workstation.

• If you use the auto-discovery feature, in order for alarms to be displayed correctly you must manually restart the AV Service and the Aimetis Interface Service after the P2000 system has auto-discovered all cameras and monitors.

2-25


• Auto-discovery of presets and dry contacts is not supported.

• Re-naming a camera in the Aimetis system does not change the name of that camera in the P2000 system; instead, it adds a new camera with that name. For proper functioning, when re-naming cameras, change the name both in Aimetis and in the P2000 system before any subsequent synchronization.

• Integration with this protocol uses a proprietary viewer application instead of the AV Player. That application does not provide an interface to start or stop recording, or to capture and export video.

• Motion Alarms require configuration of motion tracking area for each camera, and configuration of motion tracking rules. The motion tracking rules can be applied to multiple cameras. See Motion Tracking on page 2-15 for details.

• An artifact in the form of a black spot may appear in live view.

• Video streaming is not supported on systems using Windows 10.

NOTE: After making changes to the Aimetis configuration, follow this sequence: stop the P2000 AV Service, then stop and restart the P2000 Aimetis Interface Service, and then start the P2000 AV Service.

Motion Tracking

Use the following instructions as general guidelines; for detailed information refer to the manufacturer’s documentation.

To define the motion tracking area:

1. In the Server Configuration window, select the camera you want to configure.

2. Under Analytics Engines, enable VE250 – Motion Tracking.

2-26


3. Under Analytics Configuration, draw the area for motion detection. Click OK.

Selected camera Analytics Engines tab

Motion tracking option

Analytics Configuration tab Draw tool

2-27


To define motion tracking rules:

1. In the Server Configuration window, select Rules and click New.

2. The Rule Wizard opens with steps 1–5 for creating rules. Under Instructions, click Next.

3. Under Event:

• Enter a name in Sub Events.

• Select the check boxes for the cameras that use this rule.

• Select VE 250 - Motion Tracking from the video engines running on the camera.

• Draw the area for motion detection.

• Click Next.

Rules for motion tracking

Defining New rule

2-28


4. Under Action, select Raise Alarm and click Next.

5. Under Schedule, create or select a schedule, and click Next.

6. Under Summary, click Save.

Enable alarms to be raised

Example of a 24/7 rule enforcement

2-29

DVR/VMS Integration Protocol Integration Details: Avigilon Control Center24-10832-62 Rev. E

AVIGILON CONTROL CENTER

Supported Features

* Uses a proprietary viewer application instead of the AV Player.

** Requires a rule to be defined in the Avigilon™ system.

*** Video only (no audio).

Feature

Support

Enterprise Standard







Camera Send Alarm










Launch AV Player Yes* Yes*

Monitor Camera


Motion Alarm Yes**

Behavior alarm

Dry contact alarm

DVR system alarms Yes Yes

Video loss alarm Yes**

AV Player Actions

Call up live video Yes*** Yes***

Retrieve video Yes*** Yes***

PTZ control Yes Yes

Capture video Yes Yes


2-30


Configuration Notes

When you establish a connection with the Avigilon VMS, the P2000 system auto-discovers cameras and presets from the Avigilon system and populates their names in the P2000 configuration tables.

When you rename a camera and restart the P2000 services, the auto-discovery process adds the new camera name, but does not delete the old camera name. You must delete the old entry manually.

NOTE: For proper operation, you must synchronize time on the P2000 Server and the Avigilon Server.

The following Avigilon features are not supported in the P2000 integration:

• Recording Schedule template for recording during various set of days.

• Users and Access Groups to restrict the rights over the Avigilon DVR server and access or deny permission over a Camera.

• Ability to select the user groups to receive alarm notifications.

The following system alarms are not supported:

• DVR_Disconnected (triggered when the network cable is disconnected)

• DVR_Connected (triggered when the network cable is reconnected)

• OutOfDiskSpace (triggered when the Avigilon system runs low on storage space)

Additional notes:

• Motion alarm feature requires Avigilon Enterprise Edition; it is not supported in integration with Avigilon Standard Edition.

• The Avigilon Control Center (ACC) Server does not support naming the presets on cameras from vendors other than Avigilon. Therefore, the P2000 integration with Avigilon also does not support custom names for presets on cameras from these vendors. Such presets are named as numbers in the P2000 system.

• Avigilon DVR supports up to 20 presets for each camera. All of these potential presets, whether or not they are configured, are auto-discovered and appear in P2000 AV Switch configuration, as well as in the Avigilon viewer application.

• In the Avigilon viewer application, all P2000 users have access to the same cameras and presets, and share the same privilege level for camera commands.

2-31


• The alarms that occur on the Avigilon Server while the P2000 Server is down, while the integration-related P2000 services are stopped, or while the network connection is disrupted, are not transmitted to the P2000 system.

• The video loss alarms received by P2000 system may be 2 minutes delayed.

• Exporting video clips from he Avigilon viewer application takes approximately three times as long as the length of the video clip.

• If the duration of a video is more that 4 hours, you must export it directly from the Avigilon DVR using the native format (AVE). In such cases export from the Avigilon viewer application is not supported.

2-32

DVR/VMS Integration Protocol Integration Details: Genetec Omnicast24-10832-62 Rev. E

GENETEC OMNICAST

Supported Features

* See Configuration Notes on page 2-34 for additional information.

Feature Support





Camera Preset Yes


Camera Send Alarm Yes*

Camera Send Alarm Associated Input Yes*

Camera Send Alarm Associated Terminal Yes*

Camera Start Recording Yes


Camera Start Recording Associated Input Yes

Camera Start Recording Associated Terminal Yes

Camera Stop Recording Yes

Camera Stop Recording Associated Input Yes

Camera Stop Recording Associated Terminal Yes

Launch AV Player Yes

Monitor Camera Yes


Motion Alarm Yes

Behavior alarm Yes

Dry contact alarm Yes

DVR system alarms Yes

Video loss alarm Yes

AV Player Actions

Call up live video Yes

Retrieve video Yes

PTZ control Yes

Capture video

Capture image Yes

2-33


Configuration Notes

The following notes apply to the P2000 system integration with Genetec Omnicast:

• Before installing or reinstalling the P2000 software, you must manually uninstall any existing Genetec Omnicast software development kit (SDK).

• When you select the Genetec option during the P2000 software installation process, SDK 4.6 Server Release 1 is installed along with other necessary integration components. To install a newer version, first manually uninstall this SDK, and then install the appropriate SDK as provided by the vendor.

• For configuration, Genetec uses the Omnicast Server and the Omnicast Config Tool.

• Integrations with Genetec Omnicast and Genetec Security Center cannot be used together within the same P2000 SMS.

Defining Cameras

The Logical ID of the camera in the Genetec Logical View must match the number of the camera in the P2000 system. See the following example:

The Genetec Logical ID of the camera must match the number of the camera as defined in the P2000 system.

Logical View is selected

2-34


Defining Monitors

Defining monitors for integration with Genetec Omnicast requires you to specify:

• The number related the OPC Name

• Monitor ID

• Pane Number

OPC Name and Number

For the number related with OPC Name, enter a number between 1 and 9999. Genetec Omnicast does not use the OPC name and related number to reference the monitor. However, you must use a number that is unique for each monitor defined on this AV Switch.

Use a unique number for each monitor defined on this AV switch.

2-35


Monitor ID

The Monitor ID in the P2000 system must match the Logical ID of the monitor in the Genetec system. See the following example:

The Genetec Logical ID of the monitor must match the Monitor ID number as defined in the P2000 system.

2-36


Pane Number

The Pane Number in the P2000 system determines which tile in the Genetec Security Desk application will display the video. See the following example:

Pane Number determines Genetec Security Desk tile.

2-37


Defining Dry Contacts

In the Omnicast Server, dry contacts are called digital inputs.

The Logical ID of the digital input in the Genetec Physical View must match the Number of the dry contact in the P2000 system. See the following example:

Genetec Alarm Messages

The P2000 system can receive the following alarm types from Genetec:

• Motion

• Behavior

• Video Loss

• Dry Contact

These alarms must be defined in the Omnicast Config Tool.

Each alarm type has a Logical ID assigned to it. The Logical IDs in the P2000 system must match the Logical IDs defined under Genetec Alarm Management.

The Genetec Logical ID of the digital input must match the dry contact’s Number as defined in the P2000 system.

Physical View is selected

2-38


The default values for Logical IDs used in the P2000 system are listed in Table 2-2. In the rare cases when the value must be modified (for example, if a default value is already used by Genetec for a different type of alarm), see the procedure described in Changing Default Alarm Logical IDs on page 2-40.

Additionally, each camera defined on the Omnicast Server must have an action created to trigger an alarm. See Table 2-1 for some of the event types corresponding to P2000 alarms. For additional Omnicast event types, contact a Genetec representative.

Table 2-1: Corresponding P2000 Alarm Types and Genetec Event Types

P2000 Alarm Messages

The P2000 system can send P2000 Alarm messages to the Omnicast Server in the following format:

P2000 Alarm for camera ID <camera id>

The alarm must be defined in the Omnicast Config Tool.

As for other alarm types in Genetec integration with the P2000 system, the Logical IDs in the P2000 system must match the Logical IDs defined under Genetec Alarm Management. The default value for Logical ID used in the P2000 system is listed in Table 2-2. In the rare cases when the value must be modified (for example, if a default value is already used by Genetec for a different type of alarm), see the procedure described in Changing Default Alarm Logical IDs on page 2-40.

P2000 Alarm Types Genetec Event Types

Motion Motion on

Behavior Intrusion

Loitering

Tailgating

Video Loss Camera not archiving

RTP packets lost

Signal lost

Transmission lost

Dry Contact Digital input contact closing

Digital input contact opening

2-39


NOTE: The default display on the Omnicast Live Viewer shows the alarm, but does not show the text of the message as generated by the P2000 system. For information on how to change the Live Viewer settings in order to display messages created using the Genetec SDK, contact a Genetec representative.

Changing Default Alarm Logical IDs

In some instances, a Logical ID used by Genetec for a particular alarm type is different from the default Logical ID defined in the P2000 system. By editing the computer registry on the P2000 server, you can change the default P2000 settings.

In order to create a custom Logical ID, you need to create a new registry DWORD:

• The Value name of the DWORD must match the alarm type as listed in Table 2-2.

• The Value data of the DWORD becomes the custom Logical ID and must match the Genetec Logical ID.

Table 2-2: Alarm Type Logical IDs

NOTE: We highly recommend that you contact Johnson Controls for assistance before modifying default registry settings on the P2000 server.

Alarm Type Default Logical IDDWORD Value Name

DWORD Value Data (Custom Logical ID)1

1. Defined by user in the computer registry on the P2000 server.

Motion 201 MotionAlarm

Behavior 202 BehaviorAlarm

Video Loss 203 VideoLossAlarm

Dry Contact 204 TamperingAlarm

P2000 Alarm 1000 + camera ID number2

2. The Logical ID for P2000CameraAlarm depends on the offset value and the camera ID number. The LogicalID for the alarm is created by adding these two values. For example, if the default offset value of 1000 is used,camera 1 sends alarm with Logical ID 1001, camera 2 sends alarm with Logical ID 1002, and so on. The offsetvalue can be changed through the registry.

P2000CameraAlarm

2-40


The following illustration shows an example of correctly defined custom Logical ID.

Creating Custom Logical IDs

IMPORTANT: Procedures described in this section change the default settings through modifications to the registry and should only be performed by qualified professionals. In most cases the default settings are sufficient and the following procedures do not need to be performed.

Alarm Management is selected

Notice the following:

• The required DWORD Value name to define custom Logical ID for the Dry Contact alarm type is TamperingAlarm.

• The Genetec Logical ID matches the Value data for this alarm type as defined in the computer registry on the P2000 server.

2-41


To create custom Logical ID:

1. Launch regedt.exe to access and edit the registry.

2. Expand the tree and go to:

HKEY_LOCAL_MACHINE > Software > Johnson Controls > AV Vendor > Genetec

3. To create a registry new entry, from the main menu go to Edit > New > DWORD Value. The new registry entry appears on the right window pane. Enter the entry name and press the Enter key (see Table 2-2 for reference information).

In the following example, TamperingAlarm DWORD has been created.

4. Right-click the icon for the DWORD, and select Modify.

In the Edit DWORD Value window, select the Decimal radio button and enter the Logical ID for the alarm type in the Value data field.

5. Click OK.

6. Close the Registry Editor window.

2-42

DVR/VMS Integration Protocol Integration Details: Genetec Security Center24-10832-62 Rev. E

GENETEC SECURITY CENTER

Supported Features

** Launches Genetec Security Desk application instead of AV Player.

Feature Support





Camera Preset Yes


Camera Send Alarm Yes

Camera Send Alarm Associated Input Yes

Camera Send Alarm Associated Terminal Yes

Camera Start Recording Yes


Camera Start Recording Associated Input Yes

Camera Start Recording Associated Terminal Yes

Camera Stop Recording Yes

Camera Stop Recording Associated Input Yes

Camera Stop Recording Associated Terminal Yes

Launch AV Player Yes**

Monitor Camera Yes


Motion Alarm Yes

Behavior alarm Yes

Dry contact alarm Yes

DVR system alarms Yes

Video loss alarm Yes

Genetec Security Desk application

Call up live video Yes

Retrieve video Yes

PTZ control Yes

Capture video Yes

Capture image Yes

2-43


Configuration Notes

The following notes apply to the P2000 system integration with Genetec Security Center (GSC) VMS:

• When you select the Genetec Security Center VMS option during the P2000 software installation process, software development kit (SDK) 5.4 is installed along with other necessary integration components. Separate installing or un-installing of this SDK is not supported.

• The Genetec Security Center integration supports auto-discovery of cameras and presets. If you use the auto-discovery feature, in order for alarms to be displayed correctly you must manually restart the AV Service and the P2000 Genetec Security Center Interface Service after the auto-discovery is complete.

• You can enable and disable the auto-discovery of cameras and presets by editing the “EnableAutoDiscovery” registry DWORD. The auto-discovery feature is enabled by default. We highly recommend that you contact Johnson Controls for assistance

• In addition to the P2000 user, a P2000 operator is also required to have a corresponding account created at the Genetec Security Center. See User Accounts and Permissions on page 2-48 for details.

• The Genetec Security Center integration does not use the P2000 AV Player or a corresponding proprietary AV Player in P2000 SMS. Instead, it sends requests to the Genetec system to display video on the Genetec video viewer application called Genetec Security Desk. See Video Viewer Application: Genetec Security Desk on page 2-62 for more information.

• Integrations with Genetec Omnicast and Genetec Security Center cannot be used together within the same P2000 SMS.

• Configuring dry contact alarms requires special steps; see Dry Contact Alarms on page 2-54 for more information.

• If, after initial configuration, you change Logical IDs within the Genetec Security Center, for proper functioning of the integration you also need to manually update corresponding values in the P2000 system.

• Actions performed by a P2000 Event configured for any Genetec Security Center DVR actions, like Start Recoding or Stop Recording, do not generate host messages. This reduces the potential number of messages in the Real Time List.

2-44


Securing Communication with Genetec Security Center

The Genetec Security Center Server requires all SDK applications, like the P2000 GSC Interface Service, to accept and use the Genetec certificate for communications. The GSC server provides a self-signed certificate when initially installed. You can replace this with certificates provided by your organization. Requirements for secure communications are provided in the manufacturer’s documentation. At time of publication of this document, information could be found in the Genetec Security Center Administrator Guide installed on the GSC server computer. To find these requirements, open the Guide, select System Security, then TLS and Directory authentication and What is Directory authentication?

Because secured communications are required by GSC systems, any GSC client server or client software (like the Genetec Security Desk or any application using the Genetec SDK, such as the P2000 GSC Interface Service) cannot access a GSC server unless the certificate provided by the secured GSC server is installed on the computer where the SDK client application is running.

If you require Genetec Secure Communications, you must install the certificate registered on the GSC Server onto the P2000 Server and make the certificate available to the Pegasys Services user account. This allows the P2000 GSC Interface Service to connect to the Genetec Security Center Server.

If you do not require secure communications, use the check box in the Edit AV Switch configuration dialog to allow the P2000 to connect to the GSC Server unsecured.

2-45


When checked, the following popup message appears:

Selecting Yes allows the P2000 GSC Interface Service to connect to the GSC Server without validating the GSC Server or connection. The Genetec SDK is allowed to accept the certificate provided by the GSC Server one time. Future connections to the GSC Server are allowed until the Genetec system’s certificate expires or is replaced, at which point the P2000 administrator needs to check the Unsecured Communications box again to reconnect to the GSC Server.

The P2000 GSC Interface Service cannot connect to a secure GSC server unless the required certificate has been installed. An error message appears in the P2000 Real Time List and the application event log when a certificate is not installed.

Using Certificate Authorities:

To use a certificate from a Certificate Authority, please refer to the Genetec Security Center Administrator Guide.

2-46


Configuration Overview

See the following illustration for an overview of P2000 SMS integration with Genetec Security Center VMS.

Figure 2-1: P2000 SMS Integration with Genetec Security Center

P2000 Core Server

with Genetec Security Center SDK

Genetec Security Center (GSC)

including GSC Admin Tool

Genetec Security Desk Application

P2000 Workstation

with Genetec Security Center SDK

Web API (optional)*

Web UI (optional)*

IP CameraIP CameraIP Camera

P2000 SMS can integrate with more than one GSC.

* Web API and Web UI do not need to be co-located with P2000 Core server.

2-47


Installation Overview

The following notes apply to the installation process:

• For P2000 system integration with Genetec Security Center, during P2000 software installation on the server and the workstations, select the Genetec Security Center VMS codecs option. This allows you to integrate with one or several Genetec Security Centers.

• The Genetec Security Desk application is not installed by the P2000 software installer; you must install it manually from the Genetec supplied Security Center installation media. Refer to the Genetec Security Center Installation and Upgrade Guide for instructions.

This application must be installed on every machine from which you want to view the video. However, for performance reasons, we recommend that you do not install the Genetec Security Desk application on the P2000 server, but only on the P2000 workstations.

User Accounts and Permissions

In order to view video from the Genetec Security Desk, a P2000 SMS operator must have a Genetec Security Center account with the same user name and appropriate permissions. Password to these two accounts may be different.

2-48


Defining Cameras

The Logical ID of the camera in the Genetec Config Tool must match the OPC number of the camera in the P2000 system. See the following example:

The Genetec Logical ID of the camera must match the number of the camera as defined in the P2000 system.

2-49


Defining Monitors

Defining monitors for integration with the Genetec Security Center requires you to specify:

• The number related the OPC Name

• Monitor ID

• Pane Number (cannot be 0)

OPC Name and Number

For the number related with OPC Name, enter a number between 1 and 9999. The Genetec Security Center does not use the OPC name and related number to reference the monitor. However, you must use a number that is unique for each monitor defined on this AV Switch. This is particularly important when you use the same Genetec Security Desk is to define multiple monitors by using different tiles for camera display.

Use a unique OPC number for each monitor defined on this AV switch.

2-50


Monitor ID

The Monitor ID in the P2000 system must match the Logical ID of the monitor in the Genetec system. See the following example:

NOTE: After adding monitors, manually restart the CCTV Server service.

The Genetec Logical ID and the P2000 system Monitor ID must match.

2-51


Pane Number

The Pane Number in the P2000 system determines which tile in the Genetec Security Desk application will display the video. See the following example:

Pane Number determines Genetec Security Desk tile.

2-52


Defining Dry Contacts

To define Dry Contacts and allow for the dry contact alarms to be reported, you will need to follow Genetec’s instructions to create an area that contains the camera input point that triggers dry contact alarms.

NOTE: The Logical ID in the Genetec Security Center system is not the same as the Number of the Dry Contact in the P2000 system. Instead, it matches the DWORD Value Data in the P2000 system’s registry (see Table 2-4 on page 2-59).

2-53


Dry Contact Alarms

Genetec Security System cannot report input point alarms (called dry contact alarms in the P2000 SMS) directly to the P2000 system. Instead, they have to be placed into a Genetec Security System Area, and the Area then reports alarms as the P2000 dry contact alarms.

Dry contact alarms within the P2000 system are stateless. Consequently, the P2000 system does not report an alarm when the VMS system reports that the input point returned to “normal.”

Follow this general outline to add dry contact alarms to an Area in the Genetec Security Center; refer to manufacturer’s documentation for more information:

To configure dry contact alarms (to add alarms to an Area) at the Genetec Security Center:

1. After you create a Dry Contact alarm in the Genetec Security Center, in the Genetec Security Center Config Tool click the Area view tab.

2. Under Identity, add a new Area. Enter a Name and a Logical ID number. The Logical ID number is must match the dry contact Number in the P2000 system.

The Genetec Logical ID of the Area must match the dry contact’s Number as defined in the P2000 system.

2-54


3. Under Properties, add the camera input point to Inputs. For Associated Events, set the Normal State to “Door Closed” and the Active State to “Door Open.”

4. Under Identity again, define Event-to-action with the following selections:

• Normal State and Active State – “Door opened” or “Door closed” (depends on whether the input is input normally open or normally closed)

• Action – “Trigger Alarm”

• Alarm – “Dry Contact”

2-55


When you configure dry contact on the P2000 SMS side:

• Remember that the dry contact Number at P2000 SMS must match the Area view Logical ID at the Genetec Security Center.

• Wait for the AV Service to restart before you test the input point.

2-56


Genetec Alarm Messages

The P2000 system can receive the following alarm types from Genetec:

• Motion

• Behavior

• Video Loss

• Dry Contact

These alarms must be defined using the Genetec Security Center Config Tool.

Each alarm type has a Logical ID or a range of Logical IDs assigned to it. The Logical IDs in the P2000 system must match the Logical IDs defined under Alarms.

The default values for Logical IDs used in the P2000 system are listed in Table 2-4. In the rare cases when the value must be modified (for example, if a default value is already used by Genetec for a different type of alarm), see the procedure described in Changing Default Alarm Logical IDs on page 2-58.

NOTE: Since the integration supports multiple alarms in the categories of “Behavior” and “Video loss,” we recommend that you set the alarm debounce time in the Genetec Security System to “0” for these categories. This prevents loss of alarms if several alarms are generated withing the debounce time.

Additionally, each camera defined on the Genetec Security Center system must have an action created to trigger an alarm. See Table 2-3 for some of the event types corresponding to P2000 alarms. For additional Genetec Security Center event types, contact a Genetec representative.

2-57


Table 2-3: Corresponding P2000 Alarm Types and Genetec Event Types

P2000 Alarm Message

The alarms must be defined in the Genetec Security Center Config Tool > Alarms screen.

As for other alarm types in Genetec integration with the P2000 system, the Logical IDs in the P2000 system must match the Logical IDs defined under Genetec Alarms. The default value for Logical IDs used in the P2000 system are listed in Table 2-4. In the rare cases when the value must be modified (for example, if a default value is already used by Genetec for a different type of alarm), see the procedure described in Changing Default Alarm Logical IDs on page 2-58.

Changing Default Alarm Logical IDs

In some instances, a Logical ID used by Genetec for a particular alarm type is different from the default Logical ID defined in the P2000 system. By editing the computer registry on the P2000 server, you can change the default P2000 settings.

P2000 Alarm Types Genetec Event Types

Motion Motion on

Behavior1

1. By default, all alarm numbers in the 207 to 216 range are treated by the P2000 system asbehavior alarms.To specify what caused the behavior alarm, the P2000 behavior alarmdescription uses the name of the Genetec Security System. See Table 2-4.

Intrusion

Loitering

Tailgating

Video Loss2

2. By default, all alarm numbers in the 217 to 226 range are treated by the P2000 system as videoloss alarms.To specify what caused the video loss, the P2000 video loss alarm description usesthe name of the Genetec Security System. See Table 2-4.

Camera not archiving

RTP packets lost

Signal lost

Transmission lost

Dry Contact Follow Genetec’s instructions to create an Area that contains the camera input point and trigger the dry contact alarm.

2-58


In order to create a custom Logical ID, you need to create a new registry DWORD:

• The Value name of the DWORD must match the alarm type as listed in Table 2-4.

• The Value data of the DWORD becomes the custom Logical ID and must match the Genetec Logical ID.

NOTE: The P2000 alarm is used by the P2000 system to send a notification to the Genetec Security Center system for a specific camera. You must configure the Genetec system to receive this message. The Genetec configuration can perform any action or macro available on the Genetec system. Contact a Genetec representative for assistance in configuring actions and macros.

NOTE: We highly recommend that you contact Johnson Controls for assistance before modifying default registry settings on the P2000 server.

Table 2-4: Alarm Type Logical IDs

Alarm Type DWORD Value NameDWORD Value Data:Default Logical ID

DWORD Value Data:Custom Logical ID1

1. Defined by user in the computer registry on the P2000 server.

Motion MotionAlarm 201

Behavior BehaviorAlarmMin2

2. Bottom of Logical ID range.

207

BehaviorAlarmMax3

3. Top of Logical ID range.

216

Video Loss VideoLossAlarmMin2 217

VideoLossAlarmMax3 226

Dry Contact DryContactAlarm 204

P2000 Alarm P2000CameraAlarm 1000 + camera ID number4

4. The Logical ID for P2000CameraAlarm depends on the offset value and the camera ID number. The LogicalID for the alarm is created by adding these two values. For example, if the default offset value of 1000 is used,camera 1 sends alarm with Logical ID 1001, camera 2 sends alarm with Logical ID 1002, and so on. The offsetvalue can be changed through the registry.

2-59


The following illustration shows an example of a correctly defined custom Logical ID.

Creating Custom Logical IDs

IMPORTANT: Procedures described in this section change the default settings through modifications to the registry and should only be performed by qualified professionals. In most cases the default settings are sufficient and the following procedures do not need to be performed.

To create custom Logical ID:

1. Launch regedit.exe to access and edit the registry.

2. Expand the tree and go to:

HKEY_LOCAL_MACHINE > Software > Wow6432Node > Johnson Controls > AV Vendor > Genetec Security Center

The Alarms tab is selected

Notice the following:

• The required DWORD Value name to define custom Logical ID for the Dry Contact alarm type is DryContactAlarm.

• The Genetec Logical ID matches the Value data for this alarm type as defined in the computer registry on the P2000 server.

2-60


3. To create a registry new entry, from the main menu go to Edit > New > DWORD (32-bit) Value. The new registry entry appears on the right window pane. Enter the entry name and press the Enter key (see Table 2-4 for reference information).

In the following example, DryContactAlarm DWORD has been created.

4. Right-click the icon for the DWORD, and select Modify.

In the Edit DWORD (32-bit) Value window, select the Decimal radio button and enter the Logical ID for the alarm type in the Value data field.

5. Click OK.

6. Close the Registry Editor window.

2-61


Video Viewer Application: Genetec Security Desk

Integration with the Genetec Security Center uses the Genetec Security Desk application to display live and recorded video for P2000 AV Player requests from all AV Player actions in the P2000 core user interface (such as the AV Player tool bar icon, the Real Time List, or the Alarm Monitor).

NOTE: The Genetec Security Desk application is not installed by the P2000 software installer; you must install it manually from the Genetec supplied Security Center installation media. Refer to the Genetec Security Center Installation and Upgrade Guide for instructions.


For all P2000 AV Player commands, a request to see camera video is sent automatically from the P2000 SMS to the Genetec Security System, and the video is displayed in the first tile of the Genetec Security Desk Monitoring Tab where you are logged on.

If you are logged on at multiple Genetec Security Desk applications, the display request is sent to all of them.


• As the P2000 user, you have to manually start and log on to the Security Desk application. The P2000 system will not start the Genetec Security Desk automatically.

• Monitoring Tab must be open in Security Desk to display camera video. If the Security Desk does not have Monitoring Tab open, the requested camera video will not be displayed.

• The login user name for the Genetec Security Desk must be that same as the login user name for the P2000 SMS.


P2000 Core application is able to request live or recorded video display from the Genetec Security Center. Video can be requested from one camera at a time.

All video, live or recorded, requested from the P2000 Core user interface, displays in the first tile of the currently open Security Desk’s Monitoring Tab.

2-62


The following example shows video displayed in Tile 1 of “Ricks Cam Task.” New video requests would replace the video currently displayed in the same tile.

Figure 2-2: Genetec Security Desk and the P2000 SMS

Tile 1: Live or recorded video from selected camera (the only tile used for P2000 core application video requests)

Monitoring Tab

2-63



P2000 Web UI is able to request video display from Genetec Security Center. P2000 Web UI can request Genetec Security Center integration for both live and recorded video from multiple cameras.


Figure 2-3: Genetec Security Desk and P2000 Web UI

Tile 1:Live video request from Web UI

Tile 2:Recorded video request from Web UI

Tile 2 and 3:Subsequent video requests from Web UI

Monitoring Tab

2-64


Troubleshooting

To assist troubleshooting run time events, the P2000 integration with Genetec Security Center can produce log files.

To set up log for run time events:

1. On the C: drive, create a folder named P2000Debug.

2. Using the regedt32.exe utility, add the DWORD value in the following registry folder:

HKEY_LOCAL_MACHINE\Software\Johnson Controls\AV Vendor\[vendor_name]

3. Name the DWORD EnableLogFile.

4. With EnableLogFile highlighted, select Edit > Modify.

5. Enter the following values:

1 to create a log file

0 (or delete the registry entry) to stop writing to the file

6. Stop and restart the following services:

• P2000 AV Service

• CCTV Server

Log files are now generated. To stop logging runtime events, change the registry entry to 0 (as previously noted) and/or delete the P2000Debug folder from the C: drive.

2-65

DVR/VMS Integration Protocol Integration Details: Milestone24-10832-62 Rev. E

MILESTONE

Supported Features

* Uses a proprietary viewer application instead of the AV Player.

Feature

Support

Corpo-rate

Enter-prise

Profes-sional

Expert





Camera Preset Yes Yes Yes Yes


Camera Send Alarm



Camera Start Recording Yes Yes Yes Yes


Camera Start Recording Associated Input Yes Yes Yes Yes

Camera Start Recording Associated Terminal Yes Yes Yes Yes

Camera Stop Recording Yes Yes Yes Yes

Camera Stop Recording Associated Input Yes Yes Yes Yes

Camera Stop Recording Associated Terminal Yes Yes Yes Yes

Launch AV Player Yes* Yes* Yes* Yes*

Monitor Camera Yes Yes Yes


Motion Alarm Yes Yes Yes Yes

Behavior alarm

Dry contact alarm Yes Yes Yes

DVR system alarms Yes Yes Yes Yes

Video loss alarm Yes Yes Yes Yes

AV Player Actions

Call up live video Yes Yes Yes Yes

Retrieve video Yes Yes Yes Yes

PTZ control Yes Yes Yes Yes

Capture video Yes Yes Yes Yes

Capture image Yes Yes Yes Yes

2-66


Configuration Notes

The P2000 Milestone integration allows the P2000 system to control operation of the Milestone system based on events that occur in the P2000 system. It also allows both live and stored video from the Milestone system to be displayed on P2000 workstations.

When you establish a connection with the Milestone system, the P2000 auto-discovers cameras, presets, and monitors from Milestone and populates their names in the P2000 configuration tables. With auto-discovery, you only need to configure the Milestone system’s IP address, user name, and password in the P2000 system.

If you use the auto-discovery feature, you must restart the AV Service after the P2000 system has auto-discovered all cameras, monitors, and presets. Also, you must manually enable the Pan, Tilt, Zoom, and Focus functions for auto-discovered cameras. See Controls Tab on page 3-20.

NOTE: After the P2000 system completes its auto-discovery process, do not manually change the name of any cameras, presets, and monitors in the P2000 system that were previously auto-discovered.

You can also manually add cameras, presets, and monitors using the CCTV/AV Configuration Window, if needed. When manually configuring cameras, presets, and monitors, the names in the P2000 system must exactly match the names defined on the Milestone system. Note that names are case sensitive.

Instead of the AV Player, the Milestone system uses the Milestone Viewer application.

NOTE: Changes to the Milestone configuration require you to stop and restart the following services in order for the P2000 system to recognize the changes: Milestone MIP Interface Service, AV Service, and CCTV Server. (The Milestone MIP Interface Service must be stopped and restarted first.)

2-67


Requirement for Motion Alarms

The Milestone XProtect Enterprise, XProtect Professional, and XProtect Express systems (but not XProtect Corporate) provide alarms to the P2000 server through Milestone XProtect Central. This connection requires a login name and password. To receive Motion Alarms, you must enable Milestone XProtect Central and change the login name and password to the one used by the P2000 system for connecting to the Milestone server. For details refer to the manufacturer’s documentation.

Configuring Dry Inputs

Dry contacts are called inputs or input points in the Milestone MIP system.

The P2000 system does not auto-discover dry contacts.

The name of the dry contact maps onto the name of the Milestone’s Hardware Input Event. For more information, refer to the Milestone documentation.

IMPORTANT: The dry contact names between the P2000 server and the Milestone system must match.

Milestone Viewer

The Milestone Viewer application allows you to:

• View live video

• Control PTZ functions of cameras connected to the Milestone system

• Search for and play recorded video

• Export a video clip

• Export a still image

• Browse through recorded video frame by frame

The Milestone Viewer consists of the video player viewing area and tabs to access live or recorded video, or to browse recorded video frame by frame.

The Milestone Viewer window title displays the name of the currently selected camera. This information is repeated in the text above the viewing area, along with camera status information.

2-68


Milestone Viewer: Live Tab

Camera information – The text above the video display area indicates the camera name and status (live or recording). The blinking green light indicates that the camera is connected and working. The red light, in addition to the blinking green light, indicates that the camera is being recorded.

Camera – From the drop-down list, select the camera from which you want to display the live image.

Pan/Tilt/Zoom Controls – Use these buttons to pan, tilt, and zoom the camera. The zoom buttons in the middle only become enabled for PTZ cameras. To zoom in, click the plus button (+). To zoom out, click the minus button (-).

Preset – List of predefined presets used to reposition the camera.

NOTE: When integrated with the P2000 system, the Milestone Viewer allows you to select and execute presets properly, but the preset name is not displayed as selected in the drop-down list.

2-69


Milestone Viewer: Recorded Tab

A message at the bottom of the video display area provides current activity information.

Unless manually paused or stopped, video playback continues until the system reaches the beginning or the end of available video.

When the video reaches the beginning or end of the available recording, the player displays the message Start of Video or End of Video Clip at the bottom of the video display area.

If the video playback encounters a gap in the available recording, the player momentarily displays the message Video Gap Skipped at the bottom of the video display area.

Camera information – The text above the video display area indicates the camera name. The green light’s blinking rate corresponds to the playback speed.

Camera – From the drop-down list, select the camera from which the recording was made.

2-70


Date / Time – Select the date and time of recorded video. The drop-down list for the date allows you to make a selection in the virtual calendar. If you enter a new date or time, the video playback goes to that instance in the archive and stays in a paused state. Click the Play button to begin video playback at the selected date and time.

To adjust the time, select it and use the keyboard, or use the up and down scroll arrows.

Playback and Export Controls – Use these buttons to control playback and export functions:

Fast Rewind – Fast rewinds the recording at four times the normal speed.

Play Backward – Plays the recording backward. If the video has previously been paused, playback continues from the point of pause. If the video has previously been stopped, playback begins at (or near) the selected Date /Time.

Pause – Pauses playing the recording.

Stop – Stops playing the recording.

Play Forward – Plays the recording forward. If the video has previously been paused, playback continues from the point of pause. If the video has previously been stopped, playback begins at (or near) the selected Date / Time.

Fast Forward – Fast forwards the recording at four times the normal speed.

Set Start Time (Video Export) – Sets the selected time as the start time for exporting video.

Set End Time (Video Export) – Sets the selected time as the end time for exporting video.

Export Video Clip – Once you set the start and end times, this option allows you to export the video clip as an AVI file to the Milestone system or to a user-defined destination on the local computer or network. During the export process, you can include or exclude audio.

Export Image – Enables you to export the image currently displayed and save it as a JPEG file.

2-71


To export a video clip:

1. On the Recorded tab, select the desired camera.

2. Use the Date/Time fields to find the start of the video you wish to export.

3. Click Set Start Time.

4. Use the Date/Time fields to find the end of the video you wish to export.

5. Click Set End Time.

6. Click Export Video Clip. The Export Video window appears.

7. To include audio, click Include related audio devices. To exclude audio, click to clear this option.

8. If you are saving the AVI file to the Milestone system, click Database. Once you export the clip, use Milestone Smart Client to view the exported clip. Refer to the Milestone documentation for assistance.

9. If you are saving the AVI file to a user-defined destination on the local computer or network, click AVI, enter a name for the file in the AVI text box, and click Destination folder to select a destination for the file.

2-72


10. Click Export.

11. When the export process is completed, click Close.

To export a still image:

1. Pause on the camera image you wish to export.

2. Click Export Image. The Export Image window appears.

3. If you do not want to use the default save path, click Destination folder to select the location where you wish to save the file.

4. In the Export File Name text box, enter a name to assign to the file.

5. Click Export.

2-73


Milestone Viewer: Browse Tab

This tab allows you to view recorded video frame by frame, and also enables you to configure the amount of time (in seconds) between frames. This feature is useful when you need to identify video differences from one frame to the next. You can set the number of seconds between frames at 0.25 seconds (the lowest setting) up to 3,600 seconds (the highest setting).

To review recorded video frame by frame:

1. On the Browse tab, use the Date/Time fields to find the start of the video you wish to browse.

2. Use the vertical scroll bar to set the gap (in seconds) between successive frames.

3. Place the cursor on the viewing area and use the mouse wheel to change the number of frames visible in the video view area. The default number of frames is 25.

4. Use the left and right arrows to see the previous or next set of video frames in the video view area.

2-74


Troubleshooting the Milestone Integration

The error message Cannot connect to Milestone system is related to the Milestone SDK’s attempts to connect to all hardware defined in the Milestone system upon connection. Therefore, only hardware that is physically connected should be configured in the Milestone system.

Also, the following error message indicates that a name resolution issue has occurred on the network:

To resolve this issue, try one of the following:

• Set up a Domain Name Server (DNS) that can correctly resolve names on the network.

• Add an entry for the Milestone server to the hosts file on each P2000 server and workstation. This file is located at:

\WINDOWS\system32\drivers\etc

For more information on adding a DNS or modifying a computer’s host file, please consult with a qualified IT professional.

2-75


2-76

DVR/VMS Integration DVR/VMS Configuration24-10832-62 Rev. E

3. DVR/VMS CONFIGURATION

CONFIGURATION OVERVIEW

To operate the DVR/VMS system integrated with the P2000 system, you must configure the communication parameters. Configuration occurs on the P2000 CCTV/AV Configuration window.

IMPORTANT: The configuration should be performed by a system engineer or a system administrator. Although it is simple to use the DVR/VMS integration on a daily basis, the system engineer should have some specific knowledge of the DVR/VMS equipment in order to configure the hardware.

The system hardware consists of the DVR/VMS hardware (represented in P2000 as an AV switch), dry contacts, and cameras. If integrated with the CCTV advanced feature, the system may also include a CCTV switch and monitors.

The CCTV Server and AV Server components provide communication with the system hardware.

The CCTV Server is OPC-compliant (OPC stands for OLE for Process Control). For further information relating to the OPC Interface Standard, refer to the OPC Foundation Interface Specification.

You must define the protocol used by the DVR/VMS on the CCTV/AV Configuration window. The configuration of the cameras, monitors, and dry contacts may be performed automatically or customized to your particular requirements.

Configuration should progress in a logical sequence. First, configure the AV switch, followed by the cameras, monitors, and dry contacts associated with it. After you configure the system, you may return to a component to make any necessary changes.

3-1


Using the CCTV/AV Configuration Window

The CCTV/AV Configuration window provides quick access to the component configurations. All root items in the CCTV/AV Configuration navigation tree appear on the left side of the window. A plus sign (+) next to an item indicates that branches exist beneath them. When you select a branch in the navigation tree, the detailed settings and values relating to that selection are listed on the right side of the window pane.

You can add as many items to the CCTV/AV Configuration window as you need. You can edit existing items, as needed.

You access the CCTV/AV Configuration window from the P2000 Main menu.

To access the CCTV/AV Configuration window:

1. From the P2000 Main menu, select Options > CCTV/AV > Configuration.

2. Enter the password, if prompted. The CCTV/AV Configuration window opens.

To add an item to the CCTV/AV Configuration window:

1. On the left pane, select the root icon for the item you wish to add.

2. Click Add. The associated window appears.

As an alternative, you may also right-click the root icon and select Add.

3. Enter the setting information into the appropriate fields on each tab, as necessary. You may not be able to access some tabs until you enter a minimum amount of information into the active tab.

3-2


4. Click OK. The settings for the new item appear in the right pane of the CCTV/AV Configuration window.

5. Continue to add items in this manner until you have configured all items and their related controls.

To edit CCTV/AV configuration items:

1. On the left pane, select the item you wish to edit.

2. Click Edit. The Edit [Item] window appears.

As an alternative, you may also right-click the item and select Edit.

3. Edit the settings, as necessary

4. Click OK.

5. Verify the new changes on the right pane of the CCTV/AV Configuration window.

CONFIGURING DVR/VMS COMPONENTS

Configuration should progress in a logical sequence. First, configure the AV switch, followed by the cameras, monitors, and dry contacts associated with it. After you configure the system, you may return to a component to make any necessary changes.

NOTE: Before proceeding, see Chapter 2: Protocol Integration Details for additional information regarding your integration component. Some systems require additional steps, such as installation of manufacturer’s files, before you can configure the DVR/VMS components in the P2000 software.

General Configuration Notes

The following notes apply to all protocols:

• We recommend that you develop a naming convention to apply to AV switches, cameras, monitors, and dry contacts before programming the software.

3-3


• Any changes take effect only after a user has stopped and restarted the CCTV Server using the P2000 Service Control tool. For instructions on starting and stopping services using this tool, refer to the P2000 Software User Manual.

• If someone has configured the CCTV Server and AV Switch, you can use the equipment’s default settings.

• Install and operate the DVR/VMS equipment in accordance with the manufacturer’s instructions.

• The DVR/VMS equipment must be time-synchronized with the P2000 server.

IMPORTANT: In addition to the previous notes, some protocols require additional steps or particular configuration settings. Chapter 2: Protocol Integration Details contains some of that information, as available at the time of this publication. For additional information and guidance on protocol-specific settings, refer to the documentation provided by the VMS’s or DVR’s manufacturer.

CCTV Server

You must configure the CCTV Server to establish communication and control.

To add and configure a CCTV Server:

1. Open the CCTV/AV Configuration window.

2. On the left pane, select the icon for the CCTV Server, and click Add.

3-4


3. On the Edit Server window, enter the settings information, as necessary. See Edit Server Field Definitions on page 3-5 for more information.

4. Click OK.

Edit Server Field Definitions

Partition – If partitioning is available, assign the partition that can access this CCTV server information.

Public – If partitioning is available, select this option to allow all partitions to see this CCTV server.

3-5


NOTE: If you wish to assign a CCTV switch or AV switch to a different partition, set the CCTV Server to Public.

Description – User-defined description of up to 64 characters to describe the CCTV Server.

PC Name – Name of the computer on which the CCTV server resides (usually the name of the P2000 server on which you are operating). You can also search for the name using the browse button.

Prog ID – An installed CCTV server is associated with a Program ID. Select the Program ID for the CCTV Server. The default Program ID for the CCTV server is JC.CCTV. Sub-versions may be released from time to time (numbered consecutively starting with JC.CCTV1), but using JC.CCTV ensures that you use the latest version.

AV Switches

An AV switch receives video inputs from cameras and outputs the data to video outputs. Each switch operates using the manufacturer’s protocol; the functionality of the AV switch is largely determined by the protocol provided and the capacity of the equipment connected to the AV switch. For a list of currently supported protocols, refer to Supported Protocols on page 1-4.

Creating and Configuring AV Switches

A Digital Video Recorder (DVR) or a Video Management System (VMS), also called an AV switch, connects to a computer with a CCTV server running on it. The AV switch can have a variety of equipment connected to it, including monitors, cameras, and dry contacts. Equipment connected to an AV switch is presumed to be compatible with that specific AV switch. A CCTV server system may include a number of separately connected AV switches, and each may use a different protocol. However, you can use only one version of each protocol within a P2000 system.

To establish communication and control, you must configure each AV switch installed in your system using the CCTV/AV Configuration window. At the highest level, this window displays the CCTV server. To display icons for the AV switches, expand the CCTV server’s entry.

3-6


To add an AV switch and configure alarm options:

1. Open the CCTV/AV Configuration window.

2. Select the root AV Switches icon and click Add.

The Edit AV Switch window (General tab) opens.

3. Fill in the information under the following tabs:

• General

• Audio-Visual

• Message Filtering

For field reference information, see Edit AV Switch Field Definitions on page 3-10.

3-7


On each tab, click Apply to save your changes.

4. Click the System Alarm Options tab, which displays all alarm categories assigned to the AV switch.

All alarms originating at the AV switch (AV alarms) must belong to at least one alarm category. The default category for a new AV switch is P2000.

3-8


5. Click Add to assign system alarms to one or more alarm categories. (Click Delete to delete a highlighted category from the list of alarm categories assigned to this alarm.)

The Add Alarm Categories window opens and lists the default P2000 category and all user-defined categories. (If you are using an Enterprise configuration, the alarm categories defined for all P2000 sites within an Enterprise system are listed.)

6. Select one or more categories and click Add.

7. To edit alarm options for an alarm category, highlight the alarm option on the Edit AV Switch window and click Edit. You can select and edit more than one category at a time.

The Alarm Options window (General tab) opens.

8. Edit the options under the following tabs:

• General

• Events

• Escalation

• MSEA

For field reference information, see Alarm Options Field Definitions on page 3-30.

Example of user-defined categories

3-9


9. Click OK to save your changes and return to the Alarm Categories window.

10. Repeat Step 6 through Step 8 to configure all alarm categories assigned to this AV switch.

11. Click OK to save your changes and close the Edit AV Switch window.

12. Click Done to close the CCTV/AV Configuration window.

NOTE: For any DVR/VMS configuration changes to take effect, at the completion of your configuration session, stop and restart the CCTV server using the P2000 Service Control tool.

The new AV switch appears under AV Switches on the left pane of the CCTV/AV Configuration window.

Edit AV Switch Field Definitions

When creating an AV Switch definition, you must enter information on all tabs of the Edit AV Switch window to complete the configuration.

NOTE: If you enable a function that is not available for the particular protocol, then the operator’s action has no effect. The system does not check whether the functions selected at the AV switch are compatible with the functionality of the equipment.

3-10


General Tab

Partition – If partitioning is available, assign the partition that can access this AV switch information.

Public – Allows all partitions to see this AV switch (if partitioning is available).

Description – User-defined name of the AV Switch. This name appears in the AV Player window.

AV Server – Name of the CCTV server that resides on the computer to which the AV switch is physically connected. The software automatically enters the name.

NOTE: When used for the video management operation, the CCTV server is also referred to as the AV server.

OPC Name – In the text box to the right, enter the number of the AV switch. The software automatically appends the number to the prefix letter and adds it to the OPC Name field. For more information about namespace names and item numbers, see Naming Items for the AV Server Namespace on page 1-7.

Protocol – Select the protocol to be used with the make and model of the AV switch.

3-11


Audio-Visual Tab

NOTE: The Audio-Visual tab may contain fewer fields, depending on the digital video protocol you are using.

Streaming Server IP Address – IP address of the streaming server (usually the IP address of the AV switch). The streaming server allows transmission and viewing of audio and video.

Data Server IP Address – IP address of the data server (usually the IP address of the AV switch). The data server is a database server that maintains all necessary information for operating DVR/VMS integration functions, including administration, video clip logging, and so on. In addition, it handles all video retrieval requests.

NOTE: For some video integrations, configuration of this field is not required.

Storage Server IP Address – IP address of storage server (usually the IP address of the AV switch). The storage server is an archive server that typically has a number of tape libraries.


3-12


Username – Logon user name needed to access the remote DVR/VMS.

Password – Logon password needed to access the remote DVR/VMS.

Confirm Password – Confirmation of logon password needed to access the remote DVR/VMS.

Server Name – Name of the server computer responsible for manipulating a video matrix switch. This is the network ID computer name of the AV switch that communicates with the CCTV switch.

IP Address – IP address of the video matrix switch server. This is the IP address of the AV switch that communicates with the CCTV switch.


Port – The COM port of the AV switch that is physically connected to the CCTV switch.

NOTE: The software checks with the CCTV server to determine any conflict in port usage, but does not check with any other equipment that may be running.

Message Filtering Tab

3-13


Process AV Messages

Motion Detection – Time zone during which the Motion Detection AV messages are processed.

Dry Contact – Time zone during which the Dry Contact AV messages are processed.

Video Loss – Time zone during which the Video Loss AV messages are processed.

Behavior – Time zone during which the Behavior AV messages are processed.

AV Messages Debounce Time

Motion Detection – If a time between two consecutive motion detection alarms coming from the same source (camera) is less than the defined value, the system does not add the second alarm to P2000 alarm queue.

Behavior – If a time between two consecutive behavior alarms coming from the same source (camera) is less than the defined value, the system does not add the second alarm to P2000 alarm queue.

Generate AV Alarm

Mode – Select which messages are transmitted to a mapped camera as P2000 alarms.

• Select <Send none> to disable transmission of all messages.

• Select <Send all> to allow transmission of all messages that pass the Time Zone criteria.

• Select <Send filtered> to allow transmission of messages that pass the Time Zone criteria and the Message Filter Group criteria.

NOTE: Mode settings only apply to alarms that are generated for input points mapped to cameras in the input to camera application. Camera Send Alarm event actions ignore the Mode option selected here.

Time Zone – Select the time zone during which messages that pass the Message Filter Group criteria are transmitted to a mapped camera as P2000 alarms. Select <always enabled> to send messages at all times.

3-14


Message Filter Group – Select the Message Filter Group that defines which of the messages that pass the Time Zone criteria are transmitted to a mapped camera as P2000 alarms. Select <None> to transmit all messages.

System Alarm Options Tab

Select Alarm Categories

Edit – Opens the Alarm Options window and enables you to edit the alarm options for a highlighted alarm category. See Alarm Options Field Definitions on page 3-30 for more information.

Add – Opens the Add Alarm Categories window and enables you to assign this alarm to an additional alarm category.

Delete – Deletes a highlighted alarm category from the list of categories assigned to this alarm.

Cameras

Cameras physically connected to the AV Switch are recognized by their physical address.

3-15


Creating and Configuring Cameras

You must manually define cameras. We recommend that you name them in a consistent manner for easier use. See Naming Conventions on page 1-7 for more information.

To add a named camera and configure alarm options:

1. On the CCTV/AV Configuration window, expand the AV Switches option. Expand the AV Switch associated with the camera (that is, the switch to which the camera is connected).

2. Right-click Cameras and select Add.

The Edit AV Camera window (General tab) opens. (If the window is minimized, click the Windows taskbar to restore it.)


• General

• Controls

For field reference information, see Edit AV Camera Field Definitions on page 3-19.

3-16


4. On each tab, click Apply to save your changes.

5. Configure each alarm type (motion, behavior, or video loss). Select the desired alarm tab in the Edit AV Camera window:

• Motion Alarm Options

• Behavior Alarm Options

• Video Loss Alarm Options

The Select Alarm Categories list displayed under the selected alarm tab contains all alarm categories assigned to this type of alarm. The P2000 alarm category is listed by default.

3-17


6. To add more categories, click Add.

The Add Alarm Categories window opens, listing the default P2000 category and all user-defined categories. (If you are using Enterprise configuration, the alarm categories defined for all P2000 sites within an Enterprise system are listed.)


8. To delete a category from the list of alarm categories assigned to this alarm, select it and click Delete.

9. To edit alarm options, select one or more categories on the Edit AV Camera window and click Edit.You can edit more than one category at a time.



• General

• Events

• Escalation

• MSEA




3-18


12. Repeat Step 9 and Step 10 to configure all alarm categories assigned to this alarm type. Click Apply to save your changes.

13. Repeat Step 4 through Step 11 until you have configured all three alarm types (motion, behavior, and video loss alarms).

14. To verify the camera’s functionality, select the AV Camera Test tab.

15. Click OK to close the Edit AV Camera window.

Edit AV Camera Field Definitions

When creating a camera definition, you must enter information on all tabs of the Edit AV Camera window to complete the configuration. (If the window is minimized, click the Windows taskbar to restore it.)

General Tab

Partition – If partitioning is available, assign the partition that can access this camera’s information.

Public – If partitioning is available, select this option to allow all partitions to see this camera.

Description – User-defined name of the camera. This name is displayed on the AV Player window.

3-19


NOTE: For some protocols, the user-defined name must match the name of the camera as defined in the DVR/VMS. See Chapter 2: Protocol Integration Details for details.

AV Switch – Name of the AV switch to which the camera is physically connected. The software automatically enters the AV switch name into this field.

OPC Name – In the text box to the right, enter the number of the camera. The software automatically appends the number to the prefix letter and adds it to the OPC Name field. For more information about namespace names and item numbers, see Naming Items for the AV Server Namespace on page 1-7.

Controls Tab

If the majority of the cameras are of one type (for example, fixed), we recommend that you select the camera functions that apply to the majority of the equipment. Then, you can specifically configure those cameras that have different capabilities.

General String – (Optional) Up to 64 characters that appear on the monitor when the camera is operating from the AV Player window (provided the protocol allows it). For example, you could enter the name of the camera or a description of the camera’s location.

3-20


Enable PTZ – Enables the camera’s Pan, Tilt, and Zoom functions, if available.

Focus – Enables the camera’s Focus function, if available.

Iris – Enables the camera’s Iris function, if available.

Iris Automatic – Enables the camera’s Automatic Iris function, if available.

Wiper – Enables the camera’s Wiper function, if available.

Washer – Enables the camera’s Washer function, if available.

Light – Enables the camera’s Light function, if available.

Status – Enables the camera’s Status function, if available.

Lens Speed – Enter the lens speed. Refer to the manufacturer’s instructions for information on the lens speed.

Lens Speed Max – Enter the maximum speed of the lens. Refer to the manufacturer’s instructions for information on the maximum speed of the lens.

Tabs for Alarm Options

The Motion Alarm Options, Behavior Alarm Options, and Video Loss Alarm Options tabs list the alarm categories assigned to a particular alarm type, and provide access to the Add Alarm Categories and Alarm Options windows.

Alarm debounce time – Enter a minimum delay time in milliseconds. When two consecutive alarms of the same type and coming from the

3-21


same camera occur within the specified delay time, the second alarm is not added to the alarm queue. This feature is available for motion and behavior alarms.

Edit – Opens the Alarm Options window for one or more selected Alarm Categories. See Alarm Options Field Definitions on page 3-30 for more information.

Add – Opens the Add Alarm Categories window.

Delete – Deletes a selected alarm category.

AV Camera Test Tab

Click Launch AVPlayer to display a live image and, depending on the hardware you are using, to test supported functions.

Camera Presets

A preset camera position is a user-defined position that may include pan, tilt, zoom, and focus adjustments. Numbered presets are defined as part of the AV switch or camera definition; you can specify a camera preset name, which is displayed on the AV Player window. You can use named and numbered camera presets from the PTZ tab of the AV Player window, provided the equipment is available and can perform the required functions.

3-22


To add a named camera preset:

1. On the CCTV/AV Configuration window, expand the AV Switches entry. Expand the AV Switch associated with the camera (that is, the switch to which the camera is connected).

2. Expand the Cameras option and the camera that has the named preset.

3. Right-click Presets and select Add. The Edit AV Preset window opens.

4. If partitioning is available, select the Partition that can access this preset information.

5. If partitioning is available, click Public to allow all partitions to see this preset.

6. In the Description field, enter the user-defined name of the preset. The name you assign here is displayed in the AV Player window.

7. The AV Camera field displays the name of the camera to which the preset is physically connected. The software automatically enters the camera name into this field.

8. In the OPC Name field, enter the number of the preset. The software automatically appends the number to the prefix letter and adds it to the OPC Name field. For further information about namespace names and item numbers, see Naming Items for the AV Server Namespace on page 1-7.

9. Click OK to save the settings.

3-23


Monitors

Monitors are physically connected to a CCTV switch, which is controlled by the AV switch. They are recognized by their physical address.

Creating and Configuring Monitors

Monitors connected to the AV Switch can be defined automatically. However, defining individual Monitors simplifies the day-to-day operation of the system. We recommend that when someone has validated proper system performance, use a naming convention with the monitors for easier use. See Naming Conventions on page 1-7 for more information.

To add a named monitor:

1. On the CCTV/AV Configuration window, expand AV Switches. Expand the AV Switch associated with the monitor (that is, the switch to which the monitor is connected).

2. Right-click the Monitors icon and select Add. The Edit AV Monitor window opens. (The Monitor ID and Pane Number fields are specific to the Genetec protocol.)

3-24


3. Fill in the information for each field according to Edit AV Monitor Field Definitions on page 3-25.

4. Click OK.

Edit AV Monitor Field Definitions

Partition – If partitioning is available, assign the partition that can access the monitor’s information.

Public – If partitioning is available, select this option to allow all partitions to see the monitor.

Description – User-defined monitor name. This name entered here is displayed on the AV Player window.

AV Switch – Name of the AV Switch to which the monitor is physically connected. The software automatically enters the AV Switch name into this field.

OPC Name – In the text box to the right, enter the monitor number. The software automatically appends the number to the prefix letter and adds it to the OPC Name field. For further information about namespace names and item numbers, see Naming Items for the AV Server Namespace on page 1-7.

General String – User string displayed when the AV Player runs.

Decoder IP Address – Specify the IP address of the video decoder used to drive the monitor (available for some digital video systems).

3-25


Monitor ID – (Genetec only) Enter the Genetec monitor ID value.

Pane Number – (Genetec only) Specify the pane location number used to identify the location on a monitor where the camera video is displayed. If the pane value is 0, the system displays the video in the first empty pane on the monitor.

Dry Contact

Dry Contacts are two-state (open/closed) input points physically connected to a CCTV switch or one of its components (for example, an IP camera), and are recognized by their physical address.

You must manually define dry contacts. We recommend that you name them in a consistent manner. See Naming Conventions on page 1-7 for more information.

To add a named dry contact and configure alarm options:

1. On the CCTV/AV Configuration window, expand AV Switches. Expand the AV Switch associated with the dry contact (that is, the switch to which the dry contact is connected).

2. Right-click Dry Contact and select Add.

The Edit AV Dry Contact window (General tab) opens.

3-26


3. Fill in the information under this tab according to Edit AV Dry Contact Field Definitions on page 3-29.

4. Click Apply to save your changes.

5. Select the Alarm Options tab, which displays all alarm categories assigned to the dry contact.

The Select Alarm Categories list contains all alarm categories assigned to this alarm type. The P2000 alarm category is listed by default.

3-27


6. Click Add to assign system alarms to one or more alarm categories. (Click Delete to delete a highlighted category from the list of alarm categories assigned to this alarm.)

The Add Alarm Categories window opens, listing the default P2000 category and all user-defined categories. (If you are using Enterprise configuration, the alarm categories defined for all P2000 sites within an Enterprise system are listed.)


8. To edit alarm options for an alarm category, select one or more categories on the Edit AV Dry Contact window and click Edit. You can edit more than one category at a time.



• General

• Events

• Escalation

• MSEA




3-28


11. Repeat Step 7 through Step 9 to configure all alarm categories assigned to this dry contact.

12. Click OK to save your changes and close the Edit AV Dry Contact window.

13. Click Done to close the CCTV/AV Configuration window.

Edit AV Dry Contact Field Definitions

The Edit AV Dry Contact window opens at the General tab. You must enter information in both Edit AV Dry Contact tabs to complete your configuration of the dry contact.

General Tab

3-29


Partition – If partitioning is available, assign the partition that can access the dry contact’s information.

Public – If partitioning is available, select this option to allow all partitions to see the dry contact.

Description – User-defined name of the dry contact. The name entered here is displayed in the AV Player window.

AV Switch – Name of the AV switch to which the dry contact is physically connected. The software automatically enters the AV switch name into this field.

Number – Enter the number of the dry contact.

Alarm Options for DVR/VMS Integration Components

To configure alarm options for an alarm generated by an AV switch, AV camera, or AV dry contact, use the Alarm Options window.

Each AV alarm belongs to one or more alarm categories. You can configure different alarm options for each alarm category to which the alarm belongs. You can then use these different configurations with the P2000 Alarm Filter and Escalation features to design a system in which dynamic alarm routing allows for effective use of the operator’s time.

For more information on alarm categories, alarm filter, and escalation, refer to the P2000 Software User Manual.

Alarm Options Field Definitions

The Alarm Options window displays the following in the title bar:

Alarm Options - the name of the window from which it was accessed [Alarm Category].

For example:

If you are editing the alarm options for more than one category at a time, the Alarm Category is displayed as [*].

3-30


For example:

General Tab

Disable Alarm – When you clear this option, the system adds the alarm to the alarm queue and displays it in the alarm monitoring window to notify the operator of its activation. If you select this option, the system disables this alarm. Enabling/disabling of the alarm is specific to a particular alarm category. For example, you can enable the alarm for a user-defined Warehouse category and disable the same alarm for a user-defined Security category.

NOTE: Before you assign instruction text to the various pop up messages, you must first create instruction text. For more information, refer to the P2000 Software User Manual.

Alarm Popup – When you enable Alarm Popup for an alarm, the Alarm Monitor pops up at the front of the screen when the sending item is in the alarm state.

Normal Popup – When you enable Alarm Popup for an alarm, the Alarm Monitor pops up at the front of the screen when the sending item is in the normal state.

3-31


Other Popup – When you enable Alarm Popup for an alarm, the Alarm Monitor pops up at the front of the screen when the sending item is in a state other than alarm or normal.

Acknowledgement Required before Completion – Requires acknowledgement of this alarm before its completion.

Response Required before Completion – Requires response to this alarm before its completion.

Alarm Priority – Enter a value from 0 to 255. Zero equals the highest priority. This is the order in which the alarm message are placed in the alarm queue. If alarm messages have the same alarm priority, the date and time determine which alarm is positioned higher in the queue.

Alarm Timezone – If you want the item to generate alarms only at certain time of the day, select from the drop-down list the time zone during which the item activation is reported as an alarm in the Alarm Monitor window. If you select <none>, item activation at any time always results in generating an alarm.

Alarm Instruction – Alarm Instruction selected in the drop-down list is displayed in the Alarm Response window when the sending item is in the alarm state.

Normal Instruction – Alarm Instruction selected in the drop-down list is displayed in the Alarm Response window when the sending item is in the normal state.

Other Instruction – Alarm Instruction selected in the drop-down list is displayed in the Alarm Response window when the sending item is in a state other than alarm or normal.

Associated AV Channel – Select the camera to be associated with this alarm. If applicable, this selection overrides the selection made in the Input to camera mapping window.

Associated Real Time Map – Select the Real Time Map to be associated with this alarm. If applicable, this selection overrides the default behavior of the Real Time Map containing the item for the alarm. That is, when you click the Map button in the Alarm Monitor, the associated Real Time Map appears, even if it is different from the Real Time Map containing the alarm item.

3-32


Events Tab

Event 1-4 – You can define up to four events that can be triggered from the Alarm Monitor window whenever the alarm occurs and enters into the alarm queue. To define an event, enter a descriptive name and select a previously configured event from the associated drop-down list.

Escalation Tab

The alarm escalation function constantly monitors all generated alarms that have their escalation options enabled. The escalation level ranges from 0 to 10, where 0 indicates a non-escalated alarm.

The alarm escalation feature provides for two different conditions when an alarm may be escalated:

• If an alarm is generated for a specific alarm category and there are currently no operators logged on to the P2000 system that have privileges to receive alarms for that category

• If an alarm is generated and remains pending for the configured escalation timeout period

If either of these conditions occurs, that alarm is regenerated with an elevated escalation level. The escalation level is incremented by the configured escalation increment value. This process may be repeated multiple times until a high enough escalation level is reached that matches the privileges of a currently logged in operator. If no operators are logged on to the P2000 system, the software regenerates the alarm until the maximum escalation level is reached, and then no further action is taken.

3-33


After an escalated alarm has been completed, the next occurrence of that alarm is created with no escalation level.

Enable – Enables alarm escalation.

Escalation Repeat – Allows for escalation to occur more than once for the alarm. For example, if you set the Escalation Timeout to 30 minutes, and you set the Escalation Increment to 2, every half an hour the escalation value for alarms remaining in a pending state increases by 2 until it reaches the maximum value. If you do not select this option, escalation can occur only once for this alarm.

Escalation based upon visibility – System immediately escalates the alarm by a defined increment if, at the time of occurrence, no operator able to receive alarms from this Alarm Category is logged on.

Escalation Timeout (1 to 1440 minutes) – Enter the time period (in minutes) after which an alarm remaining in a pending state is escalated by the Escalation Increment.

Escalation Increment (1 to 10) – Enter the value by which to escalate an alarm each time the escalation takes place.

3-34


MSEA Tab

In facilities that use the Metasys® system advanced feature, an alarm forwarded to the Metasys system can contain an embedded reference to a Metasys graphic.

MSEA Graphic – Select a pre-defined MSEA Graphic to reference in this alarm. When an alarm is received and displayed by the Metasys system, the Metasys operator can simply click the alarm to display the graphic item associated with the alarm and the item that caused the alarm.

3-35


3-36

DVR/VMS Integration DVR/VMS Operation24-10832-62 Rev. E

4. DVR/VMS OPERATION

DVR/VMS integration operations occur through the AV Player user interface. Associated cameras can be mapped to input points and terminals. The AV Player software is part of the P2000 DVR/VMS integration application and, depending on equipment, provides controls to search and retrieve stored video clips, play live or stored video streams; take and store screen shot images; and control AV switches, CCTV switches, cameras, and presets that are all part of the DVR/VMS system.

NOTE: The number of simultaneous connections allowed per DVR/VMS depends on the protocol and license. For proper functioning, do not exceed the maximum number of allowed connections. When running, the P2000 AV Service, CCTV Server, and every instance of AV Player each consume one connection.

USING THE P2000 SOFTWARE FUNCTIONS

The Digital Video integration can use the following standard P2000 software features:

• Event Actions – The equipment connected to the system is capable of responding to event actions launched from the P2000 software. For more information, see DVR/VMS Event Actions on page 4-2. Refer also to the Creating Actions section in the P2000 Software User Manual.

• Menu Permissions – P2000 administrators can configure menu permissions for AV Configuration items, Input to Camera, and AV Player.

• Audit Trail – The audit trail lists changes to the database. You can use the standard P2000 audit trail report for details.

• Partitioning – If you are using partitioning, all items associated with DVR/VMS integration should be in the same partition. However, the software does not check to prevent a user from setting up partitions that are not practicable. For example, if you assign an AV switch and camera preset to Partition A, and the camera itself is assigned to Partition B, the operator logged on to Partition A would neither see the camera nor be able to run the preset unless they were assigned as Public.

4-1


DVR/VMS EVENT ACTIONS

A key advantage to the DVR/VMS integration is that it allows you to use the capabilities of the DVR/VMS equipment connected to the P2000 system as an integral part of the P2000 Event application.

With DVR/VMS integration, you can:

• Define event actions that start or stop camera recording

• Define event actions that activate the camera preset

• Display the image from a particular camera on a selected monitor

• Adjust the recording quality (resolution/frame rate) of a selected camera when a specific event occurs

• Launch an AV player on a selected workstation

• Define events that start recording and archiving at the same time

NOTE: When defining DVR/VMS integration event actions to adjust the camera recording quality, refer to the manufacturer’s documentation for the ideal resolution/frame rate combination quality factor.

You can use two standard action categories in the P2000 events to create a DVR/VMS event action:

• Audio-Visual Action Category – In this method you select the camera by the name you assigned when configuring the Audio-Visual item. The namespace tag is selected from a drop-down list of action types.

OPC Server Action Category – Choose this method if the action that you wish to define is not available from the Audio-Visual category, or you have not fully configured the DVR/VMS equipment from the CCTV/AV Configuration window. In this method, you select or browse for an OPC Server tag. The action type for OPC Server is OPCWrite. For details of the namespace tags and their values, see Appendix A: Namespace Definitions. You can access both categories on the Action window.

To open the Action window:

1. From the P2000 menu, select Events > Configure Events.

2. On the Configure Events window, click Add.

3. On the Configure Events - Add window (under Actions), click Add. The Action window opens.

4-2


Since operators create the DVR/VMS event actions in the same way as any other event action, for detailed instructions refer to Creating Actions and OPC Server Event Actions in the P2000 Software User Manual. The following sections provide a quick reference on how to create both types of event actions.

To configure an OPC Server event action using the Audio-Visual category:

1. From the action Category drop-down list, select Audio-Visual

2. Specify the Delay.

3. From the action Type drop-down list, select the action to be performed.

4. Depending on the action type selected, one or more additional drop-down lists may appear allowing you to define the details of the action. For example, the Camera Start Recording action type requires that you select a camera to perform the defined action.

5. Click OK to save your selections.

The new event action appears in the Actions list of the Configure Events - Add window.

To configure an OPC Server event action using the OPC Server category:

1. In the Action dialog box, select OPC Server from the Category drop-down list. The software automatically selects OPCWrite as the type by default.

4-3


2. To select an OPC Tag, click the browse button.

3. In the Items dialog box:

• Select or browse for the OPC server.

• Select the Data Type (Use native type, which is the default selection, displays all tags).

• In the Browse items box, select the item and the tag for the event action. The selected item appears in the Item Name field.

• Click OK.

4-4


The OPC Tag appears in the Action window. The PC name and Prog ID are prefixed to the item name.

4. Select the appropriate Data Type from the drop-down list and enter the Value that applies to the OPC Tag. Click OK.

The new event action appears in the Actions list of the Configure Events - Add window.

DISPLAYING DVR/VMS ITEMS IN THE REAL TIME MAP

After you configure the DVR/VMS hardware platform and create events, set up the P2000 Map Maker application to define the items you intend to use to display live or recorded video from a real time map.

To place device icons on a Real Time Map:

1. From the P2000 Main menu, select Config > Map Maker. The Map Maker window appears.

4-5


2. Select the map where you wish to place the icons, and click Edit. The Map Editor window appears.

For detailed instructions on creating maps, refer to the Creating a Real Time Map section of the P2000 Software User Manual.

When you open the Map Editor, map icons representing panels, terminals, input points, events, cameras, and other elements appear on the right window pane. You can also define new camera icons, which are available in addition to the default camera icons.

3. To place a camera icon on the map, expand the Camera item. A camera icon appears under it.

4. You can drag and drop new icons to the desired position on the map. For example, you can drag the Camera icon near the door representing where an input point or reader terminal is actually installed. When you release the mouse button, the Properties window appears.

For detailed instructions on placing device icons on a map, refer to the To Place Device Icons on a Real Time Map section of the P2000 Software User Manual.

4-6


5. Once you define the icon’s properties, click OK to close the Properties window. The icon appears on the map.

6. To add Audio-Visual-related events to the map, follow the same procedures using the Event icons. Events can be manually activated by an operator from the Real Time Map, rather than by the trigger conditions set up in the Configure Events window. Icons on the Real Time Map, such as terminals or input points, can also be configured to initiate events that start or stop recording when the input or terminal is activated.

7. When you have added all elements, click OK to close the Map Editor window.

8. Click Done to close the Map Maker window.

4-7


NOTE: Map Maker provides a default camera image icon to display the location of the camera; however, you can use your own icons to create custom image sets. For details, refer to the Adding Image Sets section of the P2000 Software User Manual.

ASSOCIATING CAMERAS TO INPUT POINTS OR TERMINALS

Input to Camera is a tool that defines mappings between an input point or a terminal and a camera (or a camera’s preset).

Input to camera mapping allows you to bring up the camera image from the Alarm Monitor or Real Time list (for this, the preset selection does not apply).

Input to camera mapping does not automatically result in recording. In order to record, as well as make use of the preset selection, you must create a P2000 event.

For example, the operator may want to issue a command to start recording images from a particular camera when someone swipes an invalid card at a reader monitored by that camera. Such action is made possible by the mapping information that describes which camera is monitoring which alarm/event source.

All system configuration items such as terminals, input points, AV switches, cameras, and presets must be registered in the P2000 database before using the Input to Camera application.

To associate cameras with input points or terminals:

1. From the P2000 Main menu, select Options > CCTV/AV > Input to Camera. The Input to Camera Mapping window appears.

4-8


2. Click Add. The Add input/terminal to camera mapping window appears.

3. In the Available Input Points/Terminals box, enter the name of the input point or terminal that is associated with a camera, and click the Search button.

As an alternative, you can also enter a filter string. The list box displays all input points and terminals that meet the search criteria. If you do not enter any names or filter strings, and click Search, the list displays all input points and terminals defined in the system.

4. Select the input point or terminal in the list.

5. In the Available Channels box, enter the name or filter string of the camera that is associated with the input point or terminal, and click Search. The list box displays all cameras that meet the search criteria. If you do not enter any names or filter strings, and click Search, the list displays all cameras defined in the system.

6. Select the camera name from the list. The Presets for the selected channel box displays all presets defined on the camera.

7. Select the preset that you want to use for the camera (the preset selection is used only for host events).

8. In the Name box, enter a descriptive name for the mapping so that the system operator can easily recognize it.

4-9


9. The Current Selection box displays the current selection of input point/terminal, camera, and preset. Click OK to add this mapping to the Existing Mapping list.

10. To edit the content of an existing mapping, select the mapping from the list and click Edit. Repeat the same steps.

11. To delete a mapping, select the mapping from the list and click Delete.

12. Click Done to close the Input to Camera Mapping window.

NOTE: The mapping fails if you change the input point or terminal name and do not redefine the mapping using the new values.

LAUNCHING THE AV PLAYER

You can launch the AV Player from the following P2000 applications:

• Real Time List

• Real Time Map

• Alarm Monitor

• Options Menu

4-10


NOTE: For information regarding specific protocols and the AV Player, see Chapter 2: Protocol Integration Details.

Launching the AV Player from the Real Time List

The AV Player allows you to review video associated with selected system transactions.

To launch the AV Player from the Real Time List:

1. Prior to launching the AV Player, you must:

• Associate a terminal or an input point with a camera (see Associating Cameras to Input Points or Terminals on page 4-8)

• Select a message line or alarm from the Real Time List

2. Click Details at the bottom of the window to launch the AV Player in live mode.

As an alternative, you can click the associated drop-down list and select AV Player (Live) to launch AV Player in live mode or select AV Player (Stored) to launch AV Player in video retrieval mode.

4-11


Launching the AV Player from the Real Time Map

You can launch the AV Player from the Real Time Map.

If you have a camera associated with an input point and have this input point on the Real Time Map, you can launch the AV Player to display live or stored video.

You can also connect a PTZ (Pan/Tilt/Zoom) camera to a particular preset or monitor from the Real Time Map by adding an event to the Real Time Map with an associated AV action and allowing this event to be triggered from the pop-up menu. See DVR/VMS Event Actions on page 4-2 for details.

To launch the AV Player from the Real Time Map:

1. Prior to launching the AV Player, you must:

• Associate an input point with a camera through Input/Terminal to Camera mapping.

• Define the items you intend to use to display live or recorded video. See Displaying DVR/VMS Items in the Real Time Map on page 4-5.

2. Right-click a map icon associated with a camera from the Real Time Map.

3. From the pop-up menu, select AV Player (Live) or AV Player (Stored).

Stored videos are available if the input point is in an alarm state. The default time stamp to obtain data is a 90-second retrieval time and a 3-minute duration.

4-12


Launching the AV Player from the Alarm Monitor

To launch the AV Player from the Alarm Monitor:

1. Prior to launching the AV Player, you must associate the alarm message displayed for an input point with a camera through Input/Terminal to Camera mapping.

2. On the Alarm Monitor window, select the specific alarm. The AV button at the bottom of the window becomes active.

3. Click the AV button, and from the pop-up menu, select AV Player (Live) or AV Player (Stored).

Stored videos are available if the input point is in an alarm state. The default time stamp to obtain data is a 90 second retrieval time and a 3-minute duration.

4-13


Launching the AV Player from the Options Menu

This method is the primary means of accessing the AV Player.

To launch the AV Player from the Options menu:

1. From the P2000 Main menu select Options > CCTV/AV > AV Player.

The Select Camera window appears, displaying the configured cameras.

2. Select a camera and click OK. The AV Player window opens.

AV PLAYER COMPONENTS AND FUNCTIONS

The AV Player consists of the following user interface components:

• Main menu

• Video player viewing area

• Tabs to access the camera and switch control panel (the Camera tab), a monitor selection screen (the Monitor tab), a search and retrieval interface (the Search tab), and a pan, tilt, and zoom controller with a presets controller (the PTZ tab)

• Buttons to control AV Player functions and indicate the camera’s recording and PTZ status

4-14


The AV Player window title displays a description of the current video stream, consisting of the OPC Server namespace tags of the AV Player and the respective camera.

Main Menu

The Main menu allows you to save the recording and select display aspect ratio for the video player.

Saving the Recording

The recording can be saved in .bmp or .avi format.

To save the recording in .bmp format:

1. Go to File > Save Picture.

2. Specify the file name and location, and click Save.

To save the recording in .avi format:

1. Go to File > Save Video.

2. Specify the file name and location, and click Save.

Video player

Tabs

Function and indicator buttons

Minimal Features (Less>>) and Full Features (<<More) toggle button Main menu

4-15


Video Display Aspect Ratio

You can choose the video player to retain or not retain the aspect ratio in the recording displayed. You can retain the aspect ratio to prevent distortion of the image.

To adjust the aspect ratio:

1. Go to View > Keep Aspect Ratio.

2. To keep the aspect ratio, select this option (a check mark appears).

To display recording without keeping the aspect ratio, click to clear this option (no check mark appears).

NOTE: Go to View > Properties to view general properties of the AV Player currently played.

Video Player

The video viewing area is an ActiveX® based video player that can render heterogeneous video streams (H.263+ or MPEG-4, and so on) or various video files.

Viewing area with Keep Aspect Ratio selected.

Viewing area with Keep Aspect Ratio not selected. Notice the image distortion.

4-16


AV Player Functions

Play – Plays the recording.

Play speed – Plays the recording with altered speed. From the drop-down list, select 1/2 to play the recording at half speed, or 2 to play the recording at double speed (available for some vendors only).

Stop – Stops playing the recording.

Pause – Pauses playing the recording.

Record – Starts recording the currently viewed live video. The video clip is created on the DVR/VMS (not on the P2000 workstation) and you can later find it from the AV Player Search tab. This feature is only available for some digital video systems.

Rewind – Rewinds the recording.

Go to first frame – Goes to the beginning of the recording.

Go to last frame – Goes to the end of the recording.

Fast forward – Fast forwards the recording.

Export file – Exports a 60-second video clip of currently viewed live or retrieved video (available for some digital video systems). The system saves the video clip as an .avi file and places it in the following folder:


Snap shot – Takes a screen shot bitmap image of a particular frame of the video image. This feature is particularly useful for instant incident reporting. The system automatically saves the file in the following folder:


4-17


Viewing Modes

AV Player has two viewing modes: minimal features and full features. Both display the video viewing area, function and indicator buttons, and the toggle button for switching viewing modes.

To toggle between viewing modes:

1. If you are in the minimal full features mode, click More.

2. If you are in the full features mode, click Less.

Minimal Features Mode

The minimal features mode is the default setting when the AV Player is launched for the real-time rendering of live video.

Audio – Displays the volume control sliding bar. Currently, vendors provide volume control through the system volume. An audio channel must be configured for this button to be activated.

PTZ – Indicates that the camera you are currently monitoring is a PTZ camera.

Recording – Indicates that the camera you are currently monitoring is recording (available for some vendors only).

4-18


Full Features Mode

In addition to the features in minimal features mode, the full features mode provides camera/switch control, video retrieval, monitor selection, and a more ergonomic PTZ control through live mode. Access to the features depends on the menu permissions assigned to the operator.

Live Video Monitoring

For live video monitoring, click the Camera in full features mode of the AV Player.

To play a live video stream:

1. Under the Camera tab, select the AV switch.

2. Select a camera associated with that AV switch (see Creating and Configuring Cameras on page 3-16).

The video player shows a live stream corresponding to the currently selected camera.

4-19


Monitor Selection

For monitor selection, click the Monitor in full features mode of the AV Player.

To select a monitor:

1. Under the Camera tab, select the AV switch.

2. Under the Monitors tab, select the monitor from the list of monitors previously created during the CCTV/AV Configuration (see Creating and Configuring Cameras on page 3-16).

4-20


Video Search and Retrieval

For video search and retrieval, click the Search tab in full features mode of the AV Player. Captured video clips can be searched based on the AV switch, camera ID, and time stamps.

To search for and retrieve a video file:

1. Under the Search tab, select the AV switch that supports the storing and retrieval of video files.

2. Select a camera associated with the AV switch.

3. Specify the start and end time (estimated by duration).

4. Based on the given criteria, a set of video clips is retrieved and played through the VCR control. In addition, any video clips manually created using the VCR record button are displayed in the file selection screen.

5. Select the video file and click Play Selected.

When you request video review from the Alarm Monitor, Real Time Map, or Real Time List, the search criteria is defined automatically.

The VCR controls (play, stop, pause, rewind, go to first frame, go to last frame, and fast forward) are active only during the playing of a stored video. You can also use the slider window pane to quickly display any image within the video clip for the time frame specified.

4-21


PTZ and Presets Control

For PTZ and presets control, click the PTZ tab in full features mode of the AV Player.

To use the PTZ interface:

1. Under the Camera tab, select a supported camera.

2. Select the PTZ tab.

Pan/Tilt – Click and hold down the mouse on the movement control square in the Pan/Tilt area to move the selected camera. The movement control returns to the center of the Pan/Tilt area when at rest. The position of the camera is as is and not centered. To pan the camera, move the movement control along the horizontal; to tilt the camera, move the camera along the vertical. Movements between the horizontal and vertical are proportional (the further from the center, the faster the movement).

4-22


You can also move the selected camera using the nudge arrows on each side of the Pan/Tilt area. The camera moves at a speed defined by the nudge factor. The nudge factor is a value in the range of 1 to 100, which determines the speed of the camera movements (the larger the number, the faster the camera moves).

Wiper – There are two wiper buttons. The left button switches off the camera wiper; the right button switches on the camera wiper.

Washer – There are two washer buttons. The left button switches off the camera washer; the right button switches on the camera washer.

Light – There are two light buttons. The left button switches off the camera light; the right button switches on the camera light or other relay device.

Zoom – There are two Zoom buttons. The left button zooms out from the object; the right button zooms in on the object.

Focus – There are two Focus buttons. The left button focuses on near objects; the right button focuses on far objects.

Iris – There are two Iris buttons. The left button closes the iris; the right button opens the iris.

If there are configured presets (from the AV configuration), the Preset drop-down list is filled with presets that are configured for the currently selected camera.

To activate a preset:

A preset operates only if the equipment supports the relevant functions.

1. Under the Camera tab, select an AV switch.

2. Select the PTZ camera associated with this switch.

3. Select the PTZ tab.

4. Select a preset from the drop-down list.

4-23


5. Click Activate.

TROUBLESHOOTING P2000 AV PLAYER

See Table 4-1 for help troubleshooting issues with the P2000 AV Player.

Table 4-1: P2000 AV Player Troubleshooting

Issue Resolution

AV Player cannot connect to the DVR/VMS.

Check you network connections and logon credentials.

I have created new objects (cameras, presets) in the AV Player, but when I run the AV Player application, those objects do not appear.

The AV Player creates a database table for each item and also creates a valid namespace entry for each object. Changes to the configuration settings do not take effect until a P2000 operator restarts the CCTV Server using the P2000 Service Control tool. So, if the service is currently running, you must stop and then restart it.

I am using multiple DVRs or VMSes. Some can connect to the AV Player, but others are unable to connect.

DVR is actually a type of modified computer, while VMS uses a computer platform. Therefore, make sure that all of the DVRs/VMSes belong to the same workgroup and domain.

The AV Player is working, but the live video feed shows the wrong date and time.

Time synchronization is critical in any DVR/VMS installation. Make sure that all of the DVRs/VMSes have the correct time, date, and regional settings. Also, verify that they all belong to the same domain.

I have an acknowledged alarm in the Alarm Monitor. When I select a stored video for this alarm, the AV Player plays a video clip recorded at a later time.

Videos for the acknowledged alarms play at the time of the acknowledgement, not at the time the alarm occurred.

4-24

DVR/VMS Integration Namespace Definitions24-10832-62 Rev. E

A. NAMESPACE DEFINITIONS

This chapter contains information about the DVR/VMS namespace definitions.

FLAGS

The following flags are used in the namespace tag tables.

Table A-1: Flags

When a value in the namespace of the DVR Runtime Server changes, the class representing the folder object checks its validity. Assuming that the new value is correct, the class subsequently issues the required command to the appropriate vendor protocol through the vendor neutral interface defined by DVR Vendor X Implementation class. The vendor protocol then performs the required action and informs the initiating class when the action has been completed. The subsequent sections list the valid values, action required, and any action to be taken by the class on command completion for each class together with other associated data.

Flags Meaning

A If set to autorepeat AND flags are WZ, Z is ignored

C Configured Value (persistence required)

D Decrements/Increments towards 0 until value becomes 0

R Readable

U The value is periodically scanned from the device and the value is updated to reflect the value in the device. If the DVR/VMS vendor protocol does not allow the scanning of this information, then the DVR vendor module updates the value after transmitting the command to the AV switch.

If updated by the vendor module, the OPC status information for the data item should return UNCERTAIN rather than GOOD.

W Writable

Z Server resets this value to 0 as soon as it processes the value written to it by a client.

A-1


DVR/VMS NAMESPACE TAGS

The % sign identifies the DVR/VMS device object, which is a four digit number from 0001 to 9999.

Table A-2: DVR/VMS Namespace Tags

Tag Name Type Flags Description

D%.Exists Integer CR Only present if a configuration database exists. The parameter is set in the database to establish that the DVR/VMS exists.

D%.Description VarChar CR -

Access Rights

D%.Partition Integer CR Database Partition

D%.Public Integer CR -

Communications

D%.DVRSiteName VarChar CR Site name of DVR/VMS installation

D%.DVRID Integer CR DVR ID: last three digits of IP Address as a number automatically assigned by a database.

D%.DVRName VarChar CR DVR/VMS Name associated with DVR ID

D%.Type Enum CR 1 = Serial

2 = TCP/IP

D%.StreamingServerIPAddress

VarChar CR IP address of video streaming and playback server on the network. Need for video playback.

D%.StorageServerIPAddress

VarChar CR IP address of video storage server on the network. Need for access physical storage.

D%.DataServerIPAddress

VarChar CR IP address of database server on the network. Need for search and retrieval of video clips.

D%.Error Integer R Error indicator, used by the DVR/VMS server to indicate communication problems.

D%.DVRType VarChar CR JC.AVGenetec

JC.AVMilestone

JC.AVMilestoneMIP

A-2


Archive

D%.ArchiveDeviceExist Integer CR Only present if a configuration database exists. The parameter is set in the database to establish that the jukebox exists.

D%.ArchiveName VarChar CR Human readable name of archive device

D%.ArchiveSize Integer CR Maximum size of archive device

D%.NumArchiveDevice Integer CR Number of archive devices

D%.ArchiveHasMedia VarChar CR -

Cameras

D%.CameraGroup Integer CR Number of camera groups configured.

D%.CameraGroupMax Integer CR Number of camera groups to be created in the namespace for this DVR/VMS.

1 to CameraGroupMax = the number of camera group instances/branches needed to match this definition (that is, the names Camera0001 to Camera<CameraMax> must exist).

-1 = check with vendor during initialization.

D%.CameraCount Integer CR Number of cameras configured

D%.CameraMax Integer CR Number of cameras to be created in the namespace for this DVR/VMS.

1 to CameraMax = the number of camera instances/branches needed to match this definition (that is, the names Camera0001 to Camera<CameraMax> must exist).


D%.ActiveCameraExists Integer CR Present only if a configuration database exists. Not supported in current release.

D%.SetActiveCamera Integer RW Present only if a configuration database exists. Not supported in current release.

Channels

D%.ChannelGroup Integer CR Number of channel groups configured.


A-3


D%.ChannelGroupMax Integer CR Number of camera groups to be created in the namespace for this DVR/VMS.

1 to ChannelGroupMax = the number of camera group instances/branches needed to match this definition (that is, the names Channel0001 to Channel<CameraMax> must exist).


D%.ChannelCount Integer CR Number of channels configured.

D%.ChannelMax Integer CR Number of channels to be created in the namespace for this DVR/VMS.

1 to ChannelMax = the number of camera instances/branches needed to match this definition (that is, the names Camera0001 to Camera<ChannelMax> must exist).


D%.ActiveChannelExists Integer CR Only present if a configuration database exists

D%.SetActiveChannel Integer RW Only present if a configuration database exists

Status Info

D%.CameraInfoUpdate Integer WZ These commands receive an information update for the equipment associated with the AV switch.

Unfortunately, the protocol specification is not very specific what information is returned. This is especially the case for:

Camera number info

Time date info

Special message info

D%.MonitorInfoUpdate Integer WZ

D%.AlarmInfoUpdate Integer WZ

D%.CameraNumberInfoUpdate

Integer WZ

D%.TimeDateInfoUpdate Integer WZ

D%.SpecialMessageInfoUpdate

Integer WZ


A-4


DVR/VMS CHANNEL NAMESPACE TAGS

To the DVR/VMS, a channel is a camera and a video input stream, which can be recorded, stored, and later recalled for playback. A channel has some characteristics of a camera (that is, PTZ controls), and other characteristics of a VCR (record, playback, and so on).

The sign # identifies the channel number, which is a four digit number starting from 0001 to 9999.

D%.CameraAttributeUpdate

Integer WZ These commands request an attribute update for the equipment associated with the AV switch.

Unfortunately, the protocol specification is not very specific what information is returned. This is especially the case for:

Camera number info

Time date info

Special message info

D%.MonitorAtrtributeUpdate

Integer WZ

D%.AlarmAttributeUpdate

Integer WZ

D%.CameraNumberAttributeUpdate

Integer WZ

D%.TimeDateAttributeUpdate

Integer WZ

D%.SpecialMessageAttributeUpdate

Integer WZ

Feature Check

D%.PresetExists Integer CR 0 = not supported

1 = supported

2 = check with vendor during initialization

Note: D%.CameraAuxiliaryExists is not supported in the current release.

D%.PresetStopExists Integer CR

D%.PresetRecordExists Integer CR

D%.PresetPlayExists Integer CR

D%.CameraAuxiliaryExists

Integer N/A

D%,CameraAuxiliaryPlayExists

Integer CR

D%.CameraAuxiliaryStopExists

Integer CR

D%.PresetMax Integer CR 0 = not supported

-1 = check with vendor during initializationD%.CameraAuxiliaryMax Integer CR


A-5


Table A-3: DVR/VMS Channel Namespace Tags


Ch#.Exists Integer CR Only present if a configuration database exists. The parameter is set in the database to show that this camera exists.

Ch#.Description VarChar CR Variable length string that describes the camera. If the server does not contain a database, or does not persist definitions, this property is not used.

Ch#.PathDS VarChar CR Variable length string that describes the access path of the camera.

This path information is used in the Video Player Client.

Access Rights

Ch#.Partition Integer CR Managing partitions. Not supported in the current release.

Ch#.Public Integer CR Define public accessibility. Value: 1 for Yes.

Ch#.ClientLockId 32 char WR Can be used by a client to lock access to this camera

General Commands/Status

Ch#.GeneralString VarChar CWR A string of characters written to the specific camera to annotation of all that is being recorded or monitored from it.

Ch#.ChannelStatus Integer WRU Bit-flagged field to define the equipment status. The status flags are to be defined at a later stage.

The status field should only be used for those status identifications that are not part of the original item list.

Ch#.StartRecordExists Integer CR Only present if a recording configuration exists. Default value: 1

Ch#.StartRecord Integer RW Issue start recording. Only present if a configuration database exists.

Ch#.StopRecordExists Integer CR Only present if a configuration database exists.

Ch#.StopRecord Integer RW Stop recording on the channel. Only present if a configuration database exists.

Ch#.RewindExists Integer CR Only present if a configuration database exists.

A-6


Ch#.Rewind Integer RW Rewind playback video. Only present if a configuration database exists.

Ch#.PauseExists Integer CR Only present if a configuration database exists.

Ch#.Pause Integer RW Pause playback video. Only present if a configuration database exists.

Ch#.FastForwardExists Integer CR Only present if a configuration database exists.

Ch#.FastForward Integer RW Only present if a configuration database exists.

Ch#.StartPlaybackExists Integer CR Only present if a configuration database exists.

Ch#.StartPlayback Integer RW Can perform manual stop on the channel. Only present if a configuration database exists.

Ch#.StopPlaybackExists Integer CR Only present if a configuration database exists.

Ch#.StopPlayback Integer RW Stop playback. Only present if a configuration database exists.

Ch#.ArchiveExportExists Integer CR Only present if a configuration database exists.

Ch#.ArchiveExport Integer RW Only present if a configuration database exists.

Ch#.SetPreAlarmExists Integer CR Only present if a configuration database exists.

Ch#.SetPreAlarm Integer RW Issue PreAlarm configured in DVR/VMS. Only present if a configuration database exists.

Ch#.SetPostAlarmExists Integer CR Only present if a configuration database exists.

Ch#.SetPostAlarm Integer RW Issue post alarm configured DVR/VMS. Only present if a configuration database exists.

Ch#.SetVideoLossAlarmExists

Integer CR Only present if a configuration database exists.

Ch#.SetVideoLossAlarm Integer RW Only present if a configuration database exists.

Ch#.SetDetectExists

Integer CR Only present if a configuration database exists.


A-7


Ch#.SetDetectAlarm

Integer RW Send detection alarm. Only present if a configuration database exists.

Ch#.SetFrameRateExists Integer CR Only present if a configuration database exists.

Ch#.SetFrameRate Integer RW Change frame rate. Only present if a configuration database exists.

Ch#.SetResolutionExists Integer CR Only present if a configuration database exists.

Ch#.SetResolution Integer RW Change resolution, DVR/VMS must support this function. Only present if a configuration database exists.

Predefining Camera Positions

Ch#.PresetExists Integer CR If configuration database exists, this defines if this camera has this ability.

0 = not supported

1 = supported

2 = check with AV switch during initialization

Ch#.PresestCount Integer CR Number of total presets defined

Ch#.PresetMax Integer CR If the channel supports presets, this value defines the maximum number of presets. Presets are numbered from 1 to (PresetMax).

Ch#.PresetStopExists Integer CR 0 = not supported

1 = supported


Ch#.PresetStop Integer WZ Clears the preset <integer>

Ch#.PresetRecordExists Integer CR 0 = not supported

1 = supported


Ch#.PresetRecord Integer WZ Defines the current camera position as preset <integer>

Ch#.PresetPlayExists Integer CR 0 = not supported

1 = supported


Ch#.PresetPlay Integer WR Forces channel to pre-specified position

Camera Movements


A-8


Ch#.TiltExists Integer CR If configuration database exists, this defines if this camera has this ability.

Ch#.Tilt Signed Integer

AWR Moves channel vertically with given speed.

< 0 down

> 0 up

Ch#.PanExists Integer CR If configuration database exists, this defines if this camera has this ability.

Ch#.Pan Signed Integer

AWR Moves channel with this speed.

< 0 left

> 0 right

Ch#.StopAllPT Integer WZ Writing a one to this property stops all Pan and Tilt commands that have not yet been issued.

Camera Lens Control

Ch#.ZoomExists Integer CR If a configuration database exists, this defines if this camera has this ability.

Ch#.Zoom Integer AWR Writing a positive number zooms wide; a negative number zooms narrow; a 0 stops zoom.

Ch#.FocusExists Integer CR If a configuration database exists, this defines if this camera has this ability.

Ch#.Focus Integer AWR Writing a positive number focuses near; a negative number focuses far; a zero stops focus.

Ch#.IrisExists Integer CR If a configuration database exists, this defines if this camera has this ability.

Ch#.IrisAutomatic Integer CWR Write one to this property to set the iris to automatic.

Ch#.Iris Integer AWR Writing a positive number drives Iris open; a negative number drives it closed; a zero stops the iris.

Ch#.StopAllZFI Integer WZ Writing one to this property stops all zoom, iris and focus commands.

Ch#.LensSpeedMax Integer CR The maximum speed of the lens. If 1, then the camera does not support variable speeds.

Ch#.LensSpeed Integer CWR Set the lens speed (0 to LensSpeedMax).

Other Camera Commands


A-9


Ch#.Arm Integer WZ Arms the camera

Ch#.Disarm Integer WZ Disarms the camera

Ch#.IsArmed Integer RWU -

Ch#.StatusExists Integer CR If a configuration database exists, this defines if this camera has this ability.

Ch#.WiperExists Integer CR If a configuration database exists, this defines if this camera has this ability.

Ch#.Wiper Integer WR Turns wipers on or off

Ch#.WasherExists Integer CR If a configuration database exists, this defines if this camera has this ability.

Ch#.Washer Integer WR Activate washers

Ch#.LightExists Integer CR If a configuration database exists, this defines if this camera has this ability.

Ch#.Light Integer WR Turns lights on or off

Auxiliary

Ch#.AuxiliaryExists Integer CR 0 = not supported

1 = supported


Ch#.AuxiliaryCount Integer CR -

Ch#.AuxiliaryMax Integer CR -1 = check with AV switch during initialization

Ch#.AuxiliaryPlayExists Integer CR 0 = not supported

1 = supported


Ch#.AuxiliaryPlay Integer AWZ Sets the auxiliary <integer>.

Autorepeat is not yet available for this tag

Ch#.AuxiliaryStopExists Integer CR 0 = not supported

1 = supported


Ch#.AuxiliaryStop Integer WZ Clears the auxiliary <integer>


A-10

We welcome your comments at [email protected].

Security Solutions(805) 522-5555

www.johnsoncontrols.com

Documents

P2000 DVR/VMS Integration Manual€¦ · 02/10/2002 · 7.0 6.14 7.0 N/A Aimetis Symphony™ 6.13 6.14 7.0 6.14 7.0 Version 6.x only: Do not install the Aimetis client on the same