Prerequisites

You must have a main site CallRex server already setup and operational. You also need to have network connectivity (e.g. ISDN, VPN, or equivalent) that allows the main CallRex server to communicate with the remote site Data Collector over TCP/IP.

Before installing the CallRex 4.x services you must install the following on all servers (including the one that will host the CallRex Data Service and any hosting the CallRex Call Recording Service:

Windows Imaging Component (WIC). This is required by the .NET Framework 4.

Download it from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8e011506-6307-445b-b950-215def45ddd&&displaying=en.
The full version of the .NET Framework 4 (not the client-only version).

Download from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9cfb2d51-5ff4-4491-b0e5-b386f32c0992&displaying.en.
Microsoft Message Queuing (MSMQ)

To install MSMQ under Windows XP or 2003:
1. In the Control Panel, open Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. Select Application Server, and then click Details.
4. Select the Message Queuing check-box.
To install MSMQ under newer versions of Windows:
1. In the Control Panel, open Programs.
2. Click Turn Windows features on or off.
3. Expand the box for Microsoft Message Queue (MSMQ) Server.
4. Select the Microsoft Message Queue (MSMQ) Server Core check-box.

Before installing on the server hosting the CallRex Call Recording Service you must ensure that port mirroring has been configured properly on the network switch and that the required network packets are being delivered to the CallRex Server. You can check this by installing and running Wireshark (http://www.wireshark.org) and confirming the presence of the RTP packets. You must also ensure that any required Computer Telephony Interface (CTI) components have been installed and configured before installing the CallRex Call Recording Service. CTI components are PBX-specific: for ShoreTel integrations, ShoreTel TAPI is required. You can confirm that TAPI is working by running Microsoft Dialer (available in all Windows installations) and confirming that the extensions to be recorded show up in the device list. For Mitel integrations, the Mitel MiTAI interface is required. You can confirm that MiTAI is working by running the MiTAI Extension Test Tool. For all other PBX integrations, CTI events are captured using the port-mirror on the network switch.