In principle you can use any TC system that you usually use for ProCall, even together with ProCall Analytics.
However for a correct evaluation of call groups, the TC system must be connected via ECSTA-driver. This is due to technical limitation in the tracking of complex call forwarding scenarios that may arise when connecting via the most common TAPI drivers.
ECSTA TAPI drivers excluded from this rule include:
For all other system drivers, please read the list of the telephone systems tested by us. In this article, you can also find information about how you can check whether your system correctly indicates the group calls without the ECSTA connection.
Note: These parameters refer to a system on which no other applications are installed. If other applications are running on your computer, the requirement for the entire system increases accordingly.
A server operating system is required for the productive use of ProCall Analytics. The following server operating systems are supported:
On workstation operating systems, ProCall Analytics can only be installed in test mode (predefined example data, no database or UCServer connection). As Microsoft® has severely restricted access from other computers to a workstation, due to technical reasons it is no longer possible to access ProCall Analytics from another computer. Access is only possible via http://localhost from the computer itself on which ProCall Analytics was installed. If you want to test access from another computer, please select a server operating system. The following workstation operating systems are supported:
To be able to use ProCall Analytics productively, you will require ProCall Analytics licenses. The number of required licenses must at least correspond to the number of ProCall workplace licenses. If you have not purchased a license, ProCall Analytics operates in test mode and you will get predefined example data displayed.
The following Knowledge Base article describes the configuration of estos UCServer and the connection of the database:
Important: Please make sure that the TCP protocol has been activated in the SQL Configuration Manager. Also make sure that the SQL Server® Browser Service is running. Otherwise ProCall Analytics will not find its database.