- Newest
- Most votes
- Most comments
You are correct that the meeting will automatically end after 24 hours. (Reference: https://docs.aws.amazon.com/chime-sdk/latest/dg/create-mtgs.html)
But you are also correct that you can build a user experience where the meeting will appear to go on for much longer. There are a number of ways that you could do that. One approach would have the connected clients (your front-end app) talk amongst themselves to have one of them create a meeting and distribute the new meeting ID. They could then coordinate a move to the new meeting to minimize the disruption. The data channel for the existing meeting can be used to communicate this. (Data channel reference: https://aws.github.io/amazon-chime-sdk-js/modules/apioverview.html#9-send-and-receive-data-messages-optional.)
Relevant content
- asked 2 months ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 months ago
Thank you Doug. This is what I suspected. We also faced a similar limitation while using the Zoom Video SDK and through some fairly simple mechanics were able to facilitate a 15-minute meeting session refresh countdown within the user experience to inform all users that their meeting session will refresh once the countdown expires. It sounds like this solution, or something similar, will work here as well.