@gauthambh, I don’t know if question 1 and 2 in detail is asking about disconnection of websocket or disconnetion of user, but I’ll asner for both.
If a user disconnects from a meeting, it doesn’t affect RTMS, it will keep on running as long as the meeting is still running. Once the meeting ends, RTMS will get disconnected.
Scenario 1. RTMS websocket is disconnected due connectivity, you will need to initiate the reconnection. The sample apps and the SDK does incorporate reconnection logic in the scenario where it is disconnected unexpectedly.
Scenario 2. Host ends the meeting and starts another meeting, you will need RTMS to connect to this new meeting. This is typically easy to automate if you we using webhook to get notification that a meeting has started.
The question about Otter AI is not related to RTMS, and is more related to a Meeting SDK bot. I’m assuming you are asking how you can create your own AI meeting bot?
From a high level summary for AI meeting bot which joins as a participant, you will need a Linux, Windows or MacOS server, it will run many instances of Meeting SDK which meetings when it received notification that a meeting is running. You will need to work with raw audio and raw video in PCM and YUV420 format. The host would also need to explicitly give your bot permission before it can access the audio and video in meeting.
One of RTMS goal is to let developers easily access video/audio/transcript without going through the process of creating a meeting bot.