Buddy Cores

Buddy Cores offer a method of high availability and redundancy where only one CTI Core records at a given time, as opposed to a system with a continuously-running redundant recorder. Buddy Core configuration can save space and resources. For instance, integrations using Avaya TSAPIClosed An acronym for Telephone Services Application Programming Interface. TSAPI is the software that provides the call control events and metadata to Uptivity. / DMCCClosed An API from Avaya that provides the ability to record calls directly from Avaya Communication Manager. DMCC is an acronym for Device Media Call Control. require only one set of DMCC stations since the Buddy Cores share the stations.

Buddy Cores should always run on different machines (including VM clusters) to avoid having a single point of failure. There are two ways to configure Buddy Cores: Primary/Secondary and Active/Inactive. The method used is determined by Uptivity Sales Engineering during the discovery process. This and other settings specific for Buddy Cores are managed in the cticore.ini file, in addition to the regular NICE Uptivity Web Portal setup.

If you are not currently using this system architecture and would like to explore the possibility, contact Uptivity Sales Engineering.