acquire-webrtc v0.3.0

System Block Diagram

P2P Flow (step 1-8 below)

[Design Doc1]

[POC Plan]

Http Server (Python)

• room and server allocation
• prestore offer

Collider (Go)

• exchange signaling message
• maintain room datastructure

New Recording Flow (no encryption or extra transcoding needed)

React Side

• Mixer of streams
• Send Kurento for recording
• S3 upload
• Lamda for S3 presigned-URL

Deploy or Start Guide

use Systemctl for Python/Go backend server

Future DevOps

Terrraform and K8S

React Component Prop/State/CSS/Store Spreadsheet

[React Tracker]

Notes of some concerns

1. Q: what is the buffer limits for the kurento recording?

   A: According to the documentation of kurento JSDoc, the kurento recorder endpoint will start storing into the file as soon as it get it. By default both AUDIO and VIDEO media types are expected, unless specified otherwise when invoking the connect method. Failing to provide both types, will result in RecorderEndpoint buffering the received media: it won't be written to the file until the recording is stopped. The recorder waits until all types of media start arriving, in order to synchronize them appropriately.

2. Q: Is the S3 uploading in real time?

   A: Yes, the S3 uploading is in real time

3. Q: How to hanlde the situation where the recording crash? Will it keep uploading to S3?

Setup kms in dev server

1. use certbot generate certificates

2. make sure to combind fullchain.pem and key.pem into one pem file

3. when spin up the kms with the offical image, you need to bind certs, config files, and record storage location to it, an example is here:

docker run --rm \
-d \
--name kms \
--network host \
-v /tmp/recordings/:/tmp/recordings/  \
-v /cert/combind.pem:/cert/combind.pem \
-v /etc/kurento/kurento.conf.json:/etc/kurento/kurento.conf.json \
kurento/kurento-media-server:latest