Installation Guide. conferencing software

Transcription

1 Installation Guide conferencing software

2 Trademark Notice Bridgit, smarttech, SMART Board and the SMART logo are either trademarks or registered trademarks of SMART Technologies ULC. in the U.S. and/or other countries. Windows is either a registered trademark or a trademark of Microsoft Corporation in the U.S. and/or other countries. Macintosh is a trademark of Apple Computer Inc., registered in the U.S. and other countries. projectiondesign is a trademark of projectiondesign Norway as. All other third-party product and company names may be trademarks of their respective owners. Copyright Notice SMART Technologies ULC. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any language in any form by any means without the prior written consent of SMART. Information in this manual is subject to change without notice and does not represent a committment on the part of SMART. Patents pending. This product includes software developed by The OpenSSL Project. Copyright All right reserved. Portions of this product were created using CAMTASIA OEM SDK. Copyright TechSmith Corporation. All rights reserved. This product includes the Spidermonkey JavaScript interpreter, which is code covered by the Netscape Public License, v1.1. The original code is available from Audio licensed from Global IP Sound Inc. Portions Copyright Global IP Sound Inc. All rights reserved. Global IP Sound, GIPS, SoundWare, NetEQ, ipcm, isac and ilbc are trademarks owned or used under license by Global IP Sound Inc. Patents Pending, Global IP Sound Inc. If you have any questions about what constitutes legal use of this product, please consult the license agreement that came with your original software, or contact SMART Technologies. Version 3.4. Printed in Canada 10/2008

3 Table of Contents Introducing Bridgit Software 1 Bridgit Software Services... 1 Bridgit Software Administration Tools... 1 Server Clusters... 1 Minimum Server Requirements 2 Bridgit Server Software Port Configuration 3 Installing Bridgit Software 4 Starting the Bridgit Software Installation... 4 Installing a Master Server... 4 Installing a Conference Server... 6 Managing Software Licenses 9 Activating the Server License... 9 Activating User Licenses Removing Server or User Licenses Viewing Status Information 13 Viewing Active Conferences Viewing Server Performance Information Viewing Server Usage Reports Configuring the Master Server 17 Assigning Conference Viewing Passwords Assigning Conference Creation Passwords Assigning a Clustering Authentication Password Assigning an Administrator Access Password Assigning an Application Programming Interface (API) Authentication Password Disabling Remote Control Disabling Conference Audio REV B0 Table of Contents i

4 Disabling Webcams...22 Disabling Text Chat...22 Adding a Message of the Day...23 Changing Master Server Setup Options...23 Configuring Conference Servers 25 Changing the Clustering Authentication Password...25 Changing Conference Server Setup Options...26 Managing Servers and Conferences 27 Placing a Server On Hold and Reactivating It...27 Ending a Conference...27 Starting, Stopping, Pausing and Restarting Bridgit Software Services28 Distributing Bridgit Software Client 29 Customizing the Bridgit Software Web Page...29 Communications Security Overview 30 Secure Sockets Layer (SSL) Standard (Version 3.0)...30 Certificates...30 Contacting SMART 31 Online Support...31 Training...31 Contacting SMART Technical Support...31 General Inquiries...31 Registration...32 Sending Feedback...32 Index 33 ii Table of Contents REV B0

5 Introducing Bridgit Software Bridgit conferencing software is a client/server application used for sharing applications and information with anyone, anywhere in the world. This guide explains how to install, configure and maintain Bridgit servers. For information about Bridgit software client, refer to its online Help. Bridgit Software Services Bridgit server software includes two services: The master server service manages the list of active conferences and balances the user load on the conference servers. The conference server service transmits conference data between the server and its clients. Bridgit Software Administration Tools Bridgit server software also includes an Administration Tools application. You can use Bridgit Software Administration Tools to configure servers and monitor their performance, manage your Bridgit software licenses and change password, sharing and remote control settings. When you install Bridgit software on a master or conference server, a shortcut to Bridgit Software Administration Tools appears on the desktop. Server Clusters Bridgit software is scalable. By default, a master server installation includes a conference server. Both are necessary on the master server. You can create a server cluster by adding more conference servers. The master server balances the load of conferences and traffic across the conference server cluster. Before you can add conference servers to a cluster, you must assign a clustering authentication password on the master server (see page 19). You ll use this password each time you install an additional conference server REV B0 Introducing Bridgit Software 1

6 Minimum Server Requirements The maximum number of users that a server can support is constrained by both the server hardware and the bandwidth available to that server. Each speaker in a conference uses about 30 kilobits per second (Kbps); therefore, a 100 Mb network supports 200 users with the standard quality settings applied. The exact number of users supported may vary depending on the available bandwidth. Allowing more than the recommended number of simultaneous users may negatively impact performance. To support more users, cluster your servers. Your system performs best if you use a fast server or one with no other applications installed. In addition, each server must meet the following minimum requirements: Pentium III 500 MHz processor (or equivalent) Windows 2000, Windows XP or Windows Server 2003 operating system 256 MB RAM NOTE: For more information, see document , Bridgit Conferencing Software: Security, Firewalls, Bandwidth and Scalability. 2 Minimum Server Requirements REV B0

7 Bridgit Server Software Port Configuration For optimal performance, it s important to configure your firewall ports correctly. Enable both primary and secondary port TCP connections and a UDP connection for audio on the server. Enabling the secondary TCP port is important because port 80 (the default primary port) is commonly restricted to HTTP traffic only. Although Bridgit software clients can connect through port 80 using HTTP, performance will suffer. Enabling the secondary port allows an alternate connection that doesn t compromise performance. Wherever you install the Bridgit server on your network, you must ensure that both the primary and secondary ports are open for incoming TCP connections. We recommend that you don t use protocol filtering for these ports. However, you can restrict port 80 to HTTP if you keep the secondary port unrestricted. You can also disable the secondary port feature entirely, but some clients may experience poor performance. Whenever possible, Bridgit software uses a UDP network connection to transmit conference audio to minimize lag in a timing-sensitive environment. If you choose to enable a UDP connection, you must ensure that the range of UDP ports you ve chosen is open for incoming and outgoing traffic on your firewall. If you don t configure your server to allow UDP connections, Bridgit software automatically switches to a TCP connection for conference audio. However, a TCP connection s additional overhead can cause poor conference audio performance and increased audio lag REV B0 Bridgit Server Software Port Configuration 3

8 Installing Bridgit Software Starting the Bridgit Software Installation 1. Download Bridgit software from and then double-click the BridgitConferenceSoftware.exe file that you saved. OR Install the software using your Bridgit software CD. Installation should start automatically. However, if it doesn t automatically start, navigate to the CD folder and double-click Setup.exe. The Conferencing Software - Installshield Wizard opens and displays the licence agreement. 2. Read the license agreement, and if you agree, accept the agreement. 3. Choose one of the following installation options: Master Server. The master server manages the list of active conferences and balances the user load on the conference servers. All Bridgit software clusters must have one master server. NOTE: The master server installation automatically includes a conference server. Both are necessary on the master server. Conference Server. The conference server service manages data for individual conferences. Install one or more conference server(s) only if you re creating a Bridgit software cluster on multiple server computers. Installing a Master Server To install master server software 1. Choose the folder you want to install Bridgit software to (the default is C:\Program Files\Bridgit). 2. Customize the master server s basic configuration: a. IPv4 address and IPv6 address. The installation software detects all IP addresses assigned to the server. To use all the addresses, select All in the IPv4 address or IPv6 address boxes. 4 Installing Bridgit Software REV B0

9 If you select all addresses, Bridgit software clients can use any IP address assigned to the server computer to contact the Bridgit server. To restrict the IP addresses through which your server is reachable, select a specific IP address. b. Public domain name. The master server and all the conference servers each require a fully qualified domain name (for example, server.company.com or conference.company.com). NOTE: If you use the computer s name as the domain name, the server will be accessible only from within the local area network. Internet users won t have access to the server. Do not mix fully qualified domain names and computer names within the same server cluster. c. Primary TCP port. By default, the master server uses port 80 as its primary port. If your server is running another application that uses port 80, you must assign Bridgit software to an unoccupied port. Configure your firewall to allow incoming and outgoing TCP traffic on your chosen port. NOTE: If you configure Bridgit server software to use a TCP port that isn t the default, users must specify the port when connecting to the server. For example, to connect to a Bridgit software server on port 8080, users must type server.company.com:8080. d. Enable secondary TCP port. By default, the master server uses port If you want to use a different port, make sure it doesn t conflict with any other applications running on the server computer. e. Enable UDP ports (audio optimization). Whenever possible, Bridgit software uses UDP for audio transmission to avoid the additional overhead of TCP in a timing-sensitive situation. We strongly recommend that you enable UDP to minimize audio lag in Bridgit conferences. You must open this range of UDP ports on your firewall to use this feature. f. Conference viewing password. Assign a conference viewing password if you want users to type a password before they can view the list of active conferences on a server. NOTE: After you ve installed Bridgit server software, you can use Bridgit Software Administration Tools to create as many additional conference viewing passwords as you want REV B0 Installing Bridgit Software 5

10 g. Conference creation password. Assign a conference creation password if you want users to type a password before they can create a conference. Users who type the conference creation password can also see the list of active conferences on the server. NOTE: After you ve installed Bridgit server software, you can use Bridgit Software Administration Tools to create as many additional conference viewing passwords as you want. 3. Click Finish to complete the installation process. Master server installation adds the Bridgit Master Service and Bridgit Conference Service, and configures them to automatically start when the computer starts. See Starting, Stopping, Pausing and Restarting Bridgit Software Services on page 28 for information on controlling the services using the Windows services adminstration console. After you finish the installation process, use Bridgit Software Administration Tools to activate the server software, install user licenses, change the server settings and view performance information. IMPORTANT The Bridgit software installation includes a 30-day evaluation license for five concurrent users. See Managing Software Licenses on page 9 for information on installing and activating server and user licenses. Installing a Conference Server IMPORTANT Before you can install a conference server, you must install a master server and define the clustering authentication password using Bridgit Software Administration Tools on the master server (see Assigning a Clustering Authentication Password on page 19). 1. Choose the folder you want to install Bridgit software (the default is C:\Program Files\Bridgit). 2. Customize the master server s basic configuration: a. Master server IP address. Enter the master server s IP address here. This address is defined in the master server s configuration. 6 Installing Bridgit Software REV B0

11 b. Master server primary port. Change this setting only if you ve changed the master server s primary port from the default (port 80). c. Clustering authentication password. To join an existing Bridgit software cluster, you must type the clustering authentication password that s been assigned on the master server (see Assigning a Clustering Authentication Password on page 19). d. IPv4 address and IPv6 address. The installation software detects all IP addresses assigned to the server. To use all the addresses, select All in the IPv4 address or IPv6 address boxes. If you select all addresses, Bridgit software clients can use any IP address assigned to the server computer to contact the Bridgit server. To restrict the IP addresses through which your server is reachable, select a specific IP address. e. Public domain name. Conference servers require their own fully qualified domain names (for example, server.company.com or conference.company.com). NOTE: If you use the computer name for the domain name, the server will be accessible only from within the local area network. Internet users won t have access to the server. Do not mix fully qualified domain names and computer names within the same server cluster. f. Primary TCP port. By default, the master server uses port 80 as its primary port. If your server is running another application that uses port 80, you must assign Bridgit software to an unoccupied port. Configure your firewall to allow incoming and outgoing TCP traffic on your chosen port. NOTE: If you configure Bridgit server software to use a TCP port that isn t the default, users must specify the port when connecting to the server. For example, to connect to a Bridgit software server on port 8080, users must type server.company.com:8080. g. Secondary TCP port. By default, the conference server uses port If you wish to use a different port, you must make sure that it doesn t conflict with any other applications on the server computer. h. Audio UDP Ports. UDP ports are configured on the master server Changing Master Server Setup Options on page REV B0 Installing Bridgit Software 7

12 3. Click Finish to complete the installation process. Conference server installation adds the Bridgit Conference Service and configures it to automatically start when the computer starts. See Starting, Stopping, Pausing and Restarting Bridgit Software Services on page 28 for information on controlling the service using the Windows services adminstration console. After you finish the installation process, use Bridgit Software Administration Tools to activate the server software, install user licenses, change the server settings and view performance information. IMPORTANT The Bridgit software installation includes a 30-day evaluation license for five concurrent users. See Managing Software Licenses on page 9 for information on installing and activating server and user licenses. 8 Installing Bridgit Software REV B0

13 Managing Software Licenses During the 30-day free evaluation period, the server allows five concurrent user connections. After the evaluation version expires, users can no longer conduct conferences on the server. To continue using Bridgit software, purchase the software before the evaluation period expires. Visit to find out where you can buy Bridgit server software and concurrent user licenses. After you place an order, you ll receive an that includes serial numbers for activating the server software and user licenses. Five concurrent users can connect to a Bridgit software conference using a single server license. To allow more than five concurrent users, you must purchase additional user licenses. Activating the Server License NOTE: If you upgrade from Bridgit software version 2 to version 3, your version 2 licenses continue to work with Bridgit software version 3. However, Bridgit software s audio features (which are new to version 3) aren t available. To enable the audio features after you upgrade to version 3, purchase a Bridgit software audio upgrade license from your SMART authorized reseller. To automatically activate the server license 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Licensing tab. 3. In the Conference Servers table, select the server you want to activate. 4. Click the Install Server License button. 5. Type your serial number in the Serial number box, and then click OK. NOTE: Your serial number appears in the Sales Order Confirmation you received from SMART Technologies when you purchased the license. After you activate the serial number, your license information appears in the Licenses for selected server table and Server License Status changes to Activated REV B0 Managing Software Licenses 9

14 Bridgit conferencing software uses a Web service to automatically activate your Bridgit server license. If the service isn t available or if another error occurs, you must manually activate the license. To manually activate the server license 1. Right-click the server you wish to activate in the Licenses for selected server table, and then select Activate. 2. Select Activate manually, and then click Continue. A Manual Activation dialog box appears. 3. Click the To automatically generate an link. Your default software opens a new message addressed to support@smarttech.com. The message contains your serial number and installation ID that a Technical Support technician uses to create your activation key. 4. Send the . A support technician will send a reply with your activation key within 24 hours. 5. If you re not connected to the Internet, or if isn t available, click the If an does not appear link. A Manual Activation Assistance dialog box appears with SMART Technical Support telephone contact information, your serial number and your installation ID. When you call Technical Support, provide the support technician with these two numbers. 6. When you receive an activation key, type it in the Activation key box and click OK. After you activate the serial number, your license information appears in the Licenses for selected server table and Server License Status changes to Activated. 10 Managing Software Licenses REV B0

15 Activating User Licenses To automatically activate user licenses 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Licensing tab. 3. In the Conference Servers table, select the server you want to activate. 4. Click the Install User Licenses button. 5. Type your serial number in the Serial number box, and then click OK. NOTE: Your serial number appears in the Sales Order Confirmation you received from SMART Technologies when you purchased the user licenses. After you activate the serial number, your user license information appears in the Licenses for selected server table and User Licenses changes to Activated. Bridgit conferencing software uses a Web service to automatically activate your Bridgit server license. If the service isn t available or if another error occurs, you must manually activate the license. To manually activate user licenses 1. Right-click the server you wish to activate in the Licenses for selected server table, and then select Activate. 2. Select Activate manually, and then click Continue. A Manual Activation dialog box appears. 3. Click the To automatically generate an link. Your default software opens a new message addressed to support@smarttech.com. The message contains your serial number and installation ID that a Technical Support technician uses to create your activation key REV B0 Managing Software Licenses 11

16 4. Send the . A support technician will send a reply with your activation key within 24 hours. 5. If you re not connected to the Internet, or if isn t available, click the If an does not appear link. A Manual Activation Assistance dialog box appears with SMART Technical Support telephone contact information, your serial number and your installation ID. When you call Technical Support, provide the support technician with these two numbers. 6. When you receive an activation key, type it in the Activation key box, and then click OK. After you activate the serial number, license information appears in the Licenses for selected server table and User Licenses changes to Activated. Removing Server or User Licenses If you remove a server license or a bundle of user licenses, the serial number(s) remain valid and you can add them again at any time. To remove server or user licenses 1. Open Bridgit Software Administration Tools on the master server. 2. Right-click the licence you want to remove in the Licenses for selected server table, and then select Delete. A confirmation dialog box appears. 3. Click OK. 12 Managing Software Licenses REV B0

17 Viewing Status Information Use Bridgit Software Administration Tools to view status information for Bridgit software, including active conferences, server performance and server usage. NOTE: Status information on a conference server applies to that server only, while status information on the master server displays information for all servers in a Bridgit software cluster. Viewing Active Conferences To view active conferences 1. Open Bridgit Software Administration Tools on either the master server or a conference server. 2. Click the Conferences tab. A table of active conferences appears. The table includes the following information: when the conference was created. the conference s name. who created the conference. the number of participants. the conference server s domain name REV B0 Viewing Status Information 13

18 To broadcast a message to all conference participants 1. Open Bridgit Software Administration Tools on either the master server or a conference server. 2. Click the Conferences tab. 3. Select the conference to which you want to broadcast a message. 4. Click the Send Message button. 5. Type the message you want to broadcast in the Message box. 6. Click OK. A dialog box containing your message appears on the screen of each conference participant. To terminate a conference 1. Open Bridgit Software Administration Tools on either the master server or a conference server. 2. Click the Conferences tab. 3. Select the conference you want to terminate. 4. Click the End Conference button. 5. If you want to broadcast a message to conference participants as the conference ends, type it in the Message box. 6. Click OK. A notification dialog box and your message (if applicable) appears on the screen of each conference participant, and the conference ends. 14 Viewing Status Information REV B0

19 Viewing Server Performance Information 1. Open Bridgit Software Administration Tools on either the master server or a conference server. 2. Click the Performance tab. A detailed system performance summary appears. The table includes the following information: conference server IP address and domain name. conference traffic measured in kilobits per second (Kbps). the number of active conferences. the number of users connected (and the total number of licenses). The server s status, which can include the following: Status Description Alive The server is active and users can connect. The conference server isn t connected to the master Offline server. Users can t connect to this server. An Administrator has placed the server on hold On Hold (see Placing a Server On Hold and Reactivating It on page 27). Viewing Server Usage Reports Bridgit software automatically creates a server usage report for each conference server and saves the report in a file named BridgitActivityLog.txt in the Bridgit software installation folder on the conference server. NOTE: If you edit the Bridgit activity log file the Bridgit software logging service may become unstable. You can control how long the log stores information about server usage using the Logs purged after box. The default value is 30 days, which means that log entries older than 30 days are automatically deleted from the log. You can enter any setting between 1 and 120 days. You can also save the server usage report as a text file for the entire period or for a range of dates you select REV B0 Viewing Status Information 15

20 To view server usage reports 1. Open Bridgit Software Administration Tools on either the master server or a conference server. 2. Click the Report tab. A server usage report for the current week appears. 3. To view a report that spans a different period, select the Report start date and Report end date that you want, and then click the Refresh button. A comprehensive server usage report appears for the period you select. To save a server usage report as a text file 1. Open Bridgit Software Administration Tools on either the master server or a conference server. 2. Click the Report tab. A server usage report for the current week appears. 3. In the server usage report, select the entries you d like to save to a text file. OR Select no entries if you want to save the entire report. 4. Click the Save Report button. A Save As dialog box appears. 5. Choose a file name and destination for the report text file, and click OK. 16 Viewing Status Information REV B0

21 Configuring the Master Server You can use Bridgit Software Administration Tools on the master server to assign client access and server access passwords, create a message of the day, and enable remote control. Although these settings are automatically implemented on all your Bridgit software servers, you must configure them using Bridgit Software Administration Tools on the master server. In this section, you ll learn to: assign a conference viewing password (this page) assign a conference creation password (page 18) assign a clustering authentication password (page 19) assign an administrator s access password (page 20) assign an application programming interface (API) authentication password (page 20) disable remote control in conferences (page 21) disable audio in conferences (page 21) disable webcams in conferences (page 22) disable text chat in conferences (page 22) create a message of the day (page 23) change server options (page 23) Assigning Conference Viewing Passwords Conference viewing passwords are optional. Assign a conference viewing password if you want users to type a password before they can view the list of active conferences on a server. You can assign as many conference viewing passwords as necessary REV B0 Configuring the Master Server 17

22 To assign conference viewing passwords 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Security tab. 3. Select the Conference viewing password check box in the Client access passwords group box. 4. Type the password(s) you want to use. Use a semicolon to separate multiple passwords. NOTE: To revoke a password, remove it from the list. 5. Click Apply. Remember to give the password(s) to everyone who is authorized to view the list of active conferences. NOTE: Participants who receive an invitation to join a conference can click the link in the invitation to bypass the conference viewing password. However, the participant can only join the conference to which they were invited and they can t view the list of other active conferences on the server. Assigning Conference Creation Passwords Conference creation passwords are optional. Assign a conference creation password if you want users to type a password before they can create a conference. You can assign as many conference creation passwords as necessary. To assign conference creation passwords 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Security tab. 3. Select the Conference creation password check box in the Client access passwords group box. 4. Type the password(s) you want to use. Use a semicolon to separate multiple passwords. NOTE: To revoke a password, remove it from the list. 18 Configuring the Master Server REV B0

23 5. Click Apply. Remember to give the password(s) to everyone who is authorized to view the list of active conferences. Assigning a Clustering Authentication Password If you want to create a server cluster, you must first assign a clustering authentication password. You must type this password on any conference servers that you want to add to the cluster. To assign a clustering authentication password 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Security tab. 3. Select the Clustering authorization password check box in the Server access passwords group box. 4. Type the password you want to assign. You may only type one password. 5. Click Apply. IMPORTANT When you change the cluster authentication password on the master server, you must also change it on each conference server (see Changing the Clustering Authentication Password on page 25) REV B0 Configuring the Master Server 19

24 Assigning an Administrator Access Password Administrators can access and monitor any conference on any server in a Bridgit software cluster using an administrator access password. To assign an administrator access password 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Security tab. 3. Select Administration access passwords in the Client access passwords group box. 4. Type the password you want to assign. You may only type one password. 5. Click Apply. The Administrator appears as Administrator in a Bridgit software conference participant list, but doesn t have any special capabilities in the conference. NOTE: If you create a conference that uses the same password as the system Administrator s, no conference members appear as Administrator in the participant list. Assigning an Application Programming Interface (API) Authentication Password An API authentication password is only used by original equipment manufacturers (OEMs) using the API. To assign an API authentication password 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Security tab. 3. Select API authorization password in the Server access passwords box. 4. Type the password you want to assign. You may only type one password. To revoke the password, clear the API authorization password box. 20 Configuring the Master Server REV B0

25 5. Click Apply. Remember to give the password to third-party users whose systems are integrated with Bridgit software. Disabling Remote Control To prevent presenters from sharing control of their computers with other participants, disable the remote control setting in Bridgit Software Administration Tools. To disable remote control 1. Open the Bridgit Software Administration Tools on the master server. 2. Click the Options tab. 3. Clear the Enable Remote Control check box. Remote Control is disabled in new conferences. However, remote control remains available in active conferences until they end. NOTE: When you disable remote control, the option no longer appears to participants in Bridgit software conferences. Disabling Conference Audio By default, Bridgit software s audio features allow conference participants to talk to each other during conferences. To disable conference audio 1. Open Bridgit Software Administration tools on the master server. 2. Select the Options tab. 3. Clear the Enable Audio check box. Conference audio is disabled in new conferences. However, audio remains available in active conferences until they end REV B0 Configuring the Master Server 21

26 To select a default audio optimization 1. Open Bridgit Software Administration tools on the master server. 2. Select the Options tab. 3. Select Optimize for high audio quality to preserve the quality of the conference audio (this setting also consumes the most bandwidth), or Optimize for low bandwidth to preserve bandwidth efficiency at the cost of some audio quality. Disabling Webcams To disable webcams in Bridgit software conferences 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Options tab. 3. Clear the Enable Webcams check box. Webcams are disabled in new conferences. However, webcams remain available in active conferences until they end. NOTE: When you disable webcams, the option no longer appears to participants in Bridgit software conferences. Disabling Text Chat To disable text chat in Bridgit software conferences 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Options tab. 3. Clear the Enable Chat check box. Text chat is disabled in new conferences. However, chat remains available in active conferences until they end. NOTE: When you disable text chat, it no longer appears to participants in Bridgit software conferences. 22 Configuring the Master Server REV B0

27 Adding a Message of the Day Select this option to create a message that users see when they open the Bridgit software client. To add a message of the day 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Options tab. 3. Select the display frequency to use in the Message of the day group box (choose from Don t show, Show once per day or Show every time client runs). 4. Type the message in the Message of the Day text box (maximum 256 characters). 5. Click Apply. Changing Master Server Setup Options When you install Bridgit conferencing software on the master server, you can specify the public domain name, IP address and listening port. You can also use the Administration Tools to change this information. To change the master server configuration, open Bridgit Software Administration Tools on the master server and click the Setup tab. On this screen, you can change several aspects of the Bridgit server configuration, including: The server s registered domain name. To access this server over the Internet, you must use a fully qualified domain name (FQDN) that exists in the records of a DNS server. If a FQDN isn t available for this server, users can access this server over the Internet using its IP address. Don t mix FQDNs and unqualified domain names (those not registered in a DNS server) in the same Bridgit software server cluster. The server s IPv4 and IPv6 addresses. During the installation process, Bridgit software detects the IP addresses bound to the server s network interface cards. You can choose to bind Bridgit software to one or all of the computer s IP addresses REV B0 Configuring the Master Server 23

28 The server s primary and secondary TCP ports. By default, Bridgit software uses port 80 as its primary and 9933 as its secondary TCP port. If the server has other applications using these ports, choose different ones here to prevent conflict. NOTE: If you configure your Bridgit software server to use TCP ports other than the defaults, users must specify the port when connecting to the server. For example, to connect to a Bridgit software server on port 8080, users type server.company.com:8080. The range of UDP ports that Bridgit software uses to transmit audio. When possible, Bridgit software uses a UDP connection to transfer conference audio. Using UDP prevents lag issues inherent to TCP connections in a timing-sensitive environment such as a multi-user conference. By default, Bridgit software uses UDP ports 9901 to NOTE: If your network uses a firewall, you must configure it to allow incoming UDP traffic on these ports. Extra Conference Fields. You can add up to three additional categories that appear with the Created, Conference Name and Owner fields in the list of active Bridgit conferences to Bridgit software users. Users or administrators that create a new conference can use these fields to further describe their conference. Extra User Fields. You can also add up to three additional fields that a user can use to describe themselves when joining or creating a conference. Configuration changes on this page don t take effect until you restart the Bridgit software services. If you have multiple servers in your Bridgit software cluster, you must restart the master service first and then restart each conference service (see Starting, Stopping, Pausing and Restarting Bridgit Software Services on page 28). 24 Configuring the Master Server REV B0

29 Configuring Conference Servers You can use Bridgit Software Administration Tools on a conference server to modify settings that directly apply to the conference server. However, you must use the Bridgit Server Administration Tools on the master server to change the conference creation password, conference viewing password, API authorization password, remote control setting and message of the day (see Changing Master Server Setup Options on page 23). Changing the Clustering Authentication Password Change the clustering authentication password on a conference server only after you change it on the master server first (see Assigning a Clustering Authentication Password on page 19). To change the clustering authentication password 1. Open Bridgit Software Administration Tools on the conference server. 2. Click the Setup tab. 3. Type the clustering authentication password you assigned on the master server in the Cluster Password box. 4. Click Apply. NOTE: Repeat this procedure on all conference servers in the cluster REV B0 Configuring Conference Servers 25

30 Changing Conference Server Setup Options When you install Bridgit software on a conference server, you can specify the public domain name, IP address and listening port. You can also use Bridgit Software Administration Tools to change this information. To change the conference server configuration, open Bridgit Software Administration Tools on the conference server and click the Setup tab. On this screen, you can change several aspects of the Bridgit server configuration, including: The server s registered domain name. To access this server over the Internet, you must use a fully qualified domain name (FQDN) that exists in the records of a DNS server. If a FQDN isn t available for this server, users can access this server over the Internet using its IP address. Don t mix FQDNs and unqualified domain names (those not registered in a DNS server) in the same Bridgit software server cluster. The server s IPV4 and IPV6 addresses. During the installation process, Bridgit software detects the IP addresses bound to the server s network interface cards. You can choose to bind Bridgit software to one or all of the computer s IP addresses. The server s primary and secondary TCP ports. By default, Bridgit software uses port 80 as its primary and 9933 as its secondary TCP port. If the server has other applications using these ports, choose different ones here to prevent conflict. NOTE: If you configure your Bridgit software server to use TCP ports other than the defaults, users must specify the port when connecting to the server. For example, to connect to a Bridgit software server on port 8080, users type server.company.com:8080. Configuration changes on this page don t take effect until you restart the Bridgit software service (see Starting, Stopping, Pausing and Restarting Bridgit Software Services on page 28). 26 Configuring Conference Servers REV B0

31 Managing Servers and Conferences You can change the connection status of servers and end conferences using Bridgit Software Administration Tools. Placing a Server On Hold and Reactivating It When a server is on hold, it doesn t allow users to connect, but doesn t end active conferences. Place a server on hold when you want to perform maintenance procedures on the server. This allows active participants to finish their conferences, and allows you to maintain the server when they ve finished. To place a server on hold or reactivate it 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Performance tab. 3. Right-click the server you want to place on hold or reactivate, and select Place Server On Hold or Re-activate Server. Ending a Conference You can terminate conferences on any master or conference server in the Bridgit software cluster. To end a conference 1. Open Bridgit Software Administration Tools on the master server. 2. Click the Conferences tab. 3. Select the conference that you want to end. 4. Click the End Conference button. The End Conference(s) dialog box appears. 5. If you want to send a message to conference participants before you disconnect them, type it in the Message box. 6. Click OK. The conference ends and all participants are disconnected REV B0 Managing Servers and Conferences 27

32 Starting, Stopping, Pausing and Restarting Bridgit Software Services You can use the Services administration console to control Bridgit software services without restarting the computer. To control Bridgit software services using the Services administration console IMPORTANT Only a master server runs both the Bridgit Master Service and Bridgit Conference Service. If you re administering a conference server, ignore steps 2 and 3 in the procedure below. 1. Open the Services administration console (Control Panel > Administrative Tools > Services). 2. Double-click Bridgit Master Service. A Bridgit Master Service Properties dialog box appears. 3. Click the Start, Stop, Pause and Resume buttons in the General tab to control the service. 4. Click OK. 5. Double-click Bridgit Conference Service. A Bridgit Conference Service Properties dialog box appears. 6. Click the Start, Stop, Pause and Resume buttons in the General tab to control the service. 7. Click OK. 28 Managing Servers and Conferences REV B0

33 Distributing Bridgit Software Client After you ve configured the Bridgit software servers, users can download the Bridgit software client by visiting the Bridgit software server s address in a Web browser. Visitors to this address see a Web page with basic instructions and a link for downloading the Bridgit software client. Customizing the Bridgit Software Web Page You can customize the Web page that users see when they use a Web browser to visit the Bridgit software server. Create an HTML page called CustomPage.htm and save it in the server s application directory (the default is C:\Program Files\Bridgit, but this location changes if you ve installed Bridgit software in a different folder). NOTE: For enhanced security, the Bridgit software server makes only CustomPage.htm available to a Web browser. If your custom page includes images or other files, those images and files must be hosted on a different server and referenced with absolute links within the custom page REV B0 Distributing Bridgit Software Client 29

34 Communications Security Overview Secure Sockets Layer (SSL) Standard (Version 3.0) Bridgit software complies with the SSL 3.0 standard for secure Web communications. Bridgit software encrypts data transmitted in SSL mode to prevent third parties from viewing the data when it s transmitted between a Bridgit software client and server. Bridgit software has been tested to ensure that the encryption mechanism and the communication layers conform to the SSL standard. The SSL standard was originally constructed by Netscape Communications Corporation to provide secure communications between a Web browser and a Web server. Since its inception, the standard has been revised several times to strengthen security and fix security concerns that existed in previous versions. Version 3.0 of the standard is mature, well established in the industry and has remained unchanged since November Software toolkit vendors supply libraries that implement the SSL standard and can be used to build SSL-capable applications. Bridgit software uses the Open SSL toolkit to provide security on both the client and the server. This toolkit implements both the SSL and the Transport Layer Security (TLS v1) protocols, and a full-strength general purpose cryptography library. For information about this toolkit, visit Certificates A certificate is a digitally signed document that serves to validate the sender s authorization. Bridgit software generates a new 256-bit SSL certificate each time the server starts. 30 Communications Security Overview REV B0

35 Contacting SMART Online Support Visit the SMART Technologies support site to view and download user s guides, how-to and troubleshooting articles, software and more. Training Visit for free training materials and information about our training services. Contacting SMART Technical Support SMART Technical Support welcomes your call. However, if you experience difficulty with your SMART product, you may want to contact your local reseller first. Your local reseller may be able to resolve the issue without delay. All SMART products include free online, telephone, fax and support: Online: Telephone: ortoll Free (U.S./Canada) (Monday to Friday, 7 a.m. 6 p.m. Mountain Time) Fax: support@smarttech.com General Inquiries Address: SMART Technologies ULC Ave SW, Suite 300 Calgary, AB T3C 0M5 CANADA Main Switchboard: or Toll Free SMART (U.S./Canada) Fax: info@smarttech.com REV B0 Contacting SMART 31

36 Registration To help us serve you, register online at Sending Feedback You can help us improve our technical documentation by ing your comments to 32 Contacting SMART REV B0

37 Index A Active Conferences Ending, 27 Viewing, 13 Administrator Access Password, 20 API Authentication Password, 20 Audio Optimization, 22 B Bridgit Software, 1 Client Software Distribution, 29 Downloading, 4 Evaluation License, 6, 8, 9 Bridgit Software Administration Tools, 1 C Cluster Authentication Password, 7, 19, 25 Conference Creation Password, 6, 18 Conference Server, 1 Installing, 7 Conference Viewing Password, 6, 17 Contacting SMART, 31 Controlling Bridgit software services, 28 D Default Installation Folder, 5, 7, 29 Domain Name, 5, 23, 26 E Extra Conference Fields, 24 Extra User Fields, 24 F Finding a SMART Reseller, 9 I IPv4 Address, 5, 7, 23, 26 IPv6 Address, 5, 7, 23, 26 L Licenses Activating (Server), 9 Activating (User), 11 Manually Activating, 10, 11 Removing, 12 Status, 9, 11, 12 M Master Server, 1 Installing, 5 Message of the Day, REV B0 Index 33

38 N Network Port Configuration, 3 Firewall Considerations, 3 W Webcam, 22 R Remote Control, 21 S Scalability, 1 Secure Socket Layer (SSL), 30 Serial Number, 11 Serial Number Location, 9 Server Cluster, 1 Server Performance Viewing, 14 Server Status, 15 Server Usage Reports Saving, 16 Viewing, 16 Starting Bridgit Software Administration Tools, 1 System Requirements, 2 Bandwidth, 2 T TCP Port Primary, 5, 8, 24, 26 Secondary, 5, 8, 24, 26 Text Chat, 22 U UDP Port, 5, 8, 24 Upgrading, 9 34 Index REV B0

39

40 SMART Technologies Avenue SW, Suite 300 Calgary, AB T3C 0MS CANADA Support: or Toll Free (U.S./Canada) REV B0