CDR 2.0 data format issue with current socket tool

londonpapakura

Customer
Joined
Nov 11, 2023
Messages
18
Reaction score
8
My setup: on-premise, 8 SC Enterprise, Version 20.0 Update 6 (Build 724 Release)

**

With v18, I had been been using a third party software Advanced PBX Data Logger by AGGSoft (100$ one-off fee). This software runs a socket and writes cdr entries real-time as it receives them from 3CX to, for example, an MS SQL database in my case.

Based on this setup, I have been using a one-number strategy: all agents call from the same number. A small CFD routes customers back to the agent who was last in contact with them or tried to reach them (based on the database with the CDR records previously exported via the socket). This worked brilliantly and made it everyone super happy.

Now at the moment, the Advanced PBX Data Logger isn't able to cope with the new format (probably since CDR 2.0 launch). I only just updated to v20 from v18 and since then, I wasn't able to set the routing up in the same great way I could with v18. AGGsoft are working on a solution at the moment.

In the meantime, what other approaches are there to write CDR real-time/immediately to a MS SQL database?

Thank you,
Stefan
 
Last edited:
@VoIPTools Exporter is probably your best option currently.
 
@VoIPTools Exporter is probably your best option currently.
Thank you - is there really no alternative? This entire package seems quite big for this minor task (and is too expensive in my use case). All I need is a standalone application that just does port listening and witing to odbc.
 
Advanced PBX Data Logger is fully functional again and a great tool that I can recommend for this use case.

Their support is very reactive and the software is being kept up-to-date on a regular basis.
 

Members Online Now

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK