At some point, your software will need to be updated to include the latest feature packs and/or bug patches. Depending on the OS your server uses, you'll need to execute the updates accordingly. For Windows Instructions, proceed below. For Linux (CentOS & Debian) click here to skip.
NOTE: For the duration of the update, logging, call recording, and (if applicable) multimedia skills-based routing will be inoperable
NOTE: Version Skipping
Do not skip major versions when updating!
- If you are on a 3.6 version, make sure you are updated to 3.6.56 before updating to 3.8.7
- If you are on a 3.8, make sure you are updated to 3.8.7 before updating to 3.12
- If you are on a 3.10 or 3.12 build, make sure you are updated to 3.12(5by) before updating to 4.x
- You need to be on the 3.8.7 branch before updating to 3.12.5, and 3.12(5by) before updating to 4.x
NOTE: Run a backup of Chronicall/ACR prior to performing any update!
- For more information on how to perform an unscheduled backup, please see this article.
Windows
- Navigate to our downloads page where you will be asked for your Xima Serial Key This can be found by opening the JavaUI and clicking on Help -> About Chronicall or Help -> About Avaya Call Reporting.
- Depending on your PBX type, you'll see it mentioned in the top Margin. If you do not, please reach out to Xima Support to confirm licensing on your Xima Serial Key:
- Upon selecting "Update", a download will initiate the relevant .exe file you selected
- Once complete, place this file on the Chronicall or ACR server within your network
- Once you are ready to update, please turn off all Chronicall/ACR services
- Stopping and starting services for Multimedia customers
- Stopping and starting services for Non-multimedia customers
- Run the file as an Administrator
- NOTE: For the duration of the update, logging, call recording, and (if applicable) multimedia skills-based routing will be inoperable. You will need to agree to EULA within the process (and there will be an additional screen for those updating from 3.12.5 to 4.0+) to complete the update.
- Once the update is complete, you will receive a dialog box indicating your update was successful
- NOTE: If the update fails for any reason, please reach out to Xima Support for further assistance.
- After receiving the completion message, please restart your peripheral services (E.g. Realtime Node, Recording Library, Multimedia, Dashboard, etc), if applicable, in order to bootstrap the updated files from the Chronicall Server
Linux (CentOS & Debian)
- Navigating to our downloads page where you will be asked for your Xima Serial Key
- This can be found by opening the JavaUI and clicking on Help -> About Chronicall or Help -> About Avaya Call Reporting
- This can be found by opening the JavaUI and clicking on Help -> About Chronicall or Help -> About Avaya Call Reporting
- Depending on your PBX type, you'll see it mentioned in the top Margin. If you do not, please reach out to Xima Support to confirm licensing on your Xima Serial Key:
- Upon selecting "Update", a download will initiate of the relevant tar.gz file you selected
- Once complete, place this file on the Chronicall or ACR server within your network via your preferred SSH client
- NOTE: If you're unsure of what you need (either Debian or CentOS), type the command below in the command line of your SSH client. This will reveal the OS your Linux machine is operating with
-
cat /etc/*-release
-
- NOTE: If you're unsure of what you need (either Debian or CentOS), type the command below in the command line of your SSH client. This will reveal the OS your Linux machine is operating with
- This file will need to be unzipped from the tar.gz format. The command we use to do so is as follows:
-
tar -zxf <downloaded_file>.tar.gz
-
- After the folder and contents within have been extracted, navigate into that unzipped directory
- Within the folder, you should see an update.sh file which will need to be run to complete the update
- Once you are ready to update, please turn off all Chronicall/ACR services
- Stopping and starting services for Multimedia customers
- Stopping and starting services for Non-multimedia customers
- Now that services are stopped, use the command below to run the update:
-
./update.sh
-
- Once executed, the command line will load all assets/resources being used in the update
- After completion, you will need to restart the peripheral services (E.g. Realtime Node, Recording Library, Multimedia, Dashboard, etc), if applicable, in order to bootstrap the updated files from the Chronicall Server