It cannot be "fixed" as it is not a bug or problem. FOP2 is a standalone tool, unrelated to the backend (FreePBX or whatever), and it will show recordings initiated by FOP2 itself in its own recording interface. So, there is nothing broken that needs fixing.
Appart from that, there are also some problems with general recordings, as the fop2 interface has an owner and a target extension, so a user can see its own initated recordings, but not others. This metadata is not available when doing general call recording, you have just a recording made by the PBX, not initiated by an extension, so it has no owner. And that poses a problem.
Now, if you have to make recordings appear in fop2, you have to populate the fop2recordings table accordingly, and that could be done using a post recording script that you can write in any language, and configuring that post recording script in freepbx advanced options. And you will have to "hardcode" the owner in some way.
Comments
Appart from that, there are also some problems with general recordings, as the fop2 interface has an owner and a target extension, so a user can see its own initated recordings, but not others. This metadata is not available when doing general call recording, you have just a recording made by the PBX, not initiated by an extension, so it has no owner. And that poses a problem.
Now, if you have to make recordings appear in fop2, you have to populate the fop2recordings table accordingly, and that could be done using a post recording script that you can write in any language, and configuring that post recording script in freepbx advanced options. And you will have to "hardcode" the owner in some way.
Best regards,