Install Guide

IndigoVision
Control Center
Installation Guide
Control Center
T HIS MANUAL WAS CREATED ON 09 APRIL 2014.
DOCUMENT ID: IU-SMS-MAN001-17
Legal Considerations
LAWS
THAT CAN VARY FROM COUNTRY TO COUNTRY MAY PROHIBIT CAMERA SURVEILLANCE . P LEASE ENSURE THAT THE RELEVANT LAWS
ARE FULLY UNDERSTOOD FOR THE PARTICULAR COUNTRY OR REGION IN WHICH YOU WILL BE OPERATING THIS EQUIPMENT. INDIGO VISION
LTD. ACCEPTS NO LIABILITY FOR IMPROPER OR ILLEGAL USE OF THIS PRODUCT.
Copyright
COPYRIGHT INDIGO VISION LIMITED. ALL RIGHTS RESERVED.
T HIS MANUAL IS PROTECTED BY NATIONAL AND INTERNATIONAL COPYRIGHT AND OTHER LAWS . UNAUTHORIZED STORAGE , REPRODUCTION,
TRANSMISSION AND/OR DISTRIBUTION OF THIS MANUAL , OR ANY PART OF IT, MAY RESULT IN CIVIL AND/OR CRIMINAL PROCEEDINGS .
INDIGO V ISION IS A TRADEMARK OF I NDIGO V ISION LIMITED AND IS REGISTERED IN CERTAIN COUNTRIES . SMS4, CAMERA G ATEWAY , AND
MOBILE CENTER ARE UNREGISTERED TRADEMARKS OF INDIGO VISION LIMITED. ALL OTHER PRODUCT NAMES REFERRED TO IN THIS MANUAL
ARE TRADEMARKS OF THEIR RESPECTIVE OWNERS .
SAVE
AS OTHERWISE AGREED WITH INDIGO VISION
LIMITED AND /OR INDIGO VISION , I NC., THIS MANUAL IS PROVIDED WITHOUT EXPRESS
T O THE FULLEST EXTENT PERMITTED BY APPLICABLE LAWS , I NDIGO V ISION LIMITED
AND INDIGO VISION , I NC. DISCLAIM ALL IMPLIED REPRESENTATIONS , WARRANTIES , CONDITIONS AND/ OR OBLIGATIONS OF EVERY KIND IN
RESPECT OF THIS MANUAL . ACCORDINGLY , SAVE AS OTHERWISE AGREED WITH INDIGO V ISION L IMITED AND/OR I NDIGO VISION , INC., THIS
MANUAL IS PROVIDED ON AN AS IS , WITH ALL FAULTS AND AS AVAILABLE BASIS . PLEASE CONTACT INDIGO VISION LIMITED ( EITHER BY
POST OR BY E - MAIL AT PARTNER. SUPPORT@INDIGOVISION .COM ) WITH ANY SUGGESTED CORRECTIONS AND /OR IMPROVEMENTS TO THIS
MANUAL .
REPRESENTATION AND /OR WARRANTY OF ANY KIND .
SAVE AS OTHERWISE AGREED WITH I NDIGO V ISION LIMITED AND/ OR I NDIGO VISION , I NC ., THE LIABILITY OF I NDIGO VISION LIMITED AND
INDIGO VISION, INC. FOR ANY LOSS ( OTHER THAN DEATH OR PERSONAL INJURY ) ARISING AS A RESULT OF ANY NEGLIGENT ACT OR OMISSION
BY I NDIGO V ISION L IMITED AND /OR I NDIGO V ISION, I NC . IN CONNECTION WITH THIS MANUAL AND /OR AS A RESULT OF ANY USE OF OR
RELIANCE ON THIS MANUAL IS EXCLUDED TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAWS .
Contact address
IndigoVision Limited
Charles Darwin House,
The Edinburgh Technopole,
Edinburgh,
EH26 0PY
Installation Guide - v17
TABLE
OF
CONTENTS
Legal Considerations
Copyright
Contact address
2
2
2
About This Guide
System configurations
IndigoVision documentation
Safety notices
7
7
7
NVR-AS Installation
System specifications
NVR-AS operating system specification
Anti-virus software
Step 1: Prepare your video library
Recording onto a local drive
Recording onto a network drive
Step 2: Install the NVR-AS
Upgrading the NVR-AS
9
9
10
10
10
10
10
11
Control Center front-end application Installation
13
Control Center front-end application operating system specification

Audit logging
Installation procedure
Control Center front-end application
Incident Player
Site database overview
Use a segmented site database
Choosing the location of the site database
Partner branding
Windows firewall
Turning off the firewall
Creating firewall exceptions
Unattended installation
Installer properties
Prerequisites
Examples
13
13
13
14
18
18
19
19
20
20
20
20
20
21
21
22
Control Center Client front-end application Installation

Control Center Client
The Control Center Client site database
Windows firewall
23
23
23
24
24
Control Center
Prerequisites
Examples
24
24
25
26
Camera Gateway Installation
27
Camera Gateway overview

Intended use
Prerequisites
Installation
27
27
27
28
28
28
Mobile Center Service Installation
31
Overview
Compatibility
Prerequisites
IIS Configuration on Windows Server 2008 R2
IIS Configuration on Windows Vista and Windows 7
IIS Configuration on Windows Server 2003
Windows 7, Windows Server 2008 R2, Windows Vista
Windows Server 2003
Using a remote site database in a workgroup
Configuration
Download and configure the Mobile Center app
Deregister a device
Change the Mobile Center Service url
Change the port on Windows 7, Windows Server 2008 R2, and Windows Vista systems
Access Mobile Center Service from a public network
Troubleshooting
IndigoVision Firewall Requirements
39
39
40
40
40
43
Ports required by 8000, 9000, 11000 Range cameras and encoders

Ports required by BXRange cameras
Ports required by Ultra Range cameras
Ports required by 8000 and 9000 Range receivers
Ports required by alarm panels
Ports required by an NVR-AS
Ports required by an NVR-AS 3000
Ports required by Windows NVR-AS
Ports required by Bandwidth Manager
37
37
39
Microsoft SQL Server Express 2008 installation fails to complete

The IndigoVision MobileCenter Administration page cannot be displayed
Upgrading mobile device to iOS 7
Mapped drive is not displayed when browsing for a remote site database
Site database cannot be edited
31
31
31
32
32
32
33
33
33
35
36
36
37
37
37
43
44
44
45
46
46
47
48
48
Control Center
Ports required by Control Center front-end application

Ports required by Camera Gateway
Ports required by Video Stream Manager (VSM)
Ports required by Mobile Center Service
Ports required by Mobile Center app
Video stream configuration port usage
NVR-AS Post-Installation Network Drive Configuration

Creating a user account
Changing the video library folder
Restarting the NVR-AS
Migrating from Control Center 3

Network Video Recorders and Alarm Servers
NVR-AS compatibility
Upgrade to the latest NVR 3 release
Upgrade to the latest Control Center 3 release
Upgrade to the latest version of Control Center front-end application
Upgrade to NVR-AS 4
Migrate alarm sources
Re-configure binary inputs on IndigoVision devices
Planning your migration of 3.x installation alarm sources
Features not supported in IndigoVision Control Center
Manual deletion of alarms from the alarm log
Tamper alarms
Assign alarms
Downgrading an NVR-AS
Installing a Windows NTP server

Installation and configuration
48
49
49
50
50
50
53
53
53
54
55
55
55
56
56
56
56
57
57
58
59
61
61
61
61
61
63
63
Control Center
ABOUT THIS GUIDE

This guide details how to install all components of IndigoVision Control Center.
IndigoVision Control Center is a powerful and easy-to-use software solution that enables you
to manage all your video surveillance operations and investigate security events quickly and
effectively in one integrated platform.
The Control Center suite consists of a number of applications that provide a complete end-toend IPsecurity solution.
System configurations
When using the Windows NVR-AS application, you can choose a system configuration to
match your requirements:
The Control Center front-end application and the NVR-AS installed on the same
computer for small systems only
The Control Center front-end application installed on one or more computers and an
NVR-AS installed on one or more different computers (recommended)
For information about requirements for Windows NVR-AS, please refer to the Windows
NVR Specification Guide
For information about specifying a system for Control Center, see the Control Center
Performance Guide
IndigoVision documentation
IndigoVision product documentation, including hardware guides and configuration guides, is
available to authorized partners via the IndigoVision website.
For a list of the new features for each Control Center release, please refer to the Release
Note available from the IndigoVision website
Safety notices
This guide uses the following formats for safety notices:
Indicates a hazardous situation which, if not avoided, could result in death or serious injury.
Indicates a hazardous situation which, if not avoided, could result in moderate injury, damage
the product, or lead to loss of data.
1 About This Guide
Control Center
Indicates a hazardous situation which, if not avoided, may seriously impair operations.
Additional information relating to the current section.
NVR-AS INSTALLATION
This chapter details how to install the Windows Network Video Recorder/Alarm Server
(NVR-AS).
IndigoVision recommends that you install your NVR-AS on a server-style system, with a
server network adaptor and server disk systems.
IndigoVision strongly recommends the use of disk redundancy technology such as RAID to
provide a single large partition to the NVR-AS.
For more information about requirements for Windows NVR-AS, please refer to the
Windows NVR Specification Guide
NVR-AS operating system specification

We recommend that you use the following guidelines for the NVR-AS PC or server operating
system.
Table 1:
Supported Operating Systems

Operating System
Notice
Supported
Windows Server 2012
Windows Server 2008 R2 x64
Y (recommended)
Windows 8
Y (small systems only - up to 16 streams)
Windows 7
Y (small systems only - up to 16 streams)
Other
IndigoVision recommends that you use Windows Server 2008 R2 x64 when using the
Windows NVR-AS.
If your NVR-AS is to be used to record more than 16 streams of video or process alarms
from more than 100 devices, we recommend using Windows Server 2012 or Windows
Server 2008 R2.
2 NVR-AS Installation
Control Center
Anti-virus software
It is possible to run anti-virus software on the same machine as the IndigoVision Windows
NVR-AS. However, IndigoVision recommends that the VideoLibrary directory (containing
.vmf recording files) should not be automatically checked while recordings are being made as
this could disrupt disk performance, possibly resulting in recordings with lost frames.
Scheduling of automatic scans should also be carefully planned with regard to a possible
overload of the server CPU. If the virus checker overloads the CPU then the NVR-AS may
again lose frames from recordings.
Step 1: Prepare your video library

During installation you are asked for a path to the Video Library. This is the folder where the
video files are stored.
Caution
The NVR- AS Video Library should always be on a separate drive from the NVR-AS
configuration data directory, and the NVR-AS configuration directory should always be
on a local hard disk.
Recording onto a local drive

If you plan to store your recordings on a local drive, these should be stored on a partition with
as much disk space as possible, and preferably not on the system partition.
Caution
IndigoVision strongly recommends the use of disk redundancy technology such as

RAID to provide a single large partition to the NVR-AS.
Recording onto a network drive

If you plan to store NVR-AS recordings on a network drive, you must first select a temporary
location on a local disk. After installation, use the NVR-AS Administrator program to specify
a permanent location.
For more information, see "NVR-AS Post-Installation Network Drive Configuration" on
page 53.
Step 2: Install the NVR-AS

If you have a Windows NVR-AS licence, insert the licence dongle into the USB port of the
PC or server. If you do not, you can still install the Windows NVR-AS, however, only one
video stream will be available for demonstration purposes.
To install the NVR-AS:
1. Insert the licence dongle into the USB port of the PC or server.
Notice
10
You can insert a licence dongle after installation. It may take several minutes for the
licence to register with the software.
Control Center
2. Insert the IndigoVision Control Center CD into the CD drive of the PC or server on
which you are installing the NVR-AS application. The IndigoVision Control Center
install screen opens.
If the install screen does not open automatically, double-click the Installer.exe file in
your Windows Explorer window, or use the Run option on the Windows Start menu
and enter the path to the Installer.exe file on the CDROM.
3. Click Install for the NVR-AS component. The NVR-AS Installation wizard opens.
4. Click Next. The End-User Licence Agreement dialog opens.
5. Read the agreement and select the check box to accept the agreement. Click Next.
The Custom Set-up dialog opens.
6. Select the way you want features to be installed, and click Next. Then click Install.
The NVR-AS installation begins.
After a period, the NVR-AS Administrator application opens.
7. Enter the server (NVR-AS) name and location as required, then click Next.
These are the name and location that are used in Control Center applications.
8. Specify the path to the video and configuration data, then click Next.
9. Configure the network settings, then click Next.
If the NVR-AS is using IP based storage, such as an iSCSI SAN, it is useful to define
the IP address.
10.Configure the disk space management setting, then click Next.
Notice
If you are recording at a high bit rate, you may want to set the Maximum Chunk
Size at a higher value to limit the number of recordings that the NVR-AS and
Control Center have to manage.
The maximum length of a chunk is limited to four hours of footage.
Enable Tamper protection on recordings to verify that recordings made by the

NVR have not been tampered with.
Tamper Protection has an impact on performance. Enabling this feature will
increase CPU usage. Consider the capabilities of your NVR-AS server before
enabling this option.
Enable video thinning to reduce the storage requirements at the expense of full
motion video.
11.Configure the alarm management settings, then click Next.

Notice
When alarms are reaped, any activations that contributed to those alarms are also
reaped.
12.Configure the email settings to enable email actions, then click Next.
13.Click Finish. The NVR-AS service starts automatically. Click OK to confirm.
14.The IndigoVision NVR-AS Set Up wizard is displayed. Click Finish to complete the
installation.
Upgrading the NVR-AS

If you are upgrading an existing NVR or NVR-AS (prior to version 11.0), you will not be able to
upgrade without inserting a valid Windows NVR-AS licence dongle.
Contact IndigoVision if you do not have a Windows NVR-AS licence dongle.
11
12
Control Center
CONTROL CENTER FRONT-END APPLICATION

INSTALLATION
This chapter describes how to install the Control Center front-end application and Incident
Player application. It also explains how to configure a Windows firewall to allow correct
operation of the Control Center front-end application and/or the NVR-AS.
For information about specifying a system for Control Center, refer to the "Control Center
Performance Guide"
Control Center front-end application operating system

specification
We recommend that you use the following guidelines for the Control Center front- end
application PC operating system.
Table 2:

Operating System
Supported
Windows 8 64-bit
Windows 7 64-bit
Other
Audit logging
The IndigoVision Control Center provides an audit logging function that logs many common
user and administrator actions in an ODBC compliant database, for example, Microsoft SQL
Server.
You can configure audit log settings when setting up your site database. Alternatively, you
can configure them at a later stage once you have logged into the Control Center front-end
application. You must be logged in as an administrator to change the audit log settings.
Notice
Audit logging is required to use the Spot Monitor Export function.

For information about setting up audit logging, refer to the Audit Log Reference Guide
This section describes the installation procedures for the Control Center front-end application
and Incident Player.
13
3 Control Center front-end application Installation
Control Center
An alternative variant that does not include site setup functionality, the Control Center Client
front-end application, is also available. Use this variant for installations that should only use
the site database provided by an administrator.
For more information, see "Control Center Client front-end application Installation" on
page 23
Control Center front-end application

You must be logged into Windows as an administrator to install the Control Center front-end
application.
When installing the Control Center front-end application, you have the option to set up your
site database. If you are installing Control Center front-end application on a PC for the first
time, you must set up the site database.
For more information about site databases, see "Site database overview" on page 18
Notice
Your Operating System may require you to authorize this installation.

1. Insert the IndigoVision Control Center CD into the CD drive of the PC on which you
are installing the Control Center front-end application. The IndigoVision Control Center
install screen opens.
2. Click Install for the Control Center front-end application, and follow the on-screen
instructions to complete the installation.
3. If you wish to change the existing site database settings, clear the Use existing site
database settings check box to open the Site Database Setup application.
If you are performing a fresh install of the ControlCenter front-end application, this
check box is unavailable.
Notice
If you do not have Microsoft .NETFramework 4, Microsoft Sync Framework 2.1 Core
Components, or Microsoft Sync Framework 2.1 Provider Services installed, the Control
Center front-end application will notify you, and install them for you before continuing.
Set up a site database

If you cleared the Use existing site database settings check box on the Custom Setup
dialog of the ControlCenter installer, the Site Database Setup application opens and you
must select the site database settings.
You have the following options to set up a site database:
Select Use existing site database if:
you have already created a Control Center site database which you want to use.
you are installing the Control Center front-end application on an operators PC, and
you want it to access a central site database.
Go to see "Use an existing Control Center site database" on page 15
14
Select Create new site database if:
this is the first time you have installed the Control Center front-end application ,
you are installing the Control Center front-end application on only one PC.
Control Center

Go to see "Create a new site database" on page 15
Select Modify current site database if:
you are already using a Control Center site database which you want to modify.
Go to see "Modify the current site database" on page 16
Select Import an existing Control Center 3 site database if:
you are upgrading from Control Center 3 and wish to create a Control Center
compatible site database from your Control Center 3 site database.
Go to see "Import an existing Control Center 3 site database" on page 17
For more information about migrating to IndigoVision Control Center, please refer to
see "Migrating from Control Center 3" on page 55
Caution
The IndigoVision Control Center alarm management configuration is significantly

different to the 3.x configuration. Therefore, migrating from 3.x installations is complex,
and alarms generated in 3.x are not compatible with later versions.
To mitigate risks, ensure you read the migration section and develop a comprehensive
migration strategy. Your system is not fully operational and does not log alarms until the
migration is complete.
Use an existing Control Center site database

Follow this procedure if you have already created a Control Center site database which you
want to use, or you are installing the Control Center front-end application on an operators PC,
and you want it to access a central site database.
1. Select Use an existing site database and click Next.
2. Click Browse and navigate to the folder where the site database is located.
3. Specify a backup site database, if required.
The backup site database is used if the requested site database is unavailable. Select
Specify a backup site database and browse to the folder where the database is
located.
4. Click Next. The Finish dialog opens.
5. Click Finish to complete the site database setup.
Create a new site database

Follow this procedure if this is the first time you have installed the Control Center front-end
application, or you are installing the Control Center front-end application on only one PC.
1. Select Create a new site database and click Next.
2. Click Browse and navigate to where you want to save the database.
3. Select if you want to create a Segmented or Unsegmented database.
A segmented site database stores information for each sub-site in separate segments
of the site database.
For more information about site database types, see "Site database overview" on
page 18
4. If you have selected to create a segmented site database, specify the number of
segments you would like to create.
You can add or remove segments at a later stage, if required.
5. Click Next. The Administrator Details dialog opens.
6. Select the authentication method used to authenticate the administrator.
15
Notice
Control Center
To use Windows authentication, either enter a Windows account or click Browse

and select the required account. When the administrator tries to log in, the Control
Center front-end application checks that the current Windows user is the same as
the Windows user linked to the administrator account. If not, an error message is
displayed and the administrator is not logged on.
To use password authentication, select Use password authentication. Enter a

password, and confirm it. The administrator must enter this password each time
they log in to the Control Center front-end application. This must contain between 8
- 14 alphanumeric characters.
You set up individual user accounts once you log into the Control Center front-end
application.
C
lick Next. The Software Upgrade Plan dialog opens.
7. If you have a Software Upgrade Plan (SUP),select Yes and enter your SUP contract
number.
Otherwise, select No.
Click Next. The Configure Audit Log dialog opens
8. Check Enable audit log to allow Control Center to log user actions to a database, and
select the required option from the drop-down list.
For more information about audit logs, refer to the Audit Log Reference Guide
Notice
Depending on the database you have selected, you may need to select
Compatibility Mode.
If you are using ODBC password authentication to access the database, enter a
username and password.
The username and password must be identical to those you set up when you configured
the database.
Click Next. The Finish dialog opens.
Notice
If you have chosen to enable audit logging, follow the connection setup instructions
provided by the driver. You may be prompted to enter the username and password again.
For more information about setting up an audit log, see the Audit Log Reference Guide.
Modify the current site database

You can modify a Control Center site database at any time using the Site Database Setup
application.
To open the Site Database Setup application outside of the installation process, from the
Start menu select Programs>IndigoVision>Control Center 11 >Site Database Setup.
1. Select Modify current site database and click Next.
The current site database folder is specified on the top of this dialog.
2. Specify the modifications required:
16
Select Upgrade PTZ protocols to upgrade to the latest protocols installed with
Control Center.
Control Center
Caution
If you have customized your PTZ protocols, do not select this option, as your changes
will be lost.
Select to Add segments or Delete a segment and specify the number of

segments to add or the segment to delete.
Click Next. The Software Upgrade Plan dialog opens.

3. If you have a new Software Upgrade Plan (SUP),or would like to modify the existing
one, select Yes and enter your SUP contract number.
Click Next. The Finish dialog opens.
Import an existing Control Center 3 site database

Follow this procedure if you are upgrading from Control Center 3 and wish to create a site
database compatible with later versions of Control Center from your existing Control Center 3
site database.
1. Select Import an existing Control Center 3 site databaseand click Next.
For more information about migrating to the latest IndigoVision Control Center, see
"Migrating from Control Center 3" on page 55
Caution

2. Use the Browse buttons to specify where the existing Control Center 3 site database
is located, and specify where you want to save the new Control Center site database.
3. Select Upgrade PTZ protocols to upgrade to the latest protocols installed with
Control Center.
Caution
will be lost.
number.
Click Next. The Configure Audit Log dialog opens.
5. Select an option and click Next.
Select No audit log if you do not want to log actions.
Select Reuse audit log from imported site database to use the audit log from
the imported site database.
Select Configure new audit log to create a new audit log for this site database.
For more information about audit logs, refer to the Audit Log Reference Guide
17
Notice
Control Center
Depending on the database you have selected, you may need to select
Compatibility Mode.
If you are using ODBC password authentication to access the database, enter a
username and password.
The username and password must be identical to those you set up when you configured
the database.
Notice
If you have chosen to enable audit logging, follow the connection setup instructions
provided by the driver. (You may be prompted to enter the username and password
again.) For more information on setting up an audit log, see the Audit Log Reference
Guide.
Incident Player
The Incident Player application can be used to view incidents you have exported using the
Control Center front-end application.
1. Insert the IndigoVision Control Center CD into the CD drive of the PC on which you
are installing Incident Player. The IndigoVision Control Center install screen opens.
2. Click Install for the Incident Player component, and follow the on-screen instructions
to complete the installation.
Site database overview

The Control Center site database stores the site configuration information. You can enter site
database information during installation, but you can change this at any time using the Site
Database Setup application.
To open the Site Database Setup application outside of the installation process, from the
Start menu select Programs>IndigoVision>Control Center 11 >Site Database Setup.
There are two configuration options for the site database:
Unsegmented Site Database - all site information is stored in a single database. This
option is suited to smaller sites.
Segmented Site Database - information for each sub-site is stored in separate

segments of the site databases (max. 250). This option is suited to large sites with
multiple administrators who are responsible for different sub-sites.
For more information, see "Use a segmented site database" on page 19

For either option, the site database can be stored locally on the PC running the Control Center
front-end application, or centrally on a Windows file server. If you have installed Control
Center front-end application on several PCs you should use a central site database.
For more information, see "Choosing the location of the site database" on page 19
18
Control Center
Notice
Only one Control Center front-end application instance should write to the site database
or a site database segment at any one time.
Use a segmented site database

A segmented Control Center site database stores information for each site directly under the
top site in separate segments of the database. Site wide information, such as user accounts,
apply to all segments.
Operators and administrators can view and manage individual segments, or choose to view
all segments for an overview of the whole site. Full administrators can grant users access to
individual segments.
You should use a segmented site database in the following scenarios:
Large site with many devices (for example, cameras, detectors etc.)
Sites with many thousands of cameras and alarms will benefit from a segmented site
database with improved performance and easier management of devices.
Multiple administrators
For installations where areas are managed independently by different administrators, a
segmented site database enables the site to be organized into independent segments.
Each segment can be administered independently, improving performance and
simplifying management.
Multiple facilities requiring central oversight

When monitoring multiple, remote facilities a segmented site database enables each
facility to operate independently while providing central oversight.
Notice
Ensure that the folder you select for the site database is accessible by all PCs running
the Control Center front-end application.
Choosing the location of the site database

There are two ways to use the site database:
Local - the site database is stored on an individual PC. If you have installed the
Control Center front-end application on only one PC you should use a local site
database.
Central - the site database is stored on a Windows file server and users access the
data across the network. If you have installed the Control Center front-end application
on several PCs you should use a central site database.
When you use a central site database, the site database can be stored in one of the following
options:
Notice
a PC where the Control Center front-end application is installed
a Windows file server
Ensure that the folder you select for the site database is accessible by all PCs running
the Control Center front-end application.
19
Control Center
Partner branding
You can customize the Control Center front-end application to include your companys name
and logo. Your company logo appears on the login screen, and company name appears in the
title bar of the Control Center front-end application.
IndigoVision provides a .bmp and a .txt file for you to edit with your company details.
1. On the IndigoVision Control Center CD, navigate to Resources\PartnerBranding.
In the partnertext.txt file, enter the text you want to appear in title bar, and save it in
the folder where the Control Center front-end application is installed.
2. Edit the partnerlogo.bmp file with the image you want to appear in the login screen,
and save it in the folder where the Control Center front-end application is installed.
Notice
The dimensions of the partnerlogo.bmp image must be identical to the Control Center
logo on the login page (390 x 65 pixels), otherwise the image may not scale correctly.
3. Open a DOS prompt and navigate to the Control Center front-end application
installation directory. Enter the following at the prompt:
ccbrand.exe
4. Open the Control Center front-end application to check the image is correctly
displayed on the login dialog and the text is correctly displayed in the title bar.
Windows firewall
Firewall protection is automatically enabled on PCs running Windows Vista , or Windows
7. If you have installed a Control Center front-end application on either of these operating
systems, the firewall may prevent correct operation of the application and/or the NVR-AS. To
ensure these applications work as expected, you can:
turn off the firewall, or
create firewall exceptions.
Turning off the firewall

Turning off the firewall completely leaves your computer unprotected against outside attack.
However, this should not be an issue as long as your network is protected by other means.
Creating firewall exceptions

Alternatively, you can create firewall exceptions for a Control Center front-end application
and the NVR-AS service. For more information about creating exceptions, see the Windows
help system.
IndigoVision port numbers are listed in see "IndigoVision Firewall Requirements" on page
43
Unattended installation enables system administrators to installthe front-end applications
using group policies. This enables system administrators to automate installation to ensure
20
Control Center
the correct version of the ControlCenter front-end application or Control Center Client frontend application is available to users.
The following sections provide the information a system administrator requires to implement
unattended installation within your organization's environment.
To perform an unattended installation of the front-end applications, the installer properties
USEEXISTINGSITEDBSETTINGS and FINALRELEASEmust be set to 1.
An example Microsoft Windows Installer Transform file (.mst) with these settings is available
in the Resources folder on the IndigoVision Control Center CD under Unattended
Installation.
Prerequisites
The installers for the front- end applications have several prerequisites for the target PC
before running the front-end application installer.
The following applications and registry settings are prerequisites for the ControlCenter frontend applications installation.
ControlCenter site database location
This is stored in the registry:

64-bit Windows: HKLM\SOFTWARE\Wow6432Node\IndigoVision\Control
Center Client 4.
Add a string value called SiteDbPath.

This contains the database location, for example, C:\IndigoSiteDb.
Microsoft .NET Framework 4 Client Profile
dotNetFx40_Client_x86_x64.exe
Available on the Control Center CD in the Control Center folder.
Microsoft Sync Framework 2.1 core components
Synchronization-v2.1-x86-ENU.msi
Microsoft Sync Framework 2.1 provider services
ProviderServices-v2.1-x86-ENU.msi
The prerequisites required depend on whether this is the first time the front-end application
has been installed on this PC or whether it is being upgraded. If the front-end application has
already been installed on the PC, depending on the version, some prerequisites may have
been previously installed.
The following tables illustrate which prerequisites are required for each scenario.
Table 3:
New Control Center installation

Prerequisite
Required
Control Center site database location
Yes
Yes
Yes
Yes
21
Notice
Control Center
These prerequisites apply even if Control Center 3 is, or has been, installed on the PC.
Table 4:
Upgrading from Control Center 4.1 or earlier

Prerequisite
Required
No
Yes
Yes
Yes
Table 5:
Upgrading from Control Center 4.2 or 4.3

Prerequisite
Required
No
Yes
Yes
Yes
Table 6:
Upgrading from Control Center 4.4

Prerequisite
Required
No
No
No
No
Examples
Examples of registry scripts are available on the Control Center CD. The scripts are an
example of how to set the site database path in the registry to C:\IndigoSiteDB. They are
editable in a text editor such as Notepad.
The scripts are available in the Resources folder on the Control Center CD under
Unattended Installation.
An example Microsoft Windows Installer Transform file (.mst) with the required settings is
available in the Resources folder on the Control Center CD under Unattended Installation.
22
CONTROL CENTER CLIENT FRONT-END

APPLICATION INSTALLATION
This chapter describes how to install the Control Center Client front-end application. It also
explains how to configure a Windows firewall to allow correct operation of Control Center
Client.
For information about system specifications, see the "Control Center Performance Guide".
Control Center Client is available on the IndigoVision Control Center CD. If you need to
distribute Control Center Client, you can copy the contents of the ControlCenterClient
folder on to a CD.
Control Center Client

You must be logged into Windows as an administrator to install Control Center Client.
Notice
Your Operating System may require you to authorize this installation.

To install Control Center Client:
1. Insert the IndigoVision Control Center CD or Control Center Client CD into the CD
drive of the PC on which you are installing Control Center Client. The IndigoVision
Control Center install screen opens.
2. Click Install for the Control Center Client front-end application, and follow the onscreen instructions to complete the installation.
Notice
If you do not have Microsoft .NETFramework 4, Microsoft Sync Framework 2.1 Core
Components, or Microsoft Sync Framework 2.1 Provider Services installed, Control
Center Client will notify you, and install them for you before continuing.
After installing Control Center Client, the Site Database Setup application opens. For
information on site databases, see "The Control Center Client site database" on page
24.
3. Click Browse to select the folder where the database is located, and select Upgrade
PTZ protocols to upgrade to the latest protocols installed with Control Center.
23
4 Control Center Client front-end application Installation
Caution
Control Center
will be lost.
number.
Click Next. The Back up Site Database Details opens.
5. Specify a backup site database, if required. The backup site database is used if the
requested site database is unavailable.
Select Specify a backup Site Database, then click Browse to select the site
database.
6. Click Next, then click Finish to complete the installation.
The Control Center Client site database

The Control Center site database stores the site configuration information. You can enter site
database information during installation, but you can change this at any time. (From the Start
menu, select Programs> IndigoVision> Control Center Client>Site Database Setup.)
During installation you are asked to use an existing site database.
Windows firewall
Firewall protection is automatically enabled on PCs running Windows Vista , or Windows
7. If you have installed a Control Center front-end application on either of these operating
systems, the firewall may prevent correct operation of the application and/or the NVR-AS. To
ensure these applications work as expected, you can:
turn off the firewall, or
create firewall exceptions.
Unattended installation enables system administrators to installthe front-end applications
using group policies. This enables system administrators to automate installation to ensure
the correct version of the ControlCenter front-end application or Control Center Client frontend application is available to users.
The following sections provide the information a system administrator requires to implement
unattended installation within your organization's environment.
To perform an unattended installation of the front-end applications, the installer properties
USEEXISTINGSITEDBSETTINGS and FINALRELEASEmust be set to 1.
An example Microsoft Windows Installer Transform file (.mst) with these settings is available
in the Resources folder on the IndigoVision Control Center CD under Unattended
Installation.
24
Control Center
Prerequisites
The installers for the front- end applications have several prerequisites for the target PC
before running the front-end application installer.
The following applications and registry settings are prerequisites for the ControlCenter frontend applications installation.
ControlCenter site database location
This is stored in the registry:

64-bit Windows: HKLM\SOFTWARE\Wow6432Node\IndigoVision\Control
Center Client 4.
Add a string value called SiteDbPath.

This contains the database location, for example, C:\IndigoSiteDb.
dotNetFx40_Client_x86_x64.exe
Synchronization-v2.1-x86-ENU.msi
ProviderServices-v2.1-x86-ENU.msi
The prerequisites required depend on whether this is the first time the front-end application
has been installed on this PC or whether it is being upgraded. If the front-end application has
already been installed on the PC, depending on the version, some prerequisites may have
been previously installed.
The following tables illustrate which prerequisites are required for each scenario.
Table 7:
New Control Center installation

Prerequisite
Notice
Required
Yes
Yes
Yes
Yes
These prerequisites apply even if Control Center 3 is, or has been, installed on the PC.
Table 8:
Upgrading from Control Center 4.1 or earlier

Prerequisite
Required
No
Yes
Yes
Yes
25

Table 9:
Control Center
Upgrading from Control Center 4.2 or 4.3

Prerequisite
Required
No
Yes
Yes
Yes
Table 10:
Upgrading from Control Center 4.4

Prerequisite
Required
No
No
No
No
Examples
Examples of registry scripts are available on the Control Center CD. The scripts are an
example of how to set the site database path in the registry to C:\IndigoSiteDB. They are
editable in a text editor such as Notepad.
The scripts are available in the Resources folder on the Control Center CD under
Unattended Installation.
An example Microsoft Windows Installer Transform file (.mst) with the required settings is
available in the Resources folder on the Control Center CD under Unattended Installation.
26
CAMERA GATEWAY INSTALLATION

This chapter details how to install the Camera Gateway.
Camera Gateway overview

The IndigoVision Camera Gateway enables third party cameras from a range of
manufacturers to be connected to IndigoVision Control Center. The Camera Gateway takes
video streams from third party cameras using their native protocols and enables users to view
the streams in a Control Center front-end application and record them using NVRs.
The cameras do not need to support ONVIF in order to connect to the IndigoVision system,
giving customers a wide choice of cameras to choose from.
The Camera Gateway supports video streams from H.264 and MPEG- 4 cameras, PTZ
control, and events.
The Camera Gateway is a software service that can be installed on a Windows server, giving
total flexibility. The Camera Gateway service enables multiple clients to stream video from
the same camera, whilst only requiring a single stream from the camera to the Camera
Gateway.
Intended use
The Camera Gateway enables third party cameras from a range of manufacturers to be
connected to IndigoVision Control Center. If, for example, you want to use ControlCenter to
view a location in which third party cameras are already installed, the Camera Gateway
allows you to do so without having to change the cameras.
The IndigoVision Camera Gateway can be installed on one of the following Windows
operating systems:
MS Windows 7 (32 bit)
MS Windows 7 (64 bit)
MS Windows Server 2008 R2
For systems with more than 16 streams it is recommended to use Windows Server 2008 R2.
IndigoVision recommends that you install Camera Gateway on a server-style system, with a
server network adaptor, and the following minimum requirements:
Server class PC
Current generation Intel Xeon processor 3.10 Ghz
4GB RAM
27
5 Camera Gateway Installation
Control Center
The Camera Gateway installer first checks the system for the prerequisite components:
Microsoft .NET Framework 4, and Microsoft SQLServer 2008 Express Edition. The installer
then installs each prerequisite component required, before installing the three components of
the Camera Gateway.
Prerequisites
The following prerequisites are required to install and use the Camera Gateway.
A valid licence key for the Camera Gateway.

If you do not have a licence key, you can still install the Camera Gateway, however,
only four video streams will be available for 30 days after installation for demonstration
purposes.
Microsoft .NETframework is enabled.
In Windows 7, click Start >ControlPanel > Programs > Turn Windows

features on or off. Verify that Microsoft .NET Framework 3.5.1 is selected.
In Windows Server, click Start > Administrative Tools > Server Manager
>Roles. Verify that the Application Server role is installed.
Installation
1. Insert the Control Center CD into the CD drive of the PC or server on which you are
installing the Camera Gateway application. The Control Center install screen opens.
Select Camera Gateway.
If the install screen does not open automatically, navigate to
English/CameraGateway and double-click the setup.exe file in your Windows
Explorer window, or use the Run option on the Windows Start menu and enter the path
to the setup.exe file on the CDROM.
2. If Microsoft SQLServer 2008 Express Edition is not installed, you will be prompted to
install it. Follow the on-screen instructions.
If the Microsoft SQLServer 2008 installation fails to complete, you must manually
remove the components.
For more information, see "Microsoft SQL Server Express 2008 installation fails to
complete " on page 39
3. If Microsoft .NET Framework 4 is not installed, you will be prompted to install it. Follow
the on-screen instructions.
4. You may need to restart your computer. Restart the computer, then open the Control
Center CD and select Camera Gateway.
5. The Camera Gateway Server installation wizard opens. Follow the on-screen
instructions.
During the installation process you will be prompted to select one of the following
licence options.
28
Select Use Demo licence to install the Camera Gateway without entering a
licence key. The demo licence enables four streams for 30 days, for demonstration
purposes only.
Select Use Offline Activation to install the Camera Gateway on a PC without

internet access. The installer then presents the necessary files to allow you to
register the Camera Gateway installation on a PC with internet access.
Control Center
Select Enter licence Key if you have a Camera Gateway licence key. Type the
licence key and click Check licence to authenticate the license.
6. Once the Camera Gateway Server has successfully installed, click Finish.
The Camera Gateway Administrator installation wizard opens. Follow the on-screen
instructions.
7. Once the Camera Gateway Administrator has successfully installed, click Finish.
The Camera Gateway Interface installation wizard opens. Follow the on-screen
instructions.
8. Once the Camera Gateway Interface has successfully installed, click Finish.
29
30
Control Center
MOBILE CENTER SERVICE INSTALLATION

This chapter details how to install the Mobile Center Service.
Overview
The Mobile Center Service enables you to view video streams from cameras in an
IndigoVision Control Center site using a mobile device.
The Mobile Center Service provides the interface between the site database and the Mobile
Center app installed on the mobile device. This enables you to access and control cameras in
your site database on the move. However, video is streamed directly from the camera
maintaining IndigoVision's robust, distributed architecture.
To use Mobile Center on a mobile device, you must install the Mobile Center Service on a PC
or server, and install the Mobile Center app on a suitable mobile device.
We recommend that you use the following guidelines for the Mobile Center Service PC or
server operating system.
Table 11:

Operating System
Supported
Windows Server 2008 R2 x64
Y (recommended)
Windows Server 2003
Windows 7
Y (recommended)
Windows Vista
Windows XP Professional
Compatibility
Mobile Center Service is compatible with the following applications:
IndigoVision Control Center 4 or later
Windows Server 2003: IIS 6.0 or later
Windows Vista, Windows 7,and Windows Server 2008 R2: IIS 7.0 or later
Mobile Center iOS app v1.5 or later is compatible with the following applications:
iOS 6 or later
Mobile Center Service v1.5 or later
31
6 Mobile Center Service Installation
Control Center
Prerequisites
The following prerequisites are required to install and use the Mobile Center Service.
IndigoVision Control Center installation
A valid licence key for the Mobile Center Service.

If you do not have a licence key, you can still install the Mobile Center Service,
however, you will only be able to register one mobile device for 30 days after
installation, for demonstration purposes.
Microsoft .NET Framework 4.0.

This will be installed as part of the installation process if it is not already available.
Internet Information Services (IIS) installed and correctly configured.

The configuration depends on the operating system. The following sections provide
information about configuring IIS. For additional information, please refer to the
Microsoft support site (http://support.microsoft.com).
IIS Configuration on Windows Server 2008 R2

Navigate to Control Panel > Programs and Features > Turn Windows Features On or
Off > Roles > Add Role and follow the wizard to ensure the following IIS features are
installed and enabled:
Web Server (IIS)
Web Server > Application Development
ASP .NET
NET extensibility
ISAPI Extensions
ISAPI Filters
Web Server > Common HTTP Features
Static Content
Default Document
Web Server > Security
Basic Authentication
Request Filtering
Management Tools
IIS Management Console
Navigate to: Control Panel > Programs and Features > Turn Windows Features On
and Off > Features > Add Feature and follow the wizard to ensure the following features
are installed and enabled:
.NET Framework 3.5.1
IIS Configuration on Windows Vista and Windows 7

Navigate to: Control Panel > Programs and Features > Turn Windows Features On or
Off > Internet Information Services and ensure the following IIS features are installed and
enabled:
Web Management Tools
32
IIS Management Console
World Wide Web Services > Application Development Features
Control Center
NET extensibility
ASP .NET
ISAPI Extensions
ISAPI Filters
World Wide Web Services > Common HTTP Features
Default Document
Static Content
World Wide Web Services > Security
Basic Authentication
Request Filtering
IIS Configuration on Windows Server 2003

Navigate to: Control Panel > Add or Remove Programs > Add/Remove Windows
Components > Application Server and ensure the following sub-components are installed
and enabled:
Application Server Console
Enable network COM+ access
Internet Information Services (IIS)
Common Files
Internet Information Services Manager
World Wide Web Service
The installation procedure for Mobile Center Service depends on the operating system of the
PC or server. This section provides details for installing Mobile Center on supported operating
systems.
The installation procedure comprises the following steps:
Install an SSLcertificate
Insert a valid licence dongle
Install the Mobile Center Service
An SSL certificate is required for a secure connection between the Mobile Center app and the
Mobile Center Service. An example SSL certificate is provided on the Control Center CD in
the Mobile Center Service folder. This is a 10- year certificate; ensure you check the
expiration date before use.
For security reasons it is recommended that you create your own or purchase a certificate
from a trusted certificate authority.
Windows 7, Windows Server 2008 R2, Windows Vista

To install the Mobile Center Service on a PC or server running Windows 7, Windows Server
2008 R2,or Windows Vista, complete the following steps:
1. Install the Mobile Center Service
2. Import theSSL certificate
3. Assign the SSL certificate
33
Control Center

1. If you have a licence key for the Mobile Center Service, insert the licence dongle into
the USB port of the PC or server. If you do not, you can still install the Mobile Center
Service, however, you will only be able to register one mobile device for 30 days after
which you are installing Mobile Center Service. The IndigoVision Control Center install
screen opens.
3. Click Install for the Mobile Center Service component, and follow the on-screen
4. During installation, the Mobile Center Service Site Database tool opens. Browse to
the location of the site database.
If you are using a remote site database, enter the user name and password Mobile
Center Service will use to access the directory where the site database is located.
For more information, see "Using a remote site database in a workgroup" on
page 36
To select a remote site database, the user account that you are logged in with must have
access to the location of site database.
If you do not want to set up the site database at this time, click Cancel to complete
the installation.
You can select the site database at any time. Access the Mobile Center Site
Database Setup tool from Start > IndigoVision >Mobile Center Service
>Mobile Center Site Database Setup.
After the installation has been completed, the Mobile Center Service Administration page
opens in your default web browser.
Notice
The first time you install Mobile Center Service, your browser will not be able to display
the Mobile Center Administration page until you have imported and assigned the SSL
certificate.
Once you have completed the subsequent installation steps, refresh your browser page to
view the Mobile Center Administration page.
Import the SSLcertificate

1. Click Start > Control Panel >Administrative Tools >Internet Information
Services.
2. Select the server instance, and double-click Server Certificates in Features View.
3. On the Actions pane, click Import.
4. Click ..., navigate to the certificate file, and clickOpen.
5. Type the password in the Password field, and click OK.
34
Control Center
Note:
Ensure Allow this certificate to be exported is selected, otherwise you

will not be able to assign the certificate.
The password is provided by the creator of the SSL certificate.
Assign the certificate

Services.
2. Select the IVMobileCenterService web site, and select Bindings... on the Actions
pane.
3. Select the binding created by the Mobile Center Service, and click Edit.
4. Select the Mobile Center Service certificate from the SSLcertificate drop-down, and
click OK.
Windows Server 2003

To install the Mobile Center Service on a PC or server running Windows Server 2003,
complete the following steps:
1. Import theSSL certificate
2. Install the Mobile Center Service
Import the SSL certificate

Services.
2. Right-click Default Web Site, and select Properties.
3. Select the Directory Security tab, and click Server Certificate....
4. Select Import a certificate from a .pfx file, and click Next.
5. Click Browse, and navigate to the certificate file.
6. Click Open, and click Next.
7. Type the password in the Password field, and click Next.
The password is provided by the creator of the SSL certificate.
8. Type 49200 in the SSL Port field, and clickNext.
9. Click Finish.

1. If you have a licence key for the Mobile Center Service, insert the licence dongle into
the USB port of the PC or server. If you do not, you can still install the Mobile Center
Service, however, you will only be able to register one mobile device for 30 days after
which you are installing Mobile Center Service. The IndigoVision Control Center install
screen opens.
3. Click Install for the Mobile Center Service component, and follow the on-screen
35
Control Center
4. During installation, the Mobile Center Service Site Database tool opens. Browse to
the location of the site database.
If you are using a remote site database, enter the user name and password Mobile
Center Service will use to access the directory where the site database is located.
For more information, see "Using a remote site database in a workgroup" on
page 36
To select a remote site database, the user account that you are logged in with must have
access to the location of site database.
If you do not want to set up the site database at this time, click Cancel to complete
the installation.
You can select the site database at any time. Access the Mobile Center Site
Database Setup tool from Start > IndigoVision >Mobile Center Service
>Mobile Center Site Database Setup.
After the installation has been completed, the Mobile Center Service Administration page
opens in your default web browser.
Using a remote site database in a workgroup

When the remote site database used for a Mobile Center Service installation is accessed
over a Workgroup, you need to ensure the site database is accessible to the service.
1. Setup a user account on the PC or server where the site database is located.
Group membership: Restricted user
Groups: Windows 7 and Server 2008 R2 - IIS_USRS
2. Ensure this user account has Read access to the directory where the site database is
located.
3. Create a user account on the PC or server where Mobile Center Service will be
installed. Use the same user name and password as the user account created in step
1.
4. Use this user name and password when selecting a site database in the Mobile Center
Site Database Setup tool.
For more information , see "Installation procedure" on page 33
Configuration
The IndigoVision Mobile Center Administration page allows you to view all registered mobile
devices.
To view the configuration page, navigate to your Mobile Center Service url. Use your
ControlCenter administrator username and password to access the administration page.
The default url is: https://<Server IP>:49200/mobilecenterservice , where <Server IP>
represents the IP address of the server.
For more information about changing the url, see "Change the Mobile Center Service url"
on page 37
If you cannot view the IndigoVision Mobile Center Administration page, there may be a
problem with your installation.
For more information, see "The IndigoVision MobileCenter Administration page cannot be
displayed" on page 39
36
Control Center
Download and configure the Mobile Center app

The Mobile Center app is available from the app store for your device.
To use the Mobile Center app, you must first register the device with Mobile Center Service.
Use the Mobile Center Service URL provided by your administrator.
To log on, use your ControlCenter username and password.
For more information about using the app, see the Mobile Center app help.
Deregister a device
You can block a device from accessing the Mobile Center Service by deregistering it on the
IndigoVision Mobile Center Administration page.
Click Block Device to deregister the device, and block it from connecting to the
Mobile Center Service.
Click Remove to deregister the device, and remove it from the list of devices. Mobile
Center users can register their device again after it has been removed.
For more information about accessing the IndigoVision Mobile Center Administration
page, see "Configuration" on page 36
Notice
This functionality is only available if you have full administrator permissions.
Change the Mobile Center Service url

The Mobile Center Service is assigned the following url by default:
https://<Server IP>:49200/mobilecenterservice
<Server IP> represents the IP address of the server.

You can change the default port number and path using IISManager. The procedure depends
on the operating system of the PC or server that Mobile Center Service is installed on.
Change the port on Windows 7, Windows Server 2008 R2, and Windows Vista
systems
Services.
2. Select the IVMobileCenterService web site, and select Bindings... on the Actions
pane.
3. Select the binding created by the Mobile Center Service, and click Edit.
4. Type the new port for the Mobile Center Service in the Port field, and click OK.
Access Mobile Center Service from a public network

To access Mobile Center Service from a public network, you can configure the Mobile Center
Service installation in the following ways:
Set up VPN access to the network on which the Mobile Center Service and cameras
are available.
37
Control Center
This is the recommended option.
Notice
38
Provide a public IP address behind a Network Address Translation (NAT) firewall for
the Mobile Center Service server as well as all the cameras you need to view.
Cameras from the BXRange do not support Network Address Translation (NAT).
TROUBLESHOOTING
This chapter provides troubleshooting information for the installation of Control Center
applications.
Microsoft SQL Server Express 2008 installation fails to

complete
If the Microsoft SQLServer Express 2008 installation fails to complete, you must remove the
following components using Control Panel >Programs and Features before reinstalling.
Microsoft SQL Server 2008
Microsoft SQLServer Native Client
Microsoft SQL Server Setup Support Files
Microsoft SQL Server VSSWriter
Microsoft SQL Server 2008 Browser
The IndigoVision MobileCenter Administration page

cannot be displayed
If the IndigoVison Mobile Center Administration page cannot be displayed when you use the
provided URL, this may indicate that:
Another application or web page is using the same port number. Use the IISManager
to change the port number that Mobile Center Service uses.
For more information, see "Change the Mobile Center Service url" on page 37
For Windows Server 2003, the following web service extensions may be prohibited.
Use the IIS Manager to allow these extension.
ASP .NET v2.0.50727
ASP .NET v4.0.30319
The first time Mobile Center Service is installed on Windows 2008 R2, the Mobile
Center Administration page will not be displayed until the SSL certificate has been
imported and assigned.
Your device does not have access to the network on which the Mobile Center Service
is installed. For example, you are accessing a private network from the public network.
For more information, see "Access Mobile Center Service from a public network"
on page 37
39
7 Troubleshooting
Control Center
Upgrading mobile device to iOS 7

IndigoVision recommends you upgrade Mobile Centre iOS app to v1.5 before upgrading your
device to iOS 7.
If you have already upgraded to iOS 7 before upgrading to Mobile Center iOS app v1.5, your
administrator must de-register your device before you can use the Mobile Center app. After
your device has been de-registered, you must re-register when you first open Mobile Center
iOS app v1.5.
Mapped drive is not displayed when browsing for a remote

site database
When using Mobile Center Site Database Setup on Windows 7, a mapped network drive may
not be displayed when browsing for a remote site database.
This can occur when the mapped drive was set up by a user without administrator
permissions.
To resolve this issue, use one of the following solutions:
Log in as an administrator and reconfigure the mapped network drive.
Map the network drive from an elevated command window.

Start >Accessories >Command Prompt >Run as administrator
net use [mapped drive letter:] [mapped drive path]
You will need to repeat this operation each time you reboot the system.
Add following registry entry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLinkedConnections"=dword:00000001
Site database cannot be edited

Control Center stores site information in the site database. Control Center may not be able to
edit the database for the following reasons:
The administrator account may not have permission to edit the database.
Ensure the administrator has the following file permissions to edit the site
database:
Windows Share Permissions: Full Control (to enable control by the NTFS Security
permissions)
NTFS Security Permissions: Synchronize, Read Permissions, Read Attributes,
Read Extended Attributes, Write Attributes, Write Extended Attributes, Delete, and
Change Permissions
If you cannot change the file permissions for mapped drives, for example, due to
corporate ITpolicies, you can disable Enhanced Database Protection for the site
database.
Disabling Enhanced Database Protection requires Control Center to use alternative
Windows APIs. This increases the risk of data loss or corruption during extreme
circumstance such as a power outage or network failure while editing the site
database.
40
The file sharing attributes for the site database are incorrect.
Control Center
7 Troubleshooting
When Enhanced Database Protection is disabled, the file sharing attributes of a
remote site database are changed when the site database is modified on the machine
on which it is hosted.
Enable Enhanced Database Protection.
If you cannot enable Enhanced Database Protection, for example, due to corporate
ITpolicies, ensure the file sharing attributes are correct on the site database, and
that all site database changes are made from a remote Control Center front-end
application.
41
7 Troubleshooting
42
Control Center
INDIGOVISION FIREWALL REQUIREMENTS

When setting up a network of IndigoVision equipment that includes firewalls, the following
information should be used to configure the firewalls.
Notice
This information applies only if communication occurs between equipment on opposite

sides of the firewall. Ports need not be opened in a firewall if the network protocol is
exchanged entirely within a subnet or subnets that do not cross a firewall boundary.
Firewalls should also support TCP and UDP connection tracking. UDP timeouts should be at
least 30 seconds.
Ports required by 8000, 9000, 11000 Range cameras and

encoders
Service
Prot.
Destination
Port
Dir.
Comments
Control Data
UDP
49300
IN
Mandatory for communications with

other IndigoVision devices including
front-end application and NVR-AS.
This is also used for UDP Video.
Serial Data
TCP
49500 - 49509
IN
Used to access PTZ cameras and

other devices connected to the
transmitter serial ports
Serial Data 2
TCP
49510 - 49519
IN
An additional second serial data

channel for integration purposes. This
service may not be used for PTZ
camera control through Control
Center.
TCP Video
TCP
4940049402,4942049422
IN
See separate section for details on

ports used for different stream
configurations.
TCP Audio
TCP
49410
IN
UDP Multicast
Video
UDP
49400, 49402,
49404, 49420,
49422, 49424
OUT
UDP Multicast
Video Control
UDP
49401, 49403,
49405, 49421,
49423, 49425
IN/OUT
UDP Multicast
Audio
UDP
49410, 49430
OUT
UDP Multicast
UDP
49411, 49431
IN/OUT
43
A IndigoVision Firewall Requirements
Service
Prot.
Destination
Port
Control Center
Dir.
Comments
Audio Control
Bandwidth
Management
UDP
49600
OUT
Used to request a bandwidth

allocation from the Bandwidth
Manager
Web
Configuration
TCP
80
IN
Only required for administration
telnet
TCP
23
IN
FTP cmd
TCP
21
IN
Used for passive FTP during bulk

upgrade
FTP data
TCP
1024-4999
IN
Used for passive FTP data transfer

during bulk upgrade
NTP
UDP
123
OUT
Used for NTP time synchronization
Syslog
UDP
514
OUT
External system logging support
SNMP
UDP
161
IN
Used for SNMP monitoring by third

party network management tools
VBLTM
UDP
50000
IN/OUT Used for VBLTM monitor
Ports required by BXRange cameras

Service
Prot.
Destination
Port
Dir.
Comments
RTSP video and

TCP
audio
554 1
IN
RTSP session control for Reliable,

Best Effort and Multicast transports.
Also used for reliable video and audio
streams. Best effort video and audio
streams use ephemeral ports.
UDP Multicast
video
UDP
49400, 49402,
49412
OUT
Video streams for Multicast

transports.
UDP Multicast
audio
UDP
49410
OUT
Audio streams for multicast

transports.
Web
Configuration
TCP
80, 443 1
IN
Web configuration pages on the BX

range devices
WS-Discovery
UDP
3702
IN/OUT
Unicast and multicast discovery of

ONVIF devices
WS-Discovery
TCP
3702
IN
Unicast discovery of ONVIF devices
1 = This is configurable through the device web page.

= This is configurable through the ONVIF Configuration Utility.
Ports required by Ultra Range cameras

Service
Prot.
JPEG2000 video TCP
44
Destination
Port
8888
Dir.
IN
Comments
JPEG2000 video streaming from
Control Center
Service
Prot.
Destination
Port
Dir.
Comments
Ultra 5K Fixed Cameras.
RTSPVideo
TCP
554
IN
RTSP session control for Reliable and

Best Effort transports. Also used for
Reliable video streams. Best Effort
video streams use ephemeral ports.
Web
Configuration
TCP
80
IN
Web configuration pages on the Ultra

5k range device.
WS-Discovery
UDP
3702
IN/OUT
Unicast UDP and multicast discovery

of ONVIF devices.
WS-Discovery
TCP
3702
IN
Unicast discovery of ONVIF devices.
Ports required by 8000 and 9000 Range receivers

Service
Prot.
Destination
Port
Dir.
Comments
Control Data
UDP 49300
IN

Control Data
UDP 49300
OUT
Used to initiate live video from

transmitters. This is also used to
receive UDP Video.
Serial Data
TCP
49500 - 49509
OUT
Used for serial connections between

a PTZ keyboard attached to the
receiver and a PTZ camera on a
remote transmitter.
TCP Video
TCP
4940049402,4942049422
OUT

configurations.
TCP Audio
TCP
49410
OUT
UDP Multicast Video
49400, 49402,
UDP 49404, 49420,
49422, 49424
IN
UDP Multicast Video

Control
49401, 49403,
UDP 49405, 49421,
49423, 49425
IN/OUT
UDP Multicast Audio
UDP 49410, 49430
IN
UDP Multicast Audio

Control
UDP 49411, 49431
IN/OUT
Video Playback
TCP
49299
OUT
Playback of footage from an NVR-AS
Web Configuration
TCP
80
IN
telnet
TCP
23
IN
FTP cmd
TCP
21
IN

upgrade
FTP data
TCP
1024-4999
IN

during bulk upgrade
45
Service
Prot.
Control Center
Destination
Port
Dir.
Comments
NTP
UDP 123
OUT
Used for NTP time synchronization
Syslog
UDP 514
OUT
SNMP
UDP 161
IN

Ports required by alarm panels

Service
Prot.
Destination
Port
Dir.
Comments
Control Data
UDP
49300
IN

Web
Configuration
TCP
80
IN
telnet
TCP
23
IN
FTP cmd
TCP
21
IN

upgrade
FTP data
TCP
1024-4999
IN

during bulk upgrade
NTP
UDP
123
OUT
Used for NTP time synchronisation
Syslog
UDP
514
OUT
SNMP
UDP
161
IN

Ports required by an NVR-AS

Service
Control Data
46
Prot.
UDP
Destination
Port
49300
Dir.
Comments
IN

front-end application
Control Data
UDP
49300
OUT
Mandatory for the NVR-AS to initiate

recording on Transmitters. Also
required to receive alarm events from
Transmitters, Receivers and Alarm
Panels
NVR Control
Data
TCP
8130
IN
Mandatory for communication

between the NVR and front-end
application
NVR Control
Data
TCP
8130
OUT
Used for Alarm Server Record

Actions and fault monitoring
Alarm Server
Control Data
TCP
8131
IN

between the Alarm Server and frontend application
Playback
TCP
49299
IN
Used to playback video in front-end

application
Control Center
Service
Prot.
Destination
Port
Dir.
Comments
TCP Video
TCP
4940049402,4942049422
OUT

configurations.
TCP Audio
TCP
49410
OUT
PTZ Control
TCP
49500 - 49509
OUT
Used for Alarm Server PTZ Actions
Firewall Friendly
transport type
TCP
ONVIF streams
80
OUT
Video and Audio may be tunneled

through HTTP for ONVIF devices
Reliable
transport type
ONVIF streams
TCP
554
OUT
UDP Multicast
Video
UDP
49400, 49402,
49404, 49420,
49422, 49424
IN
UDP Multicast
Video Control
UDP
49401, 49403,
49405, 49421,
49423, 49425
IN/OUT
UDP Multicast
Audio
UDP
49410, 49430
IN
UDP Multicast
Audio Control
UDP
49411, 49431
IN/OUT
NVR Events
UDP
49301
IN
Used to receive events from

IndigoVision Integrations and custom
integration software built using the
IndigoVision SDK.
Bandwidth
Management
UDP
49600
OUT
Used to request a bandwidth

allocation from the Bandwidth
Manager
Email
TCP
25
OUT
Used by Alarm Server Email Actions.

Port is configurable.
Ports required by an NVR-AS 3000

Service
Prot.
Destination
Port
Dir.
Comments
Web
Configuration
TCP
80
IN
telnet
TCP
23
IN
FTP cmd
TCP
21
IN
Used for archiving recordings via FTP
FTP data
TCP
1024-4999
IN
Used for archiving recordings via FTP
NTP
UDP
123
OUT
Used for NTP time synchronisation
Syslog
UDP
514
OUT
SNMP
UDP
161
IN

SNMP
UDP
161
OUT
Used to monitor UPS status
47
Control Center
Ports required by Windows NVR-AS

These may include further Windows services such as NTP and Remote Desktop
Ports required by Bandwidth Manager

Service
Bandwidth
Management
Prot.
UDP
Destination
Port
49600
Dir.
Comments
Used to issue bandwidth allocations to
Transmitters and NVR-ASs
IN
Ports required by Control Center front-end application

Service
48
Prot.
Destination
Port
Dir.
Comments
Control Data
UDP
49300
OUT
Mandatory for communications to all

IndigoVision devices.
NVR Control
Data
TCP
8130
OUT

between the NVR-AS and front-end
application
NVR Control
Events
UDP
49303
IN
Mandatory for NVR event

notifications and the front-end
application.
Alarm Server
Control Data
TCP
8131
OUT

between the Alarm Server and frontend application
Playback
TCP
49299
OUT
Used to playback video from an NVR
TCP Video
TCP
4940049402,4942049422
OUT

configurations.
TCP Audio
TCP
49410
OUT
UDP Multicast
Video
UDP
49400, 49402,
49404, 49420,
49422, 49424
IN
UDP Multicast
Video Control
UDP
49401, 49403,
49405, 49421,
49423, 49425
IN/OUT
UDP Multicast
Audio
UDP
49410, 49430
IN
UDP Multicast
Audio Control
UDP
49411, 49431
IN/OUT
Serial Data
TCP
49500 - 49509
OUT
Used to access PTZ cameras

connected to transmitter serial ports
Communication
TCP
80
OUT
Configuration of devices
Firewall Friendly
transport type
TCP
ONVIF streams
80
OUT
Communication with ONVIF devices
Reliable
transport type
ONVIF streams
554
OUT
TCP
Control Center
Service
Prot.
Destination
Port
Dir.
Comments
FTP cmd
TCP
21
OUT

upgrade
FTP data
TCP
1024-4999
OUT

during bulk upgrade
WS-Discovery
UDP
3702
OUT
Used for discovery of ONVIF cameras
WS-Discovery
TCP
3702
OUT
Used for discovery of ONVIF cameras
Additional ports may be required for Windows services including:
NTP for time synchronisation
Access to network drives for the site database
Access to ODBC database for audit logging
Telnet for administration of IndigoVision devices
Ports required by Camera Gateway

Service
Prot.
Destination
Port
Dir.
Comments
Control Data
TCP
80
IN
Camera Gateway Configuration
ControlData
TCP
25473
IN
Camera Gateway Configuration
Licence
Activation
TCP
80
OUT
Camera Gateway Licence Activation

(only required during installation)
Media
Streaming
TCP
554
IN
Camera to Camera Gateway
Media
Streaming
TCP
554
OUT
Mandatory for communications from

Camera Gateway to NVR or frontend application
Control Data
TCP
47002
IN

front-end application
Events
TCP
29170
IN
Used to listen for events from

cameras
The ports required for communication between a camera and the Camera Gateway vary
depending on the camera. If these details are not provided, please contact the camera
manufacturer.
Ports required by Video Stream Manager (VSM)

Service
Destination Port
Dir.
Comments
JPEG2000 video TCP
8888
OUT
JPEG2000 video streaming from

Ultra 5K Fixed Camera
Web Services
80
OUT
ONVIF web services requests to Ultra

5K Fixed Camera and Firewall
Friendly video streaming
Prot.
TCP
49
Control Center
Service
Prot.
Destination Port
Dir.
Comments
Web Services
TCP
8000-8009
IN
ONVIF web services for each

managed Ultra 5K Fixed Camera
RTSP
TCP
8554-8563
IN
RTSP session control and Reliable

transport video streaming for each
managed Ultra 5K Fixed Camera
WS-Discovery
UDP
3702
IN/OUT
Unicast UDP and multicast discovery

of ONVIF devices
WS-Discovery
TCP
3702
OUT
Unicast TCP discovery of ONVIF

devices
Ports required by Mobile Center Service

Service
Destination
Port
Prot.
Dir.
Comments
ControlData
UDP
49300
OUT
Mandatory for communications to

allIndigoVision devices.
Serial Data
TCP
49500-49509
OUT
Used to access PTZ cameras

connected to transmitter serial ports .
Mobile Center
Control
TCP
49200
IN
Control requests from Mobile Center

app.
Ports required by Mobile Center app

Service
Destination
Port
Prot.
Dir.
Comments
ControlData
UDP
49300
OUT
Mandatory for communications to

allIndigoVision devices.
TCPVideo
TCP
49400-49402,
49420-49422
OUT

configurations.
Mobile Center
Control
TCP
49200
OUT
Control requests to Mobile Center

Service.
Video stream configuration port usage

Each IndigoVision Transmitter can have 3 separate stream configurations on up to two
independent encoders giving a total of 6 stream configurations. For TCP and UDP multicast
video the ports used will depend on the stream configurations that have been set up. It should
be noted that multiple video streams from the same stream configuration would use the same
TCP/IP port. The table below illustrates how the ports are used by different video transport
protocols and stream configurations:
Stream
Configuration
50
UDP Unicast
Video
UDP Multicast
Video
UDP Multicast
Video Control
TCP Video
Encoder 1 Stream 1
49300
49400
49401
49400
Encoder 1 Stream 2
49300
49402
49403
49401
Control Center
Stream
Configuration

UDP Unicast
Video
UDP Multicast
Video
UDP Multicast
Video Control
TCP Video
Encoder 1 Stream 3
49300
49404
49405
49402
Encoder 2 Stream 1
49300
49420
49421
49420
Encoder 2 Stream 2
49300
49422
49423
49421
Encoder 2 Stream 3
49300
49424
49425
49422
51
52
Control Center
NVR-AS POST-INSTALLATION NETWORK

DRIVE CONFIGURATION
If you are recording to a network drive, IndigoVision recommends that you do the following:
Create a special user account for this purpose.
Change the temporary Video Library folder that you set up during installation.
Creating a user account

To allow the NVR-AS to record to this folder, you must enter the accounts user name (which
includes the domain name) and password as follows:
1. From the Start menu, select Settings>Control Panel>Administrative
Tools>Services.
2. Right-click Indigovision NVR-AS and select Properties.
3. Click the Log on tab and select the required account. The user name you enter must
have read/write access to the Video Library.
4. Enter and confirm the password, then click OK.
Only video data should be stored on a network share; configuration information should be
stored on a local drive which is directly attached to the NVR-AS machine.
Changing the video library folder

You will have set up a temporary Video Library folder during installation.
To change this to a permanent location:
1. From the Start menu, select Programs>IndigoVision>NVR-AS>NVRASAdministrator.
2. In the Video Library field, enter the required Video Library folder (UNC path). To
browse to select a network share, click
Caution
Take care not to select a mapped network drive as this will not be recognized by the
NVR-AS.
3. Click Set.
53
B NVR-AS Post-Installation Network Drive Configuration
Notice
Control Center
For optimal performance, the UNC path should be either:
an IP address, for example, \\192.168.1.2\VideoLibrary
a fully qualified domain name, for example,

\\nvrtest.indigovision.com\VideoLibrary
It should not be a NetBIOS name, for example, \\NVRTEST\VideoLibrary.
Restarting the NVR-AS

1. From the Start menu, select Settings>Control Panel>Administrative
Tools>Services.
2. Right-click Indigovision NVR-AS and select Restart.
54
MIGRATING FROM CONTROL CENTER 3

This appendix outlines the processes for migrating from Control Center 3 and NVR 3.
During migration all video and user data is copied and migrated to a new Control Center
database.
Caution

Network Video Recorders and Alarm Servers

An Alarm Server handles all alarm management for Control Center. To configure alarms using
Control Center, you must have at least one Alarm Server in your site database. This can be in
the form of a standalone NVR-AS 3000 running firmware 4.3 or later, or a Windows based
NVR-AS 4.3 or later.
NVR-AS compatibility
Caution
A system must have the same versions of the NVR-AS and the Control Center frontend application for correct operation. Mismatched front-end application and NVR-AS
versions should only occur when migrating between releases.
The following table details the features of NVR 3 used with Control Center 4 or later.
Feature
NVR 3
Continuous recording job Y

Timed recording job
Record on alarm
Playback
Alarms
Bookmarks
ONVIF
The following table details the compatibility of the standalone NVRs and NVR-AS.
55
C Migrating from Control Center 3
Control Center
Standalone NVR version
Compatibility
vp850
Not compatible
vp852
Only NVR capability (3.15.1 firmware or later)
NVR200 (vp851)
Only NVR capability (3.15.1 firmware or later)
NVR-AS 3000
NVR capability with all 3.x firmware. Upgradeable to full NVR-AS with Control
Center 4 r2 or later

1. Upgrade your NVRs to the latest NVR 3 release
2. Upgrade your Control Center front-end application to the latest Control Center 3
release
3. Upgrade your Control Center front-end application to the latest release
4. Upgrade your NVRs to the latest NVR-AS release
5. Migrate the alarm sources from your 3.x installation
6. Reconfigure the binary inputs on IndigoVision devices
Upgrade to the latest NVR 3 release

To successfully migrate to IndigoVision Control Center, you must upgrade to the latest NVR
3 release before migrating to NVR-AS 4. Please refer to the relevant Installation Guide for
further information.
Notice
Upgrade your Failover NVRs first, followed by your Primary NVRs.
Upgrade to the latest Control Center 3 release

To successfully migrate to IndigoVision Control Center, you must ensure that your site
database is compatible for the migration by upgrading to the latest release of Control Center 3
front-end application.
1. Install the latest release of Control Center 3 front-end application.
Please refer to the relevant Installation Guide for further information.
2. Log into the Control Center front-end application as an administrator.
3. Make a minor change to the site database, for example, change the top site name.
This forces Control Center to update the site database to the latest format.
4. Undo the change and close the front-end application.
Upgrade to the latest version of Control Center front-end application

You can install the latest version of the Control Center front-end application on the same PC
as Control Center 3. This allows you to configure the new version while continuing to use
your existing Control Center 3 installation.
For more information about installing Control Center, see "Control Center front-end
application Installation" on page 13
During installation, select Import an existing Control Center 3 site database on the Site
Database Details dialog. The installer creates a new site database at the location specified.
56
Control Center
The new site database contains all site information with the exception of the alarm-related
information.
Notice
The Control Center 3 site database is kept after the new version of the Control Center
front-end application is installed. This enables you to downgrade to your previous Control
Center 3 installation if necessary.
After installation, you must upgrade the audit log database to the latest version. For more
information, see the Audit Log Reference Guide.
Upgrade to NVR-AS 4
Install the latest NVR-AS 4 release. For more information about installing NVR-AS 4, see
"NVR-AS Installation" on page 9.
Notice
Upgrade your Failover NVRs first, followed by your Primary NVRs.

During installation the NVR-AS 4 installer copies the configuration data to new databases,
leaving the original NVR database available.
Should you need to revert to your previous NVR version, you can downgrade the NVR-AS
installation.
For more information about downgrading an NVR-AS installation, see "Downgrading an
NVR-AS" on page 61
Caution
Footage recorded on an NVR-AS 4 cannot be played on an NVR 3. Therefore, any

footage recorded by the NVR-AS 4 will not be accessible after you downgrade to NVR 3.
Migrate alarm sources

Once you have successfully installed Control Center, you can migrate the alarm sources
from your 3.x installation.
To migrate alarm sources you must use the Control Center Alarm Source Migration tool and
the Alarm Server Configuration tool. These tools are provided on the IndigoVision Control
Center CD.
For information about using the Alarm Server Configuration tool, refer to Alarm Server
Configuration Tool Administration Guide provided with the tool
For information about using the Control Center Alarm Source migration tool, refer to
Control Center Alarm Source Migration Tool online help provided with the tool
Before migrating your alarm sources, it is important that you plan how your alarms will be
managed in IndigoVision Control Center.
For information about planning the migration, see "Planning your migration of 3.x
installation alarm sources" on page 59
To migrate alarm sources from a 3.x installation, you need to use the following steps:
1. Plan your migration to ensure the zones and detectors created behave as expected.
2. Export the alarm sources from the 3.x installation.
3. Import the new zones, detectors and actions into an Alarm Server.
57
Control Center
4. Complete any additional configuration in Control Center as necessary.
Export 3.x installation alarm sources

To migrate alarm sources, you need to export them from the 3.x installation. If you intend to
use more than one Alarm Server in the new installation, export the alarm sources destined for
each new Alarm Server in different batches.
1. Install and open Control Center Alarm Source Migration.
During installation you must select the Control Center 3.x site database that you are
migrating.
2. Select the alarm sources that you want to migrate.
If your list is large, use the options at the top of the list to filter the list.
3. Right-click the selected alarm sources and click Export to SMS4 Format....The
Export to SMS4 Format dialog opens.
4. Enter the Base Name for the exported files and choose the Export folder these
files are saved to.
The alarm sources are exported as two .csv files. One contains details of the new
zones and detectors, the second the details of the alarm actions. The file names are
[Base Name]_Detectors.csv, and [Base Name]_Actions.csv.
5. Click OK. The alarm sources are saved to the export files and the Migration Warnings
dialog opens.
Control Center Alarm Source Migration validates the alarm sources you have selected,
and displays a list of warnings on the Migration Warnings dialog. The warnings provide
details of alarm sources that cannot be exported, as well as any additional
configuration required in later versions of Control Center.
6. Click Save and exit to save the list of warnings as an .html file that you can refer to
when configuring the alarms in later versions of Control Center. The dialog closes.
Import 3.x installation alarm sources

To complete the migration of 3.x installation alarm sources, you need to import them into an
Alarm Server using the IndigoVision Alarm Server Configuration tool. The Alarm Server
Configuration tool enables bulk creation of zones, detectors and actions on an Alarm Server.
1. Edit the detector and action .csv files if necessary.
The majority of the zone, detector and action settings can be edited in the .csv files. It
may be more convenient to make changes prior to importing, for example, grouping the
detectors by logical zones.
2. Use the Alarm Server Configuration tool to import the detector and action .csv files into
an Alarm Server.
3. After importing the new zones, detectors and actions, you may need to complete
additional configuration using Control Center.
Use the list of migration warnings to identify the additional configuration required in
Control Center.
For more information about configuring zones, detectors and activations in late versions of
Control Center, please refer to the Control Center online help.
Re-configure binary inputs on IndigoVision devices

Before you can use the physical input detectors in your IndigoVision Control Center system,
ensure the binary inputs of IndigoVision devices are correctly configured.
58
Control Center
1. For each camera, transmitter, receiver, or alarm panel, navigate to the Binary IO page
on the device's Configuration pages.
2. Ensure that both Low to High and High to Low events are configured for each input .
Alternatively, you can reconfigure large numbers of binary inputs using the Alarm Server
Configuration Tool.
Caution
If the binary input configuration is not updated, the physical input detectors may remain
in either the triggered or normal state.
Planning your migration of 3.x installation alarm sources

Control Center 4 and later provides a more sophisticated alarm management system than 3.x
installations. Events are detected by detectors such as a PIR or camera motion detection.
Detectors are grouped into zones to help manage alarms more effectively. Therefore, alarm
sources created in 3.x installation are not directly comparable to the zones and detectors in
later versions.
For more information about Control Center alarm management, please refer to the Control
Center help.
Before migrating your alarm sources, it is important that you plan how your alarms will be
managed in Control Center.
The following sections detail how 3.x installation alarm source settings are converted during
the migration. Use these sections to help you plan the migration. You have the following
opportunities to edit the alarm source to help simplify the migration:
In Control Center 3.x prior to exporting the alarm sources. For more information refer to
the Control Center help.
In the Alarm Source Migration tool prior to exporting the alarm sources.
Edit the detector and actions .csv files prior to importing into your new Control Center
installation, for example grouping detectors into zones. For more information refer to
the Alarm Server Configuration Tool Administrator Guide.
In Control Center after migration. For more information refer to the Control Center help.
Alarm sources
An alarm source maps to a single zone with one detector.
Name: Name of the Zone and the name of the Detector
Priority: Zone priority
Alarm source type

The alarm source type maps to the detector type.
Binary input: Physical
External input: External (any non-IndigoVision application that sends events to an

alarm server)
Video analysis: Analytics
Video lost: Video Fault (detector is activated on video loss, and deactivated on video
gain)
Network lost: Network Fault (detector is activated on network loss, and deactivated
on network gain)
59
Control Center
Tamper alarm source types are not migrated as they are not supported in Control Center 4
and later.
Video and Network gain events are used to deactivate Video and Network Fault detectors.
Ensure the corresponding Video or Network lost alarm source is selected to ensure a fault
detector is created.
During migration, warnings are displayed if these are present in the current 3.x installation.
Alarm source alarm procedures
Manual acknowledgement: Detector is alarmable with 0 sec dwell time
Latched acknowledgement: Detector is not alarmable with 0 sec dwell time
Timed acknowledgement: Detector is not alarmable with X sec dwell time
Automatic acknowledgement: Detector is not alarmable with 0 sec dwell time
Video source
The camera associated with the new detector is used as the default video source for that
detector. This may be different to the video source used by the original alarm source.
Recording actions on alarm sources

Recording actions map to recording actions on detectors.
Camera: The camera uses the same name.
Stop on alarm from: The recording action is configured to stop on detector

deactivation. The alarm source specified here is used for the detector deactivation
event if that alarm source type is supported in Control Center 4 or later.
However, if the activation alarm source is a Network or Video Lost, the deactivation
event will be the Network or Video gain event regardless of the alarm source defined
here.
Stop after: Stop recording after
Protect footage | Pre-alarm duration: Protect footage | Pre-event duration
Record audio: Record audio
The connection types use descriptive names:
UDP Unicast: Best effort
TCP: Reliable
UDP Multicast: Multi-cast
Relay actions on alarm sources

Relay actions on alarm sources map to relay actions on detectors.
On activation, set output pin high: Relay is normally open
On activation, set output pin low: Relay is normally closed
Automatically reset output pin X seconds after activation: Activate relay for
Xseconds
Do not automatically reset output pin: Activate relay
Video actions on alarm sources

Video action settings to move PTZ cameras to a preset map to PTZactions on detectors.
60
Default priority is 5
Control Center
Email actions on alarm sources

Email actions on alarm sources map to email actions on detectors.
Recipients are migrated
Email subject is updated to the new format
Settings not migrated

The following settings are not migrated. You will need to reconfigure these settings in Control
Center once the zones, detectors and actions have been imported.
Looped replay on video actions
Armed time
PA actions
Map Links
The following settings can be inherited from their parent sites. If they are not configured to be
inherited, you will need to reconfigure these settings in Control Center once the zones,
detectors and actions have been imported.
Alarm sound
Alarm procedure text
User response required when manually acknowledging an alarm
User access
Protection
Features not supported in IndigoVision Control Center

Certain alarm management features that were available in Control Center 3 and NVR 3 are
not supported in IndigoVision Control Center.
Manual deletion of alarms from the alarm log

Manually edit the alarm log to delete alarms. A reaping policy is now available on the Alarm
Server to control the deletion of alarms.
Tamper alarms
The tamper alarms that were associated with Tamper-Proof Alarm Panel inputs are no longer
supported.
Assign alarms
Assign an alarm to the current user so that several users do not attempt to deal with it at the
same time.
Downgrading an NVR-AS
You can downgrade an NVR-AS 4 installation to an NVR 3 if required. This may be useful if
you have received a standalone NVR-AS3000 with NVR-AS 4 pre-installed, or if you wish to
revert an upgrade. You can downgrade a Windows NVR-AS and an NVR-AS 3000.
61
Caution
Control Center
Footage recorded on an NVR-AS 4 cannot be played on an NVR 3. Therefore, any

footage recorded by the NVR-AS 4 will not be accessible after you downgrade to NVR 3.
An NVR-AS 3000 can be downgraded to NVR 3.23.1 or later. To downgrade a standalone

NVR-AS3000:
1. Navigate to the Firmware upgrade page in the Configuration pages.
2. Select the NVR 3.23.1 vex file.
A Windows NVR-AS can be downgraded to any previous NVR 3 version. To downgrade a
Windows NVR-AS:
1. Uninstall the Windows NVR-AS.
2. Install the version of NVR you require.
62
INSTALLING A WINDOWS NTP SERVER

Accurate time synchronization is critical for all elements in an IndigoVision security system.
IndigoVision cameras and NVR-AS 3000 units have built in network time protocol (NTP)
software accessible through the device web page.
Windows-based devices, including the NVR-AS 4000, VSM 4000, Camera Gateway servers
and workstations running the Control Center front-end application must be time
synchronized.
To synchronize your devices it is recommended that you use the Windows network time
protocol (NTP) server software included on the Control Center product CD.
Installation and configuration

This procedure tells you how to install and configure the Windows network time protocol
(NTP) server software.
Caution
When the Windows NTP daemon is installed, the standard Windows Time service
(W32Time) is disabled and can no longer be used.
1. Navigate to \English\Resources\NTP Server on the Control Center product CD.

2. Run vc_redist_x86.exe.
This installs the Microsoft Visual C++ 2008 Redistributable Package (x86) C++
runtime required by the NTP software.
3. Run ntp-4.2.6p5@london-o-lpv-win32-setup.exe.
This installs the Windows NTP daemon.
4. Accept the license agreement, default installation folders, and default settings.
5. On the Configuration Options dialog specify the time source for the NTP daemon.
6. Specify the upstream NTP servers using a comma separated list.
If you are installing the NTP daemon on a server (for example, NVR-AS 4000,
Windows NVR-AS, VSM 4000, or Camera Gateway) which is to be used as an
NTP server for downstream clients:
Select the check box Add local clock as a last resort reference.
If you are installing the NTP daemon on a Control Center PC, use these settings:
Do not select the check box Add local clock as a last resort reference.
7. Choose whether to create a new account or use an existing one to run the daemon.
If adding a new account the password must meet the criteria :
a. Be at least six characters in length.
b. Contain characters from three of the following four categories:
English uppercase characters (A through Z)
English lowercase characters (a through z)
63
D Installing a Windows NTP server
Base 10 digits (0 through 9)
Non-alphabetic characters (for example, !, $, #, %)
Control Center
If the password does not meet the requirements you get the error message ERROR
2245.
8. Use the default NTPService Settings.
The Windows NTP daemon is now configured to synchronize the system clock with the
upstream NTP servers. You can check the current state of time synchronization by running
the Quick NTP Status utility.
To run the utitlity:
Select Start Menu > All Programs > Meinberg > Network Time Protocol > Quick NTP
Status.
64

Install Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Install Guide

Uploaded by

Copyright:

Available Formats

IndigoVision

LTD. ACCEPTS NO LIABILITY FOR IMPROPER OR ILLEGAL USE OF THIS PRODUCT.

AS OTHERWISE AGREED WITH INDIGO VISION

Installation Guide - v17

About This Guide

Control Center front-end application Installation

Control Center front-end application operating system specification

Control Center Client front-end application Installation

Installation Guide - v17

Camera Gateway Installation

Camera Gateway overview

Mobile Center Service Installation

IndigoVision Firewall Requirements

Ports required by 8000, 9000, 11000 Range cameras and encoders

Microsoft SQL Server Express 2008 installation fails to complete

Installation Guide - v17

Ports required by Control Center front-end application

NVR-AS Post-Installation Network Drive Configuration

Migrating from Control Center 3

Installing a Windows NTP server

Installation Guide - v17

Installation Guide - v17

ABOUT THIS GUIDE

Installation Guide - v17

1 About This Guide

Additional information relating to the current section.

Installation Guide - v17

NVR-AS operating system specification

Supported Operating Systems

Windows Server 2012

Windows Server 2008 R2 x64

Y (small systems only - up to 16 streams)

Y (small systems only - up to 16 streams)

Installation Guide - v17

Step 1: Prepare your video library

Recording onto a local drive

IndigoVision strongly recommends the use of disk redundancy technology such as

Recording onto a network drive

Step 2: Install the NVR-AS

Installation Guide - v17

The maximum length of a chunk is limited to four hours of footage.

Enable Tamper protection on recordings to verify that recordings made by the

11.Configure the alarm management settings, then click Next.

Upgrading the NVR-AS

Installation Guide - v17

Installation Guide - v17

CONTROL CENTER FRONT-END APPLICATION

Control Center front-end application operating system

Supported Operating Systems

Audit logging is required to use the Spot Monitor Export function.

Installation Guide - v17

3 Control Center front-end application Installation

Control Center front-end application

Your Operating System may require you to authorize this installation.

Set up a site database

Select Use existing site database if:

Select Create new site database if:

Installation Guide - v17

3 Control Center front-end application Installation

Select Modify current site database if:

Select Import an existing Control Center 3 site database if:

The IndigoVision Control Center alarm management configuration is significantly

Use an existing Control Center site database

Create a new site database