BigBlueButton 1.1

    Welcome to BigBlueButton 1.1. This is the latest release for BigBlueButton, an open source web conferencing system for online leanring.

    This document covers the new capabilities in BigBlueButton 1.1:

    • Closed Captioning (see 2517
    • Breakout Rooms (see 1934)
    • Faster Desktop Sharing (see 3520)

    As with every release, we’ve refactored components to improve stability:

    • Updated Playback Layout (see 3521)

    We’ve also added enhancements for developers/administrators:

    • updateRecordings API call (see API)
    • getRecordings API call now returns thumbnails for recording (see 2497)
    • Packaging for Ubuntu 16.04 (see 3118)

    In moving to Ubuntu 16.04 we rewrote the old system5 init scripts into modern unit scripts in systemd. The result was a much simpler and deterministic startup sequence for BigBlueButton.

    The install steps shrank as well. Thanks to the packages available in Ubuntu 16.04, the administrator no longer needs to compile ffmpeg or add external repositories for libreoffice.

    Components of BigBlueButton were completely rewritten. The new screen sharing doesn’t require opening another port, captures the mouse, and is faster. Under the hood, the new screen sharing runs a minimized version of ffmpeg to capture the screen and transmit it over RTMP – which is similar to the implementation in commercial applications.

    We strive to make every release easier and more capable for helping you as an instructor teach remote students. If you have any feedback on this release, please share it with our communty at bigbluebutton-dev. To install see install BigBlueButton 1.1.


    Closed Captioning

    BigBlueButton now supports live captioning during a session - a moderator (such as a stenographer) can enter captions for a selected language during the class and BigBlueButton will display those captions, in real-time, to other students. After the session is finished, the captions will appear as subtitles in the recordings.

    Creating Live Captions

    A moderator first selects Closed Caption layout.


    and then selects the language to provide captions


    and then selects the first tab (it will have the name of the selected language).


    Once selected, the moderator clicks Take Ownership (this ensures only one moderator at a time is entering captions for the given language).


    At this point, the moderator can begin typing text (or using a stenograph machine to inject text) into the tet area.


    As they type, the text is visibile to viewers (see below).

    Viewer Capabilities

    When a viewer (student) selects the Closed Captioning layout, The Closed Captioning dialog will display the active language streams.


    Clicking a language opens a new tab. Clicking on the first tab shows the live captions as they are typed.


    Viewing captions in Playback

    Later, when viewing the recording, the playback bar will have a ‘CC’ button. Clicking on the ‘CC’ button will show the available captions.


    Faster Screen Sharing

    When the presenter launches screen sharing, the BigBlueButton client will download a Java Network Launch Protocol (JNLP) file called screenshare.jnlp that, when opened, will download a Java application and run the screen sharing outside the browser.

    By running outside the browser, screen sharing works on all browsers.

    Starting Screen Sharing

    To start screen sharing, the presenter clicks the screen sharing icon in the toolbar.


    BigBlueButton client will display the Screen Sharing Presenters Preview window. This will show the presenter a thumbnail view of what others see when the screen sharing starts.


    The window displays a set of images that guide the user through starting the screen sharing. These images are specific to the user’s combination of operating system and browser.

    When the user clicks ‘Start’, BigBlueButton will download screenshare.jnlp. The file may be called screenshare(1).jnlp, screenshare(2).jnlp, etc. depending on previous downloads.

    Following the steps shown in the window, the instructor can opens screenshare.jnlp, which causes Java to launch and download and run BigBlueButton Screenshare. Java will display certificate confirmation dialog requesting permissions to run BigBlueButton Screenshare.


    Once running, the Desktop Sharing Presenters Preview window shows a thumbnail video of what students are currently seeing. This thumbnail is not resizable (students see the desktop in a resizable window).


    The presenter can pause/resume the desktop sharing stream. Clicking ‘Close’ will stop the desktop sharing.


    Sharing a Region

    On Windows and Linux, the presenter has the option of sharing a region. When choosing region, the presenter will see a dashed outline of the desktop sharing area when BigBlueButton Screenshare runs.


    Clicking ‘Start Sharing’ will start sharing the selected region. As with sharing full screen, a thumbnail version of what the remote students see will appear in the Desktop Sharing Presenter’s Preview window.

    Due to the limitation of underlying components in the new screen sharing, there is no option on Mac OS X to share a region – it will only capture full-screen of the first monitor.

    Breakout Rooms

    Any moderator (usually the instructor) can now place students into breakout rooms, monitor their interaction, and end the breakout rooms at any time.

    Breakout rooms are full BigBlueButton sessions. The ability to record breakout rooms is under development. Each student in a breakout room has moderator role, which means any student can make themselves presenter and upload a presentation for sharing with other students.

    To start a breakout room, choose “Breakout Rooms …” from the gear icon.


    Configure Breakout Rooms

    When you choose “Breakout Rooms …” the following dialog box appears.


    The Breakout Room dialog enables the instructor to specify

    1. the number of breakout rooms: 2,3,4, or 5
    2. time limit
    3. enable/disable recording
    4. drag and drop users between rooms
    5. which users should not be placed into breakout room (the “Not Assigned” room)

    Student Joining a Breakout Room

    When the moderator presses the ‘Start’ button in the Breakout Room dialog, any user assigned to a breakout room will see the following dialog inviting them to join the breakout room.


    Clicking ‘Yes’ causes the breakout room session to open in a new tab. The user remains joined in the main session (where they can chat with the instructor and ask questions). BigBlueButton will disconnect drop them from the audio from the main room. This will prevent students from being joined into two different audio sessions at the same time.


    The breakout room will have a countdown timer about the chat to inform the users of the remaining time [1]. Once the timer reaches 0, the breakout room will automatically close.

    Users can return to the previous tab and rejoin the audio in the main room.

    Monitoring Breakout Rooms

    When the instructor clicks ‘Start’ in the Breakout Room dialog, a breakout room status table will appear in the Users window.


    The instructor can join the breakout room in a new tab [1], or join only the audio [2]. The instructor can also close the breakout rooms early (before the time remaining expires) [3].

    Updated Playback Layout

    The new playback layout provides an expandable list of thumbnails. The playback format also supports subtitles for sessions that had live closed captioning.


    Miscellaneous upates

    Restrict viewer webcams to only display for moderators

    There are cases where you want to restrict a student’s webcam to only be visible to the moderator. We’ve added a parameter webcamsOnlyForModerator to enforce this behaviour for a meeting.

    Param NameRequired / OptionalTypeDescription
    webcamsOnlyForModeratorOptionalBoolean Setting 'webcamsOnlyForModerator=true' will cause all webcams shared by viewers during this meeting to only appear for moderators

    Here’s a overview video demonstrating how this restriction works in a meeting.

    Client Logging

    The BigBlueButton client send log (debug) output specific destinations as definied in config.xml.

    <logging enabled="true" target="trace" level="info" format="{dateUTC} {time} :: {name} :: [{logLevel}] {message}" uri="" logPattern=".*"/>

    The valid options for target are

    Option Description
    trace write logs to Flash console (used when debug mode is enabled for FlashPlayer)
    logwindow write logs in LogWindow view (used if you enable the showLogButton option in the config.xml
    server send logs to the server at the URL defined in uri
    jsnlog use jsnlog javascript library (experimental)and output the logs to the browser’s console.

    The most useful option is server as it enables capture of logging events from BigBlueButton clients on the BigBlueButton server for troubleshooting and debugging.

    When setting the output to server, the BigBlueButton client will POST the log events to the URL endpoint provided by uri. To create an associated endpoing, create a file in /etc/bigbluebutton/nginx/client-log.nginx` with the contents

    location /log {
    	access_log /var/log/nginx/client-log.log postdata;

    Then create a file in /etc/nginx/conf.d/client-log.conf with the contents

    log_format postdata '$remote_addr [$time_iso8601] $request_body';

    Install the full version of Nginx.

    sudo apt-get install nginx-full

    Finally, restart nginx with sudo service restart nginx. Launch the BigBlueButton client in a new session and you’ll see output in /var/log/nginx/client-log.log as the client loads.

    ::ffff: [2017-05-02T00:31:00+02:00] 2017/5/1 18:30:59.425 :: UNKNOWN USER null org.bigbluebutton.main.model.users.JoinService :: [INFO] {\x22message\x22:\x22Calling ENTER api succeeded.\x22,\x22tags\x22:[\x22initialization\x22],\x22sessionToken\x22:\x22dscmp5atkg4e6iik\x22}

    These logs are useful for troubleshooting and debugging the client.

    Record and Playback

    Previously, the processing of recordings would require the completion of the processing stage for all outstanding recordings before moving to the publishing stage. This could lead to cases where a high volume of incoming recordings for processing delayed the publishing of recordings for an extended length of time.

    Each stage record – archive, process, and publish – now has it’s own worker thread and recordings can move through the stages more quickly.


    BigBlueButton 1.1 is running FreeSWITCH to 1.6.14. Compared with the version of FreeSWITCH running in 1.0, this newer version of brings improved audio quality with support for forward error correction (FEC) in WebRTC audio. This means viewers using Chrome (support for FEC is coming soon to FireFox) will have even better audio on wireless or low-bandwidh networs with packet loss.

    FreeSWITCH is a great open source project and the development team has done a solid job on creating an open source soft switch.


    This release builds upon red5 1.0.8-M13 which includes a number of stability and bug fixes over the previous release (thanks to the red5 team for being so responsive in our bug reports).

    Previous Releases

    BigBlueButton 1.0

    See Overview of features released in 1.0

    BigBlueButton 0.91

    See Overview of features released in 0.91