CTI Core is the software component that provides the PBX
An acronym for Private Branch Exchange. A telephone switching device owned by a private company that serves a particular business or office. / ACDAcronym for Automatic Call Distributor - A device used to manage and distribute incoming calls to a specific group of terminals. integration and makes call recording decisions based on customer-defined recording schedules. Some integrations require a specific CTI module that is added to the CTI CoreThe software component that provides the PBX/ACD integration and makes call recording decisions based on customer-defined recording schedules. to configure integration settings.
Uptivity supports multiple CTI Cores, both on an individual recording server and within a multi-server Uptivity system. The list of cores that have been set up is visible on the CTI Cores List. Different cores may be used for different integrations, to provide for failover recording as part of continuity and recovery planning, or for implementations with different geographic sites. CTI Core topology is created during the discovery process by the Uptivity Sales Engineer.
If CTI Core settings must be changed, only open one CTI Core at a time for editing. If you open multiple cores in separate browser tabs, you may inadvertently overwrite settings for one core when saving another.
CTI Core settings in Uptivity take effect when the core is started either manually or when the host machine starts. In most cases, CTI Core must be restarted if:
- A voice boardSoftware components that control how the system acquires the audio it records. is changed, added, or removed
- A core setting is changed (except for adding, removing, or changing schedules)
- A CTI module setting is changed or a module is added or removed
Deleting cores, components, modules, or monitors can cause the Uptivity system to stop recording. Do not delete any of these elements without permission and assistance.
CTI Monitors
A few integrations rely on CTI monitors to know which devices should be recorded. Depending on the integration, CTI monitors may be position IDs, PBX extensions, ACD DNs, ACD groups, or trunks. They are monitored by the CTI module so that the CTI Core knows when to record. In those integrations which require monitors, every device to be recorded must be included in CTI monitoring or recording will not take place.
CTI monitors must be reconfigured when channels are changed, but monitor changes do not require a restart. Monitors can be added or deleted, but not edited. CTI Core uses the Monitor Reload Frequency setting to know how often to check for new monitors.
If you are not sure whether your integration uses CTI monitors, or if you need more information, refer to the
Buddy Cores for High Availability and Redundancy
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 AvayaOne of the many integrations available with Uptivity. TSAPIAn acronym for Telephone Services Application Programming Interface. Alcatel TSAPI is the software that provides the call control events and metadata to Uptivity. / DMCCAn 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 in system is determined by Uptivity Sales Engineering during the discovery process.
Not all integrations are suitable for Buddy Core design. If you are not currently using this system architecture and would like to explore the possibility, contact Uptivity Sales Engineering.
