Video call recording bot

This project aims to improve and stabilize the existing bot that connects to online meetings (Google Meet, Zoom, Teams), records them, and uploads the recordings to S3. The bot also sends notifications via webhook upon successful completion or in case of an error. Improvements will focus on refactoring the code to enhance readability, ensure stability, and allow customization of the bot through environment variables or arguments.

Expected results:

1. A unified Dockerfile for all clients.

2. Improved code reusability by minimizing duplication and modularity.

3. Code refactoring to enhance readability and maintainability.

4. Reliable connection to meetings with a reconnect mechanism.

5. Improved container stability to prevent crashes on restart.

6. Joining the meeting via a direct link instead of login and password.

7. Customizable bot name.

8. Verified compatibility with Google Meet, Zoom, and Teams.

9. Correct saving of files in S3 in the format "meeting_id/date/uuid.mp4".

10. Optionally: saving separate audio files for each participant, if possible.

Acceptance criteria:

1. Docker unification:

   • A unified Dockerfile must be used for all clients.

   • The bot must build and run successfully using docker-compose and docker run.

   • All configuration parameters must be passed through arguments or environment variables.

2. Code refactoring and best practices:

   • Exclusion of unnecessary code duplication.

   • The code must adhere to best practices: separation into functions/modules, clear variable names, and documentation.

   • Compliance with clean code principles.

3. Reliable connection to meetings:

   • The bot must successfully connect to the meeting in no more than two attempts.

   • If the bot cannot connect after two attempts, a webhook error notification must be sent.

4. Fixing container restart issues:

   • The container must start successfully without errors after stopping and restarting.

   • The error related to starting Pulseaudio must be resolved.

5. Updating the authentication method:

   • The bot must connect to meetings via a direct link without login and password.

   • Changes in authentication must not disrupt existing functionality.

6. Customizing the bot name:

   • The bot name must be customizable via an environment variable or argument.

   • The bot must join the meeting with the specified name.

7. Saving files to S3:

   • All recordings must be saved in the format: "meeting_id/date/uuid.mp4".

   • Files must be correctly uploaded and accessible in the specified S3 bucket.

8. Webhook notifications:

   • A webhook notification must be sent upon successful completion of the recording and upload to S3.

   • In case of failure at any stage, a webhook error notification must be sent.

9. Compatibility with platforms:

   • The bot must work correctly with Google Meet, Zoom, and Microsoft Teams.

   • Meetings must be recorded without errors and failures.

10. OPTIONAL (Not a priority) - Splitting audio files:

• If possible, the bot must save separate audio tracks for each participant.

• This functionality must not interfere with the main capabilities.

Additional requirements:

• Logging and error handling mechanisms must be implemented.

• All dependencies must be documented.

• The final implementation must be thoroughly tested before submission.