How does it work

Pulling CDRs directly from PostgreSQL is not always a viable solution for our users.

With the Thrift feature enabled, the system processes CDRs normally but you can configure an aggressive CDR purge cycle (two days or so).

The advantage of using Thrift is that you are empowered to ingest, process and analyze your CDRs autonomously.


Below is a request made by one of our users which prompted our extending of the Thrift functionality with the softswitch.

Request:

As an operator of a wholesale switch, I want to retrieve CDRs in simple text format from my switch so that I can ingest that data into other systems for external use.

The switch must write Account and Vendor CDRs in an agreed text-based format (JSON or CSV) to flat files.

  • The files must be rotated every N minutes.
  • The files must be removed in a timely manner to ensure servers do not run out of space

File Naming Convention, format:

client_<time_from_epoch>_<rotation_frequency_in_seconds>
If the rotation time is set to 3600 seconds, and the file is rotated at Wed, 11 Dec 2013 22:02:15 GMT, then the file name will be 1386799335
client_1386799335_3600.bin


Further a Sippy Softswitch operator may upload thrift files to some SFTP server and use any 3rd party tools to parse these data in the desired way.