Introduction

The installation of CallRex with OCS 2007 R2 is different from a typical CallRex deployment with other PBX types. In a typical deployment of CallRex, all other services including CallControl service resides at the user level and communicate with a single status service - the only service communicating with the database. The architecture of CallRex is modified for integration of CallRex with OCS 2007 R2.

What's Different?

The difference in the architecture of the CallRex implementation with OCS 2007 R2 is the role of the CallControl service. Similar to status service, the CallRex implementation with OCS 2007 server uses only one CallControl service to communicate with the new plug-in components installed additionally:

RTPDataCollectorServiceInstaller.ms - installs CallRex RTP Data Collector Service at the recorded endpoints.
TelRexNetServiceSetup.msi - installs TelRexNetService and TelRexNetService.am on the OCS Front End Server.

If there are multiple CallControl services installed on the network, only one CallControl service should be functional.

Prerequisites

For CallRex deployment with OCS 2007 R2, the following prerequisites must be fulfilled:

The computer running OCS 2007 R2 server must have .Net version 2.0 installed.
Each end-user computer must have Office Communicator R2 installed that communicates with OCS 2007 R2.

Supported Operating Systems

Component	XP	Vista	Windows 7	WinServer2003	WinServer2008
TelrexNetService				v	v
CallRex Server	v			v
RTP Data Collector	v	v	v	v

Supported Endpoints

CallRex Call Recording supports recording endpoints that feature the following:

Microsoft Office Communicator 2007 Softphone
Microsoft Office Communicator 2007 R2 Softphone
Microsoft Office Communicator 2007 Phone Edition
Microsoft Office Communicator 2007 R2 Phone Edition

The following hardware has been tested as supported on CallRex 3.9.3 -

LG Nortel IP 8540

Limitations

The following audio codecs are supported for call recording and monitoring:

SIREN
PCMU
PCMA
G729