This article only works if you have:
SugarCRM & Asterisk on the same LAN, and in order to install you must be a linux system admin.

How to set-up call recording:

Note: this is a PRO feature.

1. You must install a SugarCRM Module (contact us to get this).

2. Create the following field names in studio:
– asterisk_caller_id_c
– asterisk_call_id_c
– asterisk_inbound_ext_c
– asterisk_user_ext_c

3. Setup in asterisk configuration to automatically record your extensions if you have not already done so.

4. In SugarCRM, callinize admin config, enable recordings and set the path to a folder which contains the call recordings. You can ignore all the other settings there. They’re left over from a previous project. If your recordings path has subdirectories such as: /var/spool/asterisk/monitor/2013/11/03/ you would enter: /var/spool/asterisk/monitor/201*/*/*
(NOTE: If your sugarcrm instance is on a different server from your SugarCRM server, you will need to somehow make the files accessible to the SugarCRM instance. Setup rsync or some other syncing method to automatically copy the recordings to a folder on the SugarCRM instance. If they are on the same network, you can do this with a network share).

5. Make sure the user your webserver is running as has read permissions to that folder.

6. Open Studio and add the asterisk_recordings field to your Detail View layouts. Once you’ve done that, when you click on a call you see icons for playing and downloading the recording. If there isn’t a call recording available, it will display “No Recording”.

Troubleshooting:

If you aren’t seeing any call recordings, then add the asterisk id field. That ID is what is searched for as part of the filename in the recording path folder. If your recording filenames for some reason do not follow the default conventions of asterisk, contact support to discuss solutions.

Comments are closed.

Do you need some help? Submit a Request