Stopping and Starting Chronicall Services

Before Starting

If you are utilizing Chronicall Multimedia Features (e.g., Skills-Based Routing or Queue Callback), please refer to this article instead.

If you are not utilizing the Chronicall Multimedia Features, then proceed.

Windows

If you need to start, stop, or restart Chronicall do the following:

• Open the Start menu and type services.msc into the search bar. A listing for Services should appear at the top of the list, click on it.
• Search through the list to find the services that begin with "Chronicall".
  The service names vary slightly depending on your version of Chronicall:
  Version 3.9.4 and older: Chronicall, Chronicall Database, Chronicall Recording Library
  Version 3.9.5 through 3.12.6: ChronicallServer, Chronicall Database (Postgres), Chronicall Database (OrientDB), ChronicallMultimedia, and ChronicallRecordingLibrary.
  For version 4.0.0 and above, the Postgres and OrientDB databases have been consolidated into BlueDB, which is part of the ChronicallServer service.
• Right-click on the related service and choose Start, Stop, or Restart to change its status.

Linux

If you need to start, stop, or restart Chronicall on a Linux device, use the following commands (each service may require root permissions):

In rare instances, you may need to go into the following directory: var/lib/Xima\ Software\Chronicall\tomcat\bin directory to manually run the startup.sh, shutdown.sh, or restart.sh.

The other bin directories will have these for other services as well. Manually restarting the Chronicall service here would look like this for example.

./restart.sh

Chronicall versions 3.9.4 and older:

1. Chronicall
   service chronicall start
   service chronicall stop
   service chronicall restart

2. Chronicall Database
   service chronicall_database start
   service chronicall_database stop
   service chronicall_database restart

3. Chronicall Recording Library
   service recording_library start
   service recording_library stop
   service recording_library restart

4. Orient Database
   service chronicall_cdr_database start
   service chronicall_cdr_database stop
   service chronicall_cdr_database restart

5. Multimedia
   service ChronicallMultimedia start
   service ChronicallMultimedia stop
   service ChronicallMultimedia restart

Versions 3.9.5 through 3.12.6:

service ChronicallServer start
service ChronicallDatabaseOrientDB start
service ChronicallDatabasePostgres start
service ChronicallRecordingLibrary start
service ChronicallMultimedia start

For versions 4.0.0 and higher builds, the Postgres and OrientDB databases have been consolidated into BlueDB, which is part of the ChronicallServer service:

service ChronicallServer start
service ChronicallRecordingLibrary start
service ChronicallMultimedia start

It is not necessary to restart the Chronicall Database or Chronicall Recording Library services unless you are moving Chronicall to a new server. For more information, see Moving Chronicall to a New Server.

While the Chronicall service is stopped, it will not record calls. It is recommended to perform Java updates and other major server changes during low call volume hours and be sure to restart each service when you are finished.