Skip to main content

Trying to get Astrerisk to write info to the CEL DB

Posted by trinicom on Tue, 07/13/2021

got the latest version of thirdlane, CEL is already enabled and everything (see below)
however the CEL table is empty in pbx_logs

any ideals?

Everything looks good, any ideal why we are not getting any data into the table?
It was turned on by the default install

Cel.conf
Enabled by default

Apps (added queue, voicemal and transfer)
CEL Tracking Application: queue
CEL Tracking Application: voicemail
CEL Tracking Application: dial
CEL Tracking Application: park
CEL Tracking Application: transfer

(I changed it to ALL we can narrow it down as we look at the data and what we need)
Events: all

This is in cel_odbc.conf by default

[cel1]
connection=pbxlogs
table=cel

When I go into asterisk –r console I get

lupetortilla*CLI> cel show status
CEL Logging: Enabled
CEL Tracking Event: ALL
CEL Tracking Event: CHAN_START
CEL Tracking Event: CHAN_END
CEL Tracking Event: HANGUP
CEL Tracking Event: ANSWER
CEL Tracking Event: APP_START
CEL Tracking Event: APP_END
CEL Tracking Event: BRIDGE_ENTER
CEL Tracking Event: BRIDGE_EXIT
CEL Tracking Event: PARK_START
CEL Tracking Event: PARK_END
CEL Tracking Event: BLINDTRANSFER
CEL Tracking Event: ATTENDEDTRANSFER
CEL Tracking Event: USER_DEFINED
CEL Tracking Event: LINKEDID_END
CEL Tracking Event: PICKUP
CEL Tracking Event: FORWARD
CEL Tracking Event: LOCAL_OPTIMIZE
CEL Tracking Application: queue
CEL Tracking Application: voicemail
CEL Tracking Application: dial
CEL Tracking Application: park
CEL Tracking Application: transfer

Thanks again

Keith


Submitted by trinicom on Tue, 07/13/2021 Permalink

the response I got back from thirdlane to help anyone else in the future

We do not build and do not load the cel_odbc module that logs to the database because we do not use it, and as a general rule, we do not build or load modules that are not used.

You do have an option to use the cel_custom module (that we build but don’t load by default) that will write a CSV file that your customer can load into whatever database they choose. Just make sure that you configure it and load the module in modules.conf

Submitted by thirdlane on Wed, 07/14/2021 Permalink

This was a personal message and I was going to post here anyway :).

Overall, while CEL can be used to capture call flow, capturing AMI events gives you much more detailed information. We use that in Thirdlane Call Center Live Monitor, Call Center Agent Portal as well as in our CRM integration where we perform a caller id lookup to find caller information for Thirdlane Connect, or display the Contact or Lead in Salesforce, Zoho, etc. We also used that for a few custom projects. Let us know of any specific use cases you or your customers may be interested in.

As far as the CEL messages in the database - we added the cel_odbc.so module to the build, so it will be available in the next release. It will not be enabled by default, but you will be able to load it by adjusting your configuration if needed.