Hi Charlie,
As long as you have one person connected in a session, it should remain active (unless the BigBlueButton server has been explicitly told to end the meeting after x minutes).
To put another way, the sessions on BigBlueButton are not permanent. Once created, they begin when the first person joins, and end whenever one of the following conditions are met:
- The length of the session has exceeded the length (in minutes) for the duration parameter passed during the 'create' API call
- The BigBlueButton server has received an 'end' API call for the meeting
- The meeting has no users
We have designed BigBlueButton so it doesn't retain state between sessions. Once one of the above conditions are met, the session is soon wiped from memory by the BigBlueButton server, and any recordings are processed by the recording scripts.
Consider if we did try to make the sessions stateful; that is, consider if the BigBlueButton server would all state between meetings (the idea here is having persistent meetings). BigBlueButton would need to store and retrieve the state of a meeting from a database, and have provisions for loading it at the point the last meeting ended. Furthermore, you would need tools to backup and restore the state as you moved BigBlueButton servers. Also, when the server is upgraded, the upgrade scripts would have to upgrade the stored meetings for new capabilities. All this capability would (significantly) increase the complexity of development and testing.
So, by keeping the rooms stateless, it greatly simplifies the design and development of the server.
Regards,... Fred
--
BigBlueButton Developer
BigBlueButton on twitter: @bigbluebutton