Call Reporting by dialed DID?

[kriley87]

Hello-

Is this possible? I'm not seeing a way to pull call reports by the DID was that was dialed.

From the reports module, I see where I can specify from any to number, but when I enter a specific DID in the number field, I am not receiving any results.

Am I doing something wrong here? Or is this just not possible and I have to rely on pulling this information from our carrier records?

 

[kriley87]

Bump?

 

[mixig]

Tried few times but no results, same as you... What I need is call report for call conference number which is not in inbound rule as a DID number

 

[Allen_Miller]

I've done this. Need Pro or Ent License and need to create a separate trunk for the DID you are interested in.
In reports module, select Trunk/DID report type.

 

[kriley87]

Thank

I've done this. Need Pro or Ent License and need to create a separate trunk for the DID you are interested in.
In reports module, select Trunk/DID report type.

Thank you, however, this only reports on the number of calls received to a specific trunk/DID. What we're looking for is a total number of calls to that DID and who called it.

I am a bit surprised and disappointed that 3CX can't do this out of the box, considering plenty of open source solutions such as FreePBX can. This is a pretty basic reporting functionality..

 

[VoIPTools]

I realize you are looking for a built-in report, but if you can't get the information you need from the built-in reports, you could build a custom report yourself. The information you need is in the optional CDR files 3CX can create. You could parse the CDR files, put the data in SQL Server, and then use whatever reporting tool you prefer to create your report..

Here is an example CDR file with all the available fields selected:

09:42:31,TerminatedBySrc,Ext.128,18016424655,128,10000,18016424655,,,,,1,0.03,default,Chain: Ext.128;18016424655;,Extension,Line,,Dinesh Sura,18016424655,,

Getting access to CDR files hosted in the cloud might be a challenge for some, and then parsing the data and putting it into SQL is another programming task that would be necessary. Our "3CX Exporter" tool can automate the entire process if you don't want to write the code yourself.

 

[kriley87]

While I can appreciate the plug for your product, this is such a basic reporting functionality that the fact that a third party tool is required to produce this report is laughable.

Ultimately our solution was to create a dummy extension and forward it to the end user and create a report on the call history for the dummy extension to get a detailed list of calls for this particular DID.

Gotta love having to use workarounds to do something so basic in a commercial platform that several other open source solutions can do out of the box.