Need Help with Removing Duplicate CDR Entries for Missed Calls in FusionPBX

[TharunV]

I’m looking for assistance with managing Call Detail Records (CDR) in FusionPBX. Specifically, I want to remove duplicate entries for both missed calls and no answer calls originating from a call center queue. Currently, when I view the CDR as a super admin, it shows separate entries for each agent’s extension instead of consolidating these into a single entry for the entire call center queue.​

Any guidance on how to proceed would be greatly appreciated!

 

[pbxgeek]

The issue stems from how CDRs are imported into the database, resulting in the creation of multiple records. This requires extensive front-end modifications to display the data in the desired format. I’ve made substantial progress on the FS PBX dashboard for FusionPBX trying to achieve this result. However, it’s not fully optimized yet. I’d estimate the work is about 90% complete, but there are still some refinements needed to achieve the final result.

 

[TharunV]

@pbxgeek i would like to be one of your Beta Tester. are we allowed to exchange contact details in this forum?

 

[pbxgeek]

I sure hope it's not against the rules. We are here to help one another. If the moderator disagrees, please let us know. Otherwise, DM me, and I'll be happy to discuss.
FS PBX is a free modern dashboard developed to enhance FusionPBX. Here is the Github link

 

[pbxgeek]

Hello everyone,

As of version 0.9.8, the FS PBX dashboard for FusionPBX now provides streamlined support for displaying a single entry per call in the CDR table. You can view all relevant details of both answered and unanswered related calls in the detailed view.

For example, in this screenshot, a call entered the queue. Extension 300 was attempted but didn't answer, followed by ext 106, which was unavailable, then ext 700, which also didn’t answer. Finally, ext 300 successfully answered the call. Each attempt is displayed on a timeline, complete with status updates, eliminating any guesswork.

No more cluttered CDRs to sift through—just one line per queue call!

 

[voipBull]

@pbxgeek that is very neat. Those additional details, I'm impressed. Is this limited to Queues only or expands to transfers/park etc.

 

[pbxgeek]

@voipBull It does more than just queues. Here is the call fragment involving a ring group and a call park.

 

[voipBull]

@pbxgeek that is really cool

 

[pbxgeek]

Thank you, @voipBull. One of the core objectives of FS PBX is to prioritize user-friendliness. After working with several systems based on Asterisk and FreeSWITCH, I noticed that none of them effectively presented CDRs in a clear, easily understandable format. So, we developed our own solution. Our system even shows which party ended the call at the end of the timeline, providing valuable insights for troubleshooting.

 

[voipBull]

@pbxgeek Yeah, I've had my fair share of struggles with the FreeSWITCH/FusionPBX CDR's being generated the way they are currently. Lately I was trying to integrate FusionPBX with CGRateS, and while I actually got it to work (partially) but some call scenarios (Like PSTN Caller > FusionPBX Extension > Call forward out to PSTN, and a few more) were not producing the CDR's as I was expecting them to be and that was ruining the whole billing process with CGRateS. I ended up scrapping the whole idea and put a OpenSIPS proxy in front with CGRateS module.

 

[pbxgeek]

@voipBull I'm not surprised. We had to perform extensive data manipulation to reach this stage. While the underlying data in the database remains unchanged, what we display is the final result of all the transformations we apply in real time.