Knowledge is Power

CallCabinet Knowledge Base Articles
  1. Home
  2. Knowledge Base
  3. CallCabinet Portal
  4. Setting up CallCabinet call recording for Asterisk and FreePBX
  1. Home
  2. Knowledge Base
  3. Asterisk
  4. Setting up CallCabinet call recording for Asterisk and FreePBX
  1. Home
  2. Knowledge Base
  3. CCModule
  4. Setting up CallCabinet call recording for Asterisk and FreePBX
  1. Home
  2. Knowledge Base
  3. FreePBX
  4. Setting up CallCabinet call recording for Asterisk and FreePBX
  1. Home
  2. Knowledge Base
  3. Call Recording
  4. Setting up CallCabinet call recording for Asterisk and FreePBX

Setting up CallCabinet call recording for Asterisk and FreePBX

This document contains information related to the installation and execution of the CallCabinet module function, referred to as CCModule. This guide and the referenced files are targeted for installation on a Linux Debian 7 / CentOS platform.

Prerequisites:
    1. Confirm Python version (Version 2.6 or higher)

python -v
or
python --version

Files/Directories required:
  1. CCModule: executable binary that provides the main process and worker thread to encrypt and transfer files contained in the CallCabinet file repository. (please contact helpdesk of your CallCabinet representative for the file).
  2. ccinitd: init.d shell script needed to start/stop the CallCabinet daemon.
  3. /home/callcabinet: directory for scripts, executables, configuration files, log files and files related to the execution of the CCModule.
  4. CCconfig.txt configuration file containing the configuration data for the CCModule. This file will be automatically created on first run of the CCModule.
Installation Steps (Root privileges are required):
  1. Register to create an CallCabinet account by visiting https://atmos.callcabinet.com/Account/Register
  2. After the call has been completed, you need to use Asterisk post call scripting (Click here for instructions on Asterisk or Click here for FreePBX) to rename the filename to something along the lines of “954389332_2014-06-16T12:54:46_3001_24_INCOMING.WAV” (the file should ideally be recorded as a GSM encoded WAV file)
  3. Make sure you have the latest CCModule Daemon (please contact helpdesk of your CallCabinet representative for the file).
  4. Create the repository directory “/home/callcabinet” for use by the ccmodule by creating a standard user named “callcabinet”.
  5. Log into user “callcabinet”.
  6. Install Sox library: NOTE! Only required if compression, as described in Step 2, is not set, this is NOT recommended.

    sudo yum install sox (for CentOS)
    sudo apt-get install sox (for Debian / Ubuntu)

  7. Copy the CCModule to the CallCabinet directory:

    mv /usr/local/pbx/cc/64bit20160622 /home/callcabinet/

  8. Set permissions:

    chmod +x ./64bit20160622

  9. Run the module:

    nohup ./64bit20160622 >a.out&

  10. Note: On the first run the command will terminate because the newly created CCconfig.txt does not have a CustomerID or SiteID.
  11. Confirm that the CCconfig.txt file has been created, if not please check the a.out file for any possible errors.
  12. Edit CCconfig.txt and insert the relevant CustomerID and SiteID into the first 2 lines (These IDs are obtained during the CallCabinet registration process (see https://atmos.callcabinet.com/Account/Register). (For Multi-tenant deployments please see notes below).

    vi CCconfig.txt

  13. Edit CCconfig.txt and change the line “Repository:<>” to the location containing the call recordings.

    Repository:</home/callcabinet/recordings/>

  14. In the CCconfig.txt, set the repository to “/home/callcabinet/recordings/” and enable tree support “Treesupport:<yes>”
  15. Run the module. NOTE this command will ensure that the module persists, to ensure it restarts if the server reboots please add it to the start-up config.

    nohup ./64bit20160622 >a.out&

Notes: Make sure the files are in /home/callcabinet and the recordings are in /home/callcabinet/recordings (or other location specified using the Repository setting in CCconfig.
Multi-Tenant Call Recording
For multi-tenant deployments please contact our support team for more information on your specific environment.
For help and support please visit our support helpdesk by clicking here.

Troubleshooting
If the CCModule will not start, please check the contents of a.out or nohup.out and ccmodule.log for possible errors.

The owner of this website has made a commitment to accessibility and inclusion, please report any problems that you encounter using the contact form on this website. This site uses the WP ADA Compliance Check plugin to enhance accessibility.