SOLVED Detail records and call recordings disappeared

Status
Not open for further replies.
Call Recordings tab seems broken in the gui today. Recordings are available via the call recordings tab.

Call detail records for yesterday seem missing. noticed this morning after updating fusionpbx via the gui yesterday evening.

Update was to xml_cdr, could this also effect cdr as well as call recordings? https://github.com/fusionpbx/fusionpbx/commit/bccc736fea3d84b76e7c0d61d722d8f3caf8b393

Info: Calls are recorded as mp3.

I'll also add in case it's relevant that my call recordings are stored using record_name=${strftime(%Y-%m-%d-%H-%M-%S)}_${destination_number}_${caller_id_number}.${record_ext} as I also use other external tools to archive recordings.

Call recordings, including historic are showing as if there are none, though they are present in the file system /var/lib/recordings/etc

Anyone else or any best suggestions?
 
Last edited:

jtarga

New Member
Dec 27, 2021
25
0
1
42
I have the same issue!
In my case some domains shows the call recordings and other not.
 

markjcrane

Active Member
Staff member
Jul 22, 2018
448
162
43
49
There was a bug in a commit on Saturday and that problem was fixed on Monday December 5th. Here is the fix in case you need visual proof. The bug affected calls that were being recorded.
The change on Saturday December 3rd requires running Upgrade -> Schema and Upgrade -> App Defaults. For those that don't know App Defaults or command line upgrade.php is an important part of the upgrade and required. Those people who skip it will see constant problems as its not optional. The App Defaults do not change defaults or update them it looks for missing defaults. In this case call recording now uses a database view the App Defaults is used to create that view or update it if needed.
 
Thanks for the explanation Mark, must confess I've stayed away from the app defaults button, the description could maybe do with a tweak.

It has indeed fixed the problem. I noticed the missing $ had been added in the most recent commit but wasn't sure if that brought on the problem as that's the point I noticed.
 
  • Like
Reactions: jtarga
Status
Not open for further replies.