Call Detail Records page is blank after update

Status
Not open for further replies.

bradgarrison

New Member
Feb 20, 2023
18
0
1
48
Last night I updated via the GUI and this morning I noticed the Call Detail Records page is blank. I tried to search for previous calls but nothing returned. Everything else seems to be working normally. If I click on statistics in the CDR screen I can see a graph of calls from the day before but nothing for today.

Prior to the update I was using the CDR and it was working fine.

System Information​
Operating System Information​
Version5.1.3
Git InformationBranch: master
Commit: 2ed2ac63aef95e3eb9e860425babfd9912316021
Origin: https://github.com/fusionpbx/fusionpbx
Status: Your branch is up to date with 'origin/master'. +0 days ago
Project Path/var/www/fusionpbx
Switch Version1.10.9 (64bit)
PHP Version7.4.33
Operating SystemDebian
Version11
KernelLinux pbx 5.10.0-25-amd64 #1 SMP Debian 5.10.191-1 (2023-08-16) x86_64 GNU/Linux
Uptime10:39:25 up 68 days, 23:39, 1 user, load average: 0.32, 0.09, 0.03
DateSat, 04 Nov 2023 10:39:25 -0400
 

Attachments

  • CDR screenshot.png
    CDR screenshot.png
    69.5 KB · Views: 18
  • CDR2 screenshot.png
    CDR2 screenshot.png
    32.4 KB · Views: 17
Last edited:

bradgarrison

New Member
Feb 20, 2023
18
0
1
48
I just restored back to before the update and everything is working. I'll wait a bit before updating again.

Before update.png
 
Last edited:

roger_roger

Member
Oct 12, 2016
198
19
18
70
That was a result of some changes to the code. Reach out to mcrane for the fix. He fixed mine but I don't recall what he did
 

technologic

New Member
Jan 25, 2020
3
0
1
41
I'm having the same issue
v 5.1.0
Branch 5.1
Commit 113a9ad6ba80ff6addb60daa1d76b4d95826cbb1

I see some commit activity on cdr related files lately, which leads me to wonder - Should I be tracking master instead of 5.1?
 

matt

Member
Oct 30, 2017
36
1
8
47
After the update (Commit 968706dac216f2189ff00f32268a86aa872eef79) today the old entries are present, but no new ones are shown...

The problem here was, that the module XML Cdr wan not running...

Now I get records again, but 3 days are missing...
 
Last edited:

adam_AMP

New Member
Feb 15, 2019
2
0
1
42
After the update (Commit 968706dac216f2189ff00f32268a86aa872eef79) today the old entries are present, but no new ones are shown...

The problem here was, that the module XML Cdr wan not running...

Now I get records again, but 3 days are missing...

Mark answered here:


This command will import the missing calls:
/usr/bin/php /var/www/fusionpbx/app/xml_cdr/xml_cdr_import.php
 

adam_AMP

New Member
Feb 15, 2019
2
0
1
42
No - it doesn´t ;)
Oh. It did for me. Sorry. I used the post I linked to fix our CDRs after a recent update.

I set up the cron job like it mentions and that command is importing my calls every minute now.
 

markjcrane

Active Member
Staff member
Jul 22, 2018
499
177
43
49
The reasons for saving CDR to the file system is the following reasons.

- Saving the CDR to files and skipping HTTP POST reduces work for the web server.
- When saving over HTTP POST the records need to be escaped perfectly for an HTTP POST for CDR records to succeed.
- FreeSWITCH doesn't escape data perfectly on all CDR records. Not as dependable.
- This means HTTP POST is not as safe. If CDR records are important to you then you shouldn't use HTTP POST.
- HTTP POST fail can save to the file system however if it does not save to the file system then the CDR records are not recoverable.
- Some servers will save them to the file system some have not been saving to the file system
 
Last edited:
  • Like
Reactions: adam_AMP
Status
Not open for further replies.