Adjusting ID and Title of Big Blue Button Meeting
See original GitHub issueWe currently generate the ID of a Big Blue Button Meeting for Video Calls randomly. As suggested by @GhaziTriki we should generate them the following way:
- meeting Id:
* private chat: zulip-deployment-id-owner-id-user
* stream topic: zulip-deployment-id-stream-id-topic-id
- meeting name:
* private chat: User Name Room
* stream topic: stream - topic
The problem I see in that is that using the formats for the id that would mean that there can not be different meetings in one stream/pm chat. I think a time aspect should be included. (like appending the unix timestamp)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Customize - BigBlueButton
By default, the BigBlueButton server will produce a recording when (1) the meeting has been created with record=true in the create API call...
Read more >API - BigBlueButton
A meeting ID that can be used to identify this meeting by the 3rd-party application. This must be unique to the server that...
Read more >FAQ - BigBlueButton
The name came from the goal of making the process to setup a virtual classroom as easy as pressing a (metaphorical) big blue...
Read more >BigBlueButton : Recording
In BigBlueButton you can use the same external meeting ID (for example “English 101”) in many recordings, but each recording will have a...
Read more >Overview - BigBlueButton
Setting, Description. Generate an optional room access code, Generates an access code that users must enter before they are allowed to join the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I feel like we could generate the IDs still randomly and just configure the name based on the current compose box location at the time the request is made to create them?
@strifel we can simply pass some JSON to the API call and write
in
zerver/views/video_calls.py:164:def get_bigbluebutton_url