2N C-CURE 9000 User manual

Configuration & User Guide
2N Intercoms Integration for C•CURE 9000
Security Classification:
Protected
Version:
1.0
Revision:
Rev1
Control:
Uncontrolled
when printed
Date
07/03/2022

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
Table of Contents
PART 1 PREFACE 5
1.1 FINDING MORE INFORMATION 5
1.1.1 C•CURE 9000 MANUALS 5
1.1.2 ONLINE HELP 5
1.1.3 CONVENTIONS 6
PART 2 INTRODUCTION 7
2.1 2N INTERCOMS INTEGRATION OVERVIEW 7
2.2 2N INTERCOMS INTEGRATION COMPONENTS 8
2.3 2N INTERCOMS INTEGRATION UTILIZATION 8
2.3.1 TERMINOLOGY 8
2.4 2N INTERCOMS SYSTEM CONFIGURATION 8
2.5 C•CURE 9000 CONFIGURATION 8
2.6 LICENSING THE 2N INTERCOMS INTEGRATION PRODUCT 9
2.6.1 C•CURE LICENSE 9
2.6.2 2N LICENSE 9
PART 3 INSTALLATION 10
3.1 2N INTERCOMS INTEGRATION DRIVER INSTALLATION 10
3.2 STARTING THE C•CURE 9000 SERVER SERVICES 13
3.2.1 REMOTE SQL CONFIGURATION 13
3.3 UNINSTALLING THE 2N INTERCOMS INTEGRATION 14
PART 4 C•CURE 9000 ENTERPRISE ARCHITECTURE CONSIDERATION 15
4.1 ENTERPRISE ARCHITECTURE CONSIDERATION 15
4.2 INSTALLATION ORDER 15
4.3 INTERCOM CONFIGURATION IN AN ENTERPRISE ARCHITECTURE 15
4.4 CREATING AN INTERCOM 15
4.5 MAS AND SAS ACTIONS 16
PART 5 C•CURE HARDWARE TREE 17
5.1 HARDWARE TREE PANE 17
PART 6 2N INTERCOMS CONFIGURATION 18
6.1 2N INTERCOMS OVERVIEW 18
6.2 2N INTERCOM TABS 18
6.3 ACCESSING THE 2N INTERCOM SERVER PANE 18
6.3.1 TO ACCESS THE 2N INTERCOMS SERVER PANE 18
6.4 CREATING A 2N INTERCOM OBJECT 19
6.4.1 TO CREATE A 2N INTERCOM 19
6.5 DELETING A 2N INTERCOM OBJECT 20

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
6.5.1 TO DELETE A 2N INTERCOM OBJECT 20
6.6 GENERAL TAB 21
6.6.1 GENERAL TAB 22
6.6.2 TRIGGERS TAB 23
6.6.3 TO CREATE A CUSTOM EVENT 23
6.6.4 CONFIGURING 2N EVENT TRIGGERS 26
6.7 STATE IMAGES TAB 27
6.7.1 CUSTOMIZING STATE IMAGES 27
6.7.2 RESTORE A DEFAULT STATE IMAGE 27
PART 7 CALL MANAGEMENT 28
7.1 HARDWARE TREE 28
7.2 DYNAMIC VIEW 28
7.3 MAPS 30
PART 8 UNLOCKING A C•CURE DOOR ON DTMF ACTIVATION 31
PART 9 MAP CONFIGURATION 32
9.1 CONFIGURING A MAP 32
9.2 MAP ANNUNCIATIONS 36
9.2.1 CONFIGURING MAP ANNUNCIATIONS 36
PART 10 C•CURE 9000 ALERTS AND JOURNALING SYSTEM 38
10.1 JOURNALING OVERVIEW 38
10.2 ACCESSING EVENT VIEWER AND ACTIVITY MONITOR 38
10.2.1 TO ACCESS ACTIVITY MONITOR 38
10.2.2 INTERPRETING JOURNAL MESSAGES 38
10.2.3 JOURNAL MESSAGES SUPPORTED 39
PART 11 TROUBLESHOOTING THE 2N INTEGRATION 40
APPENDIX 1 –CONFIGURATION OF 2N DEVICES 41
1. INTRODUCTION 41
2. SYSTEM OVERVIEW 41
3. 2N INTERCOM BASIC CONFIGURATION AND PREREQUISITES 41
3.1. LAN CONNECTION SETTING -2N IP INTERCOM 41
3.2. LAN CONNECTION SETTING -2N MASTER STATION 43
4. SETTING CALLING BETWEEN 2N IP INTERCOM AND 2N MASTER STATION 44
4.1. 2N IP INTERCOM SETUP 44
4.2. 2N MASTER STATION SETUP 48
4.3. 2N IP INTERCOM HTTP API ACTIVATION 49

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
Part 1 Preface
The 2N Intercoms Integration user manual is for new and experienced security system users who want to
learn to use this product for the C•CURE 9000 Security Management System.
1.1 Finding More Information
You can access C•CURE 9000 manuals and online Help for more information about C•CURE 9000 on the
Software House Portal.
1.1.1 C•CURE 9000 Manuals
C•CURE 9000 software manuals are available in Adobe PDF format on the C•CURE 9000 installation
media. You can access the manuals if you copy the appropriate PDF files from the C•CURE 9000
installation media Manuals\CCURE folder.
The available C•CURE 9000 Software House manuals are listed in the C•CURE 9000 Installation and
Upgrade Guide.
These manuals are also available from the Software House Member Center website:
(http://www.swhouse.com/TechnicalLibrary/TechLibSW.aspx).
1.1.2 Online Help
You can access C•CURE 9000 Help by pressing F1 or clicking Help from the menu bar in the
Administration/Monitoring Station applications.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
1.1.3 Conventions
This manual uses the following text formats and symbols.
Convention
Meaning
Bold
This font indicates screen elements, and also indicates when you should take
direct action in a procedure. Bold font describes one of the following items:
•A command or character to type, or
•A button or option on the screen to press, or
•A key on the keyboard to press
•A screen element or name
blue colour text
Indicates a hyperlink to a URL, or a cross-reference to a figure, table, or section
in this guide.
Regular Italic font
Indicates a new term.
<text>
Indicates a variable.
The following items are used to indicate important information.
NOTE
Indicates a note. Notes call attention to any item of information that may be of special
importance.
TIP
Indicates an alternate method of performing a task.
Indicates a caution. A caution contains information essential to avoid damage to the
system. A caution can pertain to hardware or software.
Indicates a warning. A warning contains information that advises users that failure to
avoid a specific action could result in physical harm to the user or the hardware.
Indicates a danger. A danger contains information that users must know to avoid death
or serious injury.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
Part 2 Introduction
This chapter introduces the 2N Intercoms Integration software that provides integration between the 2N
Intercoms and C•CURE 9000 access security management.
2.1 2N Intercoms Integration Overview
The C•CURE 9000 2N Intercoms Integration product provides integration between the 2N Intercoms and
the C•CURE 9000 Security Management System.
The C•CURE integration provides client components, server components and a Windows service. It is
based on a standard C•CURE CrossFire integration and provides the following features:
•2N Intercoms Editor
•Journal activity
•Event triggers based on server state
The integration driver acts as an interface between 2N Intercoms and the C•CURE access control system.
The solution has one main data flow component:
Outbound JSON data (driver): The driver monitors 2N intercoms through the use of their JSON REST API.
This allows the driver to retrieve the status of the devices and issue commands.
2N Master Station

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
2.2 2N Intercoms Integration Components
The C•CURE 9000 2N Intercoms Integration product introduces the following object into the C•CURE
9000 database to facilitate the integration between 2N Intercoms and C•CURE 9000.
•2N Intercoms –This represents the interface from C•CURE to 2N Intercoms where all
connection parameters are set.
2.3 2N Intercoms Integration Utilization
2.3.1 Terminology
The table below lists some terms and definitions related to the C•CURE 9000 2N Intercoms Integration
Product.
Term
Definition
2N Intercom
The configuration server object in C•CURE that represents the driver
interface between C•CURE and 2N Intercoms systems. The server object is
where all connection parameters are configured.
2N Intercoms Integration
Represents the C•CURE 9000 integration driver
2.4 2N Intercoms System Configuration
Configuration of 2N Intercoms systems is described in Appendix 1 of this document. There are some
environmental prerequisites for connectivity:
•API
oAPI connection needs to be enabled on the intercoms.
•Firmware
oFirmware needs to match the supported firmware. Please check the release notes for the
supported firmware version.
2.5 C•CURE 9000 Configuration
The C•CURE 9000 Administration Workstation is used to configure C•CURE 9000 objects. You must
configure the following objects in C•CURE 9000 for the 2N Intercoms Integration to function properly.
•2N Intercoms Server objects.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
2.6 Licensing the 2N Intercoms Integration Product
This integration has two licensing requirements:
2.6.1 C•CURE License
The 2N Intercoms Integration product is a licensed option for a C•CURE 9000 Server. You must purchase
this license from Software House support to use the software. In an Enterprise architecture, the MAS and
any SAS you wish to run the integration on must be licensed.
Only the server is licensed. You can have as many client connections as C•CURE is licensed for.
When you access the C•CURE 9000 License application on your C•CURE 9000 server, you can see if your
license includes the Cruatech - 2N Intercoms - Integration product by running the C•CURE 9000
Licensing program (Start>All Programs>Tyco>C•CURE 9000>Licensing) and clicking the Options tab. If
the Cruatech - 2N Intercoms - Integration product is selected, you have a valid license.
If you do not have a license for the 2N Intercoms Integration product, contact Software House to
purchase a license.
2.6.2 2N License
The server component also requires 2N licensing applied. The license screen is part of the installation
process:
Note: Steps to obtain/install license are described in the Installation section.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
Part 3 Installation
This chapter explains how to install and uninstall the 2N Intercoms Integration.
3.1 2N Intercoms Integration driver installation
1. Copy 2N-Intercoms-x.x.x.x.exe file to the local disk on the target C•CURE machine. The same
installation file may be run on standalone, MAS and SAS C•CURE servers and C•CURE clients.
2. From your local disk run 2N-Intercoms-x.x.x.x.exe as Administrator.
2N -Integration Setup appears:
3. Select the I agree to the license terms and conditions checkbox and click Install.
The following window appears:
4. Click Next.
If you are on a C•CURE server, the License Configuration screen appears:

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
5. Copy the Hardware Identifier using the Copy button and contact 2N Distributor to receive your
license. Once you have received your license file, copy it onto the server and click Browse to the
file path. Click Next.
6. The Destination Folder screen appears:
7. Click Next.
8. If the C•CURE server is on a domain, you will be prompted for Administrator credentials to
proceed with installation. Enter Domain, Login ID and Password details. Click Next to proceed:

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
9. The Ready to Install screen appears.
10. Click Install to start the installation.
11. The Installation Wizard Completed dialog box appears when the installation is complete.
Click Finish and then Close to complete the installation.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
3.2 Starting the C•CURE 9000 Server Services
Prior to configuring a 2N Intercoms integration object, the CrossFire Framework Service and CrossFire
Server Component Framework Service must be running.
To Start C•CURE 9000 Server Services
1. From the Start Menu, select Start>All Programs>Tyco>Server Configuration. Right-click on
Server Configuration and select Run as Administrator. The C•CURE 9000 Server Management
Application opens.
2. Click the Services tab.
3. If the Status is displayed as "Stopped" for the CrossFire Framework Service under Framework
Services, click Start.
4. If the Status is displayed as "Stopped" for the CrossFire Server Component Framework Service
under
5. Framework Services, click Start.
6. If the Status is displayed as "Invalid License" for the 2N Driver Service please contact your
C•CURE representative to obtain a valid license.
7. After the CrossFire Framework Service and CrossFire Server Component Service display a status
of "Running", start the 2N Intercoms Driver service.
When the CrossFire Framework Service, CrossFire Server and Component Framework Service and 2N
Driver service display a Status of "Running", you can configure 2N Driver Service objects in the C•CURE
9000. You only have to enable these services once.
3.2.1 Remote SQL Configuration
If the integration is installed on a C•CURE 9000 system configured with a remote SQL server, please
check the following directly after installation in the Server Configuration Application:
1. Navigate to the Database tab.
2. Find the NN.NextGenConnectedProgram.Objects entry, and confirm the Connection String is set
to the remote SQL instance.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
3.3 Uninstalling the 2N Intercoms Integration
This section describes how to uninstall the 2N Intercoms integration from the Server computer and Client
computers in your security system.
The Uninstall process removes all software components that were installed on the computer by the 2N
Intercoms Integration installation.
Please be advised that the 2N Intercoms Integration uninstall will shut down the C•CURE
9000 services. Therefore, the 2N Intercoms Integration uninstall should be planned
accordingly.
NOTE
Uninstalling this integration does not automatically remove 2N Intercoms specific
database objects.
To Uninstall the 2N Intercoms Integration
1. From the Windows Start menu, select Control Panel>Programs and Features.
2. In the list, click on 2N Intercoms Service –C•CURE Integration to highlight it.
3. Click the Uninstall button above the list.
4. Press OK to stop all Tyco services automatically.
5. Note: CrossFire Framework Service and CrossFire Server and Component Framework Service will
need to be restarted manually using the Server Configuration Application

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
Part 4 C•CURE 9000 Enterprise Architecture Consideration
This chapter provides guidelines on configuring C•CURE 9000 Enterprise Architecture configuration. If
you are configuring C•CURE for a standalone installation, then this next section can be ignored and you
can move on to the Hardware Tree chapter.
4.1 Enterprise Architecture Consideration
The Enterprise Architecture provides administrators with the ability to view and manage all aspects of
access control and security from one application - the Administration Workstation on a Master
Application Server, or MAS. From this vantage point, you can:
•View and edit 2N Intercoms server objects
•View server states
Because the Connected Program Kit integrations do not support data synchronization in an Enterprise
Architecture system, an integration can only run on a standalone C•CURE 9000 server or a Satellite
Application Server, or SAS within an enterprise. An integration that can run on a system in an Enterprise
Architecture must be specifically built to prevent unintended data synchronization with the Master
Application Server.
4.2 Installation Order
The 2N Intercoms installation must be performed in the following way in an Enterprise Architecture:
1. Install the 2N Intercoms on the MAS server first.
2. Install the 2N Intercoms on required SASs.
3. Ensure all enterprise servers have the same 2N Intercoms version installed (must be identical.)
4. If removing or upgrading the integration, perform the above steps in reverse order; uninstall the
server version from the SASs first, then remove the client from the MAS.
NOTE
The same 2N Intercoms server configuration on different SASs will be treated as separate
objects by the integration. A 2N Intercoms configured on SAS1 will not be visible on SAS2.
4.3 Intercom Configuration in an Enterprise Architecture
When creating an intercom in an Enterprise architecture there are some important factors to consider:
•You cannot create a 2N Intercom object on the MAS server partition.
•You cannot create a 2N Intercom object on the Global partition of a MAS or a SAS.
•An Intercom may only be created locally on a SAS which has the integration installed. This will
not work if configured on the SAS-partition of the MAS; (after successful configuration the
Hardware Tree of the MAS will be populated normally when viewing this SAS’s partition.)
•You cannot add 2N Intercoms objects to a map from the MAS. 2N Intercoms servers may only
be configured on a map from the appropriate SAS. Once configured, the objects will be visible
on the map from the MAS.
•A master station may only be associated with one server in an Enterprise architecture. This may
be the MAS, or a connected SAS with the 2N integration installed.
4.4 Creating an Intercom
To create an Intercom in a MAS/SAS environment carry out the following steps:
1. On a SAS with the full integration installed, Right-click a folder in the Hardware Tree and select
2N Intercom/New.
2. Fill out the appearing form, following General tab Definitions. Save and Close.
3. The Hardware Tree of the SAS, and MAS will show the 2N Intercoms server.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
NOTE
Creating and configuring the Intercom, and discovering devices for the Intercom must be
carried out directly on a SAS with the full integration installed.
4.5 MAS and SAS Actions
Once the 2N Intercoms are configured on the SAS and map objects configured as required, the
integration operates in a similar way to a standalone server in an Enterprise Architecture in C•CURE.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
Part 5 C•CURE Hardware Tree
This chapter explains how to use the 2N Intercom integration within the C•CURE 9000 Hardware Tree
Pane.
5.1 Hardware Tree Pane
The Hardware Tree displays a tree structure that shows how you have configured the integration objects
on the C•CURE 9000 system. For the 2N Intercoms integration, the 2N Intercoms group, and the servers
appear in the tree.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
Part 6 2N Intercoms Configuration
This chapter explains how to configure the 2N Intercoms in C•CURE 9000.
6.1 2N Intercoms Overview
The Intercom object represents a connection to the 2N Intercom. If intercoms are appropriately
configured, they may be auto-discovered on the network by the 2N Integration. Auto-discovery will
occur each time the driver is restarted. Any 2N intercoms discovered on the network will appear in the
first folder of the C•CURE Hardware tree (this is typically Company Name, but may be edited to re-
name).
NOTE 1
Auto-discovery only supports the device name and IP address. Username, Password,
Authentication Type and DTMF Code fields will need to be additionally configured for
auto-discovered intercoms. Master stations do not support auto-discovery.
NOTE 2
2N IP Intercoms as well as Master Stations must be configured prior to be used with the
CCure. Please see Appendix 1 of this document for more details.
6.2 2N Intercom Tabs
The 2N Intercom Server pane consists of two active tabs:
•General Tab
•Triggers
•State Images
6.3 Accessing the 2N Intercom Server Pane
This section explains how to access the 2N Intercom Server Pane.
6.3.1 To Access the 2N Intercoms Server Pane
•In the Hardware Pane of the Administration Workstation, select New, and create a 2N
Intercoms folder.
•Right click and select 2N Intercom from the context menu.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
6.4 Creating a 2N Intercom Object
This section describes how to create a 2N Intercom Object.
6.4.1 To Create a 2N Intercom
NOTE
If the installation is carried out in an Enterprise environment, please refer to the Post-
Installation in an Enterprise Environment section using General tab definitions table for
reference.
1. In the Hardware Tree of the Administration Workstation, right click the 2N Intercoms folder and
then right click on 2N Intercoms icon.
2. Select New.
3. Configure the following settings:
Field
Details
Use SIP Proxy
Check this checkbox if you wish to use SIP protocol for the
intercom –IP PBX is used in the network and the device is to be
registered to it and call through it.
SIP Number
(Read-only) The SIP number the device is registered with.
Technically, its Intercom Phone Numbers (ID) as configured in
the device.
Host
Enter the Intercom API URL to start the service on. Example:
https://192.168.170.151/
Username
The user name for the REST client to use for authentication.
This setting must match the API setting in the device.
Password
The password for the REST client to use for authentication.
This setting must match the API setting in the device.
Device Type
Endpoint/Master station. Master station supports 2N® IP Phone
D7A devices. The rest of the devices should be considered as
endpoints.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
Auth Type
Basic/Digest/None as per Intercom’s configuration.
DTMF Code
Enter the DTMF code to that will be used to open the C•CURE
door associated on the triggers tab. Only applicable for 2N
Devices.
This Code must match with “Switch Code” in 2N intercom
configuration and “Unlock PIN” in 2N Master Station
configuration.
Workstation
Enter the workstation PC name as described in the workstations
of C•CURE that the device is associated with. Only applicable for
master stations.
4. Click Save and Close to complete the configuration.
6.5 Deleting a 2N Intercom Object
This section describes how to delete a 2N Intercom Object.
Please be advised that deleting a 2N Intercom object won’t affect linked objects such as
C•CURE events and C•CURE journal messages. Even though a 2N Intercom object is not
present, C•CURE objects remain in place allowing historical data and events to be
viewed.
6.5.1 To Delete a 2N Intercom Object
1. In the Hardware pane, under the 2N Intercoms folder, select the 2N Intercom Object.
2. Right click and select Delete from the context menu.
3. Confirm the delete operation by pressing Yes, then OK.

Configuration & User Manual: 2N IP Intercoms and CCURE 9000
COPYRIGHT © 2022 2N Telekomunikace a.s. All rights reserved
6.6 General Tab
The General Tab enables the user to view and edit basic information about the 2N Intercom server
object.