I’ve verified the file in question has started recording successfully, and I’m getting a success response of “Pause/Resume recording file” from my API command. However, when inspecting the file after pausing it, I see that it’s still being written to.

Looking at the conference_record_action() function, it appears what it does is set a flag on each individual member, MFLAG_PAUSE_RECORDING, when a recording is to be paused.

At this point I’m not sure I’m clear what the result of the above API commands are — what are they intended to do? And is there a way to completely stop writing additional data to a recording file when the recording is paused?