Chronicall

I am John Doe

And I'm a Photographer

Page Content..

Stopping and Starting Chronicall Services

While updating Java on the Chronicall server or moving Chronicall to a new server, you will be required to stop and restart the Chronicall services. Restarting Chronicall can be done for multiple reasons. For example, when adding new licenses, or when trying to solve many simple errors. (I.e., Realtime being out of sync.)

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 named Chronicall, Chronicall Database, or Chronicall Recording Library for 3.9.4 and earlier for the base services in the open window

Note: For 3.9.5 and above, the service names have changed to: ChronicallServer, Chronicall Database (Postgres), Chronicall Database (OrientDB), ChronicallContactCenter, and ChronicallRecordingLibrary.

  • 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

  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. Recording Library
    service ChronicallRecordingLibrary start
    service ChronicallRecordingLibrary stop
    service ChronicallRecordingLibrary restart

  6. Multimedia
    service ChronicallContactCenter start
    service ChronicallContactCenter stop
    service ChronicallContactCenter restart

For 3.9.5 and higher builds, the service names changed.

service ChronicallServer start
service ChronicallDatabaseOrientDB start
service ChronicallDatabasePostgres start
service ChronicallRecordingLibrary 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 performing Java updates and changing servers during low call volume hours and be sure to restart each service when you are finished.

Updated about a year ago

Stopping and Starting Chronicall Services


While updating Java on the Chronicall server or moving Chronicall to a new server, you will be required to stop and restart the Chronicall services. Restarting Chronicall can be done for multiple reasons. For example, when adding new licenses, or when trying to solve many simple errors. (I.e., Realtime being out of sync.)

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.