Install Welcome to the installation guide for BigBlueButton 2.0. This document is for system administrators and developers wanting to install and configure there own BigBlueButton server. BigBlueButton is an open source web conferencing system for online learning.
The goal of the project is to enable teachers engage remote students in a high-quality online learning experience. To achieve this goal, BigBlueButton offers real-time sharing of audio, video, slides, and the presenter’s screen. For enagement, it offers chat, emoji, polling, multi-user whiteboard, breakout rooms, and shared notes. For details of the features, see. This release includes the HTML5 client for mobile users. The HTML5 client implements all features of the Flash client for viewers except two-way webcams (which is coming in a future update). All the remaining viewer capabilities – such as participating in multi-user whiteboard, breakout rooms, and polling – is implemented along with high-quality WebRTC audio.
For system administrators, this document covers installation of BigBlueButton on a Ubuntu 16.04 64-bit server, configuring it to use a hostname and SSL certificate, and, if the server is running behind a firewall, configuring the firewall to pass through specific ports to the BigBlueButton server. For developers, you may opt to install BigBlueButton on a local VM or LXC container. In such a setup, you don’t need to configure it with a hostname or SSL certiicate.
In such cases, FireFox to access your server as it doesn’t require a SSL cerificate to use web real-time commications (WebRTC). If you encounter difficulties with the installation, check out the at the end of this document. If you can’t resolve the issue, see for how to post a message to our bigbluebutton-setup mailing list. Wd 5000aav driver for mac os.
When you post for help, the more information you give the easier it is for others to help. Be sure to post:. the version of BigBlueButton you are trying to install,. any errors your received during installation, and.
the error you are receiving. All the core BigBlueButton developers hang out in this form and will attempt to help you if you get stuck. Before you install Before jumping ahead to installation steps, give youself a moment to go through this section to make sure your server meets the minimum requirements. Doing so will save you time later on. Minimum server requirements We recommend installing BigBlueButton on a ‘clean’ Ubuntu 16.04 64-bit server. The server should not have any have web applications installed (such as plesk or Apache2).
Such applications want to bind to port 80 and causes subtle conflicts with the installation and running of BigBlueButton that are difficult to resolve. $ sudo apt-get install language-pack-en $ sudo update-locale LANG=enUS.UTF-8 Next, logout and then log back into your SSH session – this will reload the locale configuration for your session – and run the above command cat /etc/default/locale again. Verify you see only the single line LANG='enUS.UTF-8'. Note: If you see an additional line LCALL=enUS.UTF-8, then remove the entry for LCALL from /etc/default/locale and logout and then log back in once more.
Next, check that your server has (at lest) 4G of memory using the command free -h. Here’s the output from one of our test servers.
Prsentation Des Configurations De Building
# netcat -l 7443 test If the word test does not appear, double-check the firewall configuration to ensure its forwarding connections on port 7443 and then test again. You want to see the word test appear before proceeding to the installation BigBlueButton. Repeat these tests with ports 80, 443, and 1935. That covers the TCP/IP ports. Next, we need to test that UDP connections in the range 8 are forwarded as well. On your BigBlueButton server, run the following netcat command to listen for incoming data via UDP on port 17000 (here, we’re picking a port in the range 8).
# netcat -u -l 17000 test2 As before, it the above test fails, double-check the settings of the firewall to ensure its properly fording UDP packets in the range 8 and test again. When BigBlueButton is running on a server, various component of BigBlueButton need to make connections to itself using the external hostname. Programs running within the BigBlueButton server that try to connect to the external hostname should reach BigBlueButton itself. To enable the BigBlueButton server to connect to itself using the external hostname, edit file /etc/hosts and add the line.
172.34.56.78 bigbluebutton.example.com Installation Before you begin the installation, here’s a quick checklist to make sure you are ready:. You have a Ubuntu 16.04 64-bit server that meets the. If the server is behind a firewall, you have to forward the appropriate ports to the BigBlueButton server (and tested that connections are getting through). You have a fully qualified domain name (such as bigbluebutton.example.com) that resolves to your BigBlueButton server’s IP address (or the IP address of your firewall). You have a valid SSL certificate for the hostname (or intend to obtain one with Lets Encrypt) If you are a developer setting up BigBlueButton for development or testing on a local VM, you can skip (2), (3), and (4).
As menitoned earlier, use FireFox for testing as FireFox supports WebRTC without a requiring an SSL connection. At this point, your ready to install. You have two options:.
Option #1: Use to install pretty much everything you’ll need with a single command (this is recommended if it’s your first time setting up BigBlueButton). Go through the step-by-step instructions below. Do this when you want to understand how to setup BigBlueButton and make changes to the default configuration. If you’ve opted to go thorugh the step-by-step instructions, the first step is to ensure your server is up-to-date. Update your server First, let’s make sure your server is up-to-date with latest packages and security updates. Login to your server via SSH. You need to have an account that can execute commands as root (via sudo).
Once logged in, first ensure that you have xenail multiverse in your /etc/apt/sources.list by doing the following. $ echo 'deb xenial multiverse' sudo tee -a /etc/apt/sources.list If you are a developer installing BigBlueButton on a VM for testing and development, some of BigBlueButton’s components, such as Tomcat, need a source of entropy when starting up. In a VM the available entropy can run low Tomcat can block for a long periods of time (sometimes minutes) before finishing its statup. To give the VM lots of entropy, install a packaged called haveged (a simple entropy daemon). $ sudo apt-get update $ sudo apt-get dist-upgrade If you haven’t updated in a while, apt-get may recommend you reboot your server after dist-upgrade finishes. Do the reboot now before proceeding to the next step.
Install apt-get key for BigBlueButton repository All packages for BigBlueButton are digitally signed with the projects public key. Before installing BigBlueButton, you need to add the project’s public key to your server so apt-get can validate the signed packages. To do this, enter the following command.
$ sudo apt-get install bigbluebutton That’s it. This single command will install all of BigBlueButton’s core components along with all their required dependencies. When prompted to proceed, type ‘Y’ and press ENTER.
Note: During install, you may see an error “Failure to download extra data files” for the ttf-mscorefonts-installer package. This is a with Ubuntu 16.04.
You can ignore this error. If the installation exits with an error before finishing, go through the checks in to see if there is a configuration error with the server. If you find an resolve any configuration errors, you can attempt to finish the installation using the command sudo apt-get install -f. After the installation finishes, restart BigBlueButton using the following command.
$ sudo apt-get install bbb-demo Once installed, you’ll be able to enter your name on the home page and click ‘Join’. This will join you into the default meeting called “Demo Meeting”. You can also check out the other examples by clicking the API examples link on the home page.
These are the same API demos installed at. To learn more about integrating BigBlueButton with your application, check out the. If this server is intended for production, you will want to. Restart your server You can restart and check your BigBlueButton server at any time using the commands. # bbb-conf -setip bigbluebutton.example.com Obtain an SSL certificate Before you can configure nginx on BigBlueButton to server content via HTTPS, you need to have a valid SSL certificate. A domain validated (sometimes called “class 1”) certificate with a 2048 bit RSA key and SHA-256 checksum is the current recommended minimum, and it should be sufficient. There are a number of providers that you could obtain a certificate from.
Many domain name sales companies also offer certificates. Some well known large providers of SSL certificates include Comodo, Symantec, GoDaddy, GlobalSign, and DigiCert. In addition, free SSL certificates are available from StartSSL and CACert, with some caveats: StartSSL certificates can’t be revoked without paying a service fee, and most people do not have the root for CACert installed in their web browser.
Each provider will give you a series of steps for generating the certificate, but they will normally include generating a private key and certificate request locally, sending the certificate request to be signed, and then receiving back the signed certificate after they have performed any required verification steps. To install the certificate in BigBlueButton, you will need to have files for the certificate, private key, and any intermediate certificates in PEM format. If you don’t yet have a SSL certificate and your server is on the Internet, you can use Let’s Encrypt to obtain a free renewable SSL certificate (expires after 90 days, but are automatically renewable). If you want to use Let’s Encrypt, then skip to. Configure nginx to use HTTPS Depending on your certificate authority (CA), you should now have 2 or more files, as follows:. Certificate.
Private key. Intermediate certificate (there may be more than one, or could be none) The next step is to install the files on the server. Create the directory /etc/nginx/ssl.
# mkdir /etc/nginx/ssl And now create the private key file for nginx to use (replace the hostname in the filename with your own). In addition, fix the permissions so that only root can read the private key: # cat /etc/nginx/ssl/bigbluebutton.example.com.key /etc/nginx/ssl/bigbluebutton.example.com.crt.
# sed -e 's -i /var/www/bigbluebutton/client/conf/config.xml Next, modify the creation of recordings so they are served via HTTPS. Edit /usr/local/bigbluebutton/core/scripts/bigbluebutton.yml and change the value for playbackprotocol as follows: playbackprotocol: https If you have installed the API demos in, edit /var/lib/tomcat7/webapps/demo/bbbapiconf.jsp and change the value of BigBlueButtonURL use HTTPS. // This is the URL for the BigBlueButton server String BigBlueButtonURL = ' Finally, to apply all of the configuration changes made, you must restart all components of BigBlueButton. # bbb-conf -restart Test your HTTPS configuration In order to ensure you didn’t make any mistakes that could cause security compromises, please test your HTTPS configuration. A well-respected site that can do a series of automated tests is - simply enter your server’s hostname, optionally check the “Do not show results” check box if you would like to keep it private, then Submit. At time of writing, the configuration shown on this page should achieve an “A” ranking in the SSL Labs test page. Using Let’s Encrypt If you have a domain name assigned to your BigBlueButton server (i.e.
Bigbluebutton.example.com) and the server is on the Internet, then can use Let’s Encrypt to obtain a free SSL certificates. First, install Let’s Encrypt configuration tool. Please run all commands in this section root. # letsencrypt -webroot -w /var/www/bigbluebutton-default/ -d bigbluebutton.example.com certonly IMPORTANT NOTES: - Congratulations!
Your certificate and chain have been saved at /etc/letsencrypt/live/bigbluebutton.example.com/fullchain.pem. Your cert will expire on 20XX-YY-ZZ. To obtain a new version of the certificate in the future, simply run Let's Encrypt again. If you like Let's Encrypt, please consider supporting our work by: Donating to ISRG / Let's Encrypt: Donating to EFF: This will generate the following files. # ls /etc/letsencrypt/live/bigbluebutton.example.com/ cert.pem chain.pem fullchain.pem privkey.pem Next, edit the nginx configuration file /etc/nginx/sites-available/bigbluebutton and add the marked lines below.
Ensure that you’re using the correct filenames to match the certificate and key files you created above (again, replace bigbluebutton.example.com with your hostname). 30 2. 1 /usr/bin/letsencrypt renew /var/log/le-renew.log 35 2. 1 /bin/systemctl reload nginx These two directives will execute the letsencrypt-auto renew command every Monday at 2:30 am, and then reload Nginx at 2:35am (so the renewed certificate will be used). The output will be piped to a log file located at /var/log/le-renewal.log, so you can always check it later. To finish the SSL configuration, continue with the steps at. Configure BigBlueButton behind a firewall Updating FreeSWITCH configuration As described in the introduction, a common setup is to have your BigBlueButton server behind a firewall (either virtual or physical).
In this configuration, the network setup resembles the following diagram (yours would have different IP address of course). For WebRTC audio to work, you need to change the configuration of FreeSWITCH to listen for connections on the external IP address of the firewall. If you haven’t modified your firewall to forward ports to your BigBlueButton server, see. With the firewall configured to forward incoming connections to the BigBlueButton server, the next step is to configure FreeSWITCH to bind to the firewall’s external IP address. Edit the following files and substitute EXTERNALIPADDRESS for the external IP address (not the external hostname). Edit /opt/freeswitch/conf/vars.xml, and change.
# cat /usr/share/meteor/bundle/programs/server/assets/app/config/settings-production.json grep enableListenOnly 'enableListenOnly': true then Kurento is providing a listen only audio stream for users of the HTML5 client (just as red5 provides listen only audio stream for Flash users). In this case, edit /usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml change the value to ip to match the external IP address of the server.
For example, if the servers external IP address is 203.0.113.1, then edit this file so the value for ip is as follows. # bbb-conf -restart To test, launch FireFox and try connecting to your BigBlueButton server and join the audio. If you see the words ‘ WebRTC Audio ’ in the lower right-hand corner, it worked. If it didn’t work, there are two likely error messages when you try to connect with audio. Detected the following WebRTC issue: Error 1002: Could not make a WebSocket connection. Do you want to try Flash instead? ErrorDetected the following WebRTC issue Probable Cause 1002: Could not make a WebSocket connection Note 1 1007: ICE negotiation failed Note 2 For Error 1002, check IP address for proxypass in /etc/bigbluebutton/nginx/sip.nginx is pointing to the external IP address of the firewall.
# curl -trace-ascii - -k Info: Trying 203.0.113.1. # ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo validlft forever preferredlft forever inet EXTERNALIPADDRESS/32 scope global lo validlft forever preferredlft forever inet6::1/128 scope host validlft forever preferredlft forever You should see the EXTERNALIPADDRESS for your firewall listed above. Next, edit /opt/freeswitch/conf/sipprofiles/external.xml and ensure the value for wss-binding uses the external IP address. # The loopback network interface auto lo iface lo inet loopback post-up ip addr add EXTERNALIPADDRESS/32 dev lo pre-down ip addr del EXTERNALIPADDRESS/32 dev lo The above will enable users outside the firewall to access your BigBlueButton server. For users themselves who are behind a firewall, you will want to setup a TURN server (next section). Setup a TURN server BigBlueButton normally requires a wide range of UDP ports to be available for WebRTC communication. In some network restricted sites or development environments, such as those behind NAT or a firewall that restricts outgoing UDP connections, users may be unable to make outgoing UDP connections to your BigBlueButton server.
The is designed to allow UDP-based communication flows like WebRTC to bypass NAT or firewalls by having the client connect to the TURN server, and then have the TURN server connect to the destination on their behalf. In addition, the TURN server implements the STUN protocol as well, used to allow direct UDP connections through certain types of firewalls which otherwise might not work. Using a TURN server under your control improves the success of connections to BigBlueButton and also improves user privacy, since they will no longer be sending IP address information to a public STUN server. Required Hardware The TURN protocol is not CPU or memory intensive. Additionally, since it’s only used during connection setup (for STUN) and as a fallback for users who would otherwise be unable to connect, the bandwidth requirements aren’t particularly high. For a moderate number of BigBlueButton servers, a single small VPS is usually sufficient.
Having multiple IP addresses may improve the results when using STUN with certain types of firewalls, but is not usually necessary. Having the server behind NAT (for example, on Amazon EC2) is OK, but all incoming UDP and TCP connections on any port must be forwarded and not firewalled. Required Software We recommend using a minimal server installation of Ubuntu 18.04 where possible. (Ubuntu 16.04 is also ok, but includes an older version of coturn.) The software requires port 443 for its exclusive use in our recommended configuration, which means the server cannot have any dashboard software or other web applications running. Coturn is already available in the Ubuntu packaging repositories for version 16.04 and later, and it can be installed with apt-get.
Sudo apt-get update sudo apt-get install coturn Note: coturn will not automatically start until configuration is applied (see below). Required DNS Entry You need to setup a fully qualified domain name that resolves to the external IP address of your turn server. You’ll used this domain name to generate a TLS certificate using Let’s Encrypt (next section). Generating TLS certificates You can use certbot from to easily generate free TLS certificates.
To setup certbot enter the following commands on your TURN server (not your BigBlueButton server). Sudo certbot certonly -standalone -preferred-challenges http -deploy-hook 'systemctl restart coturn' -d turn.example.com Current versions of the certbot command set up automatic renewal by default. Note that when certbot renews the certificate, it will restart coturn so coturn will start to use the updated certificate files. This will interrupt any ongoing TURN connections. You may wish to change the schedule of certbot renewals or disable automatic renewal if this is a concern. Configure coturn coturn configuration is stored in the file /etc/turnserver.conf. There are a lot of options available, all documented in comments in that file.
We include a sample configuration below with comments indicating the recommended settings, with some notes in locations where customization is required. You can repace the contents /etc/turnserver.conf with this file and make two changes:. Replace turn.example.com with the hostname of your TURN server, and. Replace to a random value for a shared secret (instructions for generating a new secret are in a comment in the file). # Example coturn configuration for BigBlueButton # These are the two network ports used by the TURN server which the client # may connect to. We enable the standard unencrypted port 3478 for STUN, # as well as port 443 for TURN over TLS, which can bypass firewalls.
Listening-port =3478 tls-listening-port =443 # If the server has multiple IP addresses, you may wish to limit which # addresses coturn is using. Do that by setting this option (it can be # specified multiple times). The default is to listen on all addresses. # You do not normally need to set this option. #listening-ip=172.17.19.101 # If the server is behind NAT, you need to specify the external IP address. # If there is only one external address, specify it like this: #external-ip=172.17.19.120 # If you have multiple external addresses, you have to specify which # internal address each corresponds to, like this. The first address is the # external ip, and the second address is the corresponding internal IP.
#external-ip=172.17.19.131/10.0.0.11 #external-ip=172.17.18.132/10.0.0.12 # Fingerprints in TURN messages are required for WebRTC fingerprint # The long-term credential mechanism is required for WebRTC lt-cred-mech # Configure coturn to use the 'TURN REST API' method for validating time- # limited credentials. BigBlueButton will generate credentials in this # format. Note that the static-auth-secret value specified here must match # the configuration in BigBlueButton's turn-stun-servers.xml # You can generate a new random value by running the command: # openssl rand -hex 16 use-auth-secret static-auth-secret = # If the realm value is unspecified, it defaults to the TURN server hostname. # You probably want to configure it to a domain name that you control to # improve log output. There is no functional impact. Realm =example.com # Configure TLS support.
Restart your BigBlueButton server to apply the changes. Going forward, when users connect behind a restrictive firewall that prevents outgoing UDP connections, the TURN server will enable BigBlueButton to connect to FreeSWITCH and Kurento via the TURN server through port 443 on their firewall.
Upgrading from an earlier build Upgrading from 1.0 (or earlier) If you want to upgrade a BigBlueButton 1.0 (or earlier) server, which ran on Ubuntu 14.04 64-bit, we recommend to starting with a new Ubuntu 16.04 64-bit server, installing BigBlueButton on it,. Upgrading from 1.1 to 2.0 To upgrade your BigBlueButton server from 1.1 to 2.0, login to the 1.1 server via SSH and edit the file /etc/apt/sources.list.d/bigbluebutton.list. Edit the line to read. Sudo bbb-conf -setip sudo bbb-conf -check The use of sudo bbb-conf -setip will ensure that all configuration files are updated with the servers hostname (or IP address if you are not using a hostname for your server). Common Customizations There are a number of common customizations that administrators do to their BigBlueButton server after inital install. Remove the API demos If you are setting up a production server with custom front-end, you will want to remove the API demos after testing.
To remove the API demos, enter the command. $ bbb-conf -secret URL: Secret: 577fd5f05280c10fb475553d200f3322 Link to the API-Mate: The link to API-Mate is an excellent tool provided by, a company that has made many contributions to the BigBlueButton project over the years.
API-Mate lets you interactively create API calls to test your server. Assign a hostname For any production BigBlueButton server, you need to assign it a hostname. If you have not done so already, you need to purchase a domain name from a domain name service (DNS) provider and, using the provider’s web interface, configure an A record to point to your server’s IP address (see the documentation for your DNS provider on how to do this step). After the A record is setup, enter the following command and EXTERNALHOSTNAME with the hostname of your BigBlueButton server. $ ping demo.bigbluebutton.org PING demo.bigbluebutton.org (146.20.105.32) 56(84) bytes of data. 64 bytes from 146.20.105.32: icmpseq=1 ttl=44 time=27.5 ms Note: If your server doesn’t allow ICMP traffic, then no bytes will be returned, but you should see your server’s IP address returned in the brackets after the hostname. If the hostname is resolving to the server’s IP address (or the IP address of the firewall), next use the BigBlueButton configuration utility bbb-conf to update BigBlueButton’s configuration files to use this hostname.
$ sudo bbb-conf -setip bigbluebutton.example.com At this point, you have BigBlueButton server listening to an IP address (or hostname) and responding to API requests. However, if you tried to login from the server’s default page with a browser, you would get an error HTTP Status 404 - /demo/demo1.jsp. The BigBlueButton server comes ready to list to API calls, but doesn’t have a front-end installed by default. You can easily install the API demos to test the server. We’ll cover installing the API demos in the next step. However, you don’t need the API demos if you intend to use another for the BigBlueButton server, for example, if you have a Moodle server and you want to configure the to access the BigBlueButton server.
Modify the default landing page The default HTML landing page is located in. /var/www/bigbluebutton-default/index.html Change this page to create your own landing page. Use the GreenLight front-end BigBlueButton comes with GreenLight, a simple front-end application that let’s users quickly and easily create meetings, invite others, join meetings, and manage the recordings. For more information see.
Install the HTML5 client The BigBlueButton project has been activly developing an HTML5 client for mobile and desktop devices. While the HTML5 client is initially targeting viewers os, it can upload documents, make a user presenter, share screen, and start/stop recording – all the functionalty needed to run a meeting. For more information on the HTML5 client, along with links to install steps, see. Enable background music when only one person is in a session FreeSWITCH enabled you to have music play when only one users is in the voice conference. To enable background music, edit /opt/freeswitch/conf/autoloadconfigs/conference.conf.xml (as root). And around line 204 you’ll see the music on hold (moh-sound) commented out. # bbb-conf -restart and join an audio session.
You should now hear music on hold if there is only one user in the session. Add a phone number to the conference bridge The built-in WebRTC-based audio in BigBlueButton is very high quality audio.
Still, there may be cases where you want users to be able to dial into the conference bridge using a telephone number. Before you can configure FreeSWITCH to route the call to the right conference, you need to first obtain a phone number from a and configure FreeSWITCH accordingly to receive incoming calls via session initiation protocol (SIP) from that provider. To route the incoming call to the correct BigBlueButton audio conference, you need to create a dialplan which, for FreeSWITCH, is a set of instructions that it runs when receiving an incoming call. When a user calls the phone number, the dialplan will prompt the user to enter a five digit number associated with the conference. To create the dialplan, use the XML below and save it to /opt/freeswitch/conf/dialplan/public/myprovider.xml. Replace EXTERNALDID with the phone number phone number given to you by your Internet Telephone Service Provider (such as ).
Beans.dynamicConferenceService.securitySalt = To change the shared secret, do the following:. Generate a new Universal Unique ID (UUID) from a UUID generator such as at. This will give a long string of random numbers that will be impossible to reverse engineer. Run the command sudo bbb-conf -setsecret newsecret. Note: If you have created you own front-end or are using a to connect to BigBlueButton, its shared secret; otherwise, if the shared secrets do not match, the checksum for the incoming API calls will not match and the BigBlueButton server will reject the API call with an error. Change the default presentation When a new meeting starts, BigBlueButton displays a default presentation.
The file for the default presentation is located in /var/www/bigbluebutton-default/default.pdf. You can replace the contents of this file with your presentation. Whenever a meeting is created, BigBlueButton will automatically load, convert, and display this presentation for all users. Alternatively, you can change the global default by editing /var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties and changing the URL for beans.presentationService.defaultUploadedPresentation. DefaultWelcomeMessage= defaultWelcomeMessageFooter= When a front-end creates a BigBlueButton session, it may also pass a welcome parameter in the API call.
The final welcome message shown to the user (as blue text in the Chat window) is a composite of welcome + defaultWelcomeMessage + defaultWelcomeMessageFooter. The welcome message is fixed for the duration of a meeting. If you want to see the effect of changing the welcome parameter, you must the current meeting or wait until the BigBlueButton server removes it from memory (which occurs about two minutes after the last person has left). If you change the parameters in bigbluebutton.properties, you must restart BigBlueButton with sudo bbb-conf -restart for the new values to take effect. Other configuration options Increase the file size for an uploaded presentation The default maximum file upload size for an uploaded presentation is 30 MB. To increase this size, edit /var/www/bigbluebutton/client/conf/config.xml and edit maxFileSize` to the new value (note: if you have the development environment you need to edit /dev/bigbluebutton/bigbluebutton-client/src/conf/config.xml and then rebuild the client). Next, change the corresponding limit in nginx.
Edit /etc/bigbluebutton/nginx/web.nginx and modify the value for clientmaxbodysize. Location /bigbluebutton proxypass proxyredirect default; proxysetheader X-Forwarded-For $proxyaddxforwardedfor; # Allow 30M uploaded presentation document. Clientmaxbodysize 30m; Restart BigBlueButton with sudo bbb-conf -restart. You should now be able to upload larger presentations within the new limit.
Turn off the “comfort noise” when no one is speaking FreeSWITCH applies a “comfort noise”’” that is a slight background hiss to let users know they are still in a voice conference even when no one is talking (otherwise, they may forget they are connected to the conference bridge and say something unintended for others). If you want to remove the comfort noise, edit /opt/freeswitch/conf/autoloadconfigs/conference.conf.xml and change.
Timer # Disable the default timer OnUnitInactiveSec= # Run every minute from 18:00 to 05:59 OnCalendar=18,19,20,21,22,23,00,01,02,03,04,05:. and save the file. See the man page systemd.time (under CALENDAR EVENTS) for more details about the syntax for OnCalendar=. Transfer existing published recordings If you want to do the minimum amount of work to quickly make your existing recordings on an older BigBlueButton server, transfer the contents of the /var/bigbluebutton/published and /var/bigbluebutton/unpublished directories. In addition, to preserve the backup of the original raw media, you should transfer the contents of the /var/bigbluebutton/recording/raw directory. Here is an example set of rsync commands that would accomplish this; run these on the new server to copy the files from the old server. $ rsync -rP root@old-bbb-server:/var/bigbluebutton/published/ /var/bigbluebutton/published/ $ rsync -rP root@old-bbb-server:/var/bigbluebutton/unpublished/ /var/bigbluebutton/unpublished/ $ rsync -rP root@old-bbb-server:/var/bigbluebutton/recording/raw/ /var/bigbluebutton/recording/raw/ Other methods of transferring these files can also be used; for example, you could create a tar archive of each of the directories, and transfer it via scp, or use a shared NFS mount.
You will then need to fix the permissions on the newly copied recordings. $ bbb-conf -setip bigbluebutton.example.com The transferred recordings should be immediately visible via the BigBlueButton recordings API. Re-process raw recordings After transfer of recordings (see above), view a sampling of the recordings to ensure they playback correctly (they should). If you have transferred over the raw content, you can also reprocess the recordings using the newer scripts to rebuild them with the latest playback format (including any bug fixes made in the latest version). Note: Re-processing can take a long time (around 25% to 50% of the original length of the recordings), and will use a lot of CPU on your new BigBlueButton server while you wait for the recordings to process. If you are interested in reprocessing the older recordings, try it first with one or two of the larger recordings.
If there is no perceptible difference, you don’t need to reprocess the others. If your old server has all of the original recording files in the /var/bigbluebutton/recording/raw directory, then you can transfer these files to the new server, for example with rsync: This example rsync command could be run on the new server, and will copy the recording file from the old server. CamQualityPicture='70' To reduce the quality of the picture (and increase the frame rate), lower the value of camQualityPicture. Corresponding, to increase the quality of the picture (and reduce the frame rate), increase the value of camQualityPicture.
However, as camQualityPicture is already ninety percent, you’ll find that slight increases are not very noticeable in picture quality, but do decrease the frame rate. You can change the video quality through the client’s config.xml file, by default located in /var/www/bigbluebutton/client/conf. Scroll down to the entry named VideoconfModule. The value of the videoQuality attribute can be anywhere from 0 to 100. 0 means priority is given to the bandwidth and if bandwidth is low, quality will suffer.
Quality of 100 means no video compression will be done at all, and you will get maximum quality at the expense of bandwidth. If the bandwidth is low, the frame rate will suffer.
For more information see. Change the /client/BigBlueButton.html portion of the URL Using nginx, you can rewrite the incoming URL for /client/BigBlueButton.html to appear as a different link, such as /conference/. First, modify /etc/bigbluebutton/nginx/client.nginx and comment out the following section. Sudo systemctl restart nginx Now login to the demo page and you’ll see the URL now shows /conference/ instead of /client/BigBlueButton.html.
Always record every meeting By default, the BigBlueButton server will produce a recording when (1) the meeting has been created with record=true in the create API call and (2) a moderator has clicked the Start/Stop Record button (at least once) during the meeting. However, you can configure a BigBlueButton server to record every meeting, edit /var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties and change.
The Right Technology Stack for the Job at Hand Developers are constantly challenged with choosing the most effective runtime, programming model, and architecture for their application's requirements and team's skill set. For example, some are best handled by a technology stack based on synchronous blocking I/O architecture, whereas others would be better served by an asynchronous, nonblocking stack built on the reactive design principles described in the. Reactive Spring represents a platform-wide initiative to deliver reactive support at every level of the development stack: web, security, data, messaging, etc. Spring Framework 5 delivers on this vision by providing a new reactive web stack called Spring WebFlux, which is offered side by side with the traditional Spring MVC web stack.
The choice is yours!