Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.It is actually possible to run a meeting again. However, meeting settings can be set and change only before the first start of the meeting.
The meeting settings shall be modifiable again as there are no particular reasons not to run this meeting again and that meeting information might be different the next time.
For the same reason, it might be necessary to add a flag "Enable on-line meeting for this node"
This will allow the issuer :
- to decide if the meeting is definitely over and to re-enable it at anytime with possible different information,
- to make possible to use the same node type for regular and on-line meetings - which is very often the case nowadays. Currently, an "event" node set for bbb will always be enabled for web conference even if it is not the intent. One might define a specific node type for bbb, but my guess is that bbb is more an optional capability that can also be enable/disabled on a per node basis
Note that one needs to change a setting in bbb:
edit /var/lib/tomcat6/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties
change (or add) "beans.dynamicConferenceService.minutesElapsedBeforeMeetingExpiration=1"
Default is 60 (1 hour) which can be frustrating. 0 seems to prevent meeting expiration. 1 is the minimum value that will bolck the meeting for 1 minute after it ended.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | 936714.patch | 3.23 KB | Owen Barton |
Comments
Comment #1
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedI would like a little more clarification.
Can meetings be re-enabled after the moderator kicks people off?
I think you are saying they can if you change the value in the config file from 60 to 1.
Is that correct?
Comment #2
jvieille CreditAttribution: jvieille commentedYes, meeting are re-enabled after the time set by default to 60 minutes, that you can change to 1.
(I tried 0, but this seems to hold the meeting forever)
On the BBB side, the meeting is totally erased after the elapsed time.
However, the bbb module does not behave accordingly: you can no longer change the meeting settings once it has run the first time, not restart it (you have to delete and recreate the node) hence my request
Edit 2017/03/11
BBB has changed the default settings (version 1.1). The meeting cleared 1 minute after ending as we need:
# Remove the meeting from memory when the end API is called.
# This allows 3rd-party apps to recycle the meeting right-away
# instead of waiting for the meeting to expire (see below).
removeMeetingWhenEnded=true
# The number of minutes before the system removes the meeting from memory.
defaultMeetingExpireDuration=1
# The number of minutes the system waits when a meeting is created and when
# a user joins. If after this period, a user hasn't joined, the meeting is
# removed from memory.
defaultMeetingCreateJoinDuration=5
Comment #3
jvieille CreditAttribution: jvieille commented+1
Comment #4
jvieille CreditAttribution: jvieille commented+1
Comment #5
geldim CreditAttribution: geldim commented+1
Comment #6
jvieille CreditAttribution: jvieille commented+1
Comment #7
jvieille CreditAttribution: jvieille commentedI found something:
For whatever reason, a conference node that has been ran is purged from the bbb_meeting table. (sometimes it isn't)
In bbb.module, line 356, under case 'update': I replaced
// bbb_update_meeting($node, $node->bbb);
by bbb_store_meeting($node, (array) $node->bbb);
Then, when you edit and save a past conference, it works again
This is just a temporary fix, I still don't understand well the underlaying logic of the module for dealing with terminated conferences
Comment #8
jvieille CreditAttribution: jvieille commentedBack to this issue
Can we have the opinion of the maintainer on this
- add a setting at the node level to allow BBB meetings or not
- allow re-running a meeting without having to delete and recreate a node
This might very well be 2 separate issues, but simple enough to possibly solve all at once
Thanks
Comment #9
jhezsie20 CreditAttribution: jhezsie20 commentedI was able to terminate a meeting for 1 minute then it will automatically available for another session if needed without recreating the node. This is very useful for my "sticky web conference rooms" and specially for moderating and force termination of a meeting session.
Comment #10
Owen Barton CreditAttribution: Owen Barton commentedThis patch doesn't address making meetings editable, but it does add an option, and allows you to skip the hasBeenForciblyEnded check.
Comment #11
Owen Barton CreditAttribution: Owen Barton commentedA couple of notes:
- This has a bug in that if you try and restart a meeting before the timeout you get "FAILEDmeetingForciblyEndedYou can not re-join a meeting that has already been forcibly ended. However, once the meeting is removed from memory (according to the timeout configured on this server, you will be able to once again create a meeting with the same meeting ID" in the iFrame/window. It would be better to detect this and replace with a drupal_set_message.
- The edit form would need quite a bit of work - we need to make each of the items not disabled if the setting is enabled, as well as loading in the existing node values (right now it only shows the content type defaults). I haven't worked out if we need to alter the code to update the meeting on the bbb side.
Comment #12
jvieille CreditAttribution: jvieille commentedActually, the problem is that it is not possible to change the meeting settings once it has run.
All the meeting fields are grayed. Even if the disabled attribute is commented out, the values are not taken into consideration.
What is missing is considering an edit of a meeting as creating a brand new meeting (for bbb, not for Drupal).
I tried that in #7, but this does not seem to work.