Best Practices After Server Reboot(s)

The services for Chronicall are designed to startup automatically after a server is rebooted. However, here are some steps you can take to ensure continued call logging, recording, and skills based routing.


Checking system status of Chronicall:

When logged into Chronicall's client and on the homepage, you will see a status icon (bell) in the top right corner.

If the icon includes a green checkmark , all services are running as expected.

However if the status icon has a Exclamation Point  there is an issue with one of the services. Simply click on the status icon to see a breakdown:


Restarting Services (Windows)

If a service is not running or not connected, the first recommended step is to restart that service on the server which the service resides. 

Open Services on the server. This can be found by searching for "Services" in the Windows search bar OR opening Run and enter services.msc

If on the correct server, you will find Chronicall services below:

Simply select restart then check then relaunch Chronicall and check the status.



Chronicall: This is the base service of all Chronicall, it is needed for call logging and realtime monitoring and required for all services including recording and skills based routing to function properly.

Chronicall Recording Library: Processes recordings and inserts them into the database. NOTE: this service does not always reside on the same server as the Chronicall service. It can be found on the server in which a VRTX box is connected OR the server where VMPro is populating recordings.

Chronicall Multimedia: This service will always be on a seperate server from the Chronicall services. This service handles call routing and queue callbacks for skill groups as well as web chat.


Best Practice for Restarts

It is not required but recommended you follow the sequence below when restarting all services:

Restart Chronicall Service ► then restart Chronicall Recording Library service ► then restart Chronicall Multimedia service


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk