You will learn very quickly that 3CX will flag your PBX as "unsupported" if they find out that you are accessing the PostgreSQL database directly. Don't do it.
The only supported approaches to custom reports are (1) using the information provided through the optional CDR files that 3CX can create, or (2) running existing 3CX reports and exporting the data to be used in combination with other reports data and after further refinement.
Unfortunately, while indeed VERY useful, the CDR information is fairly basic. Exporting report data to be combined and refined is labor-intensive. Neither choice is an ideal solution.
While the above is completely true and others will undoubtedly confirm shortly, I have a solution for you. I freely admit this is going to appear self-serving. Nevertheless, I encourage you to take a look at our
3CX Exporter tool.
Our tool, in combination with our VoIPTools REST API, automatically replicates all the data 3CX uses for their built-in reports, to either SQL or MySQL. Further, we also automatically process all the CDR data (CSV files) and place this information in SQL too.
We do NOT use the IP socket approach to obtaining the CDR data. I personally feel this is a completely unreliable approach to synchronizing the data. With an IP socket, if the socket goes down for any reason, even momentarily, the data is lost and cannot be recaptured. Taking the approach of processing the CDR files ensures that even if there is a lengthy outage, we can simply start where we left off without any loss of data. And it does not matter if your 3CX server is hosted. We handle that too.
