|
ClientConfiguration
Configuring bbb-client.
NOTE: This doc is in the process of being updated.IntroductionA detailed discussion of the client's config.xml file. This document shows you how to configure the client to work to your liking, and what options are available. Config.xmlThe config.xml file is located in the deployed client directory, default location /var/www/bigbluebutton/client/conf/config.xml. If you are working with the source code, it is located in the client's src/conf directory, default location /home/firstuser/dev/source/bigbluebutton/bigbluebutton-client/src/conf/config.xml. Open up the config.xml file. This is a line by line discussion of it's properties, applicable for version 0.8. The template can be found here Main parameters <localeversion suppressWarning="false">0.8-beta4</localeversion>
<version>VERSION</version>
<help url="http://HOST/help.html"/>
<porttest host="HOST" application="video"/>
<application uri="rtmp://HOST/bigbluebutton" host="http://HOST/bigbluebutton/api/enter" />
<language userSelectionEnabled="true" />
<skinning enabled="false" url="branding/css/theme.css.swf" />
<layout showLogButton="false" showVideoLayout="false"
showResetLayout="true" showToolbar="true"
showHelpButton="true" showLogoutWindow="true"/><localeversion suppressWarning="false">0.8-beta4</localeversion> This should be left as is. It has to do with the client caching localization files. If you're having problems with the Warning Dialog for old localizations, you can set the suppressWarning parameter to true. <version>VERSION</version> This has to do with the caching of the client as a whole. Should also be left alone, in general. <help url="http://HOST/help.html"/> This is the url that you would like users redirected to when they click the Help button in the client. <porttest host="HOST" application="video"/> The ip and red5 application the client uses to test whether necessary ports are open, and determine whether tunneling should be used. The host should be your bbb server ip. The application should be left as video. <application uri="rtmp://HOST/bigbluebutton" host="http://HOST/bigbluebutton/api/enter" /> The url that the client queries for the user information when the user joins the meeting. <language userSelectionEnabled="true" /> This enables/disables the language selector combo box in the client. Enable this if you would like your users to be able to select the language of their BigBlueButton client themselves instead of the language being detected automatically for them. <skinning enabled="false" url="branding/css/theme.css.swf" /> Set enabled to true and set the url to the swf file with your theme modifications. This enables/disables skinning support for the client. If the value is false, the url attribute will be ignored. Otherwise the url attribute specifies the compiled CSS file to load on startup. See Branding for more details. <layout showLogButton="false" showVideoLayout="false"
showResetLayout="true" showToolbar="true"
showHelpButton="true" showLogoutWindow="true"/>showLogButton="false" Show or hide the button (lower right-hand corner) to display the debug window. If you are running BigBlueButton 0.8, see showLogButton. showVideoLayout="false" Show or hide the video layout button on the lower-right corner of the client. showResetLayout="true" Show or hide the reset layout button on the lower-right corner of the client. showToolbar="true" Show or hide the main toolbar on the top part of the client. showHelpButton="true" Show the help button on the main toolbar. showLogoutWindow="true" Show the logout window when the client logs out. ModulesThe BigBlueButton client is comprised of one or more modules. You can specify which modules you would like loaded in the config.xml file. The modules will be loaded at startup. The properties for the different currently available modules are shown here in no particular order. Most of the modules share certain attributes: nameThe unique name of the module urlThe url to the compiled module .swf file. Usually has a version appended to it, to prevent caching of old version when a new version of BigBlueButton is released. uriThe uri the module will connect to using rtmp. This is usually your bbb server ip with /bigbluebutton appended to it. Apart from making sure the ip is correct, you don't have to worry about it. depends onOptional parameter that should be included in the case that the module being loaded depends on another BigBlueButton module being loaded first in order to work properly. windowVisibleSet to false to hide the window. positionLocation of module on the screen. There are a number of pre-defined positions that you can assign a module to change its layout.
Chat Module<module name="ChatModule" url="ChatModule.swf?v=VERSION" uri="rtmp://HOST/bigbluebutton" dependsOn="ViewersModule" translationOn="false" translationEnabled="false" privateEnabled="true" position="top-right" /> translationOnDetermines whether the automatic translation of Chat messages to the users' language on by default. If true, all messages the user receives in the chat will be translated to their detected or selected language. The users can see the original message by rolling over the message in the Chat. They can also disable the translation in the '+' Tab of the chat window. NOTE This feature won't work because Google has stopped the translate service. translationEnabledIf set to true, the user will have the option of enabling/disabling automatic translation from the '+' Tab in the chat window. They will also be able to detect the language they want their messages translated to. privateEnabledSet to true to enable private chat. Viewers Module<module name="ViewersModule" url="ViewersModule.swf?v=VERSION" uri="rtmp://HOST/bigbluebutton" host="http://HOST/bigbluebutton/api/enter" allowKickUser="false" windowVisible="true" /> allowKickUserDetermines whether or not the Moderators of the meeting are able to kick a user from the conference. If set to true, a Moderator will be given the option of kicking a selected user from the conference by clicking on their name and the Kick button inside the Viewers window. windowVisibleWhether the viewers window will be displayed or not. Listeners Module <module name="ListenersModule" url="ListenersModule.swf?v=VERSION"
uri="rtmp://192.168.0.36/bigbluebutton"
recordingHost="http://192.168.0.36"
windowVisible="true"
position="bottom-left"
/>
The Listeners Module is the window which shows who is currently connected to the voice conference in the Listeners window. Nothing special here. The recordingHost attribute is not functioning and should be removed. Desktop Sharing <module name="DeskShareModule"
url="DeskShareModule.swf?v=VERSION"
uri="rtmp://192.168.0.36/deskShare"
autoStart="false"
/>The Desktop Sharing module. Note that it connects to /deskShare, which is a red5 application on the server separate from the /bigbluebutton application. autoStartSet to true to automatically start the desktop sharing module. Phone Module <module name="PhoneModule" url="PhoneModule.swf?v=VERSION"
uri="rtmp://192.168.0.36/sip"
autoJoin="true"
skipCheck="false"
showButton="true"
enabledEchoCancel="true"
dependsOn="ViewersModule"
/>
The Phone Module is the shows as the small headset icon in the upper left of the client. It allows users to join the meeting through VoIP by using a headset. Note again the separate /sip server side application. autoStartSet to true to show the button in the title bar. autoJoinSet to true to have the user automatically join the voice conference bridge. showButtonSet to true to have the headset icon visible on the toolbar. enabledEchoCancelSet to true to enable the acoustic echo cancellation. Videoconf Module<module name="VideoconfModule" url="VideoconfModule.swf?v=VERSION" uri="rtmp://HOST/video" dependsOn="ViewersModule" videoQuality="70" presenterShareOnly="false" resolutions="320x240,640x480,1280x720" autoStart="false" showButton="true" publishWindowVisible="true" viewerWindowMaxed="false" viewerWindowLocation="top" camKeyFrameInterval="5" camModeFps="15" camQualityBandwidth="0" camQualityPicture="70" h264Level="4.1" h264Profile="main" /> The Video Conferencing Module. Allows users to share their webcams with the room. It connects to the separate /video application on the bbb server. videoQualityAn attribute set to between 0 and 100. 0 means that priority will be given to optimizing bandwidth at the cost of quality. 100 means that no compression will be done, for maximum quality. This takes up high bandwidth and the frame rate may suffer. A quality of 100 is NOT recommended as it will eat up your server bandwidth quickly. Default is 70. Set to lower if you are concerned about bandwidth. presenterShareOnlyIf set to true, only the current presenter will have the option of sharing their webcam. This is useful in one-to-many meetings, where there is one presenter that everyone should be focusing on, such as a webcast or a virtual classroom. resolutionsConfigure the resolutions you want the user to choose from. autoStartStart the webcam automatically. This will choose the first option in the resolutions entry. showButtonShow button in main toolbar. publishWindowVisibleMake the webcam publish window visible. If you set to false, you need to make autoStart to true. Otherwise, you won't be able to start camera. viewerWindowMaxedMaximize the webcam viewer window. viewerWindowLocationSet the preferred location of the viewer window when it pops up. camKeyFrameInterval, camModeFps, camQualityBandwidth, camQualityPictureConfigure quality and framerate of webcam. See http://help.adobe.com/en_US/FlashPlatform/beta/reference/actionscript/3/flash/media/Camera.html h264Level, h264ProfileNOTE You need to uncomment and compile source to make this work. This only works on Flash Player 11 (still in Beta). See the following: http://help.adobe.com/en_US/FlashPlatform/beta/reference/actionscript/3/flash/media/H264Level.html http://help.adobe.com/en_US/FlashPlatform/beta/reference/actionscript/3/flash/media/H264Profile.html Videodock ModuleThis module will dock viewed webcams and and tile them. <module name="VideodockModule" url="VideodockModule.swf?v=VERSION"
uri="rtmp://192.168.0.36/bigbluebutton"
dependsOn="VideoconfModule, ViewersModule"
autoDock="true"
maximizeWindow="false"
position="bottom-right"
width="172"
height="179"
layout="smart"
oneAlwaysBigger="false"
/>autoDockAutomatically dock all webcam windows. maximizeWindowMaximize the docking window. oneAlwaysBiggerAlways have one of the video windows bigger. Present Module <module name="PresentModule" url="PresentModule.swf?v=VERSION"
uri="rtmp://192.168.0.36/bigbluebutton"
host="http://192.168.0.36"
showPresentWindow="true"
showWindowControls="true"
dependsOn="ViewersModule"
/>
The Presentation Module which lets users share slides and other documents in the main viewing area inside of BigBlueButton. showPresentWindowSet true to show the presentation window. showWindowControlsSet true to show the presentation window controls. Whiteboard Module<module name="WhiteboardModule" url="WhiteboardModule.swf?v=VERSION" uri="rtmp://192.168.0.225/bigbluebutton" dependsOn="PresentModule" /> The Whiteboard Module is a transparent overlaid canvas on top of the presentation window. It allows users to draw annotations on top of uploaded slides and documents. Dynamic Info Module<module name="DynamicInfoModule" url="DynamicInfoModule.swf?v=VERSION"
uri="rtmp://192.168.0.225/bigbluebutton"
host="http://192.168.0.225"
infoURL="http://HOST/client/conf/example-info-data.xml?user={userID}&role={role}&meetingID={meetingID}"
/>An experimental module that allows you to inject custom data into the conference. Example Chat Module<module name="ExampleChatModule" url="ExampleChatModule.swf?v=56"
uri="rtmp://192.168.0.225/bigbluebutton"
host="http://192.168.0.225"
/>A rudimentary module meant to provide sample code on how to build your own BigBlueButton module. For more information see SampleModule Breakout Module<module name="BreakoutModule" url="BreakoutModule.swf?v=VERSION" uri="rtmp://192.168.0.225/bigbluebutton" host="http://192.168.0.225" dependsOn="ViewersModule" salt="1708e5ecf25b7142b06f2338b4ea3cf1" /> The Breakout Module allows the Moderator of the meeting to create and launch users of a meeting into other rooms. This is useful when you have a large meeting or a classroom which you would like to separate into smaller collaborative groups. This module uses the BigBlueButton API. saltThe security salt needed to create meeting. This is required by the BigBlueButton API. By default, the salt is found in /var/lib/tomcat/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties | |