Install Guide

IndigoVision
IndigoVision SMS4
Installation Guide
IndigoVision SMS4
T HIS MANUAL WAS CREATED ON 25 APRIL 2012.
DOCUMENT ID: IU-SMS-MAN001-5
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 - v5
TABLE
OF
CONTENTS
Legal Considerations
Copyright
Contact address
2
2
2
About This Guide
System configurations
IndigoVision documentation
Safety Notices
7
7
8
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
Control Center Installation
9
9
10
10
10
10
10
13
Control Center operating system specification

Audit logging
Installation procedures
Control Center
Incident Player
The Control Center site database
Using a local site database
Using a central site database
Preventing changes to the site database
Partner branding
Windows firewall
Turning off the firewall
Creating firewall exceptions
Unattended Installation
Installer properties
Prerequisites
Examples
13
13
13
14
17
17
17
18
18
18
19
19
19
19
20
20
21
Control Center Client Installation
23
Installation procedure
Control Center Client
The Control Center Client site database
Windows firewall
23
23
24
24
IndigoVision SMS4

Prerequisites
Examples
24
24
24
25
25
26
Camera Gateway Installation
29
Camera Gateway overview

Intended use
Prerequisites
29
29
29
30
30
Installation
30
Mobile Center Service Installation
33
Overview
Prerequisites
Windows Vista, Windows 7 and Windows Server 2008
Windows XP
Windows Server 2003
Install SSLcertificate
Windows XP
Windows Server 2003
Windows 7, Windows Server 2008 R2, Windows Vista
Configuration
Download and configure the Mobile Center app
Deregister a device
Change the Mobile Center Service port
Windows XP, Windows Server 2003
33
33
33
33
34
34
34
34
35
36
36
36
37
37
37
37
38
Troubleshooting
39
Microsoft SQL Server Express 2005 installation fails to complete

The IndigoVision MobileCenter Administration page cannot be displayed
IndigoVision Firewall Requirements

Ports required by transmitters
Ports required by 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
Ports required by Control Center
Ports required by Camera Gateway
Ports required by Mobile Center Service
Ports required by Mobile Center app
39
39
41
41
42
43
43
44
44
45
45
46
46
46
IndigoVision SMS4
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 to IndigoVision SMS4
47
49
49
49
50
51
Network Video Recorders and Alarm Servers

NVR-AS compatibility
Upgrade to the latest NVR 3 release
Upgrade to the latest Control Center 3 release
51
51
52
52
52
Upgrade to Control Center 4

Upgrade to NVR-AS 4
Re-configure alarms
Re-configure binary inputs on IndigoVision devices
Features not supported in IndigoVision SMS4
Manual deletion of alarms from the alarm log
Tamper alarms
Assign alarms
Downgrading an NVR-AS
52
53
53
53
54
54
54
54
54
IndigoVision SMS4
ABOUT THIS GUIDE

This guide details how to install version 4 of all components of the IndigoVision Security
Management System (SMS).
IndigoVision SMS4 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.
IndigoVision SMS4 consists of two main applications: Control Center, the client software,
and NVR-AS, the recording and alarm management software. Additional applications are
provided to enhance the capabilities of the solution.
"NVR-AS Installation" on page 9 details NVR-AS installation, and takes you through
required system specification, preparatory steps, and installation.
"Control Center Installation" on page 13 details Control Center and Incident Player
installation.
"Control Center Client Installation" on page 23 details Control Center Client

installation.
"Camera Gateway Installation" on page 29 details Camera Gateway installation.
"Mobile Center Service Installation" on page 33 details Mobile Center Service

installation.
System configurations
When using the Windows NVR-AS application, you can choose a system configuration to
match your requirements:
Control Center and the NVR-AS installed on the same computer for small systems
only
Control Center 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 "SMS 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
1 About This Guide
IndigoVision SMS4
Safety Notices
This guide uses the following formats for safety notices:
Warning
Indicates a hazardous situation which, if not avoided, could result in death or serious
injury.
Caution
Indicates a hazardous situation which, if not avoided, could result in moderate injury,
damage the product, or lead to loss of data.
Notice
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.
Caution
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
Supported
Windows Server 2008 R2 x64
Y (recommended)
Windows Server 2008
Windows Storage Server 2008
Windows Server 2003
Windows Server 2003 x64
Windows Storage Server 2003
Windows 7
Y (small systems only - up to 16 streams)
Windows Vista
Windows XP Professional
Windows XP Home / Media / Tablet
Windows 2000
Windows NT 3.x / 4.x
2 NVR-AS Installation
Notice
IndigoVision SMS4
IndigoVision recommends that you use Windows Server 2008 R2 when using the
Windows NVR-AS. If your NVR-AS has video library volumes of greater than 2 TB you
must use Windows Server 2003 SP1 or later.
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 2008 R2 or
Windows Server 2004 x64.
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 on how to do this, see "NVR-AS Post-Installation
Network Drive Configuration" on page 49.
Step 2: Install the NVR-AS

To install the NVR-AS:
1. If you have a license key for ONVIF video streams, insert the license dongle into the
USB port of the PC or server. If you do not, you can still install the NVR-AS, however,
10
IndigoVision SMS4
only one ONVIF video stream will be available for demonstration purposes.
You do not need a licence key for video streams from IndigoVision devices.
Notice
You can insert a license key after installation. It may take several minutes for the license
to register with the software.
2. Insert the IndigoVision SMS4 CD into the CD drive of the PC or server on which you
are installing the NVR-AS application. The IndigoVision SMS4 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 by IndigoVision Control Center and
other client applications.
8. Specify the path to the video and configuration data, then click Next.
9. Configure the network settings, then click Next.
Notice
Only choose encoder 2 if all transmitters to be recorded provide dual encoders.
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 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.
11
12
IndigoVision SMS4
CONTROL CENTER INSTALLATION

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

We recommend that you use the following guidelines for the Control Center PC operating
system.
Table 2:

Operating System
Supported
Windows 7 32-bit
Windows Vista 32-bit
Windows XP Professional 32-bit
Y (recommended)
Windows 7 64-bit
Y (recommended)
Windows Vista 64-bit
Windows XP Professional 64-bit
Audit logging
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 Control Center (you must be
logged in as an administrator).
Control Center provides an audit logging function that enables many common user actions
can be logged in an ODBC compliant database, for example, Microsoft SQL Server.
Notice
Audit logging is required to use the Spot Monitor Export function.

For information on setting up audit logging, see the Audit Log Reference Guide
Installation procedures
This section describes the installation procedures for Control Center and Incident Player.
13
3 Control Center Installation
IndigoVision SMS4
An alternative variant that does not include site setup functionality, Control Center Client, 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 Installation" on page 23
Control Center
You must be logged into Windows as administrator to install Control Center.
When installing Control Center, you have the option to set up your site database. If you are
installing Control Center on a PC for the first time, you must set up the site database.
For more information on site databases, see "The Control Center site database" on page
17
Notice
Your Operating System may require you to authorize this installation.
Install ControlCenter
1. Insert the IndigoVision SMS4 CD into the CD drive of the PC on which you are
installing Control Center. The IndigoVision SMS4 install screen opens.
2. Click Install for the Control Center component, 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 ControlCenter, 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, Control
Center 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, you must select the site database settings.
1. Select an option and click Next.
Select Use existing Control Center 4 site database if:
you have already created a Control Center 4 site database which you want to use.
you are installing Control Center on an operators PC, and you want it to access a
central site database.
Go to step 2 if you select this option.
Select Create new site database if:
this is the first time you have installed Control Center 4, or
you are installing Control Center on only one PC.

14
Select Import an existing Control Center 3 site database if:
IndigoVision SMS4

you are upgrading from Control Center 3 and wish to create a Control Center 4
compatible site database from your Control Center 3 site database.
For more information about migrating to IndigoVision SMS4, please refer to
"Migrating to IndigoVision SMS4" on page 51
Caution
The IndigoVision SMS4 alarm management configuration is significantly different to the

3.x configuration. Therefore, migrating from 3.x installations to a 4.x installation is
complex, and alarms generated in 3.x are not compatible with 4.x.
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.
2. If you have selected to use an existing Control Center 4 site database, click Browse
and navigate to the folder where the database is located.
Select Upgrade PTZ protocols to upgrade to the latest protocols installed with
Control Center.
Caution
If you have customized your PTZ protocols, do not select this option, as your changes
will be lost.
Click Next. The Software Upgrade Plan dialog opens.
3. If you have a Software Upgrade Plan (SUP),select Yes and enter your SUP contract
number.
Otherwise, select No.
Click Next. The Back up Site Database Details opens.
4. 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.
Click Next. The Finish dialog opens. Go to step 12.
5. If you have selected to create a new site database, click Browse and navigate to
where you want to save the database.
Click Next. The Administrator Details dialog opens.
6. Select the authentication method used to authenticate the administrator.
Notice
To use Windows authentication, either enter a Windows account or click Browse

and select the required account. When the administrator tries to log in, Control
Center 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 Control Center. This must contain between 8 - 14 alphanumeric
characters.
You set up individual user accounts once you log into Control Center.
15
IndigoVision SMS4
number.
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, see 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. Go to step 12.
9. If you have selected to import an existing Control Center 3 site database, use the
Browse buttons to specify where the Control Center site database is located, and
specify where you want to save the new Control Center 4 site database.
Select Upgrade PTZ protocols to upgrade to the latest protocols installed with
Control Center.
Caution
will be lost.
10.If you have a Software Upgrade Plan (SUP),select Yes and enter your SUP contract
number.
Click Next. The Configure Audit Log dialog opens.
11.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, see 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.
12.Click Finish to complete the site database setup.
16
IndigoVision SMS4
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
Control Center.
To install Incident Player:
1. Insert the IndigoVision SMS4 CD into the CD drive of the PC on which you are
installing Incident Player. The IndigoVision SMS4 install screen opens.
2. Click Install for the Incident Player component, and follow the on-screen instructions
to complete the installation.
The Control Center 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>Site Database Setup.)
There are two ways to use the site database:
Notice
Locally - the site database is stored on an individual PC. If you have installed Control
Center on only one PC you should use a local site database.
Centrally - the site database is stored on a Windows file server and users access the
data across the network. If you have installed Control Center on several PCs you
should use a central site database.
Only one Control Center instance should write to the site database at any one time.
Using a local site database

During installation you are asked to select whether you want to create a new site database or
use an existing one.
Notice
Although you specify a location for the site database during installation, you can
change this at any time using the Site Database Setup Utility
(Programs>IndigoVision> Control Center>Site Database Setup).
If this is the first time you have installed Control Center on this PC, select Create new
site database. A site database file is automatically created in the folder specified.
If you are re-installing Control Center 4 on this PC and already have a site database,
select Use existing site database and enter the folder in which it is stored.
17
IndigoVision SMS4
If you are upgrading from Control Center 3 to Control Center 4, select Import an
existing Control Center 3 site database. and select the location of the existing
Control Center 3 site database, and where you want to create the new Control Center
4 site database.
Using 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 Control Center is installed
a Windows file server
Ensure that the folder you select for the site database is accessible by other PCs.
Preventing changes to the site database

Once you have set up your site hierarchy and completed configuration, you may want to
modify the Windows security settings for your site database to prevent changes being made
by unauthorized users.
1. Locate the site database folder, for example, C:\IndigoSiteDB, using Windows
Explorer.
2. Right-click this folder and select Properties.
3. Click the Security tab.
4. Modify the security settings as required. Please consult the Windows help system for
detailed information on security settings.
Security settings must be applied to the site database folder as a whole, not to individual files
or folders within it.
Partner branding
You can customize the Control Center interface to include your companys name and logo.
Your company logo appears on the login screen, and company name appears in the Control
Center title bar.
IndigoVision provides a .bmp and a .txt file for you to edit with your company details.
1. On the IndigoVision SMS4 CD, navigate to Resources\PartnerBranding.
In the partnertext.txt file, enter the text you want to appear in Control Centers title bar,
and save it in the folder where Control Center 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 Control Center 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 installation directory. Enter the
following at the prompt:
ccbrand.exe
4. Open Control Center to check the login screen and title bar are customized.
18
IndigoVision SMS4
Figure 1: Example of customized login screen
Figure 2: Example of customized title bar
Windows firewall
Firewall protection is automatically enabled on PCs running Windows Vista , or Windows
7. If you have installed Control Center on either of these operating systems, the firewall may
prevent correct operation of Control Center 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 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.

Alternatively, you can create firewall exceptions for the Control Center application and the
NVR-AS service. For more information about creating exceptions, see the Windows help
system.
IndigoVision port numbers are listed in "IndigoVision Firewall Requirements" on page 41
Unattended installation enables system administrators to installControlCenter or Control
Center Client using group policies. This enables system administrators to automate
installation to ensure the correct version of ControlCenter or Control Center Client is
available to users.
The following sections provide the information a system administrator requires to implement
unattended installation within your organization's environment.
19
IndigoVision SMS4
To perform an unattended installation of ControlCenter or ControlCenter Client, 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 SMS CD under Unattended Installation.
Prerequisites
The Control Center and Control Center Client installers have several prerequisites for the
target PC before running the Control Center or Control Center Client installer.
The following applications and registry settings are prerequisites for ControlCenter
Installation.
ControlCenter site database location
This is stored in the registry:

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

This contains the database location, for example, C:\IndigoSiteDb.
Windows Installer 3.1 v2 or later
WindowsInstaller-KB893803-v2-x86.exe
Available on the SMS4 CD in the Control Center folder.
This component is already installed on Windows Vista and later.
Microsoft .NET Framework 4 Client Profile
dotNetFx40_Client_x86_x64.exe
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 Control Center 4 or
ControlCenter Client 4 has been installed on this PC or whether it is being upgraded. If
Control Center or ControlCenter Client 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 4 installation

Prerequisite
20
Required
Control Center site database location
Yes
Windows Installer 3.1 v2
Windows XPonly
Yes
Yes
Yes
IndigoVision SMS4
Notice
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
No
Yes
Yes
Yes
Table 5:
Upgrading from Control Center 4.2 or 4.3

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

Prerequisite
Required
No
No
No
No
No
Examples
Examples of registry scripts are available on the product 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 SMS CD under Unattended
Installation.
An example Microsoft Windows Installer Transform file (.mst) with the required settings is
available in the Resources folder on the SMS CD under Unattended Installation.
21
22
IndigoVision SMS4
CONTROL CENTER CLIENT INSTALLATION

This chapter describes how to install the Control Center Client 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 SMS4 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 SMS4 CD or Control Center Client CD into the CD drive of the
PC on which you are installing Control Center Client. The IndigoVision SMS4 install
screen opens.
2. Click Install for the Control Center Client component, and follow the on-screen
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 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 Installation
Caution
IndigoVision SMS4
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 Control Center on either of these operating systems, the firewall may
prevent correct operation of Control Center 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 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.

Alternatively, you can create firewall exceptions for the Control Center application and the
NVR-AS service. For more information about creating exceptions, see the Windows help
system.
IndigoVision port numbers are listed in "IndigoVision Firewall Requirements" on page 41
Unattended installation enables system administrators to installControlCenter or Control
Center Client using group policies. This enables system administrators to automate
24
IndigoVision SMS4
installation to ensure the correct version of ControlCenter or Control Center Client 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 ControlCenter or ControlCenter Client, 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 SMS CD under Unattended Installation.
Prerequisites
The Control Center and Control Center Client installers have several prerequisites for the
target PC before running the Control Center or Control Center Client installer.
The following applications and registry settings are prerequisites for ControlCenter
Installation.
ControlCenter site database location
This is stored in the registry:

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

This contains the database location, for example, C:\IndigoSiteDb.
Windows Installer 3.1 v2 or later
WindowsInstaller-KB893803-v2-x86.exe
This component is already installed on Windows Vista and later.
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 Control Center 4 or
ControlCenter Client 4 has been installed on this PC or whether it is being upgraded. If
Control Center or ControlCenter Client 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.
25

Table 7:
IndigoVision SMS4
New Control Center 4 installation

Prerequisite
Notice
Required
Yes
Windows XPonly
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
No
Yes
Yes
Yes
Table 9:
Upgrading from Control Center 4.2 or 4.3

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

Prerequisite
Required
No
No
No
No
No
Examples
Examples of registry scripts are available on the product 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 SMS CD under Unattended
Installation.
26
IndigoVision SMS4
An example Microsoft Windows Installer Transform file (.mst) with the required settings is
available in the Resources folder on the SMS CD under Unattended Installation.
27
28
IndigoVision SMS4
CAMERA GATEWAY INSTALLATION

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

The IndigoVision Camera Gateway enables 3rd party cameras from a range of manufacturers
to be connected to an IndigoVision SMS4 system. The Camera Gateway takes video
streams from 3rd party cameras using their native protocols and enables users to view the
streams in Control Center 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 motion detection 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 3rd party cameras from a range of manufacturers to be
connected to an IndigoVision SMS4 system. If, for example, you want to use ControlCenter
to view a location in which 3rd 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 (32bit)
MS Windows 7 (64bit)
MS Windows Server 2008 R2
IndigoVision recommends that you install Camera Gateway on a server-style system, with a
server network adaptor. For systems with more than 16 streams it is recommended to use
Windows Server 2008 R2.
29
5 Camera Gateway Installation
IndigoVision SMS4
The Camera Gateway installer first checks the system for the prerequisite components:
Microsoft .NET Framework 4, and Microsoft SQLServer 2005 Express Edition. The installer
then installs each prerequisite component required, before installing the three components of
the Camera Gateway.
Notice
We don't recommend installing the Camera Gateway on a system with Microsoft SQL
Server 2008 already installed.
Prerequisites
The following prerequisites are required to install and use the Camera Gateway.
You require a license key to use the Camera Gateway. If you do not have a license
key, you can still install the Camera Gateway, however, only four video streams will
be available for 30 days after installation for demonstration purposes.
Ensure the .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 SMS4 CD into the CD drive of the PC or server on which you are installing
the Camera Gateway application. The SMS4 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 2005 Express Edition is not installed, you will be prompted to
install it. Follow the on-screen instructions.
If the Microsoft SQLServer 2005 installation fails to complete, you must manually
remove the components.
For more information, see "Microsoft SQL Server Express 2005 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 SMS4
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
license options.
30
Select Use Demo License to install the Camera Gateway without entering a
license key. The demo license enables four streams for 30 days, for demonstration
purposes only.
IndigoVision SMS4
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.
Select Enter License Key if you have a Camera Gateway license key. Type the
license key and click Check License 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.
31
32
IndigoVision SMS4
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 site using a mobile device.
The Mobile Center Service provides the interface between the IndigoVision site database and
the Mobile Center app installed on the mobile device.
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.
Notice
The Mobile Center Service must be installed on the same PCor server that hosts the
IndigoVision site database.
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
Prerequisites
Before installing the Mobile Center Service, you must configure the Internet Information
Services (IIS) feature. The configuration depends on the operating system.
Windows Vista, Windows 7 and Windows Server 2008

Ensure the following features are installed and enabled.
IIS 6 Management Compatibility
IISManagement Console
33
6 Mobile Center Service Installation
.NETextensibility
ASP .NET
ISAPI Extensions
ISAPI Filters
Default Document
Static Content
Basic Authentication
Request Filtering
IndigoVision SMS4
Windows XP
Ensure the following subcomponents of Internet Information Services (IIS) are installed and
enabled.
CommonFiles
Internet Information Services Snap-In
World Wide Web Service
Windows Server 2003

Ensure the following subcomponents of Application Server are installed and enabled.
Internet Information Services.
1. Install the SSL certificate provided.
For more information, see "Install SSLcertificate" on page 34
2. If you have a license key for the Mobile Center Service, insert the license 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
installation, for demonstration purposes.
3. Insert the IndigoVision SMS4 CD into the CD drive of the PC or server on which you
are installing Mobile Center Service. The IndigoVision SMS4 install screen opens.
and enter the path to the Installer.exe file on the CDROM
4. Click Install for the Mobile Center Service component, and follow the on-screen
instructions to complete the installation.
Install SSLcertificate
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 SMS4 CD in the
Mobile Center Service folder, but for security reasons it is recommended that you create
your own or purchase a certificate from a trusted certificate authority.
The installation procedure depends on the operating system of the PC or server that Mobile
Center Service is installed on.
34
IndigoVision SMS4
Windows XP
To install the SSL certificate on a PC or server running Windows XP, there are three steps
that need to be completed.
1. Add the Certificates snap-in.
For more information, see "Add the certificates snap-in" on page 35
2. Import theSSL certificate.
For more information, see "Import the SSL certificate" on page 35
3. Assign the SSL certificate.
For more information, see "Assign the certificate" on page 35
Add the certificates snap-in

1. Click Start > Run, and type mmc.
The Microsoft Management Console opens.
2. Click File > Add/Remove Snap-in....
3. Click Add, select Certificates and click Add.
4. Select Computer account, and click Next.
5. Select Local computer, and click Finish.
Certificates is added under Console Root.
6. Close all other dialog boxes as necessary.
Import the SSL certificate

1. Click Start > Run, and type mmc.
The Microsoft Management Console opens.
2. Expand Certificates.
3. Right-click Personal, and select All Tasks > Import....
The Certificate Import Wizard opens.
4. Click Next.
5. Click Browse, and select .pfx in the Files of type drop-down.
6. Navigate to the certificate file, 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. Ensure Place all certificates in the following store: Personal is selected, and click
Next.
9. Click Finish.
Assign the certificate

1. Click Start > Control Panel > Administrative Tools > Internet Information
Services.
2. Right-click Default Web Site, and select Properties.
3. Select the Directory Security tab, and click Server Certificate....
4. Select Assign an existing certificate, and click Next.
5. Select the Mobile Center Service certificate from the list, clickNext, and click Finish.
35
IndigoVision SMS4
Windows Server 2003

1. Click Start > Control Panel >Administrative Tools >Internet Information
Services.
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.
8. Type 49200 in the SSL Port field, and clickNext.
9. Click Finish.

To install the SSL certificate on a PC or server running Windows 7, Windows Server 2008
R2,or Windows Vista, there are two steps that need to be completed.
1. Import theSSL certificate.
For more information, see "Import the SSLcertificate" on page 36
2. Assign the SSL certificate.
For more information, see "Assign the certificate" on page 36
Import the SSLcertificate

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.
Assign the certificate

You must install the Mobile Center Service application before assigning the SSLcertificate.
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.
Configuration
The IndigoVision Mobile Center Administration page allows you to view all registered mobile
devices.
36
IndigoVision SMS4
To view the configuration page, navigate to https://<Server IP>:49200/mobilecenterservice,

where <Server IP> represents the IP address of the server. Use your ControlCenter
administrator username and password to access the administration page.
You can change the port number using IIS Manager.
For more information, see "Change the Mobile Center Service port" 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
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 on using the app, see the Mobile Center 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 on 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 port

The Mobile Center Service uses port 49200 by default. You can change this port using
IISManager. The procedure depends on the operating system of the PC or server that Mobile
Center Service is installed on.
Windows XP, Windows Server 2003

1. Click Start > Control Panel > Administrative Tools > Internet Information
Services.
3. Select the Web Site tab.
4. Type the new port for the Mobile Center Service in the SSLPort field, and click OK.
37
IndigoVision SMS4

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.
38
TROUBLESHOOTING
This chapter provides troubleshooting information for the installation of SMS4 applications.
Microsoft SQL Server Express 2005 installation fails to

complete
If the Microsoft SQLServer Express 2005 installation fails to complete, you must remove the
following components using Control Panel >Programs and Features before reinstalling.
Microsoft SQL Server 2005
Microsoft SQLServer Native Client
Microsoft SQL Server Setup Support Files (English)
Microsoft SQL Server VSSWriter
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 port" on page 37
For Windows Server 2003, the web service extension ASP .NET v2.0.50727 may be
prohibited. Use the IIS Manager to allow this extension.
The Windows service Mobile Center Service DB watcher (IVDBService) is not

installed and running. To install this service, run Install Windows Service.bat from
the Mobile Center Service folder on the SMS4 CD.
39
7 Troubleshooting
40
IndigoVision SMS4
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 transmitters

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

IndigoVision devices including Control
Center 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
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
OUT
UDP Multicast
Audio Control
UDP
49411
IN/OUT
Bandwidth
Management
UDP
49600
OUT
Used to request a bandwidth allocation from

the Bandwidth Manager
41
A IndigoVision Firewall Requirements
Service
Prot.
IndigoVision SMS4
Destination Port
Dir.
Comments
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 synchronisation
Syslog
UDP
514
OUT
External system logging support
SNMP
UDP
161
IN
Used for SNMP monitoring by 3rd party

network management tools
Ports required by receivers

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

Center and NVR-AS.
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

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
IN
UDP Multicast Audio Control UDP
49411
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
Used for passive FTP during bulk

upgrade
FTP data
TCP
1024-4999
IN

bulk upgrade
NTP
UDP
123
OUT
IndigoVision SMS4
Service
Prot.
Destination Port
Dir.
Comments
Syslog
UDP
514
OUT
SNMP
UDP
161
IN

Ports required by alarm panels

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

Center and NVR-AS.
Web Configuration
TCP
80
IN
telnet
TCP
23
IN
FTP cmd
TCP
21
IN
FTP data
TCP
1024-4999
IN

bulk upgrade
NTP
UDP
123
OUT
Syslog
UDP
514
OUT
SNMP
UDP
161
IN

Ports required by an NVR-AS

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

Center
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 Control Center
NVR Control Data
TCP
8130
OUT
Used for Alarm Server Record Actions and

fault monitoring
Alarm Server
Control Data
TCP
8131
IN

Alarm Server and Control Center
Playback
TCP
49299
IN
Used to playback video in Control Center
TCP Video
TCP
4940049402,4942049422
OUT

43
Service
Prot.
IndigoVision SMS4
Destination Port
Dir.
Comments
TCP Audio
TCP
49410
OUT
PTZ Control
TCP
49500 - 49509
OUT
Used for Alarm Server PTZ Actions
Firewall Friendly
transport type
ONVIF streams
TCP
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
IN
UDP Multicast
Audio Control
UDP
49411
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
Syslog
UDP
514
OUT
SNMP
UDP
161
IN

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

These may include further Windows services such as NTP and Remote Desktop
44
IndigoVision SMS4
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

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

IndigoVision devices.
NVR Control Data
TCP
8130
OUT

NVR-AS and Control Center
Alarm Server
Control Data
TCP
8131
OUT

Alarm Server and Control Center
Playback
TCP
49299
OUT
Used to playback video from an NVR
TCP Video
TCP
4940049402,4942049422
OUT

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
IN
UDP Multicast
Audio Control
UDP
49411
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
ONVIF streams
TCP
80
OUT
Communication with ONVIF devices
Reliable transport
type ONVIF
streams
TCP
554
OUT
FTP cmd
TCP
21
OUT
FTP data
TCP
1024-4999
OUT

bulk upgrade
Additional ports may be required for Windows services including:
NTP for time synchronisation
45
IndigoVision SMS4
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
License Activation
TCP
80
OUT
Camera Gateway License 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 Control
Center.
Control Data
TCP
47002
IN
Mandatory for communications with Control

Center
Events
UDP
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 Mobile Center Service

Service
Prot.
Destination Port
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
ControlData
46
Prot.
UDP
Destination Port
49300
Dir.
OUT
Comments
Mandatory for communications to
allIndigoVision devices.
IndigoVision SMS4
Service
Prot.
Destination Port
Dir.
Comments
TCPVideo
TCP
49400-49402,
49420-49422
OUT

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
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
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
47
48
IndigoVision SMS4
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.
49
B NVR-AS Post-Installation Network Drive Configuration
Notice
IndigoVision SMS4
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.
50
MIGRATING TO INDIGOVISION SMS4

Due to the change in architecture between Control Center 3 / NVR 3 and IndigoVision SMS4,
it is not possible for all database information to be migrated, for example, no alarm sources, or
alarm actions can be migrated. All video and user data is copied and migrated to a new
Control Center 4 database.
This appendix outlines the processes for migrating from Control Center 3 and NVR 3.
Caution
The IndigoVision SMS4 alarm management configuration is significantly different to the

3.x configuration. Therefore, migrating from 3.x installations to a 4.x installation is
complex, and alarms generated in 3.x are not compatible with 4.x.
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.
Network Video Recorders and Alarm Servers

An Alarm Server handles all alarm management for Control Center 4. To configure alarms
using Control Center 4, 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 Control Center for correct
operation. Mismatched Control Center and NVR-AS 4 versions should only occur when
migrating between SMS releases.
The following table details the features of NVR 3 and NVR-AS 4 which can be used from
Control Center 4.
Feature
NVR 3
NVR-AS 4
Continuous recording job
Timed recording job
Record on alarm
Playback
Alarms
Bookmarks
ONVIF
51
C Migrating to IndigoVision SMS4
IndigoVision SMS4
The following table details the compatibility of the standalone NVRs and NVR-AS with
SMS4.
Standalone NVR version
Compatibility
vp850
Not compatible with SMS4
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 SMS4
r2

1. Upgrade your NVRs to the latest NVR 3 release
2. Upgrade your Control Center to the latest Control Center 3 release
3. Upgrade your Control Center to the latest Control Center 4 release
4. Upgrade your NVRs to the latest NVR-AS 4 release
5. Reconfigure the alarms using Control Center 4 or the Alarm Server Configuration tool
6. Reconfigure the binary inputs on IndigoVision devices.
Upgrade to the latest NVR 3 release

To successfully migrate to IndigoVision SMS4, 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 SMS4, you must ensure that your site database is
compatible for the migration by upgrading to the latest release of Control Center 3.
1. Install the latest release of Control Center 3.
Please refer to the relevant Installation Guide for further information.
2. Log into Control Center 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 Control Center.
Upgrade to Control Center 4

You can install Control Center 4 on the same PC as Control Center 3. This allows you to
configure Control Center 4 while continuing to use your existing Control Center 3 installation.
For more information about installing Control Center 4, see "Control Center 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 Control Center 4 site database at the
52
IndigoVision SMS4
location specified. 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 Control Center 4 installation. 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 54
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.
Re-configure alarms
Once you have successfully installed Control Center 4, you need to reconfigure the alarms.
You can reconfigure the alarms using Control Center, or the Alarm Server Configuration Tool.
In Control Center 4, events are detected by detectors such as a PIR or pressure-sensitive
pad. Detectors are grouped into zones to help manage alarms more effectively.
For information about creating zones and detectors, refer to Manage zones and
detectors in the Control Center online help
The Alarm Server Configuration Tool enables bulk creation of zones, detectors and actions
on an Alarm Server (NVR-AS). The tool is provided on the IndigoVision SMS4 CD.
For information about using the Alarm Server Configuration Tool, refer to Alarm Server
Configuration Tool Administration Guide provided with the tool
Re-configure binary inputs on IndigoVision devices

Before you can use the physical input detectors in your IndigoVision SMS4 system, ensure
the binary inputs of IndigoVision devices are correctly configured.
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 .
53
IndigoVision SMS4
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.
Features not supported in IndigoVision SMS4

Certain alarm management features that were available in Control Center 3 and NVR 3 are
not currently supported in IndigoVision SMS4.
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.
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.
An NVR-AS 3000 can be downgraded to NVR 3.22.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.22.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.
54

Install Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Install Guide

Încărcat de

Drepturi de autor:

Formate disponibile

IndigoVision

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

AS OTHERWISE AGREED WITH INDIGO VISION

About This Guide

Control Center Installation

Control Center operating system specification

Control Center Client Installation

Turning off the firewall

Camera Gateway Installation

Camera Gateway overview

Mobile Center Service Installation

Microsoft SQL Server Express 2005 installation fails to complete

IndigoVision Firewall Requirements

Video stream configuration port usage

NVR-AS Post-Installation Network Drive Configuration

Migrating to IndigoVision SMS4

Network Video Recorders and Alarm Servers

Upgrade to Control Center 4

ABOUT THIS GUIDE

"Control Center Client Installation" on page 23 details Control Center Client

"Camera Gateway Installation" on page 29 details Camera Gateway installation.

"Mobile Center Service Installation" on page 33 details Mobile Center Service

1 About This Guide

Additional information relating to the current section.

IndigoVision strongly recommends the use of disk redundancy technology such as

NVR-AS operating system specification

Supported Operating Systems

Windows Server 2008 R2 x64

Windows Server 2008

Windows Storage Server 2008

Windows Server 2003

Windows Server 2003 x64

Windows Storage Server 2003

Y (small systems only - up to 16 streams)

Y (small systems only - up to 16 streams)

Y (small systems only - up to 16 streams)

Windows XP Home / Media / Tablet

Windows NT 3.x / 4.x

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

Only choose encoder 2 if all transmitters to be recorded provide dual encoders.

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

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

CONTROL CENTER INSTALLATION

Control Center operating system specification

Supported Operating Systems

Windows Vista 32-bit

Windows XP Professional 32-bit

Windows Vista 64-bit

Windows XP Professional 64-bit

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

3 Control Center Installation

Your Operating System may require you to authorize this installation.

Set up a site database

Select Use existing Control Center 4 site database if:

Select Create new site database if:

this is the first time you have installed Control Center 4, or

you are installing Control Center on only one PC.

Select Import an existing Control Center 3 site database if:

3 Control Center Installation

The IndigoVision SMS4 alarm management configuration is significantly different to the