The "Record" module of PhoneUP bundle consists of several components and provides various deployment options. The PhoneUP recording solution may be deployed on a single server or with multiple instances across the enterprise network. The right deployment option depends on enterprise network topology, type of devices to be recorded and expected software load.
The recording solution consists of:
- PhoneUP Core – main PhoneUP component (interacts with CUCM, provides user interfaces, stores records metadata);
- PhoneUP SPANless Recorder – recording component to record calls of Cisco IP Phones with Built-In Bridge;
- PhoneUP SPAN Recorder – recording component to record SIP calls with SPAN approach;
- PhoneUP Trancoder – converts recorded calls to WAV/MP3/OGG;
- PhoneUP FileManager – provides interfaces to access recorded calls;
- PhoneUP MediaSense Gateway – gateway to Cisco MediaSense.
In basic scenario all components may be deployed on a single server. But in the case of high load it is recommended to install Recorder on a separate server.
In case the enterprise network is distributed geographically it is recommended to install Recorders on each company site. In that case all calls of remote location will be recorded by local Recorder. On the example illustrated below phone calls of the main company site are recorded with BiB-approach, but calls of the remote office are recorded by local SPAN-Recorder.
Each Recorder is managed by PhoneUP Core and doesn't provide any user interface. The Recorder component works independently and doesn't require a permanent connection to PhoneUP Core. The user interface provided by PhoneUP Core contains metadata about all records made by any Recorder.
High load deployment
In high load deployments it is recommended to install components on separate servers. In the example below the Transcoder is installed separately and works with two Recorders. In this case all calls are recorded and stored in "raw" format, but may be transcoded later depending on the Transcoder load.