MiroTalk SFU: Recording not possible?

[shrey]

@james

MiroTalk SFU 2.0.17

[james]

Ah, I see your issue. You are still using AWS_S3_BUCKET_NAME and not AWS_S3_BUCKET which was posted to be the wrong variable and fixed upstream.
Small detail, leading to fail.
Change AWS_S3_BUCKET_NAME to AWS_S3_BUCKET restart and it should be working.

[shrey]

@james said in MiroTalk SFU: Recording not possible?:

Change AWS_S3_BUCKET_NAME to AWS_S3_BUCKET restart and it should be working.

Thanks!
That did get it working.

---

@mirotalk-57bab571 Just one more kink remaining:

When i 'disconnect' the call without stopping the recording, the Recording seems to get saved only in the local directory, and not S3. The S3 upload seems to be triggered only when an ongoing recording is stopped explicitly.

[james]

Hello @shrey

@shrey said in MiroTalk SFU: Recording not possible?:

The S3 upload seems to be triggered only when an ongoing recording is stopped explicitly.

Oh, so you mean if the meeting is exited by a recording member, his recording is not stopped and thus never saved/uploaded?
Could you give more details about what you'd expect and what the current behavior is that you have observed?

[shrey]

@james
Current behaviour:

1. I start a meeting as Host
2. Start the Recording (only Host is allowed to record)
3. Once meeting is over, i stop the meeting by clicking on "Leave Room"
4. The recording is available in /app/data/rec but not in S3.

If, in Step 3:
i stop the Recording and then stop the meeting, then the Recording gets uploaded to S3.

Expectation:
Recording should get uploaded to S3 regardless of the path taken to 'stop' the meeting and without explicitly stopping the recording.

[shrey]

Additionally, it seems like if:
Start recording > [time elapses] > Stop recording > Start Recording again > [time elapses] > Stop Recording/Exit Meeting
Only the last recording gets saved (overwriting the first part).