Skip to end of metadata
Go to start of metadata

Contrib: BigBlueButton

 

Introduction

Sakai BigBlueButton integrates a Sakai instance with a BigBlueButton server, allowing Sakai users to easily create, manage and join BigBlueButton meetings from a Sakai worksite.

 

Features

  • Control meetings - create/edit/update/delete BBB meetings from Sakai.
  • Meeting access - define meeting access by selecting all users, groups, roles or individual users in site.
  • Tool access - define who can do what on the Sakai tool.
  • Scheduling - optionally, define meeting start dates and/or end dates and add it to site Calendar.
  • Notification - optionally, send an email notification to meeting participants.
  • Simplicity - the user interface is designed to be simple.
  • Fast - the Ajax driven interface (Javascript + JSON + Trimpath templates) provides good end-user experience and low server load.
  • RESTful - full RESTful support via EntityBroker.
  • Statistics - the tool logs information automatically processed by the Site Stats tool.

 

Release information

1. Requirements
  • Sakai:
    • 2.7.0 or higher ( — or — )
    • 2.6.0 + EntityBroker 1.3.9 or higher ( — or — )
    • 2.5.0 + EntityBroker 1.3.9 or higher + SAK-10801 - Add contextId (siteId) field to Event Closed applied
  • BigBlueButton 0.80 or higher [Installation intructions]
2. Download
3. Installation
4. Support

 

Configuration

1. Required settings

Configuration key

Description

Version

Default value

bbb.url

A comma separated list of BigBlueButton servers (example: http://your-server.edu/bigbluebutton)

1.0+ (single value) 1.0.5+ (comma separated values)

-

bbb.salt

A comma separated list of BigBlueButton salt keys (see BBB FAQ)

1.0+ (single value) 1.0.5+ (comma separated values)

-

2. Optional settings

Configuration key

Description

Version

Default value

bbb.autocloseMeetingWindow

Whether the browser window of BBB should be automatically closed after logging out of meeting. If false, the configured bigbluebutton.web.loggedOutUrl from BigBlueButton will be used instead.

1.0+

true

bbb.versionCheckInterval

Time - in milliseconds - to periodically check the API version of the configured BigBlueButton server. This is useful for performing BBB upgrades without having to restart Sakai.

1.0.1+

0 (disabled)

bbb.notice.text

Optional text to be displayed on the tool main page.

1.0.2+

-

bbb.notice.level

Message level in which the text will be displayed (BBB-37). Valid values: info, warn, success

1.0.2+

info

bbb.default.permissions.ROLE

List (comma separated) of default permissions for role ROLE. Will only be applied if no bbb.* permission is defined on site (BBB-45).

1.0.4+

-

bbb.default.participants.owner

If set (and not 'none'), meeting owner will be added to new meetings by default, with specified BBB role (BBB-45). Valid values: none, moderator, attendee.

1.0.4+

moderator

bbb.default.participants.all_users

If set (and not 'none'), all site participants will be added to new meetings by default, with specified BBB role (BBB-45). Valid values: none, moderator, attendee.

1.0.4+

none

bbb.autorefresh.meetings

Auto-refresh interval for updating meeting status is expressed in milliseconds. When the value is set to 0 the auto-refresh is turned off.

1.0.7+

0

bbb.autorefresh.recordings

Auto-refresh interval for updating recording list and and info. It is expressed in milliseconds. When the value is set to 0 the auto-refresh is turned off.

1.0.7+

0

bbb.descriptionmaxlengthEstablishes the maximum length for the meeting description. Since the description is also used as a welcome message in the BigBlueButton client, this is an important parameter due this limit should be less than the one set up for query strings on a GET request in the BigBlueButton server or any web server working as intermediary between Sakai and BigBlueButton.1.0.7+2048
bbb.recording.enabledSet up to [true/false] for enable or disable the recording capability to all the meetings. When enabled its setting can be changed for each meeting using the Add/Edit user interface. This parameter replaces the bbb.recording parameter introduced in 1.0.7.1.0.8+true
bbb.recording.defaultSet up to [true/false] the default setting for the meetings when created. When a meeting has this setting enabled, the sessions will be created with recording capabilities.1.0.8+false
bbb.duration.enabledSet up to [true/false] for enable or disable the duration capability to all the meetings. When enabled its value can be changed for each meeting using the Add/Edit user interface.1.0.8+false
bbb.duration.defaultThe duration is expressed in numeric format and means the default duration for the meetings when created. The maximum duration for a meeting is counted in minutes since the first user joins the session and all users are kicked out once the limit is reached. If its value is 0 no limit will be set.1.0.8+120
bbb.waitmoderator.enabledSet up to [true/false] for enable or disable the waiting for moderator capability to all the meetings. When enabled its value can be changed for each meeting using the Add/Edit user interface.1.0.8+true
bbb.waitmoderator.defaultSet up to [true/false]  the default setting for the meetings when created. When a meeting has this setting enabled, all users in the viewer role will not be able to join the session until a user with moderator role joins.1.0.8+true
bbb.multiplesessionsallowed.enabledSet up to [true/false] for enable or disable the 'multiple sessions allowed' capability to all the meetings. When enabled its value can be changed for each meeting using the Add/Edit user interface.1.0.8+false
bbb.multiplesessionsallowed.defaultSet up to [true/false]  the default setting for the meetings when created. When a meeting has this setting enabled, users will be able to join the same sessions in multiple tabs. If1.0.8+true

 

Authors

Contributors:

 
  • No labels

8 Comments

  1. For 2.6.x I had to (thanks to Nuno for his help) :
    + Upgrade the entity broker to 1.3.9 (actually pulled new source down, instead of changing the version number as mentioned)
    svn co https://source.sakaiproject.org/svn/entitybroker/tags/entitybroker-1.3.9/
    + Upgrade maven - requires 2.2.1+ (if not, you'll get : Failed to validate POM for project...) error
    + Turn off the YUI compressor in bbb/tool/pom.xml set <yuicompressor.phase>none</yuicompressor.phase> (if not you'll get syntax errors during the clean install) (or add the -Pdev flag when you run clean install sakai:deploy
    + removed all entitybroker.* files from /tomcat/shared/lib and re-deployed the entitybroker

    after doing those three things, mvn clean install sakai:deploy worked great.

  2. We upgraded our installation of BBB to 0.71

    They suggest using Freeswitch with the new installation, but we had a problem with this. The Demo of big blue button works but as soon as you run this tool through sakai the sound in the conference did not work.

    Thanks to Nate and Fred pointing to a link in the FAQ of BBB http://code.google.com/p/bigbluebutton/wiki/FAQ#Why_did_my_voice_conference_number_worked_in_0.7_but_not_in_0.71

    I found that I had to change some code in freeswitch to make it work.

    I edited the /opt/freeswitch/conf/dialplan/public.xml on the BBB server and changed the following line

     <condition field="destination_number" expression="^(7\d{4})$">
    

    to

    <condition field="destination_number" expression="^(\d{5})$">
    

    This will allow Freeswitch to accept all 5 digit numbers.
    I do not know if you guys what to update the bbb sakai contrib code just to generate a a 5 digit code that starts with a 7 to make freeswitch work out of the box:

    Change the code of BaseBBBAPI.java line 136 form

    Integer voiceBridge = 10000 + new Random().nextInt(89999);
    

    to

    Integer voiceBridge = 70000 + new Random().nextInt(9999);
    
  3. BBB is now on 0.8 beta3 version and i hope there will be a final version very soon. The 1.0.6 tool works with bbb 0.8, but with a few bugs.

    Moodle already have a 0.8 compatible module, with recording and playback features support. Do you have plans to support the BigBlueButon 0.8 API ?

    It would be awesome, because the bbb-sakai-tool is the best tool for using BBB.

    Regards,

    Pablo

  4. Hi Pablo,

    I am one of the developers of BigBlueButton.  As you saw, we recently updated our Moodle integration for Moodle 2.0/2.1 to support the record and playback capabilities in BigBlueButton 0.8.

    We're now working with Adrian Fish to update the Sakai Meeting Tool to support the record and playback capabilities in BigBlueButton 0.8.  For the announcement of our efforts, see: http://collab.sakaiproject.org/pipermail/sakai-dev/2011-September/014052.html

    I'll post an update here when we have an updated Sakai Meeting Tool for the community to test.

    Regards,... Fred

    BigBlueButton Developer

  5. Hello,

    Is the tool working with Sakai 10.1?

    Will it be working with the next version of BBB 0.90?

     

    Thank you,

    Alaa

  6. Hello,

    I discovered two Bugs in the Meetings Tool:

    1. Meeting Description: Once I click on the Text Area to enter the description of the Meeting, the whole area just disappears!
    2. Student1 from Group1 CAN see recordings of Meetings he is not invited to!

    let me explain the second Bug:

    I created a Meeting and I've added on Group1 (created with student1 only) as attendee.

    I run the meeting with recording feature.

    PROBLEM: Student2, from Group2 CAN see the Meeting recording done with Student1 (Group1)

    Issue: Student2 MUST NOT SEE recordings of meetings he wasn't invited to!

    SPECS:

    Sakai: 2.10

    BigBlueBottun: 0.90

    Meetings Tool: Version 1.0.8 (Instaleld on 15/09/2014)

    Thanks for having a look at this.

     

    1. Hi Alaa,

      Best place to report issues is through JIRA https://jira.sakaiproject.org/browse/BBB

      Create a new one for each issue you found.

      The first one is a problem with the CKEditor library that I could not find the way to fix. It actually fails only when you click is some areas of the box, but not always, which is odd.

       

  7. Hi Jesus,

    I'm creating a JIRA for the Recordings permissions Bug.

     

    As for the CKeditor, I would prefer a function to "show/hide editor", much like text area in SAMIGO, while editing assessments. With the default as plain text.

    This way, we can have a functioning text area, meanwhile, you can work on the fully functional Editor.