C yberTech International

P.O. Box 75709

1070 AS Amsterdam

Hazenkoog 25

1822 BS Alkmaar

The Netherlands

Tel.: +31 (0)72 566 2 566

Fax: +31 (0)72 566 2 567

E-mail: info@c ybertech-int.com

Internet: www.c ybertech-int.com

IPC INTEGRATION

INSTALLATION MANUAL

For CyberTech Recording System 5.3.0 and higher

and CyberTech IPC CDR V3.14.0 or higher

Version: 1.25
Date: April 2010
Reference: CT-06-MV-IPC-IM

© 2010 All rights reserved. Nothing of this document may be duplicated and/or made public by means of print, photocopy,
microfilm or any other means without prior written consent of CyberTech B.V., The Netherlands.
Content

1 Introduction................................................................................................4
1.1 CyberTech Recording System ................................................................................... 4
1.2 CDR............................................................................................................................ 4
1.3 IPC ............................................................................................................................. 5

2 CDR integration ..........................................................................................6

2.1 E1 Recording Overview ............................................................................................. 6
2.2 Analogue Recording.................................................................................................. 7
2.2.1 Audio Connectivity....................................................................................... 7
2.2.2 Mixing........................................................................................................... 7
2.2.3 Cabling ......................................................................................................... 8
2.3 Time synchronization ................................................................................................. 8
2.4 IPC CDR Call Record Details ..................................................................................... 9
2.5 User management based on Trader ID ...................................................................11
2.6 Trader (Group) based archiving...............................................................................11
2.7 Required customer information ...............................................................................12
2.8 Limitations................................................................................................................12
2.9 Maintenance ............................................................................................................12

3 Installation and configuration....................................................................13

3.1 CyberTech Server / Core Server / Satellite ................................................................13
3.1 14
3.2 Separate server........................................................................................................14
3.3 Upgrading IPC installations .....................................................................................15
3.3.1 Removal existing CTI Processor software ..................................................15
3.3.2 Activation of legacy operation mode.........................................................15
3.4 CDR connectivity configuration ...............................................................................16
3.5 CDR channel mapping configuration ......................................................................16
3.5.1 Multiple speaker boxes ..............................................................................17
3.6 CDR Resilience.........................................................................................................19
3.7 Activate configuration changes ...............................................................................19
3.8 NTP Time synchronization .......................................................................................19

4 E1 Recording Resilience options N+1 Satellite failover .............................21

4.1 Analogue Resilience ................................................................................................22
4.2 Installation of N+1 failover components and licensing ...........................................23

IPC integration – installation manual 2

 4.2.1 Installation Prerequisites ............................................................................23
4.2.2 Installing the Resilience Components........................................................23
4.2.3 Licensing Details ........................................................................................24
4.3 Resilience groups.....................................................................................................24
4.3.1 Adding a resilience group..........................................................................24
4.3.2 Editing a resilience group ..........................................................................25
4.4 Resilience hosts .......................................................................................................25
4.5 Resilience configuration for N+1 resilience.............................................................27
4.6 N+1 Resilience operation ........................................................................................28

5 Appendix A – RS232 pin lay-out ...............................................................29

6 Appendix B - Parrot DSC PCM30 ..............................................................31

7 Appendix C – Parrot DSC-Mod Analogue .................................................33

8 Appendix D – Analogue Recording Cable Configuration...........................34

9 Appendix E - IPC CDR Database fields .....................................................35

10 Appendix F - Stand alone CDR server .......................................................38

11 Appendix G – N+1 resilience alarming......................................................39

12 Appendix H – Software Setup ...................................................................40

IPC integration – installation manual 3

1 Introduction

1.1 CyberTech Recording System

The CyberTech Recording System is built using open standards and
COTS hardware. The architecture is both flexible and scalable.
Recorder users will experience the same GUI for all solutions. All
recordings, even for multiple sites, can be archived to a central
storage. Rules based archiving and mirrored archiving is standard.
The recorder system is capable of recording trunk side, set side,
analogue and VoIP telephony. All types of recording can be mixed in a single recorder
system. Search and replay from the centralized storage location is achieved using a
centralized SQL database and the same recorder GUI. All the entries in the recorder are
logged in audit trails.
The D-channel signalling is available and used to determine: recording start and stop
triggers, call directions and number information. This allows the system to store voice and call
data at the same location, on a per call basis. Call information can be AES-256 encrypted and
MD5 fingerprinted when stored to hard disk.
The recorder operation and health is monitored locally or centrally using SNMP, web GUI, e-
mail and remote dial-in. All systems are built using similar hardware components, therefore
spare parts are universal for all systems around the world. Hardware resilience options like
dual hot-swap PSU and RAID disk solutions are included in the offering.
Multiple satellites can be connected to a single Core Server using an Ethernet network
connection. If for any reason this link fails, the Satellite will run in stand-alone fallback mode
until the link is re-established.
An optional CTI/CDR server can be used to send additional information from the Telecom
Switch to the CyberTech Recording System. This additional information is stored, linked to
the audio of the call, in the database.
For the IPC integration with the CyberTech recording System, a CDR connection is used.

1.2 CDR
In telecommunications, a Call Detail Record (CDR) (also Call Detail Recording) or Station
Message Detail Recording (SMDR) is a record containing information about recent system
usage, such as the identities of sources (points of origin), the identities of destinations
(endpoints), the duration of each call, the amount billed for each call, the total usage time in
the billing period, the total free time remaining in the billing period, and the running total
charged during the billing period. The format of the CDR varies among telecom providers
and call-logging software. Some software allows the CDR format to be configured by the
user.
CDR’s may be output to a file, may be sent as packets on a network, or may be output from a
serial port on telecom hardware.

IPC integration – installation manual 4

1.3 IPC
IPC Information Systems is a leading provider of mission-critical communications solutions to
the world's largest financial services firms, as well as to public safety; government security;
energy and power; and transportation organizations. IPC offers customers a suite of products
and enhanced services that include advanced Voice over Internet Protocol (VoIP) technology,
and integrated network and management services to more than 40 countries.
The Alliance MX system is designed as an open switching platform that allows
communication between user desktop instruments (turrets, consoles, speakers and intercom
modules), computers, data networks and telecommunications lines. With a modular design
each system can be configured for a firm's unique requirements.
Features:
• Utilizing VoIP technology allows for flexible deployment
• Performance under extreme conditions
• Stand alone support for 4,000 users and 16,000 lines per switch. Multi-switch
networking enables greater capacity.
• Unique mesh architecture ensures that complete system failures are not possible.
• Can provide every user with access to every line, radio channel, global intercom or
PaBX extension on the system.
• Fully non-blocking system
• Integration of disparate technologies to provide unified and interconnected
communications capability.

IPC integration – installation manual 5

2 CDR integration

2.1 E1 Recording Overview

The E1 integration between the CyberTech recorder and IPC Alliance For the IPC E1integration,
the following IPC switch
uses the Call Logging Port (CDR) and Voice Recorder Cards (TIC) specifications are assumed:
outputs of the IPC switch.
The Call Logging Port is a RS232 port provided by IPC System Center Brand IPC
connection. Appendix A contains connectivity details. The CDR output
will send a call record typically about 20 seconds after the call ends. Type Alliance
The CyberTech CTI server will collate the call and add IPC CDR IQMX
information to the database. v7.1.1 or
higher

The Voice Recorder Cards (TIC = Turret Interface Card) for E1/PCM30 recording are located
in the Alliance MX cabinet. Before connecting the recorder a mapping of the voice recorder
(E1/PCM30) channels against Station LAC including all mixing details, must be present.
Appendix B contains CyberTech Parrot DSC recorder card details.

IPC integration – installation manual 6

The CyberTech IPC integration adds additional IPC related information to the recorder
database. For IPC systems 2 types of recordings are available.
ƒ IPC CDR data is converted to separate recording entries of type ‘CDR’.
ƒ IPC PCM30 audio recording is energy trigger based. Audio is stored in separate
recording entries of type ‘VOX’.
ƒ The Group based archiving feature is introduced in CyberTech IP CDR kit IPC_CDR_02.
This functionality introduces updating the IPC PCM30 audio recordings to be tagged
with the involved Trader ID.
If a CDR call is selected for replay, the corresponding VOX recordings are combined for
replay. Users will see both the VOX and CDR entries in the list of recorded calls.
If needed VOX recordings can be filtered in the web interface. This will prevent customers to
accidentally play VOX recordings on IPC systems. Disable VOX recordings in the web
interface via the web interface (system installation, global settings, call settings/preferences,
Available call types). Set this value to CDR. All recorder users will now ONLY see CDR based
call records.
In IPC recording multiple audio devices can be mixed in one recording channel. Mixing of
Left Handset + Right Handset + Speaker in one channel is possible. A single VOX triggered
recording could contain multiple IPC CDR records. E.g. a CDR record for the Left Handset
and another CDR record for the Right Handset, etc.

2.2 Analogue Recording

The IPC Analogue integration between the CyberTech recorder and IPC Alliance uses the
Call Logging Port (CDR) and the Analogue recording outputs from the TDM Turrets (Slimline
turret) & IQMX turrets. Analogue Recording is not available for the IQ/MAX turrets.
The Call Logging Port and CDR Output remain unchanged from the E1 Recording solution as
described in section 2.1. Please refer to Appendix A for RS232 connectivity details.

2.2.1 Audio Connectivity

Connectivity for Analogue Recording is provided by an RJ12 interface with pin-out
dependent on switch settings for the main TDM Turret (Slimline turret) module and RJ10 per
each 4-channel speaker module.
The breakout boxes for the IQMX turrets do not have dip-switch settings for analog output
mixing.
Analogue Recording is NOT supported for IQ/MAX turrets

2.2.2 Mixing
TDM Turrets (Slimline turret)
Mixing is set via switches on the main module:
• 1-4 off = unmixed record
Pins 1&2 = HFM, Pins 3&4 = left handset, Pins 5&6 = right handset.
• 3&4 on, 1&2 off = mixed record left and right handset
Pins 1&2 = HFM, Pins 3&4 = left and right handset, do not use pins 5&6.
• 1-4 on = mixed record left/right handset and ICM
Pins 1&2 = HFM and left/right handset, Do not use Pins 3,4,5&6.

IPC integration – installation manual 7

(HFM = hands free module i.e. hands free speaker)

IQMX
Analog output is fixed for left/right handsets and handsfree speaker at the breakout box. In
order to do handset mixing recording, the left and right handset recording output must be
tapped to the same recording channel.
The back of each speaker unit has an analog recording output, all speaker channels and
microphone channels are already mixed into one.

2.2.3 Cabling
Please refer to Appendix C for suggested cable configuration

2.3 Time synchronization

The recorder system must run time synchronous to the IPC system. At recording, audio is
time stamped to the local Recorder system time it is captured on. IPC CDR data contains the
local IPC timestamp which is used for stored IPC CDR calls. On replay of an IPC CDR call, the
system will internally match corresponding audio based on input channel and time
information. Both Audio and CDR information needs to have similar time stamping. In
practice the time deviation between IPC and CyberTech Recorder must not exceed 2
seconds.
Time synchronization options are:
• The CyberTech system linked to IPC for CDR data processing will set its local time to
the IPC CDR time stamp time. This CyberTech system acts as NTP time source to the
rest of the linked CyberTech recorders. The CyberTech IPC integration CD contains the
NTP software to be installed on each CyberTech recording system. Paragraph 3.5 of
this manual included installation details.
• The CyberTech recordings systems are all linked to the same time source the IPC
system is linked to. This could be done linking the standard Windows NTP service to
this time source.
• The CyberTech recordings systems linked to the domain time source. The IPC system is
linked to this domain source as well. Preferred solution for most customers as
CyberTech recording systems will already be linked to their domain time source.
• There will be no automated time synchronization. The customer will weekly correct the
recorder/IPC time to be less than 2s accurate. Important to set both recorder and IPC
to the same time zone and daylight saving configuration.

IPC integration – installation manual 8

2.4 IPC CDR Call Record Details
The “call record” from the IPC Alliance MX system provides information about a call dialled.
The call record is defined in the following table:

Field Name Description Size Default Range

Value

1 Total number of Total number of bytes in the 5 None 0-99999

Bytes record

2 Data Record ID of a type of record 3 001 001-007

Type

3* Station LAC Logical address code of the 5 None

(Turret lac) station at which the call was 65535 or -1
dialled null LAC)

4* TRID (Trid) Trader ID of the trader who 5 None 00001-01999

dialled the call

5 Billing Group (Bill Billing group to which the 3 None 001-064

grp) trader is assigned
16

6 Record Separator Pipe symbol (|) 1 0x007c (|) N/A

/ Delimiter

7* Line LAC (Line Logical address code of the 5 None 1024-9029,

lac) line involved in the call 600000-
639999

8* Call Type (Type) Type of Call (pre-defined 3 None 001-127

codes)

9* Timestamp Time at which the call was 10 Number of sec. 0-

dialled since 1/1/70 4294967295
(GMT)

10* Duration Duration of the call in 1-10 None 0-

seconds 4294967295

11 Dialed Digit Semi-colon (;) 1 0x003b (;) N/A

Separator /
Delimiter

12 Number of Number of digits dialled 2 None 00-40

Dialed Digits
(num dd)

14* Dialed Digits Actual digits dialled 1-40 None 0-9

(maximum 40
chars.)

15 Deliminator Semi-colon (;) 1 0x003b (;) N/A

16 SCSA ID (Scsaid) Uniquely identifier that 3 0 001-999

defines a SCSA cable

IPC integration – installation manual 9

17 SCSA Offset Assigned SCSA channel 4 0 0-1023
(Offset) within the CSSA cable chain

18* Channel Type Handset or Speaker 1 None 1-9

19 Logical Channel Column assigned to the 1 1 N/A

logical channel value from
t_port_group

*) These fields are used in the CyberTech Recording System.

The CDR fields are added to the recorder database:

• Start Time and Duration
Standard recorder Call Start and Duration Fields
• Trader ID (TRID)
Additional recorder database field CVSC00
• Linked recorder user
Standard recorder User Information field.
• Station LAC (Logical Address of Trader panel)
Additional recorder database field CVSC01
• Number Information
Standard recorder Number Information field.
• Line LAC (Logical Address of involved line)
Additional recorder database field CVSC02
• Call Type (Incoming, Outgoing, Transfer...)
Additional recorder database field CVSC03
• Channel Type (Speaker, Handset)
Additional recorder database field CVSC04
• Trader Name
Additional recorder database field CVSC05
• Line Label (8 Character key name on dealer board)
Additional recorder database field CVSC06
• Line description
Additional recorder database field CVSC07
PC CDR data is converted to separate recording entries of type ‘CDR’ as described in
paragraph 2.1.
The VOX call fields merged to the recorder database:
• Trader ID (TRID)
Additional recorder database field CVSC00
• Linked recorder user
Standard recorder User Information field.

The CyberTech CTI server connected to the IPC CDR output, automatically synchronises its
time with the IPC system. The CDR output provides special TIME records for synchronization.
All CyberTech Recorder Systems (CTI Server, Satellites and Servers) must be synchronized
with the CyberTech CTI Server using NTP.

IPC integration – installation manual 10

2.5 User management based on Trader ID
Recorder users can be automatically created and linked to IPC recorded calls. For these users
the involved Trader Name and Trader ID are received from the IPC CDR integration and used
to create or match recorder users.
The recorder system will automatically created new user accounts for Trader ID’s not linked to
users yet. For these new accounts the receiver Trader Name and Trader ID are configured.
They will have type ‘Free Seating’ with the Trader ID as free seating extension. Automatic
created user accounts will appear in the AutoCreateUsers group and will have no recorder
access rights. The recorder administrator is able to move these users to the right user groups
and give them the access rights then need.
Alternatively per recorded Trader, a recorder user could be created in advance. This user is a
Free seating user with his Trader ID as free seating extension. Leading zero’s in a Trader ID
can be left out.

From now on all recorded calls for Trader ID 2002 will be automatically linked to this user.
This allows full recorder user/group management for IPC Traders.
The functionality of matching recorder users and automatically creating recorder users could
be disabled by editing the CTI&CDR_Processor.ini file located in the c:\program
files\cybertech\ini_files directory. The configuration items:
DatabaseGetExtensionUser=yes
DatabaseAutoCreateExtensionUser=yes
These configuration parameters could be set to either ‘yes’ which is default or ‘no’ to disable
this functionality. Paragraph 3.4 describes the procedure to activate these configuration
changes.

2.6 Trader (Group) based archiving

The recorder archive functionality allows archiving based on specific database field content.
For IPC Trader based archiving configure the Archive Rule for archiving ‘Based on database
fields’. Select the database field CVSC00 (Trader ID). Specify the list of Trader ID’s to be
archived for this archive rule. Multiple archive rules can be defined for multiple groups of
Traders. Consult the CyberTech Installation manual for more information on archiving
configuration.
Configure a unique archive location per Trader group and set this location for the
corresponding Archive rule for this Trader Group.
Trader CDR calls and VOX calls will be archived to dedicated archive locations as configured
in the archive rules.

IPC integration – installation manual 11

2.7 Required customer information
In order to install CyberTech IPC integrations, the following is required from the customer:
1. A complete mapping of the recording channels against Station LAC’s, including all
mixing details. This information is included in a ‘Station List’ export from the IPC
system.
2. Available connection to a SubD-9 or SubD-25 RS-232 connection supplying the call
logging records.
3. For E1 Recording a Voice Recording Card (MPIC/TIC/TIC2) in the IPC cabinet. The card
must be configured for E1 audio output. Cards can also be set to SCSA (MPIC/TIC) or
Network (TIC2) output mode. In this case the E1 audio output will be disabled as the
cards can only have one output mode active simultaneously. IPC configuration is
required to change the output mode to from SCSA/Network to E1.

2.8 Limitations
These are the limitations on the CyberTech IPC integration, using CDR:
1. It is not possible to obtain the mapping of the Voice Recorder channel to Station LAC
through a dynamic method. A manual process is needed to keep the Voice Recorder
channel to Station LAC accurate.
2. If a trader opens a speaker channel for long periods of time, typically days or weeks,
the only way to associate these calls with a trader ID is to trigger a timer which sends a
tag to each speaker channel every 15 minutes (this period is adjustable). The one
limitation with this is that there will not always be voice associated with all of these
speakers segments.

2.9 Maintenance
In order to keep the CyberTech IPC integration up-to-date, the following maintenance needs
to be done:
1. Any station that is added or moved need to be manually amended in the Unify
mapping table.
2. Any alterations to the switch software revisions may affect the call logging output and
thus affect the ability to tag calls with details.

IPC integration – installation manual 12

3 Installation and configuration

Before installing the IPC CDR software, read appendix C for additional database fields.
Installing the software is done by running the CyberTech IPC CDR Integration Vx Setup file.
The IPC CDR software can be installed on:
• A CyberTech Server / Core Server or Satellite
• A separate server, which is used dedicated for the IPC CDR software
The following paragraphs describe the installation procedure for the different type of
installations.

3.1 CyberTech Server / Core Server / Satellite

Software installation is achieved by running the CyberTech IPC CDR Integration Vx
Setup file (where ‘x’ is the version number of the software). During the setup procedure,
the first configuration item is the “Licensing Assignment Types.

The default option is “Dynamic Licensing”, with which the CyberTech CTI/CDR Processor
will automatically ‘claim’ the first free IPC license available in the system. No extra
configuration required. This option is typically used for CyberTech Recording Solutions
that have only one CyberTech CTI/CDR Processor running.
The option “Fixed Licensing” should be used for CyberTech Recording Solutions that
have multiple CyberTech CTI/CDR Processor running. By choosing this option, the setup
will request for a serial number. This should be the serial
number of the board that contains the IPC license. This
provided serial number will force the CyberTech CTI/CDR
Processor to use the license of that board. All other CyberTech
CTI/CDR Processors running in the CyberTech Recording Solution should be configured
to use their own dedicated board. This means every CyberTech CTI/CDR Processor
needs a serial number that isn’t used by any of the other CyberTech CTI/CDR Processors.
Next step is to fill in the serial port connection details.

• The Serial Port field requires the serial port number that’s connected to the IPC Sun
CDR feed
• The Parity field requires parity configured for the serial port, which can be “Even”
or “Odd”. This is configured on the IPC Sun system and can be verified there.
To finalize the installation, CDR channel mapping file need to be configured. Consult
chapter 3.4 for more details.
Note: although the service start-up type of CyberTech CTI/CDR Processor is automatic, it
does require a manual start after the setup if CyberTech R5.1 or older is used. Release

IPC integration – installation manual 13

 5.3 and newer contain automatic service restarts, which will start the CTI/CDR Processor
automatically.
For continuous recording of speaker calls, recording needs to be split to prevent
continuous recording causing huge files. Make sure the PCM30 firmware is configured to
split its audio recordings into 15 minute chunks. Consult Appendix B - Parrot DSC PCM30
for call_split configuration details.
For Analogue Recording
For continuous recording of speaker calls, recording needs to be split to prevent
continuous recording causing very large files. Make sure the firmware is configured to
split its audio recordings into 15 minute chunks. Consult Appendix C – Parrot DSC-Mod
Analogue for call_split configuration details.

3.2 Separate server

In addition to the installation instructions in chapter 3.1, the installation of the IPC CDR
software on a separate server requires some additional configuration items.

Database Settings
• The Hostname field requires the IP address or hostname of the CyberTech (Core)
Server
• The Database Name field requires the name of the CyberTech Recording Solution
database, which shall always be ‘recorder’
• The Username field requires the username of the CyberTech ‘recorder’ account
• The Password field requires the password of the CyberTech ‘recorder’ account
• The Recorder Id field requires the ID of the system where this software is installed
on. This shall always be ‘0’ (zero). Alarms generated by this system will be identified
by this ID
Log-file Settings
• The Log-file Location field requires the location for the log files of the CDR
Processor. The default value for this is “c:\logfiles”
• The Log-file Retention (Days) field requires the retention period for the log files of
the CDR Processor to be kept on the system. The default value is 14 days, which
means log files older than 14 days will be removed automatically

IPC integration – installation manual 14

 If any of these settings need to be changed afterwards, the ‘SetupDB’ tool can be used
for this. This tool is located in the following directory: C:\Program
Files\CyberTech\cti_processor_ipc\
Consult Appendix F - Stand alone CDR server for more information.

3.3 Upgrading IPC installations

When upgrading an existing IPC installation, existing IPC components may need to be
manually removed.
IPC installations older than the IPC_CDR_02 kit (16-05-2008) some additional installation
options exist. A legacy mode could be enabled to set the IPC additional information fields to
the older versions. Additional fields Trader Name, Line Label and Line Description will not be
supported. Corresponding additional database fields do not have to be added to the
customers database.
Existing mapping configuration files (c:\program files\cybertech\ini_files\ cti_config.csv) could
still be used. Make sure a copy exists of the original cti_config.csv at installation. This original
file could be placed in the c:\program files\cybertech\ini_files directory after upgrading. This
will restore all IPC Station LAC to recording channel mapping information is restored.
Paragraph 3.3 outlines the mapping details.

3.3.1 Removal existing CTI Processor software

At installation of IPC_CDR_02 existing any CDR&CDR_Processor will not automatically be
removed. Removal could be done manually be following these steps:
Open the command box via Start->run CMD.
Remove the existing CTI&CDR_Processor service from the registered services using this
command:
“c:\program files\cybertech\cti_processor\CTI&CDR_processor.exe" -r

3.3.2 Activation of legacy operation mode

To use this legacy operation mode.
- Rename existing CTI&CDR_Processor.ini to CTI&CDR_Processor_new.ini. - Rename file
CTI&CDR_Processor_legacy.ini to CTI&CDR_Processor.ini.
The ‘CyberTech CTI_CDR Processor’ service needs to be restarted to use this new ini-file.
Make sure all configuration details for serial port configurations are set as scribed in the next
paragraph.

IPC integration – installation manual 15

3.4 CDR connectivity configuration IPC RS232 Connection
details:
The connection details are configured during the setup of the software
- 19.2 K baud rate
installation, but can be changed afterwards by editing the
- 7 bit Odd Parity
CTI&CDR_Processor.ini
- 1 Start bit
- 1 Stop bit

file located in the c:\program files\cybertech\ini_files directory. For No Flow Control

serial RS232 connections only the connectivity details Com Port have to
be defined. Set the right comport number used on the CyberTech CTI Server chassis. The
serial connection parameters are preset for IPC CDR.
#
# SERIAL connectivity settings
#
com_port=com1:
serial_parms=baud=19200 parity=O data=7 stop=1
#

All other ini-file settings may not be altered! This might affect proper CDR operation.

3.5 CDR channel mapping configuration

The CDR channel mapping configuration defines the channel names used in the telephony
system. The configuration file
cti_config_ipc.csv
located in the c:\program files\cybertech\ini_files directory.
The file contains one or more Groups. Each group has a list of Channels and a list of
corresponding channel names called Line IDs. The example shows channel configuration for
default Parrot DSC channel mapping.
Group,0,
channel,1,2,3,4,5,6,7,8,
lineid,XXXXX_X,16500_1,16500_2,16500_6,16501_1,16501_2,16501_6,16502_1,
Group,1,
channel,9,10,11,12,13,14,15,16,
lineid,16502_2,16502_6,16503_1,16503_2,16503_6,16504_1,16504_2,16504_6,
Group,2,
channel,17,18,19,20,21,22,23,24,
lineid,XXXXX_X,16505_1,16505_2,16505_6,16506_1,16506_2,16506_6,16507_1
Group,3,
channel,25,26,27,28,29,30,31,32,
lineid,16507_2,16507_6,16508_1,16508_2,16508_6,16509_1,16509_2,16509_6,

Each line (channel or line id) can contain a maximum of 32 items. Make sure no more items
are configured. If more items are added per line, the items 33 and beyond will be ignored in
mapping.
The Group section allows splitting series of channels is separate configuration lines. In
practice all channels could be defined in a single Group section. To make the configuration
file more readable, multiple sections can be defined.
The Channel indicates a recorder Channel Number. The Line ID is the corresponding
‘Stations LAC + Channel Type’ from the IPC system. The Station LAC is the corresponding
Trader Console hardware position mapped to the PCM30 channel. The Channel Type
describes the mapped audio source on the Trader Console.

IPC integration – installation manual 16

Types are:

Channel Type Not available on IPC CDR output 0

LEFT_HANDSET 1

RIGHT HANDSET 2

SPKRS_BY_2 4

SPKRS_BY_4 5

SPKRS_BY_8 6

The sample shows a common IPC Station LAC mapping. For each Trader Console 3 PCM30
channels are used. ‘Left Handset’ (LAC_1), ‘Right Handset’ (LAC_2) and ‘Speakers by 8’
(LAC_6). The speaker channel includes the audio of 8 Trader Console speakers mixed into
one PCM30 channel. In total 10 Trader Consoles are mapped to the PCM30 output.
PCM30 channels 1 and 17 are NOT USED for audio. They are used in the mapping by setting
them to Line ID XXXXX_X.
If the Parrot DSC PCM30 channel mapping is set to map11, channels 1 and 17 are hidden.
Channel 1-30 will be visible which are all audio channels. Configuring Line ID XXXXX_X for
channels 1 and 17 not needed in this case as channels 1-30 are all audio channels to be
mapped.
If the Channel Type field in the CDR output contains the value 0, the Channel information is
not provided by the IPC system. In this case the Channel Type is determined based on the
Call Type value in the IPC CDR output.
If handsets and/or speakers are mixed on the same PCM30 channel, just duplicate the
mapping for this PCM30 channel.
Group,0,
channel,2,2,3,4,4,5,
lineid,16500_1,16500_2,16500_6,16501_1,16501_2,16501_6,

The above sample contains mapping for PCM30 channels (2-5). Mapping:
Channel 2: Station LAC 16500: LEFT_HANDSET, RIGHT_HANDSET mixed
Channel 3: Station LAC 16500: SPKRS_BY_8
Channel 4: Station LAC 16501: LEFT_HANDSET, RIGHT_HANDSET mixed
Channel 5: Station LAC 16501: SPKRS_BY_8

3.5.1 Multiple speaker boxes

When multiple speaker modules are recorded on one (mixed) recorder channel or more, the
following configuration steps are required:
- add and configure the parameter channels_per_speaker_box in the
CTI_CDR_processor.ini file to support multiple speaker boxes
- adjust the mapping file to map the extra speaker channels to the right recorder
channel
- restart the CTI_CDR_Processor to activate the changes
The parameter channels_per_speaker_box defines the number of speakers per speaker
box, e.g. 4. If it is set to 0 or not present at all, it will only support one speakerbox. The
parameter needs to be placed under the section [IPC] in the CTI_CDR_processor.ini file.
The following tables show the channel type output which is used as part of the line ID for
different channels_per_speaker_box settings.

IPC integration – installation manual 17

line id channel type output when channels_per_speaker_box=8

Speaker box 1 Speaker box 2

Spk. ch. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

linei d
channel 6_1 6_1 6_1 6_1 6_1 6_1 6_1 6_1 6_2 6_2 6_2 6_2 6_2 6_2 6_2 6_2
type

line id channel type output when channels_per_speaker_box=4

Speaker box 1 Speaker box 2

Spk. ch. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

line id
channel 6_1 6_1 6_1 6_1 6_2 6_2 6_2 6_2 6_3 6_3 6_3 6_3 6_4 6_4 6_4 6_4
type

line id channel type output when channels_per_speaker_box=1

Speaker box 1 Speaker box 2

Spk.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
ch.

line id
channel 6_1 6_2 6_3 6_4 6_5 6_6 6_7 6_8 6_9 6_10 6_11 6_12 6_13 6_14 6_15 6_16
type

The following examples show two different speakers box recording scenario’s.

All turrets have two speaker boxes with 4 speakers per speaker box, audio is mixed onto 1
channel

Parameter to be used channels_per_speaker_box=4

Mapping file example channel,3,3

lineid,16500_6_1,16500_6_3

All turrets have two speaker boxes with 8 speakers per speaker box, audio is mixed on 1
channel per speaker box (2 channels in total for 16 speakers per turret)

Parameter to be used channels_per_speaker_box=8

Mapping file example channel,3,4

lineid,16500_6_1,16500_6_2

IPC integration – installation manual 18

3.6 CDR Resilience
CDR Resilience ensures a continuation of CDR record processing. For proper CDR Resilience
two instances of the IPC CDR Processor are running. One instance per server:

For the installation of the IPC CDR Processor, consult chapter 1. Installation steps are the
same for both servers. The only configuration that needs to be done on both servers, is to
change the following parameter in the CTI&CDR_Processor.ini file (under the section
[general]):
CheckForDoubleCallsOnSeparateInsert=yes
A restart of the IPC CDR Processor is required to apply this configuration. Consult chapter 3.7
for more information.

3.7 Activate configuration changes

To activate the configuration changes the CDR Processor component has to
be restarted. This applies for both connectivity and channel mapping
changes. Right-click the My Computer desktop icon and select the option
Manage. Select the ‘Services and Applications’, ‘Services’ section and
search for the CyberTech CTI CDR Processor.

Right-click this line and select the Restart option. Now all configuration
changes will be activated.

3.8 NTP Time synchronization

The CyberTech CTI server connected to the IPC CDR output, automatically
synchronises its time with the IPC system. The CDR output provides special
TIME records for synchronization. All CyberTech Recorder Systems (Satellites
an (core)Servers) must be synchronized with the CyberTech CTI Server using
NTP.
The NTP service installer ntp-4.2.0a@1.1354-o-win32-setup.exe is located on
the IPC CTI Installation CD. This software must be installed on all CyberTech
Recorder Systems (CTI Server, Satellites an (core)Servers). Use the SYSTEM
account option for the NTP service settings.

IPC integration – installation manual 19

The CTI Installation CD contains 2 NTP configuration (ntp.conf) files for:
ƒ CTI Server configuration
ƒ Recorder Satellite, Server configuration
Copy these configuration files to the c:\program files\ntp\etc directory on the corresponding
CyberTech systems. For CyberTech Recorder Satellites and Servers, configure the IP address
of the CyberTech CTI Server in the ntp.conf file. Restart the NTP service (Network Time
Protocol Daemon) to activate the NTP settings.
Right-click the My Computer desktop icon and select the option Manage. Select the ‘Services
and Applications’, ‘Services’ section and look for the Network Time Protocol Daemon. Restart
this service.

IPC integration – installation manual 20

4 E1 Recording Resilience options N+1
Satellite failover
The CyberTech Recording system version 5.3 offers N+1 Satellite resilience for
trading environments based on E1 recording. A standby N+1 recording satellite can
be linked via a failover switch matrix to the recording system. At failure of a
recording satellite, the E1 lines linked to the failing satellite are automatically
switched to the standby N+1 satellite.

IPC CDR tagging is automatically redirected to the N+1 satellite channels, therefore
the customer will not experience any change in call search & replay and archiving.

Each satellite is capable of recording up to 16 E1 links. The N+1 switch matrix unit is
capable of switching 16 E1 lines to an N+1 failover satellite. A maximum of 4
satellites + an N+1 satellite can be linked to the switch matrix. This creates a 4+1
satellite combination.

Configuration of the N+1 failover functionality is embedded in the web GUI.

Definition of recording satellites and resilience role are defined in the menu defined
in the menu [system installation -> resilience hosts]. Definition of N+1 failover
configuration is defined in the menu [system installation -> resilience groups]
A detailed explanation is provided in the following paragraphs.

IPC integration – installation manual 21

Failover behaviour shown in picture below.

Failover Alarm triggering failover to N+1 Satellite

Failed over

remapping
In N+1 failover status.

Channel

timeout
Normal
Failing Satellite recordings
operation
mapped to N+1 channels

Time

Failback Re-commissioning failed Satellite

Normal operation
Hold-off timeout
Relay switch

Dialing
+ status
N+1 failover Normal operation
Ringing

Time

The moment an alarm occurs on a Recording Satellite which affects recording,

failover is trigged. The E1 lines for the failing Satellite are now immediately switched
to the N+1 system. The E1’s stay linked to the failing satellite as well.

For a short period called the ‘Channel remapping timeout’, recording is active on
both the failing satellite and the N+1 satellite. This limits loss of recording at failover
to a minimum. After the remapping timeout, calls recorded on the failing satellite will
be mapped to spare recording channels (the channels of the N+1 system). No new
N+1 failover can occur now as the switch matrix is set to failover position.

A similar mechanism is used at Fallback. For a short period called the ‘Relay switch
Hold-off timeout’, recording is active on both the fallback satellite as well as the N+1
satellite. After the Relay switch timeout, the E1 lines are disconnected from the N+1
system. The recorder is in normal operation mode again, failover mechanism
available for new failover.

4.1 Analogue Resilience

N+1 failover is NOT available for IPC Analogue recording solutions

IPC integration – installation manual 22

4.2 Installation of N+1 failover components and licensing
N+1 failover components are included in an add-on setup to CT5.2 or higher recording
systems. The setup contains both the core server and satellite components; the type of
installation should be selected during setup. This installer must be run on all recorder
satellite servers in the system (including the N+1 satellite), and the core server.

4.2.1 Installation Prerequisites

Before installing the redundancy components, the following items must first be installed;
Core Server
• CyberTech Recorder Core Server Installation, CT 5.2 or higher
• Microsoft .Net framework v3.5
• Pickering Series 60 Setup (Relay matrix drivers)

Satellite Recorder Server

• CyberTech Recorder Satellite Installation CT 5.2 or higher
• Microsoft .Net framework v 3.5

4.2.2 Installing the Resilience Components

After installing the prerequisites, the redundancy components installer should be run on the
core server. The installer is called ‘RedundancyComponentsSetup_{V}.exe’, where V is the
version of the application.
When installing on a satellite, it is recommended that the user shuts down the recorder
services using the CyberTech Recorder Solution Monitor tool. Checks should be made to
ensure the services are completely stopped before running the resilience components
installer.
• Now run the installer.
• If the prerequisites were installed correctly, the ‘Welcome’ page will be displayed.
Click next to proceed.
At this point, the type of installation should be selected;
• The ‘E1 N+1 Redundancy Satellite Components’ should be selected if installing on a
satellite recorder. These components pass status information to the resilience server
(the core server). Click ‘next’ to proceed.
• The ‘E1 N+1 Redundancy Core Server Components’ should be selected when
installing on the Core Server. It installs the components to manage failover, control
the switch matrix and receive Satellite status information for triggering failover. Click
‘next’ to proceed.

In this next page, the CyberTech Recorder service account user ID and password
have to be supplied. This is needed so the installer can add new data schema to the
database. Click next to proceed.
• Proceed to install the software by clicking ‘Install’. At this point the CyberTech
Recorder services will be stopped if installing on CT5.2 – this is necessary in order to
update some of the recorder’s components.
• When the components finish copying, the final page will be displayed. Click ‘finish’
to quit the installer and reboot the PC.

IPC integration – installation manual 23

4.2.3 Licensing Details
N+1 failover is licensed by the following license field = Datafield 20 value [0..7].
Multiple resilience licenses can be combined in this license field. If multiple resilience
licenses are combined, the license value is based on the following definition.
resilience Licensing value bitwise 0000001 010 011 010, where bits represent:
0000001 : Licensed Passive Satellites resilience groups.
010: Licensed CTI Server resilience groups.
011: Licensed Active Satellite resilience groups.
010: Licensed E1 N+1 Satellite groups.

4.3 Resilience groups

A resilience group contains one ore more servers of the same type, grouped for
resilience purposes. (Hosts of the specified server type may be added to the group
in the ‘hosts’ page.) Once a resilience group has been added, clicking on the group
in the list will show the group configuration settings, which may be edited.

4.3.1 Adding a resilience group

• First of all, add a new resilience group by clicking the button in the top
right corner of the group list pane.

• In the resilience group edit pane below, provide a name for the resilience
group. (For example, ‘E1 N+1 Resilience’.).

• To configure N+1 resilience for IPC recording, first a resilience group must be
created for server type ‘Satellite Recorder’ and Failover type ’E1 N+1
Satellite’. Although the ‘Failover type’ dropdown shows resilience options for
all types of resilience, it will only be possible to add a group of a particular
resilience type when a license exists for it in the system.

IPC integration – installation manual 24

 • The ‘Error profile’ dropdown includes Alarm Profiles configured via menu
‘System configuration -> Alarm profile’. For N+1 failover a default alarm
profile is included called ‘E1 N+1 Satellite redundancy errors’. This profile
contains all alarms indicating recording issues on a Satellite. If an alarm is
raised included in the selected alarm profile, failover is activated.

• Click the ‘add record’ button to add the group. (Only one resilience group
may be added in the current version of the software).

4.3.2 Editing a resilience group

Once a resilience group has been created, it is then possible to edit the group
name, error profile, and the configuration for E1 N+1 redundancy. (The
configuration is covered in section 4.4)

Click on the resilience group shown in the list, and the details will be made
available for editing in the lower panes;

4.4 Resilience hosts

The resilience hosts page provides an overview of all the known hosts in the
recording system. It is a view of all servers – it is not possible to add or remove hosts
in this page, since it is just a view. The servers may be of the following types;
• Core Server
• Satellite Recorder
• CTI Server
• Screen Recorder
Recording Satellites and Servers are automatically displayed in this list when they are
added in other parts of the user interface. Hosts can be included in resilience groups
configured with a matching host type. For each host, its role in the resilience group
is defined either being Active or Standby. Failover (in case of satellite recorder
failure) can be enabled or disabled for each host.

IPC integration – installation manual 25

The above screen shows a system setup based on one Core Server, 2 Satellites and a
N+1 failover satellite (standby).

Columns description:
Server ID: Recorder ID for server. Unique reference number.
Server Type: System type either Core Server, Satellite Recorder, CTI Server,
or Screen Recorder.
Server Name/IP: Hostname and IP address for server.
Resilience Group: Group to which the host belongs.
Role: Role for the host, either Active or Standby. At failover of an
Active system, its function is taken over by a Standby system.
Failover: Failover method defined for this server. Methods are:
- [Disabled] No failover defined for this server.
- [Immediate] Failover defined for this server, no failover delay.
- [Disabled for x minutes]. By disabling failover for x minutes,
service or maintenance can be done on the system without
accidentally triggering failover. After the x minutes have
expired, the failover configuration automatically changes to
Immediate, enabling failover again.
Alarms raised during this disabled
period will not trigger failover. They need to be cleared and
confirmed before failover is enabled again. Active alarms within
the failover profile, will trigger N+1 failover the moment
failover is enabled.
Status: Failover state for this server. States are:
- [-] No failover occurred.
- [Failing over] Executing failover now, this server failed.
- [Failed over] Server has failed over successfully to the standby
server.
Heartbeat: Server link indication to resilience system. Every few seconds
the heartbeat time is updated indicating server resilience is up.
ID: Resilience ID. Unique reference number for server. CTI Servers
can have similar Server ID, the ID in this column is always
unique. This ID is used in resilience alarms to referring to a
unique server.

For each listed host, some values are configurable, these are the ‘Group Name’,
‘Role’ and ‘Failover’ method.

IPC integration – installation manual 26

To test the failover procedure and N+1 wiring, failover could be forced by pressing
the ‘Force Failover’ button. This triggers the host to go to Failed status activating the
Standby N+1 system and switching the E1 lines to the N+1 system.

The button [Re-commission] is enabled for hosts in ‘Failed over’ status. By pressing
this button the failed host is Re-commissioned which triggers FALLBACK of the N+1
system. The E1 lines are switched from the N+1 system. The Failed recorder is in
normal state again. The N+1 system is available for new failover.

4.5 Resilience configuration for N+1 resilience

After defining the resilience group and adding the hosts to the group, the actual
N+1 failover configuration could be made. For failover type N+1 Resilience, the
following parameters can be configured.

Relay Unit IP Address: IP Address of Pickering switch matrix. This device

switches the E1 lines to the N+1 failover system.
Relay Unit IP Port: TPC/IP port for Pickering switch matrix communication.
Should be 1024.
Relay Unit Connection…: Number of seconds no response from switch matrix.
If the unit does not response alarm 11038 is raised
indicating a connection failure with the switch matrix.
No N+1 resilience switching possible now.
Default value 10s.
Channel Remapping…: Overlap time in minutes to record from both the failing
and N+1 recorder, the moment failover is activated.
This ensures least loss of recordings at failover as both
recorders are temporary active. Default value 15min.
Relay switch-off hold…: Overlap time in minutes to record from both the
re-commissioned and N+1 recorder, the moment
fallback is activated. This ensures no loss of recordings
as both recorders are temporary active.
Default value 15min.
Resilience Agent/Service…: Keep alive timeout between the recording satellites and
the system controlling failover to check connections.
Database poll period: Database check for failover and re-commission actions.

IPC integration – installation manual 27

4.6 N+1 Resilience operation

For N+1 Satellite Resilience a maximum of 5 recording satellites can be combined in

a resilience group. 4 Satellites having role Active, the 5th having role Standby. All
Active satellite E1 links are linked to IPC system, the switch matrix linked in parallel
to these E1’s. The Standby satellite E1 links are linked to the switch matrix only.

In case an Active recording satellite fails, the Standby recording satellite is

automatically switch to in parallel to the E1 lines of the failing satellite. The failed
recording satellite is left in a ‘Failed over’ status until re-commissioned. At re-
commissioning Fallback is triggered disconnecting the E1 lines from the Standby
recording satellite.

Alarms and warnings are raised to indicate Failover attempts, success/failure of this
failover and re-commissioning of a failing recording satellite.

To use N+1 satellite resilience, the following configuration steps need to be done.

1) Create a Resilience Group including the recording satellites

2) Define Active satellites and one Standby satellite.
3) Set the Resilience Configuration for this Group to use E1 N+1 Resilience
4) Assign the provided E1 N+1 Resilience Error Profile as failover profile.

Now the recording satellites are linked as N+1 resilience group. If an alarm occurs
listed in the ‘E1 N+1 Resilience Error Profile’ the Standby recording satellite is
switched parallel to the E1 lines of the failing satellite.

IPC integration – installation manual 28

5 Appendix A – RS232 pin lay-out

SubD-25 (Port B) on Sparc5 and Sparc20 system.

Pin# Signal Description Remarks

NA = Not Connected
1 NC NC

2 TXD_B Transmit Data B Pin# 2 (Rx) on SubD9

3 RXD_B Receive data B

IPC RS232 Connection
details:
4 RTS_B Read to Send B - 19.2 K baud rate
- 7 bit Odd Parity
5 CTS_B Clear to Send B
- 1 Start bit

6 DSR_B Data Set ready B - 1 Stop bit

No Flow Control
7 GND Signal Ground B Pin# 5 (GND) on SubD9

8 DCD_B Data carrier detect B

9 NC NC

12 NC NC

13 NC NC

14 NC NC

15 RTXC_B Transmit Clock B

16 NC NC

17 RXC_B Receive Clock_B

18 NC NC

19 NC NC

20 DTR_B Data terminal Ready B

21 NC NC

22 NC NC

23 NC NC

24 TXCB Data Terminal Ready B

25 NC NC

IPC integration – installation manual 29

SubD-9 (Port B) on Sparc Ultra19 system:

Pin# Signal Description Remarks

1 CD Data carrier detect IPC RS232 Connection

details:
2 RXD Receive data - 19.2 K baud rate
- 7 bit Odd Parity
3 TXD Transmit data Pin# 2 (Rx) on SubD9
- 1 Start bit
- 1 Stop bit
4 TDR Data Terminal Ready
No Flow Control
5 GND Signal Ground Pin# 5 (GND) on SubD9

6 DSR Data Set ready

7 GND Signal Ground

8 CTS Clear to Send

9 RI Ring Indicator

IPC integration – installation manual 30

6 Appendix B - Parrot DSC PCM30

For PCM30 recording the firmware ‘vox_e1_mod_pci_05’ or higher must be loaded in one of
the modular Parrot DSC cards listed.
C34563 MV-PRO-1 E1/T1-PCI (1x PCM30 recording card)
C34564 MV-PRO-2 E1/T1-PCI (2x PCM30 recording card)
C34565 MV-PRO-3 E1/T1-PCI (3x PCM30 recording card)
Parrot DSC PCM30 Board, codec type settings:
Audio codec A-Law/Mu-Law:
IPC PCM30 output is Mu-Law audio. The Parrot DSC card is configured for Mu-Law using the
MaintenanceTool command ‘law_overrule 1’.
Ignore unused signalling channels:
Channels 1 and 17 in the PCM30 stream are not used. These channel can be disabled in the
Parrot DSC card using the MaintenanceTool command ‘set_map 11’. The system must be
rebooted to activate this Parrot DSC programming! CDR channel mapping (§3.2) must be
adjusted.
Speaker Call recording:
IPC Speaker channels give continues audio. To record this continues stream, recording must
be split into 15 minute chunks. Configure the Parrot DSC card using the MaintenanceTool
command: ‘call_split all 15’ to split recording in 15 minute chunks.
Speaker Call voice activated recording:
IPC PCM30 recording is voice activity triggered. Factory defaults already include the right
voice sensitivity for IPC PCM30 recording. If these factory defaults are still not sufficient
(Inactive speaker channels might cause some noise while idle) voice sensitivity could be
changed. Monitor speaker call behaviour with the MonitorTool by checking channel activity. If
needed adjust voice sensitivity in the Parrot DSC card using the MaintenanceTool command
‘vox_mask <value>’. Vox mask values are: 70,78,7c,7e and 7f (increasing voice
sensitivity). The factory default value is 78.
Unused channels in PCM30 link:
The use of PCM30 channels is configured in the IPC system. Depending on this configuration,
not all 30 channels within the PCM30 link could contain audio. To prevent any recording
triggered on unused PCM30 channels, these channels can be deactivated in the Parrot DSC
card. Even if PCM30 channels are not used within the IPC configuration, glitches could trigger
short (5s) recordings on these channels. Monitor channel behaviour with the MonitorTool by
checking channel activity. PCM30 channels which are NOT included in the IPC CDR Channel
mapping (cti_config.csv) can be switched off in the Parrot DSC card. Use the
MaintenanceTool command ‘prog <channel> directaudio clr’ to deactivate a
channel. To re-activate a channel use ‘prog <channel> directaudio set’. Keep in
mind that the channel numbers in the Parrot DSC card start from 0, but the channels on the
MonitorTool and in the channel mapping start from 1! To disable mapping channel 8, you
must use channel 7 in the prog command.
If new firmware is loaded in the Parrot DSC card, these commands must be re-entered!
The Parrot DSC PCM30 circuits might need to be terminated for IPC recording.
When linking the recorder Parrot DSC PCM30 recording channels direct to the IPC outputs,
termination on these Parrot DSC channels must be set.

IPC integration – installation manual 31

The PCM30 Module (called MPBE1PASxx) contains 2 switches. The default position for these
switches is OFF, termination disabled.

PCM30 (Tx only)

IPC Recorder
(terminated)

Linking the recorder direct to the IPC PCM30 outputs, termination must be set. Change the
position of both switched on the Parrot DSC module to the ON position to activate
termination.

PCM30 (Tx only)

IPC
2N Recorder
(both terminated)

Linking a 2N recorder (2 recorders in parallel) to the IPC PCM30 outputs, termination must be
set for both recorders. Change the position of both switches on the Parrot DSC modules to
the ON position to activate termination.

PCM30 (Tx->Rx loop)

IPC (2N) Recorder
Non terminated

Linking a recorder (single N or 2N) to a IPC PCM30 which is locally looped back, no
termination is required at Parrot DSC side. The PCM30 output is terminated at IPC side by
loop back wiring. This is the preferred wiring method for 2N installations.

IPC integration – installation manual 32

7 Appendix C – Parrot DSC-Mod
Analogue
For Analogue recording the firmware ‘analog_mod_pci_23’ or higher must be loaded in one
of the modular Parrot DSC cards listed.

Myracle Analogue boards: -

C35120,C35711,C34509,C35712,C35713,C34515,C35714,C35715,C34510,C35716,C34511,
C35717

Pro Analogue boards: -

C35542,C35820,C35005,C35821,C35822,C35006,C35823,C35824,C35007,C35825,C35008,
C35826,

Analogue Programming Description:

The following settings have been tested as working. To program the Parrot DSC-Mod
Analogue Card, the following commands can be used from the Maintenance Tool to change
the analogue card settings:

1) ee_defaults :This sets the card to its default settings

2) prog all hookstart clr :Disables hookstart
3) prog all directaudio set :Card in vox mode
4) call_split all 15 :Split calls into 15 min chunks
5) analog_energy 31 mV rms :Set energy level threshold

6) vox_setup 2 50 5000 :Vox trigger settings (this is the default

setting, included here for completeness )

If new firmware is loaded in the Parrot DSC card, these commands must be re-entered!

IPC integration – installation manual 33

8 Appendix D – Analogue Recording Cable
Configuration

IPC integration – installation manual 34

9 Appendix E - IPC CDR Database fields
The IPC CDR data includes a number of additional fields which must be added to recorder
database (system installation, database fields).

Column Signal Description Type Size

CVSC00 Trader ID The Trader ID Textual 20

CVSC01 Station LAC Logical Address of the used Station Textual 20

CVSC02 Line LAC Logical Address of the involved Line Textual 50

CVSC03 IPC Call Type IPC Type of call Textual 20

CVSC04 Channel Type Recorder port channel type Textual 20

CVSC05 Trader Name The Trader Name corresponding with the Trader ID Textual 40

CVSC06 Line Label Line label for involved Line LAC on dealer board. Textual 20

CVSC07 Line Description Line description defined in IPC system for involved Line LAC Textual 50

Make sure these fields are defined BEFORE starting the IPC CDR integration software!

For the database fields ‘IPC Call Type’ and ‘Channel Type’ a lookup
list could be defined. The IPC CDR installation CD contains two file
named ‘IPC Call Type Lookup list’ and ‘Channel Type Lookup
list.txt’
Copy the text from the file and it the ‘Database filed special
formatting’ box. This could be done for both the ‘IPC call Type’ and
‘Channel Type’ fields. The example below shows the lookup list for
the Channel Type field.

Press the [>] button for a more convenient overview of the lookup list. Texts can be altered
on customer request.

In the recorded calls page the information showed in the Channel Type column will now be
the text in stead of the number.

Example of recorded calls page including Channel Type and IPC Call Type text defined in the
lookup list.

IPC integration – installation manual 35

IPC Call Type (IPC Call Type Lookup list.txt) Decimal Value IPC Release
INVALID_MIS_CALL_TYPE 000 9.0.1 and later
NOT_ASSIGNED 001 9.0.1 and later
INCOMING_LINE 002 9.0.1 and later
OUTGOING_LINE 003 9.0.1 and later
BRIDGED_CALL 004 9.0.1 and later
INCOMING_TURRET 005 9.0.1 and later
OUTGOING_TURRET 006 9.0.1 and later
INCOMING_LINE_HS2 007 9.2 and later
OUTGOING_LINE_HS2 008 9.2 and later
BRIDGED_CALL_HS2 009 9.2 and later
DDI_INCOMING_LINE 010 9.2 and later
DDI_OUTGOING_LINE 011 9.2 and later
DDI_BRIDGED_CALL 012 9.2 and later
DDI_INCOMING_LINE_HS2 013 9.2 and later
DDI_OUTGOING_LINE_HS2 014 9.2 and later
DDI_BRIDGED_CALL_HS2 015 9.2 and later
TRANSFER_HOLD_INCOMING 016 11.1
TRANSFER_HOLD_OUTGOING 017 11.1
TRANSFERED_TO 018 10.1 and later
SPEAKER_CALL_START 019 11.1
TRANSFER_HOLD 020 10.1 and later
SPEAKER_CALL_END 021 11.1
DDI_SPEAKER_CALL_START 022 11.1
DDI_SPEAKER_CALL_END 023 11.1
INCOMING_HOLD 024 11.1
OUTGOING_HOLD 025 11.1
DDI_INCOMING_HOLD 026 11.1
DDI_OUTGOING_HOLD 027 11.1
INCOMING_HOLD_HS2 028 11.1
OUTGOING_HOLD_HS2 029 11.1
DDI_INCOMING_HOLD_HS2 030 11.1
DDI_OUTGOING_HOLD_HS2 031 11.1
SPEAKER_CALL_REFRESH 032 11.1
DDI_SPEAKER_CALL_REFRESH 033 11.1
INCOMING_TURRET_HS2 034 12 and later
INCOMING _TURRET_ICM 035 12 and later
OUTGOING_TURRET_HS2 036 12 and later
OUTGOING_TURRET_ICM 037 12 and later
OUTGOING_BROADCAST 038 12 and later
OUTGOING_BROADCAST_HS2 039 12 and later
OUTGOING_BROADCAST_ICM 040 12 and later
INCOMING_ANSWER_BACK 041 12 and later
INCOMING_ANSWER_BACK_HS2 042 12 and later
INCOMING_ANSWER_BACK_ICM 043 12 and later
ANSWERED_INCOMING 044 12 and later
EXCLUSIVE_HOLD 045 12 and later

IPC integration – installation manual 36

Channel Type (Channel Type Lookup list.txt) Decimal Value
LEFT_HANDSET 001
RIGHT_HANDSET 002
MIXED_HANDSETS 003 (not used)
SPEAKERS_BY2 004
SPEAKERS_BY4 005
SPEAKERS_BY8 006
RESERVED 007
PLAYBACK 008
INTEGRITY_TONE 009

IPC integration – installation manual 37

10 Appendix F - Stand alone CDR server

For system containing 60+ IPC recording channels, the IPC CDR components must be
installed on a stand alone server. Installation is similar to the standard installation.
Additionally the IP address and login of the CyberTech Server System must be defined during
the installation setup. This can be changed
afterwards by running the SetupDB application.

The SetupDB application is by default installed at

location c:\program
files\cybertech\cti_processor\SetupDB.exe. It could
be started from here if required.
For Stand Alone CTI Servers (dedicated server
system for IPC CDR integration) configuration needs
to be done. Press the ‘Read from registry’ button and set the following parameters:
- Database Hostname: IP address or Hostname from (Core)
Server for the linked recorder.
- Database Name: <recorder>
Do not change this configuration.
- Database Username/password: Enter Recorder account details for the
linked recorder.
- Recorder ID: Must be 0 for Stand Alone CTI servers.
- Log file location and expiration: To be defined at installation.
Press the Write to registry button to save changes.
When changing the recorder account on the Server system, run this SetupDB application on
the CyberTech CTI server as well. The new recorder account details must also be configured
for the CyberTech CTI server.

IPC integration – installation manual 38

11 Appendix G – N+1 resilience alarming

11030
Message: E1 N+1: Satellite failover attempt started for Satellite Recorder <ID>,
due to error <alarm #>
Description: Failover is triggered. Failover attempt is started. The N+1 standby satellite will
be activated.
11031
Message: E1 N+1: Failover attempt succeeded for recorder <ID>
Description: Failover successful. The failing satellite could now be taken in service without
affecting the recording system.
11032
Alarm: E1 N+1: Failover attempt failed for recorder %s. Fail reason: <reason>
Description: Failover was not successful. Reason for unsuccessful failover could be a failing
switch matrix.
11033
Message: E1 N+1: Failover re-commissioning started for recorder <time>
Description: The failed satellite is re-commissioned by a service user. Fallback to the
repaired recording satellite is initiated.
11034
Message: E1 N+1: Failover re-commissioned successfully for recorder <ID>
Description: Re-commissioning successful. Operation for recorder <ID> restored. Standby
recording satellite available for new failover.
11035
Alarm: E1 N+1: Failover re-commissioning failed for recorder <ID>. Reason: <reason>
Description: Re-commissioning was not successful. Reason for unsuccessful re-
commissioning could be a failing switch matrix.
11036
Alarm: E1 N+1: Resilience Agent Keep-Alive time-out occurred for recorder <ID>
Description: Connection lost between recording satellite and resilience control system. No
failover or re-commissioning possible for recording satellite <ID>.
11037
Message: E1 N+1: The user initiated a forced failover on recorder <ID>
Description: Manual failover activated by a service user. Failover is triggered. Failover
attempt is started. The N+1 standby satellite will be activated.
11038
Alarm: E1 N+1: Failed to connect to E1 N+1 Relay Unit <IP address>
Description: Connection lost between failover control system and switch matrix (relay unit).
System not able to failover or re-commission while connection is lost.
11039
Error: E1 N+1: The configuration is incorrect, failover will not proceed.
Reason <reason>
Description: Failover could not be done due to incorrect failover configuration.

11040
Alarm: E1 N+1: Failed to switch the relay unit <IP address>
Description: Unable to control the relay unit. Attempt to failover or re-commission failed.

11041
Error: E1 N+1: A failover occurred but the standby N+1 recorder <ID> is failed with
<alarm>
Description: System is unable to failover to the N+1 standby recorder as the N+1 standby
recorder is in failed state.

IPC integration – installation manual 39

12Appendix H – Software Setup
Installing IPC CDR integration on a CT 5.x recording system requires these software setups:
Before installing the CDR integration:

1. Make sure to have CyberTech recording software, version 5.x.x. installed on the Core
server (and Satellites if applicable)

2. Make sure a Parrot DSC board is installed in the Core server (or Satellite if applicable)
with:
- A valid license for IPC CDR (Datafield 12: type 138)
- Sufficient CTI channels (Datafield 13: should at least have the amount of channels
that will be recorded).

License information can be obtained from the Web GUI: Go to ‘system status >
general info > license information’.

3. Create 8 additional database fields in the Web application to be used for the CDR
record’s call details. How to:
3.1. Open Web GUI by clicking the CyberTech icon on the desktop of the Core server
3.2. Log in using the Service account credentials.
3.3. Go to: ‘system installation > database fields.

IPC integration – installation manual 40

 3.4. Use the ‘+’ icon to add 6 database fields. Make sure to press the ‘Add record’
button after configuring each separate field. The database field to be added are:

CVSC00: Name= Trader ID, Type= Textual, size= (20)

CVSC01: Name= Station LAC, Type= Textual, size= (20)
CVSC02: Name= Line LAC, Type= Textual, size= (50)
CVSC03: Name= IPC Call Type, Type= Textual, size= (20)
CVSC04: Name= Channel Type, Type= Textual, size= (20)
CVSC05: Name= Trader Name, Type= Textual, size= (50)
CVSC06: Name= Line Label, Type= Textual, size= (50)
CVSC07: Name= Line Descr, Type= Textual, size= (50)
For Call type (CVSC03), copy the content of the ‘Call type Lookup list.txt’ to
the ‘Lookup list’ window in the ‘Database field special formatting’ window.
For Channel type (CVSC04) copy the content of the Channel type lookup
list.txt’ file to the ‘Lookup list’ window in the ‘Database field special
formatting’ window.

4. Make sure the time on all computers is synchronized with the time on the SUN system
center. Preferably, all computers (including SUN) use 1 time server on the customer’s
Domain. Time can be synced using the NTP application that is supplied on the
installation CD or can be synced using the Domain resources.

Installation of the CDR processor:

1. Download the CyberTech IPC CDR V3.10.0 software from the partner web site: (log in
and go to: software > integrations > IPC)

2. Copy the software to the computer that will have the CDR processor installed and
extract the .zip file. Any location on this computer is o.k.

3. Open the extracted software folder

4. Make sure you’re logged on to Windows with a Administrator account ( that has
permission to install a service)

5. Run the CyberTech IPC CDR Integration Vx Setup (where ‘x’ is the version of the
software)

6. The installation wizard starts and will come up with the following screen:

Press Next to continue the setup. If multiple IPC CDR processors are installed,
choose “Fixed Licensing”. Consult chapter 3 for more information.

IPC integration – installation manual 41

 7. If you install the CDR processor on a separate CDR server, you’ll have to fill out the
following details

Where the hostname should be the host name or IP address of the Core Server and
the username and password that of the Windows ‘recorder’ account.

8. Next step is to fill in the serial port connection details.

Make sure that the serial port settings match with IPC’s

9. Press Next and finalize the installation, wait for the setup to install all software
components.

10. To check at any time if the service is started, go to computer management >
applications and services > services. Following highlighted service should be
‘started’.

IPC integration – installation manual 42

 11. To map the information from the IPC CDR records to the correct channels in the
recorder, we use a mapping file. This cti_config_ipc.csv file can be found in following
location: C:\Program Files\cybertech\INI_files.

12. For each Turret we need to tell the recorder to which channels we map its Left
Handset, Right Handset and Speakers. We identify a Turret Left Handset call by
configuring it in the mapping file as StationLAC_1, Right Handset call is identified by
configuring it as StationLAC_2 and Speakers:StationLAC_6 (_6 is Speakers by 8, refer
to the CyberTech IPC installation manual for other types)

Following example shows a typical mapping where Left Handset is mapped to the
first channel, Right Handset to the second and Speakers to the third.

As we are recording E1 output from a TIC card, the first and seventeenth channel are
not used (time slots 0 and 16 on the trunk) In this example the Left Handset of station
16500 is mapped to channel 2, Right Handset of 16500 to channel 3 and Speakers by
8 of 16500 to channel 4.

Map all StationLAC items that need to be recorded in this way. Refer to the
CyberTech IPC installation manual if Handsets or Speakers are summed on an E1
timeslot.
Above example shows the mapping of 4 E1’s to the recorder. Remember never to
put more than 32 line_id items in 1 Group.
After making changes to the cti_config_ipc.csv file, the CyberTech CTI_CDR
processor service needs to be restarted.

13. In the Web GUI, go to ‘system installation > settings per recorder’, select every
recorder and set the in-law to: U-law

IPC integration – installation manual 43

 14. Go to the CyberTech monitor (located on the desktop of each recorder computer),
press CTRL+spacebar and start the Maintenance tool: (to open the monitor tool
make sure you’re logged on to Windows with an Administrator account)

15. In the Maintenance tool, for each board, type: call_split all 15

To select separate boards in the Maintenance tool, use CTRL+number (e.g. CTRL+3
will select the 3rd board)

IPC integration – installation manual 44

 16. Connect a Serial null-modem cable between the IPC SUN system center and the
CyberTech computer that has the CDR processor service installed.

To check if the CDR processor is working correctly, make a test call on a Turret and
check if the CDR record is shown in the Recorded calls listing in the Web GUI.

IPC integration – installation manual 45

Version history

Date Version Remark

01-05-2006 1.0 Initial document

17-07-2006 1.1 IPC details added

10-08-2006 1.2 IPC appendixes and field information added. Detailed configuration and installation
description including NTP.

6-10-2006 1.3 MynaVoice free seating user linked to IPC Trader ID. Configuration needed for this
feature.

IPC Call Type and Channel Type lookup list in database fields

12-10-2006 1.4 Appendix D added

01-11-2006 1.5 Speaker call data field length CVSC02 changed from 20 to 50 characters. Speaker calls
might include multiple lines. Additional Parrot DSC configuration commands added in
appendix B.

05-02-2007 1.6 Logo updated. Minor installation changes after review support. Added PasswordTool
option at stand alone CDR server configuration.

16-05-2008 1.7 Updated for Group based archiving functionality

19-05-2008 1.8 Added upgrade information for existing IPC installations.

03-06-2008 1.9 Added remark E1 termination in appendix B.

Minor textual changes based on internal review.
Updated lay-out

8-04-2009 1.10 Added Appendix E: software setup

17-04-2009 1.20 Added N+1 functionality.

Changed Appendix E: to F: and changed its layout.
Added Appendix E: N+1 Alarming.

05-06-2009 1.21 Added chapter “Multiple speaker boxes”

2009-07-30 1.22 Updated chapter 3 with new setup details

Updated Appendix D: minor text changes as a result of new setup
Updated Appendix F with new setup details

2009-10-09 1.23 Added CDR Resilience (chapter 3.6)

2009-11-05 1.24 Updated Appendix F (minor text change)

2010-04-07 1.25 Added Analogue Recording detail

IPC integration – installation manual 46