QMS Media Processing Service

The Data Service, SQL Database, Call Recording Service can be installed on the same server for small or medium sized deployments of up to 100 simultaneous recordings.

The Call Recording and Media Processing services can be co-located on the same server. This configuration would be similar to earlier versions of QMS where the Call Recording Service handled the media conversion work.

The Media Processing service can be deployed on its own dedicated server to handle media processing requests from one or more Call Recording services.

Several Media Processing servers can be configured to function as a Media Processing Pool. The Media Processing Pool can then be assigned to one or more Call Recording services. When a Call Recording Service as a Media Processing Pool assigned to it, the Call Recording Service will load balance its media processing needs across all Media Processing services in the pool.

It is recommended that operating system files and recordings reside on different volumes or physical disks. Media Processing can be a very disk-intensive process so higher speed storage is recommended.

System volume: The primary disk volume of the server running the Media Processing service must have enough storage space to store application logs. It is recommended that 30 GB of free space, in addition to the storage required for the operating system and applications, is allocated to the system volume for the purpose of log storage.

Recording volume: If recordings are being stored on the media processing server, the disk volume that stores call recordings will need enough storage space to hold all recordings for the entire duration in which they are needed. If QMS is configured to automatically move recordings to a secondary storage location, it is still recommended to have at least enough space for one week of recordings on the server. One gigabyte of storage will hold approximately 210 hours of mono voice recordings or 105 hours of stereo recordings when using the OPUS audio codec. One gigabyte of storage will hold approximately 72 hours of mono voice recordings or 36 hours of stereo recordings when using the MP3 audio codec.

For example, if OPUS (mono) is selected as the codec type and there are 100 users making phone calls and each user talks on the phone for five hours per day and recordings must be stored for one year (260 work days) then the calculation is:

100 x 5 x 260 = 130,000 hours of recording

130,000 / 210 = 619.05 GB of storage required

The Media Processing Service requires the following ports to be open for inbound connections: