table of contents - bebpublishing€¦ · tic2 cards: • enterprise ip recording tic2 cards...

Table of Contents iii

Table of Contents

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ii

Chapter 1: Enterprise IP Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11.1 Supported Alliance MX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.1.1 Stations Supported by IP Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21.1.2 Switching Center Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21.1.3 Mixed Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31.1.4 EASe Failover Support for IP Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

1.2 Typical Enterprise IP Recording System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41.2.1 About the IPC Common Platform Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

1.3 IP Recording Network Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91.3.1 Network Configurations that Continue to Be Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91.3.2 Unsupported Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

1.4 Multi-Site Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121.5 Enterprise IP Recording Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

1.5.1 Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131.5.2 Long Term Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141.5.3 Recording Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

1.6 SCSA – IP Recording Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141.7 Call Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.8 Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.8.1 Network Bandwidth Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161.8.2 Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161.8.3 IP and UDP Port Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171.8.4 Remote Access for Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

1.9 Server Operating Systems and Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.9.1 Time Zone Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211.9.2 Operating System Security Fixes and Service Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211.9.3 Server Environmental Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

1.10 Installing IP Recording Hardware in a Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.11 Shutting Down and Restarting the IP Recording Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241.12 DAT Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.13 Installing the Optional Dialogic Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261.14 Maintaining Enterprise IP Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1.14.1 Swapping a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261.14.2 Replacing Power Strips in the Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281.14.3 Removing Servers from a Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291.14.4 Swapping a Hard Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301.14.5 Hard Drive Failure and Using RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311.14.6 NIC Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

1.15 Setting Up IP Recording at the OneMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.15.1 Enable IP Recording Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341.15.2 Enable Record On Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341.15.3 Enable the Recording Warning Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341.15.4 Set Up Port Configuration for TIC2 Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351.15.5 Set the IP Address of the Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371.15.6 Configure Session Control Device IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381.15.7 Configure OneMS for ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

IPC Systems Inc. Confidential and Proprietary Alliance MX 16.1 Recording Installation and Maintenance

DO NOT COPY OR DISTRIBUTE

Note

This sample excerpt is for your personal review only and must not be copied or distributed.

1: Enterprise IP Recording 1

1 Enterprise IP Recording

This topic provides an overview of Enterprise IP Recording and installation details for IPC IP recording components.Enterprise IP Recording uses the customer network as the backbone for recording through the Alliance MX. Enterprise IP Recording lets you record from one or more sites that are connected to your network onto recorders that are located anywhere on your network.Additionally, whereas SCSA and E1 recording are assigned to a particular station, Enterprise IP Recording is assigned to a TRID, so recording follows traders if they log into stations connected to a TIC2 card with Enterprise IP Recording enabled. This feature supports global free seating and redundancy for business continuity planning (BCP).To let you manage your recordings and provide for long-term storage and easy retrieval, Enterprise IP Recording uses NICE™ Systems software and storage.

Enterprise IP Recording provides:• Audio-to-recorder transmission over the customer network (no port monitoring required).• Load balancing algorithm distributes line recording evenly across many recording servers.• N+M redundancy options: All recording servers are active at all times. Failure of a recording server is

compensated for by adjustment of the load balancing (unlike SCSA, where the single redundant logger sits idle until needed to make up for a failure).

• Network redundancy: Two Ethernet ports per card support two sets of Ethernet cables that can be linked through duplicate switches to the network.

• Microsoft .NET-based client applications to permit playback from any Windows PC.• Audio compression between the TIC2 station card and the logging system using the g.729

specification. • Programmable recording options per TRID:

• Handsets (summed, individual, transmit only, receive only)• Speakers (summed, individual speakers, any mixing combination)• Microphone (can be recorded on a separate channel)

• Real-time call records available over the customer network.• Up to 200 recording channels per recording server.• 50,000 hours online storage per recording server.The Alliance MX system tracks:• Who the traders are.

For a graphical representation of IP recording on a network, see section 1.3 IP Recording Network Configurations on page 9.


2 1: Enterprise IP Recording2 1: Enterprise IP Recording

• Their recording requirements.• Which traders are logged onto each station.• Whether there is redundancy (see section 1.5.1 Redundancy on page 13).• Each station’s audio equipment (handset, speakers, and microphone).• The list of recording servers.The IP recording system tracks:• How many recording servers there are.• How many channels each recording server has allocated to it.• Which channels on those recording servers are in use and by whom.• Which channels in those recording servers are free.• Licensing information, whether it is by number of channels or by number of traders that are available.

1.1 Supported Alliance MX SystemsEnterprise IP Recording is supported on Alliance MX release 12.0 and later.

1.1.1 Stations Supported by IP RecordingThese stations support IP recording for these turrets:• IQ/MAX and MAXaccess Soft Turret• ICMX• IQMX

1.1.2 Switching Center CardsEnterprise IP Recording is supported only by the TIC2 cards. TIC2 cards includes the following kinds of TIC2 cards:

• Enterprise IP Recording TIC2 cards released with Alliance MX 12 – these cards support only IP recording.

• TIC2 Station cards, released with Alliance MX 14.1 – these cards support IP recording or E1 recording. However, a mixed environment of IP recording on TIC2 cards and E1 recording on TIC2 cards is unsupported.

MPIC and first-generation TIC cards do not support Enterprise IP Recording.TIC2 cards do not support SCSA recording.

In multi-switch environments, remember that like TRIDs are not supported. Each One Management System, hereinafter referred to as OneMS, must have unique TRIDs. Example: TRID 100 cannot have IP Recording enabled on both sites. That is, if Site 1 has TRID = 100, Site 2 cannot contain a TRID = 100.

Enterprise IP Recording TIC2 cards released with Alliance MX 12 do not support E1 recording. TIC2 station cards, released with Alliance MX 14.1, support E1 recording or IP recording.

April 2010 IPC Systems Inc. Confidential and Proprietary

1.1 Supported Alliance MX Systems 3

1.1.3 Mixed RecordingThe Alliance MX supports a mixed recording environment in which TIC2 cards perform all IP recording and TIC (first-generation TIC) cards perform either E1 or SCSA recording. • You cannot mix SCSA and E1 recording together using one OneMS.• You cannot mix IP recording on TIC2 cards with E1 recording on TIC2 cards. • You can mix IP recording on TIC2 cards with E1 recording on TIC (first-generation TIC) cards.• You can mix IP recording on TIC2 cards with SCSA recording on TIC (first-generation TIC) cards.IP, SCSA, and E1 recording are enabled by a field in the OneView System Feature work area.• To enable IP recording for TIC2 cards, see section 1.15.1 Enable IP Recording Feature on page 34.• To set up IP recording, see Chapter 3: E1 Recording on page 79.• To enable E1 recording and disable SCSA recording, see section *3.6.1.1 Enabling E1 Recording in

System Feature on page 82.• To enable SCSA recording and disable E1 recording, see section 5.3.1 Set Max Recorder Channels on

page 103.

1.1.4 EASe Failover Support for IP RecordingEASe is the IPC business continuity planning (disaster recovery) solution. See your EASe documentation for more information. However, if your failover sites are set up correctly for IP recording, then recording can be supported by the failover scenario.

Table 1-1: TIC2 Cards Overview

Card Types Card Purpose Number of IP Addresses Used by Card

AICX IQ/MAX station card 21

1. One IP address is for the IPC voice network and the other is for the customer network where recording takes place.

IICX ICMX station card 21

TICX IQMX station card 21

RAIX Enterprise IQ/MAX station card 1

REIX Enterprise ICMX station card 1

RETX Enterprise IQMX station card 1

FAIX Failover IQ/MAX station card2

2. Failover is unsupported for Alliance MX 14.1; An EASe update planned for Alliance MX 15.3 can manage spare cards that failover, see section 1.1.1.4 EASe Failover Support for IP Recording on page 13.

1

FEIX Failover ICMX station card (EASe) 1

FETX Failover IQMX station card (EASe) 1



1.2 Typical Enterprise IP Recording SystemA typical IP recording system has these components connected by a LAN:• A Windows-based database and applications server (DB/APP)

A server where you configure and administer the recording system and store call records using NICE™ software.

• One or more Windows-based IP recording serversServers on the customer’s network that use NICE software and store voice recordings.

• A customer-supplied administration workstation you can use for playback or remote administration of the IP recording system.

• EMC®, Centera™, or other customer-supplied storage center servers for long-term storage or recordings.

• A customer-supplied NMS server for SNMP alarming.• Alliance MX system.For more information, see section 1.2.1 About the IPC Common Platform Servers on page 7.

The NICE hardware cannot be connected to the Alliance MX network, it must be connected to the customer network.


1.2 Typical Enterprise IP Recording System 5

Figure 1-1: IP Recording TIC2 Cards/No Enterprise Stations

Speaker Speaker Speaker

System Center

Database and

Applications

Server

IPC Voice Network

Recording

Server

Recording

Server

System Center

Gateway Card

TIC2 Card*

Stations on IPC Voice Network

Two IP Addresses

IQMX IQMX IQMX

Customer Network

Administration

Workstation

Also ICMX modules on their own

TIC2 cards

* AICX, IICX, or TICX

MAXaccess

Soft Turret

(record from

the TIC only)



Figure 1-4: Server Panel (front view)

The Server LCD Panel displays status, including reporting power supply and hard drive failures.

Figure 1-5: Server LCD Panel

There are four controls on the Server LCD Panel:• Power button – Lights when power is on. Push this button to turn off power.• NMI button – Used to troubleshoot software and driver errors. Use this only if directed by IPC or

Dell.• System identification button – Used to find a server in a cabinet. Push this button, or the system

identification button on the back of the server, and the LCD panel and the blue system status indicator on the back flash until one of the system identification buttons is pushed again.

Table 1-2: Common Server Drive Bay Configurations

Server Type Logical Drive 0 Logical Drive 1

Database and Applications

Three 36 GB or 146 GB hard drives1 in a RAID 5 configurationStores O/S and application softwareBays 0, 1 and 2

1. The 36 GB hard drives are in the Series II for NICE 9.09. The Series III for NPR3 has 146 GB hard drives.

Three 146 GB hard drives in a RAID 5 configurationStores database files (data)Bays 3, 4 and 5

Recording Two 36 GB or 146 GB hard drives1 in a RAID 1 configurationStores O/S and application softwareBays 0 and 1

Three 146 GB hard drives in a RAID 5 configurationStores voice recordingsBays 2, 3 and 4

Hard Drive LEDsServer LCD Panel Hard Drive Bays 0-5 Hard Drive Bays 6 & 7

(empty, spare bays)

Server LCDNMI buttonPower button

System identification button


1.3 IP Recording Network Configurations 9

• Server LCD – Lights during normal operation. Flashes blue if the system identification button is pushed. Lights amber and displays an error code and descriptive text if an error is detected. See the Dell documentation for help with error codes (http://support.dell.com/support/edocs/systems/pe2950/en/hom/html/about.htm#wp1096182).

Field-serviceable parts consist of the hard drives and power supplies, both of which can be swapped from outside the server case. There are currently no field-replaceable parts inside the server case. Failure of items inside the server case require replacement of the entire server.

1.3 IP Recording Network ConfigurationsThe following sections describe network configurations that are supported and unsupported by Enterprise IP Recording.

1.3.1 Network Configurations that Continue to Be SupportedThe following networking configurations continue to be supported.

Figure 1-6: Everything in One Subnet – Supported Configuration


http://support.dell.com/support/edocs/systems/pe2950/en/hom/html/about.htm#wp1096182



1.5.2 Long Term StorageEnterprise IP Recording solution uses a NICE Storage Center server along with an EMC Centera, or other long-term storage device, to provide long-term storage of recording data. This solution eliminates the need to manage tapes and simplifies retrieval by making all calls available for replay in real-time over the customer network.Additionally, customers might optionally choose to archive to the DAT 72 tape drive, which comes installed with the Dell 2950 common server (series 2 and 3). For a description of the DAT 72 drive, see section 1.12 DAT Tape Drive on page 25.

1.5.3 Recording ApplicationsNICE Systems provides several recording applications, for example:• Playback Organizer – Search and playback of calls• Graphical view of traders calls• User Administration• System Administration• Audit Trail• Lists Editor – Lets you customize the Web interface• Rules ManagerOther applications, such as analytical voice-based searches (word spotting) and voice-identification (voice signature) based search, may be available. Refer to NICE documentation that is applicable to your system.

1.6 SCSA – IP Recording ComparisonTable 1-3: SCSA Recording and Enterprise IP Recording Comparison

Feature SCSA Enterprise IP Recording

Channels per recorder 496 200

Free seating Yes (requires station be configured for recording)

Yes (associated with TRID not a station)Free seating with Enterprise IP Recording requires a trader log on at a station connected to a TIC2 that has Enterprise IP Recording enabled.

Database sharing Only via NICE approval Yes

Audio compression G.729 compression in recorder (optional)

G.729 compression between the TIC2 and the recording server and on the recording server (standard)

Call record delivery CDR from OneMS (non real-time) using serial port

Real-time call records from TIC2 using the network

Storage

Online storage Up to 27,000 hours (standard)Up to 81,000 hours (optional)

50,000 hours standard


1.8 Network Requirements 19

Table 1-6: Overall TCP and UDP Port Usage by Recording Server summarizes the TCP and UDP ports used for recording server (also called the interactions server) tasks by the NICE logging system. These tasks are discussed in the NICE Systems documentation.

TCP IPC IBM Informix Database 1541 Connecting NICE database to IPC’s (using Linked Server) ODBC service.

TCP Playback Server (DB/APPS)

8001, 8002, 8003, 8010

Requests to initiate playback to user extension.

TCP Intel Dialogic software on Playback Server (DB/APPS)

12001, 12002, 12004,

12005, 20001

Internally used by Dialogic SR6 software. Port list is based on Intel Dialogic system prerequisites these ports may change and additional arbitrary TCP ports in the range between 1024 - 5000 may be utilized, as well as TCP and UDP ports 135 to allow remote DCOM across firewalls if required. Refer to Intel Dialogic System Release 6.0 PCI for Windows Documentation.

1. These can use any client PC port that is configured. DB/APPS is the Application Server; RM is the Recording Machine.

Table 1-5: Overall Port Usage by Database and Applications Server (continued)

Protocol Purpose within the NICE Logging System1

Database and

Application Server Port

Notes

Table 1-6: Overall TCP and UDP Port Usage by Recording Server

Protocol

Purpose within the NICE Logging

System

Recording Server Port

Database and Applications Server Port

TIC2 Port Notes

UDP Logger Control (short)

20002012

Arbitrary

TCP Logger Retrieve 2001 Arbitrary Playback audio from the external storage.

TCP Logger Control (long)

2011 Arbitrary Control of the playback server.

TCP Session Control 5500 Arbitrary

TCP CTI Data 5501 Arbitrary Allows the system equipment and user configuration.

UDP Voice Capture Ports

50000–50210 Arbitrary Defines rules to be executed by the rule engine.

TCP CAPI Connection 62050 Arbitrary Query the interactions database for the NICE Business Analyzer.



1.8.4 Remote Access for TroubleshootingTo provide remote access for troubleshooting Enterprise IP Recording, the customer must develop a remote access plan consistent with their security practices, such as secure VPN. All servers include a modem for remote access.

1.9 Server Operating Systems and RequirementsThe IPC-supplied database and applications servers and recording servers include:• Windows Server 2003 with service packs installed (follow NICE Systems’ installation instructions) • Symantec pcAnywhere™ for remote log on and technical support• ConeXware Power Archiver file compression and archiving software• Microsoft Internet Information Services (IIS)• SNMP service• Microsoft .NET Framework 1.1 (2.0 on the common server)• ASP .NET

TCP .NET Remoting 62051 Arbitrary Retrieving recorded media from logger or storage center on behalf of a remote playback server.

TCP CLS Monitor on Interaction Center (RM)

62061-62064 IPC-IP License management.

TCP DB Server on Interaction Center [RM]

62055 Passing requests to insert/update, interactions and contacts to/in database. (.NET Remoting HTTP service).

TCP CLS SNMP Agent (part of SNMP.EXE service) on Interaction Center [RM]

62059 Passing notifications for SNMP traps from CLS processes to CLS SNMP Agent. (.NET Remoting HTTP service).

TCP RCM on Interaction Center [RM]

62069 Handling recording requests from Call Server. (.NET Remoting HTTP service).

Table 1-6: Overall TCP and UDP Port Usage by Recording Server (continued)

Protocol

Purpose within the NICE Logging

System

Recording Server Port

Database and Applications Server Port

TIC2 Port Notes


1.9 Server Operating Systems and Requirements 21

1.9.1 Time Zone SettingsTime zone settings must match between the OneMS and IP recording servers. Use the same NTP source or manually configure these components to the same time. For more information, see section 1.15.9 Setting Up NTP for IPVR on page 43.

1.9.2 Operating System Security Fixes and Service PacksEnterprise IP Recording uses NICE Systems standard policies regarding Microsoft service packs and security fixes. As part of the installation process, it is the responsibility of IPC installation technicians to verify that all certified Microsoft OS service patches and all critical security fixes are installed using Windows Update on the recording servers and database and applications servers.For ongoing security support, Enterprise IP Recording uses the certification testing performed by NICE Systems to approve security fixes and service packs. Installation of all service packs and security fixes are the responsibility of the customer. Customers may choose to install critical security patches on the servers prior to official certification, however, we recommend installing these in a lab environment before doing so on a production system. IPC installation personnel can install service packs and security fixes at the customer’s request (the customer must define which service packs and which security fixes to implement).NICE Systems provides technical notes on a regular basis summarizing certification results. These results are also posted on NICE’s extranet site (www.extranice.com) under EIS & Public Safety, Technical Documentation, Technical Notes, General Notes. These pages are available for EIS and public safety end users.

1.9.2.1 Antivirus SoftwareEnterprise IP Recording servers include Norton® AntiVirus™ Small Office Pack software. The IPC installation technician must verify that all virus definition updates for Norton AntiVirus are installed. Servers are configured to receive automatic updates of the virus definition files from Symantec® during the installation process.

For additional time drift and time zone instructions, see the Alliance MX 16.1 Guide to Troubleshooting Tools booklet.


http://www.extranice.com


1.9.3 Server Environmental ConsiderationsServer environmental considerations for the Series II and III Dell machines:

Table 1-7: Series II Environmental Considerations

Condition Parameter

Maximum Power Requirements for Database and Applications Server

1.74 amps at 220 volts1.85 amps at 208 volts3.21 amps at 120 volts3.34 amps at 115 voltsRedundant power supplies are installed: the load across both power supply feed will not exceed the amperage listed above at the stated voltage

Maximum Power Requirements for Recording Server

1.53 amps at 220 volts1.62 amps at 208 volts 2.81 amps at 120 volts2.93 amps at 115 voltsRedundant power supplies are installed: the load across both power supply feeds will not exceed the amperage listed above at the stated voltage

Nominal Power Requirements of Recording /Database and Applications Servers

0.91 amps at 220 volts0.96 amps at 208 volts1.66 amps at 120 volts1.71 amps at 115 volts

Server Weight Database and Applications server: 50 lbs. Recording server: 50 lbs.

Dimensions of Recording/Database and Applications Servers

29.31 in. (74.4 cm) D x 17.5 in. (44.43 cm) W x 3.4 in. (8.64 cm) H

Humidity Range for Recording/Database and Applications Servers

20%-80% non-condensing twmax = 84.2°F (29°C)

Operating Temperature Range for Recording/Database and Applications Servers

50°F (10°C) to 95°F (35°C)

Nominal Heat Dissipation for Recording/Database and Applications Servers

681 BTUs per hour


1.10 Installing IP Recording Hardware in a Cabinet 23

1.10 Installing IP Recording Hardware in a CabinetIPC recommends that you install servers for Enterprise IP Recording in their own cabinet whenever possible. For more information, see the Alliance MX 16.1 Hardware Installation, Configuration, and Maintenance booklet.

Table 1-8: Series III Environmental Considerations

Condition Parameter

Maximum Power Requirements for Database and Applications Server

1.62 amps at 220 volts1.72 amps at 208 volts2.98 amps at 120 volts3.11 amps at 115 voltsRedundant power supplies are installed: the load across both power supply feed will not exceed the amperage listed above at the stated voltage

Maximum Power Requirements for Recording Server

1.47 amps at 220 volts1.56 amps at 208 volts 1.70 amps at 120 volts2.81 amps at 115 voltsRedundant power supplies are installed: the load across both power supply feeds will not exceed the amperage listed above at the stated voltage

Nominal Power Requirements of Recording /Database and Applications Servers

0.98 - 1.08 amps at 220 volts1.03 - 1.14 amps at 208 volts1.79 - 1.98 amps at 120 volts1.87 - 2.06 amps at 115 volts

Server Weight Database and Applications server: 50 lbs. Recording server: 50 lbs.

Dimensions of Recording/Database and Applications Servers

29.31 in. (74.4 cm) D x 17.5 in. (44.43 cm) W x 3.4 in. (8.64 cm) H

Humidity Range for Recording/Database and Applications Servers

20%-85% non-condensing twmax = 84.2°F (29°C)

Operating Temperature Range for Recording/Database and Applications Servers

32°F (0°C) to 104°F (40°C)

Nominal Heat Dissipation for Recording/Database and Applications Server

733.2 BTUs per hour



1.11 Shutting Down and Restarting the IP Recording ServersYou may need to shut down shutdown or restart services on the DB/APP and IP Recording servers when TRIDs cannot log onto the IP Recording or 601/602 alarms occur.The NICE Services Configuration Manager application (Figure 1-12) is used to turn services on and off on the servers.

Figure 1-12: NICE Services Configuration Manager

To access the NICE Services Configuration Manager• On a DB/APP Server, click Start > Program Files > NICE Systems > Applications > Tools > NICE Services

Configuration Manager.• On a Recording Server, click Start > Program Files > NICE Systems > Interactions Center > Tools > NICE

Services Configuration Manager.

References to the number of services for the following procedures are for NICE 9.09 SP1 software. The number of services varies with software versions.


1.12 DAT Tape Drive 25

Use the following procedures to start and stop the servers.

To stop a DB/APP Server1 With the NICE Services Configuration Manager, stop all NICE services. Click to highlight the service (or

press Ctrl A to select all) then click the Stop icon in the menu bar.2 When the services are down, then you can shut down the server with the Windows Start > Shutdown

option.

To stop an IP Recording Server1 With the NICE Services Configuration Manager, stop all NICE services (about five services). Click to

highlight the service (or press Ctrl A to select all) then click the Stop icon in the menu bar. 2 On the Recording Servers, close the Dispatch window (answer Yes to terminate the CLS Server).3 Close the rest of the minimized windows.4 To complete the shutdown, use the Windows Start > Shutdown option.

To start a DB/APP Server1 Power on the DB/APP server if it was shut down and log in.2 With the NICE Services Configuration Manager, verify that all Nice services are started (between 13 and

17 Nice services).

To start an IP Recording Server

1 Power on the Recording Server and log in.2 With the NICE Services Configuration Manager, verify that all Nice services are started (about five).

1.12 DAT Tape DriveBoth the Recording Server and the Database and Application Server (Dell 2950, series 2, 3) include a DAT 72 tape drive for backing up data and voice recordings. The software used by this drive is installed and ready for you to use. See the NICE Systems documentation for information on using this drive.

Figure 1-13: DAT 72 Tape Drive Location

The Nice SystemAdministrator service shuts down more than ten services.

!Do not Power on the Recording Servers until after the DB/APP Server is completely up and running.

1 DAT 72 tape drive1



1.13 Installing the Optional Dialogic Card

The Database and Application Server includes a Dialogic card, an analog card with four RJ-11 jacks that are used for playback of recordings through an extension. The software used by this card is installed and ready to use. See the NICE Systems documentation for information on using this card.

Figure 1-14: Dialogic Card Location (Server Rear View)

1.14 Maintaining Enterprise IP RecordingThis section discusses IP recording hardware.

1.14.1 Swapping a Power SupplyThe server includes a redundant power supply; should one power supply fail, the other power supply runs the server without any decrease in performance. Replace failed power supplies as soon as possible. The server’s power supplies are hot-swappable: you can replace a failed power supply whether or not power to the server is turned off. If there is a failure, the LCD screen on the front of the server turns yellow. The screen displays error codes and a description of any failure. Additionally, refer to the power supply indicator lights on the rear of the server. See Figure 1-15.

Figure 1-15: Power Supply Indicators

The power supply has three indicator lights• Power supply status – Green indicates the power supply is working.• Power supply fault – Yellow indicates there is a problem with the power supply.• AC line status – Green indicates that a valid AC source is being used by the power supply.

!When working inside the case of the server, take precautions against electrostatic discharge (ESD), including wearing a grounding strap that attaches to the chassis of the server. For more information, see the Alliance MX 16.1 Hardware, Configuration, and Maintenance booklet.

1 Dialogic card with four RJ-11 jacks

1

1 Power supply status

2 Power supply fault

3 AC line status

1

2

3


1.14 Maintaining Enterprise IP Recording 27

To remove a power supply1 From the back of the server, unplug the power supply you are going to replace.2 Push the red tab to the right to unlatch the power supply you want to remove.3 Pull the unlatched power supply from the server.

Figure 1-16: Removing and Reinstalling a Power Supply (Server Rear View)

To install a power supplyRefer to Figure 1-17 while performing these steps. 1 Ensure the red tab is unlatched (pushed to the right) and that the black lever is up. 2 Firmly push against the power supply grid, sliding the power supply into the slot, until it latches. You

will hear a click. Do not push against the black lever to insert the power supply because this action will inadvertently close the latch and prevent the power supply from connecting.

1 Serial port

2 SCSI port

3 Video port

4 USB ports

5 Network (Ethernet) ports

6 Modem

7 Dialogic card

8 Power supply latch

9 Power Supplies

98

3

4

5

1

7

6

2



Figure 1-17: Power Supply

1.14.2 Replacing Power Strips in the CabinetA cabinet is equipped with a back plate for power strips on the bottom right side of the cabinet and another on the bottom left. Each back plate has four power strips attached to it. There are a maximum of eight power strips (two back plates) per cabinet. Each power strip can support four server power supplies. One server uses one outlet on each side of the cabinet. In Figure 1-18, see 1 and 2:1 One nut at each end holds the power strip in place by attaching to a stud installed on the back plate.2 Four power strips oriented the same way fit on a back plate.

Figure 1-18: Power Strips on a Back Plate

1 Grid

2 Power supply latch/unlatch tab

3 Lever

4 Connector

32 4

1

12



To replace a power strip

1 Remove the power strip.a Note the orientation of the power strip on the back plate.b Turn off power to the power strip you want to remove.c Unplug the cable that supplies power to the power strip from its source, then remove the C-19

connector on that cable from the power strip.d The power strip is held in place by two 8-32 nuts, one at each end, that thread onto studs

protruding from the back plate. Remove these two nuts and pull the power strip from the cabinet.2 Install the new power strips on the brackets alongside the existing power strips in the same orientation

as the power strip you removed.a The power strip is held in place by two 8-32 nuts, one at each end, that thread onto studs

protruding from the back plate. Hold the power strip in place and install these two nuts.b For the cable that supplies power to the power strip, plug the C-19 connector into the power strip.c Connect the other end of the cable that supplies power to the power strip to the customer power

outlet.d Enable power to the cable that supplies power to the power strip.

1.14.3 Removing Servers from a Cabinet

To remove a server from the cabinet1 Disconnect power from the server.2 Disconnect the Ethernet cables from the back of the server.3 Unscrew the two front screws that secure the front of the server to the front vertical posts in the

cabinet.

4 Slide the server forward out of the cabinet.To install a server, see the Alliance MX 16.1 Hardware, Configuration, and Maintenance booklet.

!Use only IPC approved power strips. Failure to use IPC approved power strips could result in damage to Alliance MX hardware and interruption of service.

Extend only one server out of the cabinet at a time. Extending more than one server at a time can cause the cabinet to tip over.

!When working inside the case of the server, take precautions against electrostatic discharge (ESD), including wearing a grounding strap that attaches to the chassis of the server. For more information, see the Alliance MX 16.1 Hardware, Configuration, and Maintenance booklet.

Each server weighs about 50 pounds. Use two people to remove a server from the cabinet to minimize the chance that you drop the server and to reduce the risk of injury caused by lifting the heavy weight. Dropping a server could cause damage to the server and might injure personnel.



1.14.4 Swapping a Hard DriveThe server’s hard drives are hot-swappable: you can replace a hard drive whether or not power to the server is turned off. The server’s RAID is designed for the failure of a single hard drive. If more than one hard drive fails in one logical drive array, you must replace the server.To determine which hard drive has failed, look at the two LEDs by each hard drive. The upper LED (drive status indicator) is off on a failed hard drive. Additionally, the Server LCD Panel indicates the bay number of the failed drive.

Figure 1-19: Hard Drive Indicator Lights

The hard drives have two indicator lights:• Drive status indicator – This light can be yellow or green. The light remains on when the drive is okay.• Drive activity indicator – This light is only green. This light flashes to indicate hard drive activity.

For more information, see: http://support.dell.com/support/edocs/systems/pe2950/en/hom/html/about.htm#wp1096182.

To remove a hard drive1 Pinch the hard drive release mechanism together.

Refer to Figure 1-20 for the release mechanism location, and Figure 1-21 for a close-up of the release mechanism.

2 Pull the hard drive out of the server.

1 Drive status indicators

Table 1-9: Hard Drive Indicator Light Patterns

Light Pattern Drive Condition

Flashes green twice per second Identify drive/preparing for removal

Off (no light) Drive ready for insertion or removal

Flashes green, amber, and off Predicted drive failure

Flashes amber four times per second Drive has failed

Flashes green slowly Drive is rebuilding

Steady green Drive is online working normally

Flashes green for three seconds, then amber for three seconds, then off for three seconds

RAID rebuild has been aborted

1





Figure 1-20: Removing and Reinstalling a Hard Drive (server front view)

Figure 1-21: Hard Drive in its Tray

To install a hard drive1 Slide the hard drive into the empty hard drive bay in the front of the server.2 Push the hard drive firmly until you feel it latch into the hard drive bay. The RAID automatically

configures the new drive for use; see the next section 1.14.5 Hard Drive Failure and Using RAID.

1.14.5 Hard Drive Failure and Using RAIDThe Recording Server uses RAID 1 for the two hard drives in bays 0 and 1, and RAID 5 for the three hard drives in bays 2, 3, and 4, whereas the Database and Applications Server uses two RAID 5 configurations for the three GB hard drives in bays 0, 1, 2 and 3, 4, 5 respectively.

1 Hard drive release mechanism

1 Hard drive

2 Tray

3 Hard drive release mechanism

4 Mounting screws

1

34

2

1



If a hard drive fails, the LCD panel on the front of the server (see The Server LCD Panel displays status, including reporting power supply and hard drive failures. on page 8) and the hard drive indicator lights (see Figure 1-19 on page 30) indicate the failure. A server supports the failure of only one hard drive in one logical drive array. If a hard drive fails, replace it. If more than one hard drive fails, contact IPC Global Support Engineering.When you replace a single hard drive into one of these RAID configurations, the server automatically rebuilds the RAID.

Authorized personnel can access the RAID BIOS when the server boots by pressing Ctrl+R.

1.14.5.1 RAID Controller Battery BackupThe RAID controller in this server is equipped with battery backup. If the server is not connected to a power source within two months of being shipped from the factory, the battery may become discharged. If the battery is discharged, the following will be displayed during boot-up.

Figure 1-22: Discharged Battery Message

In addition to the messages displayed upon boot-up, the front panel LCD will display a ROMB Battery error. The server must remain under power for up to an hour for the battery to fully recharge. Once recharged, the error on the LCD will clear and the message at boot-up will no longer be displayed. There are no issues with normal server functionality during this time.

1.14.6 NIC Indicator LightsThe Ethernet ports have two indicator lights:• Link indicator – If this light and the activity indicator are off, there is no network connection. If this is

green, the NIC is connected to the network.

!Editing the RAID configuration using the RAID BIOS can destroy data. Use of the RAID BIOS should be limited to authorized personnel only.


1.15 Setting Up IP Recording at the OneMS 33

• Activity indicator – If this light and the link indicator are off, there is no network connection. If this light is flashing yellow, network data is being transmitted.

Figure 1-23: NIC Indicator Lights

For location of these network ports on the server’s back panel, see Figure 1-16 on page 27.

1.15 Setting Up IP Recording at the OneMSThis section outlines the steps you take to set up IP recording at the OneMS for a Dell PowerEdge R710 and 2950.

1 Check that the Enterprise IP Recording feature is enabled. See section 1.15.1 Enable IP Recording Feature on page 34.

2 Enable the recording warning tone (applied by station). See section 1.15.3 Enable the Recording Warning Tone on page 34.

3 Set the port configuration for the TICX-based cards. See section 1.15.4 Set Up Port Configuration for TIC2 Cards on page 35.

4 Configure the OneMS for ODBC. See section 1.15.7 Configure OneMS for ODBC on page 38.5 Configure the second IP address for any TICX, IICX, or AICX (local) cards that will be doing IP

recording. See section 1.15.5 Set the IP Address of the Cards on page 37.6 Enter the session control device IP addresses into a OneMS table. See section 1.15.6 Configure

Session Control Device IP Addresses on page 38.7 Reload the cards.8 Enable ODBC access from OneView using Configure System Center (configure_syscen). See section

1.15.7 Configure OneMS for ODBC on page 38.9 Restart OneMS console.10 Define any custom mixes you want to use for recording. See section 1.15.8.1 Creating New Recording

Mixes on page 39.11 Assign traders to the mixes, then log off and log back in all TRIDs whose assignments you have

changed. See section 1.15.8.3 Assigning Recording Mixes to TRIDs on page 42.

1 Activity indicator

2 Link indicator

21

!The information in this section supersedes information provided in earlier documents, including early releases of the Alliance MX Recording Installation and Maintenance Manual.

If you encounter inconsistent call logger output, see the Alliance MX 16.1 Guide to Troubleshooting Tools booklet for instructions on how to verify call logger output time and correcting time drifts.



1.15.1 Enable IP Recording Feature

To check that the Enterprise IP Recording feature is enabled1 In OneView, click Main Menu System Settings > System Feature.2 Verify that the IP Recording check box is selected.3 Set the Recording Site ID field. The number must be unique for each OneMS console connected to a set

of recorders. You must set a number for Recording Site ID even if you only have one OneMS.

1.15.2 Enable Record On DemandThe ROD feature allows the dynamic control of IP and E1 recording from the IQ/MAX turret handsets and the MAXaccess 1000 Callback line. With specially programmed ROD buttons, a trader can control whether or not they are recorded on their handsets or Callback line.

For complete instructions, see section 1.22 Record On Demand: Configuration and Troubleshooting on page 69.

1.15.3 Enable the Recording Warning ToneTo enable the tone (beep) a user hears on the turret that indicates a call is being recorded, follow instructions in section 3.6.1.2 Enabling or Disabling Recording (Warning) Tone in System Data on page 82 for setting the Param Id 147. For a complete description of the warning tone feature, see the Alliance MX 16.2 Setting Up Audio Features booklet.After changing the tone setting, the database schema must be reconfigured, see the Alliance MX 16.1 Deployment and Upgrading booklet for more information.

Multi-switch sites must have their own Recording Site ID (1, 2, 3, etc.).

At this time, dynamic recording control is a specific requirement of worker union and regulations in Germany and Italy only. Use of this feature outside of that region could violate other regulations.



1.15.4 Set Up Port Configuration for TIC2 CardsFigure 1-24: Supported Recording Configurations for TIC2 Cards shows supported connection profiles for use of Enterprise IP Recording with TIC2 cards. Table 1-10: TIC2-Based Card Supported Network Connections describes those connections.

Figure 1-24: Supported Recording Configurations for TIC2 Cards

AICX, IICX, and TICX cards have two IP addresses, one for the IPC voice network and the second for the customer network, where the recording servers are. FAIX, FEIX, FETX, RAIX, REIX, and RETX cards have only one IP address that connects to the customer network.

Table 1-10: TIC2-Based Card Supported Network Connections

Card Type Condition Connections

AICXTICXIICX

Uses IPC voice networkNo IP recording

Fiber or Ethernet port #1 to the ESR.

Uses IPC voice networkWith IP recording

Fiber or Ethernet port #1 to the ESR.Ethernet ports 3 and 4 to the customer network.

FAIXFEIXFETXRAIXREIXRETX

Uses customer networkNo IP recording

Fiber to the customer network for voice traffic.OREthernet ports 3 and 4 to the customer network for voice traffic.

Uses customer networkWith IP recording

Fiber to the customer network for both voice and IP recording traffic.OREthernet ports 3 and 4 to the customer network for both voice and IP recording traffic.

Figure 1-25: Ticx2 Port Config OneView Work Area and its description are only examples. This data should not be copied to your system, but should be used only for reference.

X

XX

Ethernet #2

Ethernet #3

Ethernet #1

Ethernet #4

Fiber port

Ethernet #2

Ethernet #3

Ethernet #1

Ethernet #4

Fiber port

AICX

IICX

TICX

FAIX

FEIX

FETX

RAIX

REIX

RETX

Local IP Station

Enterprise IP Station

IP Recording

Server

Database and

Applications

Server

IPC Voice

Network

Customer

Network

Fiber OR copper

Fiber OR

copper



Figure 1-25: Ticx2 Port Config OneView Work Area

Figure 1-25: Ticx2 Port Config OneView Work Area shows port configurations for TIC2 cards that support Enterprise IP Recording. Those configurations are explained as follows:• CardLac 16627 – An AICX, IICX, or TICX using Enterprise IP Recording.

• NIC 1 Port – Communicates with the stations.• NIC 2 Port – Unused.• NIC 3 Port – Communicates with the recording servers using the customer network.• NIC 4 Port – Communicates with the recording servers using the customer network.• Fiber Port – Unused.

• CardLac 16706 – An AICX, IICX, or TICX using Enterprise IP Recording.• NIC 1 Port – Unused.• NIC 2 Port – Unused.• NIC 3 Port – Communicates with the recording servers using the customer network.• NIC 4 Port – Communicates with the recording servers using the customer network.• Fiber Port – Communicates with the stations using a fiber connection.

• CardLac 16787 – An FAIX, FEIX, FETX, RAIX, REIX, or RETX using Enterprise IP Recording over a copper-wire connection.• NIC 1 Port – Unused.• NIC 2 Port – Unused.• NIC 3 Port – Communicates with the stations and recording servers using the customer network.• NIC 4 Port – Communicates with the stations and recording servers using the customer network.• Fiber Port – Unused.

• CardLac 16866 – An FAIX, FEIX, FETX, RAIX, REIX, or RETX using Enterprise IP Recording over a fiber connection.• NIC 1 Port – Unused.• NIC 2 Port – Unused.• NIC 3 Port – Unused.• NIC 4 Port – Unused.• Fiber Port – Communicates with the stations and recording servers using the customer network.



To create a new recording mix1 In OneView, click Main Menu > Voice Recording > IPVR Record Utility > IP Recording Mix Utility. The

Recording Mix form opens.

Figure 1-26: Recording Mix OneView Work Area

• The left side of the window displays mixes that are already defined.• The right side of the window displays what a mix is and lets you create mixes.

If you click an existing mix in the left side of the window, the right side of the window displays what comprises the mix you selected.

2 Type a unique Mix ID (labeled ID). This ID is used only for ranking the mixes on the left side of the window, so we recommend adding one to the last ID that is listed.

3 Type a unique description for the mix. We recommend text that describes what is being recorded.4 Select a unique configuration to record by clicking buttons on the right side of the window. You

cannot duplicate an existing mix that has a different description and ID.

1 Default Mixes

2 Mix ID

3 Mix Name/Description

You can select an existing mix, edit it, and save it using a different name and ID.

2 31



5 After you finish setting up your mix, click Save Mix.

To manage properties of a recording mix1 In OneView, click Main Menu > Voice Recording > IPVR Record Utility > IP Recording Mix Utility. The

Recording Mix form opens.2 To add a new mix, enter an ID and Description.3 To edit an existing mix, click to select the mix in the Existing Mixes box. The buttons on the right side

of the Recording Mix form shows what is selected for the mix.4 To clear all settings, click Clear Mix. The ID, Description, and all the buttons on the right side of the

window are cleared.5 Edit selections and then click Save Mix to save your changes.

To delete a recording mix

1 In OneView, click Main Menu > Voice Recording > IPVR Record Utility > IP Recording Mix Utility. The Recording Mix form opens.

2 Click an existing mix to select it.3 Click Delete Mix. The selected recording mix is deleted.

1.15.8.2 SCSA Equivalent MixesWhile Enterprise IP Recording lets you create a wide array of custom mixes, we recommend the SCSA equivalent mixes. SCSA equivalent mixes are an efficient way to set up recording.The following seven SCSA equivalent mixes are defined by default and are available for assignment to TRIDs:• Left Handset – records the left handset (ear and mouth) on one channel.• Right Handset – records the right handset (ear and mouth) on one channel.• Mixed Handsets – records both handsets (ear and mouth) on one channel.• Both Handsets – records both handsets (ear and mouth) on two separate channels.• Mix by 2 (sets SPKR_BY_2 parameter) – records four channels per speaker module.• Mix by 4 (sets SPKR_BY_4 parameter) – records two channels per speaker module (every other source

gets recorded on one, the rest on the other).• Mix by 8 (sets SPKR_BY_8 parameter) – records all sources on one channel per speaker module..

Mixes can be created from buttons in the Recording Mix form (see section Figure 1-26: Recording Mix OneView Work Area on page 40). See Table 1-11 for a graphical representation of speaker assignments.

Do not assign more than one SPKR-BY configuration to a trader. For more information, see section 1.15.8.2 SCSA Equivalent Mixes on page 41.

!If you delete a recording mix, the mix is removed from all TRIDs that use it and there is no way to recover the mix or restore it without creating it as a new mix and reassigning it to TRIDs.

Never assign more than one SPKR_BY configuration to a trader. SPKR_BY buttons set channels for all the trader’s speaker modules. For example, if a trader’s IQMX turret has three speaker modules (speaker fours), selecting the SPKR_BY_8 configuration creates three channels (one on each speaker module).



1.15.8.3 Assigning Recording Mixes to TRIDsUse IP Recording MAP: Assign/Delete Trader Mixes to map traders to recording mixes. For changes to take effect, the trader must log off and on to the turret.

To assign a recording mix to a single TRID1 In OneView, click Main Menu > Voice Recording > Recording Map Utility > IP Recording MAP:

Assign/Delete Trader Mixes. The IP Recording MAP: Assign/Delete Trader Mixes form opens. The system displays all known TRIDs.

2 Type a number in the Channel field. The number must be unique for each TRID and not already in use for a given TRID. The number you are assigning sets the order of the appearance of Mixes assigned to Trid.

3 Double-click a mix you want to assign to a TRID. The mix you select displays in the Selected Mix field.

4 Double-click a TRID to which you want to assign a mix. The TRID you select displays in the Copy scheme from Trid field.

5 Set the Audio Codec/Compression Type as needed. (By default, G.729 ab is supported.)6 Click Assign Mix to assign the mix you selected to the TRID you selected.7 Click Close.8 Log off then log on the trader whose recording assignments you changed.

a Click Main Menu > Trader Config > Trader Utilities > Trader Logon > Relogon Traders. A Relogon Traders BHC form opens.

Table 1-11: Speaker Mixing for IP Recording SCSA Equivalent Mixes

Speaker Module

Type

Station Parameter

Channel Numbers Mic Ch

1Ch 2

Ch 3

Ch 4

Ch 5

Ch 6

Ch 7

Ch 8

8 Ch Spkr SPKR_BY_8 1 x x x x x x x x x

SPKR_BY_4 1 x x x x x

2 x x x x x

SPKR_BY_2 1 x x x

2 x x x

3 x x x

4 x x x

4 Ch Spkr SPKR_BY_8 1 x x x x x

SPKR_BY_4 1 x x x

2 x x x

SPKR_BY_2 1 x x

2 x x

3 x x

4 x x

A TRID can be assigned more than one recording mix, but each mix must have a unique Channel number.



b Specify the TRID (or TRID range), or Trader Group.c Click Relogon Traders>>.

To assign a recording mix to a range of TRIDs1 In OneView, click Main Menu > Voice Recording > Recording Map Utility > IP Recording MAP: Copy Trader

Mixes. The IP Recording MAP: Copy Trader Mixes form opens. The system displays all known TRIDs.

2 Select a TRID that has the mixes you want to assign to a range of TRIDs from the Copy Scheme from TRID list.

3 In the First TRID field, type the number of the first TRID to which you want to copy the mixes. The TRID you select first must be a lower number than the TRID you select last.

4 In the Last TRID field, type the number of the last TRID to which you want to copy the mixes.5 Click Copy. The mixes from the TRID in the Copy scheme from Trid field are copied to the First TRID,

Last TRID, and all TRIDs between the first and last.6 Click Close.7 Log off then log on the trader whose recording assignments you changed.



To delete a recording mix from a TRID1 In OneView, click Main Menu > Voice Recording > Recording Map Utility > IP Recording MAP:

Assign/Delete Trader Mixes. The IP Recording MAP: Assign/Delete Trader Mixes form opens. The system displays all known TRIDs.

2 Click the TRID from which you want to delete a mix.3 Click Delete Mix. The mix with the highest Channel number is deleted from the TRID’s recording

profile.4 Log off then log on the trader whose recording assignments you changed.5 Click Close.6 Log off then log on the trader whose recording assignments you changed.



1.15.9 Setting Up NTP for IPVRPaying close attention to time drift and time zone settings is essential for successful IPVR recording. Keep the following rules in mind when working with time and time zones:• The time zone will be set according to your location and will not be adjusted during daylight savings

time.• The time on the DB/APP and Recorders will not change during daylight saving time.• The Work Station will have the correct playback time if it’s set to daylight saving time. The customer

needs to be made aware of this.

You can create a template TRID to use as a basis for assigning the same mixes to a range of TRIDs.



• Time on IPVR servers needs to be re-adjusted after the OneMS Configure System Center procedure has been run (Step 1 to Step 3 in the following procedure). Perform this procedure: To re-adjust or initially configure NTP on IPVR servers (perform on each) on page 45.

Use the following procedures to set up the OneMS and re-adjust IPVR servers.

To configure NTP for IPVR Recording1 From a OneView BHC window, select and run the configure_ntp script. This opens the Configure

Syscen Tools menu directly to where you can choose to Add/Delete/Update server IP addresses or hostnames for System Center time synchronization.

2 To begin, type y in the Enter Response text box and press ENTER.3 To add an NTP time server:

a Type 1 in the Enter Response text box and press ENTER.b Type the IP/Hostname for NTP time server 1, 2, or 3. For example, type 159.63.70.247 for the

Customer Qualified NTP Server. A confirmation prompt displays. c Press ENTER to continue.d Type e in the Enter Response text box and press ENTER. The following prompt displays:

Configuring NTP...Configuring NTP complete - Please REBOOT the System Center!Press <Return> to Continue

e Press ENTER to continue. The Configure Syscen Tools main menu displays.f Type e in the Enter Response text box and press ENTER to exit the script. You can now close the

BHC window and reboot the OneMS. As an IPC Technician, in a Terminal window, type sudo -u root /sbin/reboot and press ENTER.

4 Verifying that NTP is polling. As an IPC technician, open a Terminal window on the OneMS console or in a remote ssh session:a At the prompt, type /usr/sbin/ntpq and press ENTER. b At the ntpq> prompt, type peers and press ENTER. The IP address of the NTP server displays,

see Figure 1-27.c Type exit.

For additional time drift and time zone instructions, see the Alliance MX 16.1 Guide to Troubleshooting Tools booklet.

To view all configuration options of the Configure Syscen Tools menu click Main Menu > Tools > System > Configure System Center instead. For more information, see the Alliance MX 16.1 Using configure_syscen in OneView booklet and help system.

!The reboot must be done during non-trading hours. For instructions, see the Alliance MX 16.1 Troubleshooting Guide.



Figure 1-27: ntpq Sample Output

5 Continue with the following procedure: To re-adjust or initially configure NTP on IPVR servers (perform on each).

To re-adjust or initially configure NTP on IPVR servers (perform on each)1 Stop all NICE services. This step must be completed or recordings could be lost.2 Modify all the host files in the following directory: \windows\system32\driver\etc directory

a IP Address and Name = syscennic2 (of the OneMS 2nd NIC)Example: 159.63.71.33 syscennic2

b Ping the IP Address and the name from a cmd tool window (Open a cmd tool from start„» run-» cmd-» OK)

3 Set the Time zone correctly on each IPVR Server:a Open the Date and Time Properties window and verify.

Example: Eastern Time = GMT -5

Figure 1-28: Date and Time Properties Window, Time Zone Tab

4 Set the Time correctly match the OneMS times within a second.5 Backup W32Time from the following directory path:

a Type regedit from the start„» Run-»b HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time

c Right-select the W32Time and select Export.

The time zone will be set according to your location and will not be adjusted during daylight savings time.



2 Open the server’s DVD drive and insert the PING CD.3 Start or reboot the server. Refer to the appropriate NICE documentation for instructions on powering

the machine on and off.

Figure 1-34: PING Image Software Boot Up Prompts

When the boot process is complete, a PING location save/restore dialog box displays.

If you encounter a problem mounting the device, the device may have be removed improperly the last time. Try connecting it to a laptop and using the eject icon to remove the device; begin the image process again.

You will know that the machine is successfully booting up from the DVD drive and the PING software will load when you see the Loading_kernal... prompt display (see Figure 1-34), If it does not, press F11 when prompted and select the DVD drive.


1.19 Using PING to Backup/Restore an NPR3 Server Image 53

Figure 1-35: Image Save Location

4 Use the down arrow to select the Local disk/partition. This is the location for saving disk images. PING also supports backing up to a network share.Press ENTER to display a list of partitions to backup. Figure 1-37 and Figure 1-36 display examples of a DB/APP and Recorder server.

Figure 1-36: Example of a DB/APP Server with Several Partitions Selected to Backup



Figure 1-37: Example of a Recorder Server with Several Partitions Selected to Back Up

5 Select the NPR3 partitions to back up using the arrow and space bar keys. Refer to Table 1-12 for a list of Linux to Windows disk equivalencies.

a Use the down arrow to select sda1 and press the space bar. b Repeat to select sda2, sda5 (and sda6 for a DB/APP). Selected partitions are indicated by an

asterisk (*) between the brackets. Do not select the external hard disk.c When you are through selecting partitions, press ENTER.d In the next window that displays (Figure 1-38), press the space bar to select the external hard

drive as the target location to store the image files. For example, EXT_USB_DRIVE.

! You must back up the Extended Logical Disk.

Table 1-12: Linux Disk and Windows Equivalency

Linux Windows Equivalent

sda1 C:\

sda2 Extended Logical Disk

sda5 D:\

sda61

1. sda6 (E:\) displays on the DB/APP server list of drives

E:\

sdb1 Extended Logical Disk

sdb5 F:\

sdc# USB External Drive



Figure 1-51: IP Recording Map Report–Option 1, Display Status of All Cards (Part 2 of 3)

*** Quantity of Turrets that be recorded: 0

*** Quantity of Turrets which aren't logged on: 0

*** Quantity of Turrets which aren't plugged in: 16

*** Quantity of Turrets with no mix value in the database: 0

*** Quantity of Turrets that should be recorded but aren't: 0

=============================================================

Y (1.3.10).1 17432 1302 00000 159.063.074.101 05501 L,1-16

N (1.3.10).2 17437 1206 No mix value in database for the station!

N (1.3.10).3 17442 Not Plugged in!

N (1.3.10).4 17447 Not Plugged in!

N (1.3.10).5 17452 Not Plugged in!

N (1.3.10).6 17457 Not Plugged in!

Y (1.3.10).7 17462 1309 00000 159.063.074.101 05501 L,1-12

Y (1.3.10).8 17467 1107 00000 159.063.074.101 05501 L,

Y (1.3.10).9 17472 1308 00000 159.063.074.101 05501 L,1-12

N (1.3.10).10 17477 Not Logged on!

N (1.3.10).11 17482 Not Logged on!

Y (1.3.10).12 17487 1303 00000 159.063.074.101 05501 L,1-12

-------------------------------------------------------------

*** Quantity of Turrets that be recorded: 5

*** Quantity of Turrets which aren't logged on: 2

*** Quantity of Turrets which aren't plugged in: 4

*** Quantity of Turrets with no mix value in the database: 1

*** Quantity of Turrets that should be recorded but aren't: 0

=============================================================

N (1.4.9).1 18126 1609 Should be recording but it's not!

N (1.4.9).2 18131 1202 No mix value in database for the station!

Y (1.4.9).3 18136 1310 00000 159.063.074.101 05501 L,R,1-8

Y (1.4.9).4 18141 1304 00000 159.063.074.101 05501 L,R,1-4

Y (1.4.9).5 18146 1808 00000 159.063.074.101 05501 L,R,1-8

Y (1.4.9).6 18151 1312 00000 159.063.074.101 05501 R,1-4

N (1.4.9).7 18156 Not Logged on!

Y (1.4.9).8 18161 1603 00000 159.063.074.101 05501 L,1-4


2: E1 Hardware Installation 75

2 E1 Hardware Installation

This chapter discusses installing E1 recording hardware components.

2.1 Site PreparationBefore installing E1 recording, make sure the customer site is set up. Consider the following sections to be sure a site is set up correctly:• 2.1.1 Telephony Considerations on page 75• 2.1.2 Materials Inspection on page 75• 2.1.3 Logger and Server on page 75• 2.1.4 Power on page 76• 2.1.5 Handle Static-Sensitive Equipment on page 76

2.1.1 Telephony ConsiderationsIf telephone outputs are to be used in the site (i.e., using RAP/DigiRAP unit), verify that the required number of telephone lines or extensions are available and accessible to the recorder outputs.

2.1.2 Materials InspectionVerify that all required third-party components and accessories are present, in the correct quantity, and without signs of damage, before starting the installation process.

2.1.3 Logger and ServerThe E1 logger (recorder) and server are not supplied by IPC. See the documentation provided with your hardware for environmental considerations, installation, and operating instructions.At a minimum, consider the following environmental conditions before installing your E1 loggers:• Ventilation and access – There must be clearance in front, behind, and between each recorder to

permit ventilation and access for maintenance.• General environment – Make sure the operating temperature and humidity requirements of your

recording hardware are met.

To keep the ambient room temperature low• Avoid positioning the recorder/server near heaters or heating system outputs.• Avoid positioning the recorder/server in direct sunlight.

!Since a logger, recorder, and server generate heat, keep the ambient room temperature lower than the maximum temperature listed for a device.


76 2: E1 Hardware Installation76 2: E1 Hardware Installation

• Do not position the recorder/server near doors or walkways that are used frequently.• Position the recorder/server in a room with limited access.• Keep the area clean. Dirt, such as dust particles and smoke, can cause a recorder or server to

malfunction.• Do not position the recorder or server on or near the floor or near any surfaces that tend to collect

dust.• Do not position the recorder or server near printers or paper products that create dust.• Do not position the recorder or server in a smoking area.• Plan regular cleaning for the room where the recorder or server is located.• If the general environment is dirty, consider installing an air cleaning system in the room where

the recorder or server is located.

2.1.4 PowerEnsure that the power requirements are met for your recording installation. See your hardware’s documentation for more information.

2.1.4.1 Emergency Backup Power SupplyWe recommend you use an uninterruptable power supply (UPS) for each recorder or server.

2.1.5 Handle Static-Sensitive EquipmentElectrostatic discharge (ESD) can cause serious problems including damaging hardware unless proper ESD prevention procedures are followed during transport, installation, and maintenance of both trading floor and backroom equipment. ESD can cause the following types of problems:• Immediate problems upon installation• Gradual component degradation starting with installation• Complete and sudden failures after installation• Intermittent failures causing module swapping and affecting all backroom hardware and station

equipment

To avoid ESD-related problems1 Do not transport components unless they are in ESD preventive packaging.2 Do not handle and/or remove components from ESD preventive packaging unless you are wearing a

properly grounded wrist strap. The wrist strap must be grounded to a properly grounded cabinet.3 Remove all jewelry before handling any equipment.

To prevent ESD when installing any equipment1 Put on a properly grounded ESD wrist strap.2 Remove the item from its ESD preventative packaging.3 Install the piece of equipment.

To prevent ESD when removing any equipment1 Put on a properly grounded ESD wrist strap.2 Remove the equipment and immediately place it in ESD preventative packaging.

Follow ESD prevention procedures when assembling and handling recording hardware.


2.2 E1 Recording Support 77

2.2 E1 Recording SupportSupport for E1 recording depends on the version of Alliance MX you use and the station cards you install.• Alliance MX 14.1 and later – TIC2 station card, TIC, and MPIC support for E1 recording.• Alliance MX 12 and earlier – TIC and MPIC support for E1 recording.Additionally, the DXIX card supports E1 recording for those line cards supported by an Alliance MX version. For more information about DXIX cards, see 3.6.5.1 Setting up a DXIX Groomer Card on page 90 and the Alliance MX Switching Center Cards Handbook.

2.3 Connect Alliance MX Recorder Data Lines to E1 RecorderTo record audio, you must connect the audio sources to a logger. Connect the E1 ports on the TIC2, TIC, or MPIC cards directly to the E1 ports on the E1 logger.Alternatively, you can connect partially-used E1 ports to a DXIX groomer card and connect that card to E1 ports on the loggers.

IPC does not provide servers or loggers (recorders) for E1 recording.

For TIC1 cards, the second E1 port on the card (the second E1 port from the top) cannot be used; you can only record output using ports 1, 3, and 4. For TIC2 cards, the third E1 port on the card (the third E1 port from the top) cannot be used; you can only record output using ports 1, 2, and 4 after installing Alliance MX14.03.07, patch 31 (downloadable from the Support site; patch applied in Alliance MX 15.02 Patch 2 release).MPIC cards feature two E1 ports and both are functional.


78 2: E1 Hardware Installation78 2: E1 Hardware Installation

Figure 2-1: Typical E1 Cabling

CD

VALID

PWR

ON

100 BASE -T

E1–4

100 Base -F

TIC

CD

VALID

PWR

ON

100 BASE -T

E1–4

100 Base -F

TIC

CD

VALID

PWR

ON

100 BASE -T

E1–4

100 Base -F

TIC

S

C

S

A

CD

VALID

PWR

ON

100 BASE -T

E1–4

100 Base -F

TIC

S

C

S

A

S

C

S

A

S

C

S

A

CD

VALID

PWR

ON

100 BASE -T

E1–4

100 Base -F

TIC

S

C

S

A

CD

VALID

PWR

ON

100 BASE -T

E1–4

100 Base -F

TIC

S

C

S

A

CARD

VALID

POWER

ON

PORT 5

PORT 1

MPIC

ADIF3N+1

ANALOG

OUTPUT

MS

ED

PC

OP

LE

GE

UPU0

DSP1

DSP2

DSP3

DSP4

W.D.

PWR

DSP5

FW

DSP6

ADIF3N+1

ANALOG

OUTPUT

MS

ED

PC

OP

LE

GE

UPU0

DSP1

DSP2

DSP3

DSP4

W.D.

PWR

DSP5

FW

DSP6

E1s Groomed

for Efficiency

Partially Used

E1s Connect to

DXIX

Fully Used

E1s Connect to

Loggers Directly

Loggers Receive E1

Channels from TIC2/TIC/MPIC

and from DXIX

TU 1

Re

co

rde

rs/L

og

ge

rs

TU 2

TU 3 Optional

DXIX


table of contents - bebpublishing€¦ · tic2 cards: • enterprise ip recording tic2 cards...

Documents