TM-210, TM-270, TM-510, TM-560, TM-600,
TM-800, TM-1000, TS-300, TS-700, TW-100
Administrator Manual
Version 5.1
The RHUB TM-210 and TM-270 “6-in-1” web conferencing
and TW-100 webinar servers
The RHUB TM-510 and TM-560 “6-in-1” web conferencing
and TS-300 remote support servers
The RHUB TM-600, TM-800 and TM-1000 “6-in-1” web
conferencing and TS-700 remote support appliances
RHUB Communications, Inc.
4340 Stevens Creek Blvd.
Suite 282
San Jose, CA 95129
support@rhubcom.com
http://www.rhubcom.com
Contents
1. INSTALLATION & REGISTRATION ................................................................. 3
1.1. ACCESSING YOUR RHUB WEB CONFERENCING SERVER..................................... 3
1.2 REGISTERING YOUR RHUB WEB CONFERENCING SERVER.................................. 5
2. CONFIGURING THE RHUB WEB CONFERENCING SERVER.................... 6
2.1. CONFIGURE SERVER IP SETTINGS........................................................................ 8
2.2. SYSTEM SETTINGS ............................................................................................. 10
2.3. MANAGING YOUR SSL CERTIFICATE................................................................. 13
2.4. SCHEDULED MEETINGS AND ACTIVE MEETINGS................................................ 15
2.5. RESTORE OR TRANSFER EXISTING, EXPIRED OR DELETED MEETINGS ...............16
2.6. CUSTOMIZING THE MEETING START AND PROMOTION PAGES ........................... 16
2.7. WEBINAR REGISTRATION................................................................................... 19
2.8. INTEGRATION WITH APPLICATION SERVER ........................................................ 21
2.9. INTEGRATION WITH LDAP FOR USER AUTHENTICATION................................... 21
2.10. INTEGRATION WITH A PBX SYSTEM OPTION ..................................................... 22
3. CONFIGURING THE FIREWALL..................................................................... 25
3.1. BEHIND FIREWALL AND ACCESSIBLE BY USERS OUTSIDE FIREWALL................. 25
3.2. OUTSIDE THE FIREWALL .................................................................................... 26
3.3. BEHIND FIREWALL AND NOT ACCESSIBLE BY USERS OUTSIDE FIREWALL......... 27
4. MANAGE USERS .................................................................................................. 28
4.1. USER GROUPS.................................................................................................... 29
5. START MEETINGS............................................................................................... 31
6. REPORTING .......................................................................................................... 33
7. RESET SERVER.................................................................................................... 34
8. LICENSE UPGRADES: ADDITIONAL MEETING ROOMS AND USERS.. 35
9. RHUB HIGH AVAILABILITY CONFIGURATION AND OPERATION...... 36
9.1. BACKUP YOUR DATABASE................................................................................. 36
9.2. SET UP YOUR HA SERVERS................................................................................ 37
9.3. START OR STOP HA SERVERS ............................................................................ 37
9.4. CHECK THE HA SERVER STATUS....................................................................... 37
9.5. TEST IF HA WORKS PROPERLY.......................................................................... 38
SUPPORT CONTACT................................................................................................... 40
2
1. Installation & Registration
The Web conferencing server package includes:
TM-200, TM-260, TS-300, TM-510, TM-560, TM-600 TM-800, TM-1000, or TS-700 server
Analog console cable
Power cord. Power brick (for TM-200, TS-300, TM-260, TM-250E, and TM-550 only)
1.1. Accessing your RHUB Web Conferencing Server
There are two ways to access the TM-200 and TM-260 servers: b y using plug-and-play or by
using a direct cable connect. To access the TM-510, TM-560, TM-600, TM-800, TM-1000, TS-300
and TS-700 servers, use plug-and-play. In all cases, an Internet browser needs to be used to
access and configure the server.
I. Plug-and-Play
This method requires that you have:
A DHCP server on your network
A computer with Microsoft Windows (2000, XP, Vista, Windows 7, or Windows 8)
It is important to follow the instructions below to start the server for initial setup:
1. Connect the server with an Ethernet cable (not a crossover cable) to your network
2. Plug in the power cord to automatically power on the server
3. Wait for the ready light to turn green. This usually takes about 30 seconds.
Open a browser on your computer and type “http://myonlinemeeting”. The following page should
appear:
If the page does not display and you are familiar with your router, check the IP address your
router has assigned to the RHUB server, which is named “myonlinemeeting”. Then input the IP
address in your browser’s address bar and you will be able to access the RHUB server.
Figure 1.1 Home Page
3
If the page does not display and you are not familiar with your router, go to the following initial
startup method.
II. Local Access
For the TM-600, TM-800, TM-1000, and TS-700 servers only, if you fail to access the server by
the above method, do the following:
Plug in your keyboard, mouse and monitor to the server
Power on the server
Wait for 1 minute
Type “turbomeeting” as the Username and “password” as the Password
Wait for up to a couple of minutes and you will be connected to the Fedora desktop.
Open a browser by clicking the browser icon on the top banner
This will take you to the TurboMeeting web login page (Figure 1.2)
Follow the sections below to configure the server using the browser.
Figure 1.2. Login
For the TM-250-E, TM-550, TM-510 and TM-560 servers only, if you fail to access the server by
Plug-and-Play, do the following:
Plug a serial cable between the server and a computer
Power on the server
Wait for 1 minute
Use HyperTerminal or the open source Tera Term program. The serial port settings are:
Baud rate: 115200 Data: 8 bit Parity: none Stop: 1 bit
Type “admin” as the Username and “password” as the Password
Type “ifconfig” to determine the IP address (inet addr) of the server
Follow the sections below to configure the server using the browser.
III. Direct-Cable Connection
The direct-cable connection method is for the TM-200, TM-260, TM-210, TM-270, TM-510 and
TM-560. Before you use this method, configure your computer (in any operating system) with the
following IP setting:
IP Address: 192.168.1.100
Subnet Mask: 255.255.255.0
Next, do the following:
4
Disconnect your computer from any network including the wireless
Power on the RHUB server (as described above)
Wait for the ready light to turn green. This usually takes about 90 seconds
Connect the RHUB server to your computer using a crossover-cable or any inter n et cable
On your computer, open a browser and in the address bar type
The home page (Figure 1.1) should display.
Because your server is not connected to the Internet, when you click the link “Web
Conferencing Server Management”, the registration page (Figure 1.3) will not display. To
bypass the registration page, type
Once you have accessed the meeting server, you are ready to configure the server. Do not
disconnect your computer from the meeting server before you complete the configuration
described in the next section. After the configuration, connect the RHUB server to your network
using a regular Ethernet cable (which is not included).
Note that after you change the system IP settings, the web page will hang. You will need to use
the new IP address to access the server.
http://192.168.1.192/as/wapi/login?b=y.
http://192.168.1.192.
1.2 Registering your RHUB Web Conferencing Server
When you receive your RHUB server, you have to register in order to receive software updates
and technical support. To register your server, access the meeting server home page (Figure
1.1), and click the “Web Conferencing Server Management” link. The Registration Page (Figure
1.3) appears. If you are using the direct-cable connection method to access your server (Section
1.1, Part III), type
the server is not connected to the internet yet.
It is important to specify an email address that will last a long time to insure that you receive
important notices such as product release notes from the manufacturer.
http://192.168.1.192/as/wapi/login?b=y to bypass the registration page since
Figure 1.3 Registration Page
5
2. Configuring the RHUB Web Conferencing Server
After you access the meeting server home page (Figure 1.1), click the “Web Conferencing Server
Management” link. If your RHUB server is new, you will have to submit
admin for the Email field
password for the Password field
To change the default administrator account, you use “Manage Users” (see Section 4) to change
the default email and password to your choice.
Figure 2.1 Login Page
6
After login, the System Management home page is displayed. The System Management
Navigation frame is shown in Figure 2.2:
Figure 2.2 Management Home Frame
7
2.1. Configure Server IP Settings
In the left frame of the System Management page, under Configuration click the IP Settings link.
Figure 2.3 is displayed:
Note that if you change the IP settings and submit the changes, your browser may hang because
the IP is changed. You should use the updated IP to access the server.
Figure 2.3 Configure Server IP Settings
8
The following describes the fields in Figure 2.3.
Public IP Address
In order for users outside your LAN to host or join meetings, you have to assign a public
IP address. If you don’t have a fixed public IP address, you can go to
http://www.dyndns.com to set up a domain name and copy the domain information and
your DynDNS user account information to the meeting server configuration page. After
that, you can always access your RHUB server by the domain name you set at DynDNS.
Note that RHUB offers the DynDNS client as a convenience to our customers. RHUB is in
no way affiliated with DynDNS or responsible for their service. Any fees that you may
incur with DynDNS are between you and DynDNS and have nothing to do with RHUB.
Authorized Public IP’s to Join Internal Meetings
If you have branch offices outside your LAN and you don’t have a VPN, use this setting
to allow employees from those branch offices to join an internal secured meeting hosted
in your LAN.
Current IP Settings
These are the IP addresses that the meeting server has currently.
Permanent IP Settings
The Permanent IP Settings refer to the desired IP settings you want your meeting server
to have. The permanent IP address can be the same as the “Public IP Address” or
different from the “Public IP Address“. If the permanent IP is a local IP address, it will be
different from the public IP address. In such a case, you will need to do port forwarding
on your firewall router to forward TCP traffic from the ports (80 and 443) and TCP and
UDP traffic from the port (8889) at the public IP address to the corresponding ports at
the permanent IP address. See the next section for details.
Carefully check that the DNS settings are correct. Correct DNS settings are needed to
allow the meeting server to connect to the RHUB Communications’ release servers so
firmware updates can be applied. Correct DNS settings are also needed to allow updated
audio conference numbers to be sent to your meeting server.
Note that after you change the permanent IP settings, the web page will hang because
the server IP address has been changed. You will need to use the new IP address to
access the server.
If you make a mistake in configuration, you need to reset the server. See Sectio n 7 for details.
9
2.2. System Settings
In the left frame of the System Management page, under Configuration click the
link. Figure 2.4 is displayed.
System Settings
Figure 2.4 System Settings
The following describes the fields in Figure 2.4.
Language
The language for the TurboMeeting System Management UI can be changed to English,
Chinese (Simplified), Chinese (Traditional), Japanese, Spanish, French or Portuguese.
Time Zone, Time & Date, and Date Format
Set the correct time zone, time and date, and date format for the RHUB server.
Max free speakers in a VoIP session
Set the maximum number of free speakers in a VoIP session before attendees must use
the Push-to-Talk button in order to be heard in a meeting. 5 is the default maximum
number of free speakers. The presenter and the controller are always free to talk. All
attendees should use good quality headsets, such as those from Plantronics, to avoid
10
echo and background noise. Internet traffic can grow quickly if too many free speakers
are allowed on your server at once.
Max Webcam Height
Change the Maximized Webcam height when the host clicks the Webcam’s Maximize
button. The default maximum height is 240 pixels. Other choices include 320 pixels, 480
pixels and 560 pixels. Webcams use 10 times as much bandwidth in a meeting
compared to other features; and a “560” pixel setting will use twice as much bandwidth
as the “240” pixel setting.
Webcam Image Quality
Set the image quality of webcams. The possible settings are Low, Low to Medium,
Medium, Medium to High, and High. The “High” setting can use twice as much
bandwidth as the “Low” setting.
Default audio mode
Set the default audio mode for attendees who have not already chosen their audio mode.
The possible settings are “Use Telephone” and “Use Mic & Speakers”. The host of the
meeting can override this setting in TurboMeeting’s Tools | Preferences dialog.
Max number of participants shown on the meeting control panel all time
Set the maximum number of participants that are shown in the “short list” in the meeting
control panel. The presenter can open a window that shows a “long list” of all the
meeting participants. Attendees that require attention (such as if they raise their hand)
move to the top of each of these lists. The “long list” can be sorted by participant name.
Allow attendees to record
This setting determines whether any attendees are allowed to record during a meeting.
Enable multipoint video conferencing
This setting determines if multipoint video conferencing is enabled for this RHUB server.
Multipoint video conferencing allows up to four meeting participants to show their
webcams.
Access this server only via SSL
By default, screen images during a meeting are transmitted with RHUB proprietary 256bit encryption for efficiency. However, you can use SSL for encryption by enabling the
Access this server only via SSL option. Your own SSL certificate is not required for
this setting.
Use SSL to manage the server web pages
This setting determines if SSL is always used when displaying the TurboMeeting System
Management web pages. It is recommended that you use your own SSL certificate with
this setting so that web browsers do not complain about a domain name mismatch. See
11
the section Manage Your SSL Certificate about how to upload your own SSL
Certificate.
Enable auto update of system
The RHUB server retrieves software updates automatically if this is enabled. This is done
at 3 AM for the time set on the server. Updates typically happen twice per year.
Update System Now
This feature retrieves updated RHUB server software from the RHUB web site.
12
2.3. Managing Your SSL Certificate
In the left frame of the System Management page, under Configuration click the SSL Certificate
link. Step 1 of setting up an SSL certificate is displayed as in Figure 2.5.
Figure 2.5 Setting up an SSL Certificate, step 1
The following describes the fields in Figure 2.5.
Common Name
This is the domain name for your RHUB server. This must match the domain name you
specify in your SSL certificate.
Organization Name
This is the Organization Name you specify in your SSL certificate.
State, City and Country
This is the State, City, and Country that you specify in your SSL certificate.
Next, obtain an SSL certificate as shown in Step 2 (Figure 2.6). For the SSL certificate, specify
the same Common Name, Organization, State, City and Country that you specified in Step 1.
Choose the SHA-2 signature algorithm for your SSL certificate, if you are given a choice.
Figure 2.6 Setting up an SSL Certificate, step 2
You should use Chrome or Firefox to upload your SSL Certifcates. Locate your SSL Certificate file
and your CA Root Certificate file (which may be called a “bundled root”). Sometimes your SSL
provider may bundle these two into the same file. Using Microsoft WordPad, copy and paste the
contents of these files into the files shown in step 3 (Figure 2.7).
13
Figure 2.7 Setting up an SSL Certificate, step 3
Test your SSL Certificate as described in step 4 (Figure 2.8).
Figure 2.8 Setting up an SSL Certificate, step 4
Note that the RHUB server does not accept wildcard certificates.
14
2.4. Scheduled Meetings and Active Meetings
In the left frame of the System Management page, under Meetings click the Scheduled link. This
feature shows you the list of scheduled meetings for your RHUB server. The provided URLs show
all of the public meetings and provide a link for how to join the meeting.
Figure 2.9 List of scheduled meetings
In the left frame of the System Management page, under Meetings click the
feature shows you the list of active meetings for your RHUB server. As the administrator, you
can stop an Active meeting by clicking the
Figure 2.10 List of active meetings
Stop link as shown in Figure 2.10.
Active link. This
15
2.5. Restore or Transfer Existing, Expired or Deleted Meetings
In the left frame of the System Management page, under Meetings click the Restore Meeting link.
This feature allows you to restore a meeting that has expired or was deleted; and it allows you to
transfer a meeting to another user, which is helpful if the original host of the meeting is
unavailable.
To restore a meeting to its original owner, enter the meeting ID and select Restore to “Current
owner”; click “Submit”. To transfer a meeting to a new owner, enter the meeting ID, selec t
Restore to “New owner whose email/username is” and specify the email id or user name; click
“Submit”.
Figure 2.11 List of scheduled meetings
2.6. Customizing the Meeting Start and Promotion Pages
In the left frame of the System Management page, under Customization click the Name & Logo
link. This feature allows the Administrator to use show your company’s name and logo on the
standard meeting home page.
Figure 2.12 Change the name and logo on standard meeting home page
16
In the left frame of the System Management page, under Customization click the Entry Page link.
This feature allows the Administrator to use a different home page as the standard meeting
home page.
Figure 2.13 Use a new page for the meeting home page
The system home page specified in Figure 2.13 should contain ways for users to host and join
meetings. There are two ways for users to host and join meetings:
1. click URLs (or buttons associated with the URLs) on your page
2. submit forms on your page
Using URLs is the easiest way for customization. Using forms gives you a better control of
customization. In the following examples, substitute for yourMeetingServerAddress the
host name (e.g. webmeeting.company.com) for your RHUB server.
Here is the URL that is used to host a meeting:
http://yourMeetingServerAddress/as/wapi/goto_downloader?role=host
Here is the URL that is used to join a meeting:
http://yourMeetingServerAddress/as/wapi/goto_downloader?role=attendee
Here is the HTML code used to allow users to host a meeting:
<form action=”http://yourMeetingServerAddress/as/wapi/goto_downloader”
method="post">
<input type="hidden" name="role" value="host">
Email Address:
<input type="text" name="email" value="">
Password:
<input type="password" name="user_password" value="">
<input type="submit" name="submit" value="Host Meeting">
</form>
17
Here is the HTML code used to allow users to join a meeting:
<form action=”http://yourMeetingServerAddress/as/wapi/goto_downloader”
method="post">
<input type="hidden" name="role" value="attendee">
Meeting ID:
<input type="text" name="meeting_id" value="">
Meeting Password:
<input type="password" name="password" value="">
Your Name:
<input type="text" name="name" value="">
<input type="submit" name="submit" value="Join Meeting">
</form>
In the left frame of the System Management page, under Customization click the Promotion Page
link. This allows the Administrator to change the web page that meeting attendees see when a
meeting ends. The web page can be used to solicit feedback, sell products or services, or display
your organization’s home page.
Figure 2.14 Change default promotion page
In the left frame of the System Management page, under Customization click the
Conference link. This allows the Administrator to change the telephone number used for audio
conferencing.
Figure 2.15 Change audio conference phone number
Audio
18
2.7. Webinar Registration
In the left frame of the System Management page, under Webinar Registration click the
Configuration link. This feature allows the Administrator to setup a registration page for all of
your webinars. Figure 2.16 shows the fields that can be customized for this registration page:
Figure 2.16 Registration page for all webinars
19
In the left frame of the System Management page, under Webinar Registration click the
Management link. This feature allows the Administrator to list, create, edit and disable upcoming
webinars. As shown in Figure 2.17:
Figure 2.17 List, Create, Edit and Disable Webinars
The resulting registration page for webinar attendees will look what is shown in Figure 2.18:
=
Figure 2.18 Webinar Registration page for Attendees
20
2.8. Integration with Application Server
In the left frame of the System Management page, under Integration click the Application Server
link. This feature allows the Administrator to use their own authentication server, such as a CRM
system, for user authentication.
Figure 2.19 Integration with your server for user authentication
For more details on how to integrate with an authentication server:
1. Go to
2. Click the “Support” link
3. Click the
http://www.rhubcom.com
Integration link
2.9. Integration with LDAP for User Authentication
LDAP Integration works on all servers. The LDAP feature is enabled for free on the TM-600, TM800, TM-1000, and TS-700 servers. Login to your RHUB server and enter the management page
shown in Figure 2.2. Under Integration click the
Figure 2.20. To integrate with the LDAP server, specify:
• the LDAP server’s IP address as the Host IP address
• the LDAP Port for TCP communication (not the SSL port). We recommend port 3268.
• any user’s distinguished name as the User DN
• the Password for the user specified in the User DN field
LDAP link and you will be shown the settings in
Figure 2.20 Enable LDAP integration
21
Only LDAP Version 3 is supported. No SSL encryption can be used for User DN and Password
authentication. Simple Bind authentication is used to connect to your LDAP server. If a user
with valid credentials fails to pass authentication by your LDAP server, check the following:
• Your LDAP configuration meets with the work conditions of this system.
• Your LDAP entries have the "distinguishedName" (DN) attribute filled with proper values.
Empty values are not allowed. A Microsoft Active Directory server should automatically fill
proper values for distinguishedName. To determine a distinguishedName for a user (i.e.:
a User DN), use an LDAP browser like
You can test whether individual users can be found for the given LDAP settings as shown in
Figure 2.21. Enter the login name and password for a specific user. The resulting page will say
either “LDAP authentication succeeds” or show a detailed trace of where the LDAP authentication
failed.
Figure 2.21 Test specific LDAP Users to insure correctness of LDAP settings
If you have an LDAP server with many thousands of users, or if only a small subset of your LDAP
users are going to host meetings on the RHUB server, you can achieve faster LDAP user lookups
by specifying multiple Base DN’s. Taken together, these multiple Base DN’s will likely have fewer
users than your entire LDAP tree.
JXplorer, or on Windows ADSI Edit (adsiedit.msc)
2.10. Integration with a PBX System Option
The PBX integration is an option that must be purchased. When PBX integration is enabled on
your RHUB server, the meeting host connects to your PBX server and participants can call into
your PBX and talk with RHUB’s audio conference callers and TurboMeeting VoIP talkers if the
RHUB administrator chooses to “Allow users to include additional dial-in numbers provided by the
manufacturer's audio conferencing services”.
When the PBX integration setup is complete, TurboMeeting will display a “Connect” button when
a meeting is running. When the host clicks this Connect button, a connection with your PBX
system (or SIP server) is initiated.
22
Figure 2.22 PBX integration settings
The SIP Server IP (or SIP Server domain name) and Port are what the RHUB Audio
Conferencing server needs to call into your SIP Server. The Display Name is the name that
appears in the TurboMeeting application’s list of Telephone callers. The Phone Number for
Meeting Invitation is your SIP Server’s phone number that TurboMeeting lists in the email
invitation and in the GUI. The other parameters are the special values that need to be entered to
get into a meeting room. If a value is Editable by users, then there will be a corresponding
profile field for each user in TurboMeeting’s Tools | Preference’s “Conference Call” settings.
These ports must be open for the RHUB SBC (Session Border Controller) to call in to your PBX:
UDP 5060-5070
UDP: 20000-30000
23
You can limit access on these ports to IP address: 64.71.140.86 (the RHUB SBC, which is the
caller IP). You don't need another static IP address for your PBX. You can still use 80/443 for
your web server if it uses the same IP address.
To facility the debugging, please download free X-Lite software and use it to call your system.
Note that it is important to uncheck "Register domain and receives call" as the RHUB server will
not register with the domain (see the image below). After you verified that your settings work
with X-Lite, the RHUB server should work with the same settings.
Figure 2.23 Use X-Lite to debug PBX integration settings
24
3. Configuring the Firewall
There are three ways to deploy your RHUB server:
1. Outside the Firewall
2. Inside the Firewall and Accessible by Users outside Firewall
3. Inside the Firewall and not Accessible by Users outside Firewall
Depending on the deployment, you may or may not need to configure your firewall.
3.1. Behind Firewall and Accessible by Users outside Firewall
This deployment (Figure 3.1) is most popular and it is typically done by connecting RHUB server
with the DMZ port of your router. You can also place the RHUB server anywhere on your LAN.
In order for external users to access your server, you need to open the inbound TCP ports: 80
and 443 and the TCP and UDP port 8889 on your firewall/router and forward the inbound TCP
and UDP traffic on these ports to the corresponding ports of the local IP address of your RHUB
server.
If you are using a SOHO or home router, opening inbound ports and doing port forwarding are
fairly easy. For example, in a LinkSys router, you usually look for the “Applications” link. In a
Belkin router, you look for the “Virtual Servers” link. After clicking the link, you will see a page
similar to Figure 3.2. Fill in the two TCP ports (80 and 443) and the TCP and UDP port (8889)
and your RHUB server local IP address. The firewall configuration is done.
In Figure 3.2, the “Private IP address” is the RHUB server’s local IP address, which you define
when you configure the meeting server IP settings; the “Inbound port” may be called “Source
port”; the “Private port” may be called “Destination port”. You can input anything in the
“Description” field. Don’t forget to check the “Enable” fields.
Figure 3.1 Inside Firewall and Accessible by Users outside Firewall
25
Figure 3.2 A sample of firewall configuration
This deployment gives you the maximum flexibility in terms of meeting access security control.
With this deployment, you can host two types of meetings:
Internal meetings that only users behind your firewall can join (including users in the
Virtual Private Network, or VPN)
Note: You can manually allow external users by specifying a list of IP addresses
External meetings that anyone including attendees outside your firewall can join.
If you have difficulty in configuring port forwarding, please refer to the following URL for step-bystep guidance for your router:
http://portforward.com/english/routers/port_forwarding/routerindex.htm
On the page, find your router model or a model similar to yours. Click the link for your router. On
the next page, click “Click here to skip this advertisement... “. Now it shows a long list of
applications you can do port forwarding for. Just pick one application. Replace this application’s
port(s) with three different definitions for ports 80 and 443 using TCP and port 8889 using TCP
and UDP.
3.2. Outside the Firewall
With this deployment (Figure 3.3), your RHUB server is completely outside your corporate
firewall. There is no firewall configuration needed.
To configure the server settings (Figure 2.3) for this deployment, you will need to obtain from
your Internet service provider (ISP) the IP address, subnet mask, default gateway and DNS
settings. Input the IP address in the “Public IP Address” field and other IPs in the “Permanent IP
Settings”.
Figure 3.3 Deployment Outside the Firewall
26
3.3. Behind Firewall and Not Accessible by Users outside Firewall
This deployment (Figure 3.4) disallows users from connecting to the meeting server from the
Internet outside your firewall and provides the maximum meeting access security. It will not
allow any users outside your firewall (VPN) to join any meetings hosted on the server.
On the Server IP Settings configuration page (see Section 2.1), choose the option “No public IP
address. This server is used only by internal users.” Then assign a static local IP, subnet mask,
default gateway, and DNS servers for the meeting server (Figure 2.3).
You do not need to do any configuration on your firewall.
Figure 3.4 Inside Firewall and Not Accessible by Users outside Firewall
27
4. Manage Users
Users
Login to the home page for your RHUB server and enter the management page shown in Figure
2.2. Under the User Management category, click the
shown below.
You can click the Add New User button to add a new user. Under the “Action” column, click the
Edit link to edit a user profile or Delete link to delete a user profile from the system. Figure 4.2
below shows the page to create a user. You can define the meeting functions for each user.
Figure 4.1 List of
Users link. A list of users will display as
Figure 4.2 Create a user profile
28
User Groups
4.1. User Groups
User groups can be created to define the same set of meeting privileges, audio conference
setting and promotional URLs for a group of users. Once a user group is created, users can be
assigned to this user group. This makes it easier to assign similar meeting privileges to similar
users.
User Groups definitions can also apply to user groups defined in LDAP. When creating a User
Group using the following steps, insure that the user group name exactly matches the LDAP user
group name.
To access user groups, login to the home page for your RHUB server and enter the management
page shown in Figure 2.2. Under the User Management category, click the
list of user groups will display as shown below.
User Group link. A
You can click the New User Group button to add a new user group. Under the “Action” column,
click the
delete a user group, you must first remove all the users from that group. Figure 4.3 below
shows the page to create a user. You can define the meeting functions for each user group .
Edit link to edit a user group or Delete link to delete a user group from the system. To
Figure 4.3 List of
29
Figure 4.4 Create a user group
30
g
5. Start Meetings
After you complete the above configuration, you can start to host and invite people to join your
meetings. Open your browser and type the IP address of the RHUB server into your browser. You
should see the home page shown in Figure 1.1.
Click the “Host” button to host a meeting. The next page will ask you to accept a Java Applet.
Accept it. TurboMeeting starts to run (Figure 5.1).
The Meeting Server Address in Figure 5.1 is your meeting server IP address. Type your email and
password to start a meeting. The meeting control panel switches to the entry meeting control
panel shown in Figure 5.2.
Figure 5.1 Login to Start a Meetin
Figure 5.2 Enter Meeting Control Panel
31
Click on the “Host” button as shown in Figure 5.2 and then select a meeting type. Your meeting
starts (Figure 5.3).
After the meeting starts, invite people to join your meeting by telling them the Meeting Server
Address and the meeting ID shown on your meeting control panel. You can also click the “Invite”
attendees button for more invitation details.
Figure 5.3 Main Meeting Control Panel
32
6. Reporting
In the left frame of the System Management page, click the
feature. The reporting feature allows the Administrator to view details on all meetings that have
taken place using a RHUB server. The report can be run for any specified dates and optionally
for any set of users. The report data can also be downloaded into an Excel file.
Report link to use the Reporting
Figure 6.1 Report of meeting activity
33
7. Reset Server
The following are two cases when you have to reset your server:
1. You forgot the administrator password
2. You move the server to a different network and you cannot access the server because
you did not change the server IP settings for the new network while you could access the
server in the previous network.
The RHUB server does three things during the reset:
1. It resets the system administrator account to the default one: "admin" as the email and
"password" as the password. If you have multiple administrators, it only resets the first
one's account.
2. It changes the IP settings to use DHCP.
3. It removes your own system home page URL so that you can easily access the server by
a new IP address.
The reset does not affect any other data including user profiles, meeting logs, scheduled
meetings, SSL certificate, audio integration setting, etc.
To reset the RHUB TM-200, TM-210, TM-260, TM-270, TM-510, TM-560, TS-300, or TW-100
servers, you just push a pin into the reset button on the back and hold it for over 10 seconds
until the “Ready” light turns off. After about 60 seconds when the “Ready” light turns on, you can
access the server.
To reset the RHUB TM-600, TM-800, TM-1000, or TS-700 servers, you need to connect it with
your monitor, keyboard and mouse. The server runs in a Fedora Linux system. The default
operating system login name is "turbomeeting" and the password is "password". After logging in,
right click on the desktop and open a Terminal session. Type "./ResetTM", which resets the
server. Then open a browser and type "http://localhost" to access the TurboMeeting
administration pages. Use the system default account: "admin" as the email and "password" as
the password.
Refer to the Section 1.1 about how to access to your server after the reset.
34
8. License Upgrades: Additional Meeting Rooms and Users
To add meeting rooms or additional user licenses to your server, login as an administrator to
your TurboMeeting System Management web page and click the
number of additional meeting rooms and users and click Submit:
Copy and paste the resulting page, below, into an e-mail and send it
Request link. Then fill in the
sales@rhubcom.com :
You will be sent an e-mail with a license request key. Login as an administrator to your
TurboMeeting System Management web page and click the
Request Key into the New License Key field and click Submit. Your license will be upgraded.
Upgrade link. Copy and paste the
35
9. RHUB High Availability Configuration and Operation
The RHUB High Availability (HA) function requires two servers: a master server and a
slave server. As soon as HA starts, the master server provides service to the
TurboMeeting users and the slave server stands by until the master server goes offline.
The master and slave server roles change automatically based on availability of a server.
When the initial master server becomes offline for up to 20 seconds, the current slave
server will become the master server and stay as the master server until it becomes
offline.
Each server has an Ethernet port. Simply connect the port to your LAN. The following
figure shows how it is deployed. It is not required that the two servers be on the same
network although it is recommended.
HA1
Figure 9.1 Master and Slave HA server setup
Here are the steps to deploy your HA cluster.
Internet
Firewall / router
HA2
9.1. Backup your Database
This is very important! Because the slave server’s database will be replaced with the
master server’s database every minute, you should back up your database before you
setup and start the HA servers. Also, it is recommended that you backup both the master
server and slave server databases every day.
Since the HA servers may be automatically assigned with different public IP addresses
over time, use the servers’ local IP addresses for backup. The HA servers’ local IP
addresses never change unless you change them.
Please go to the following FAQ for backup instructions:
http://www.rhubcom.com/v4/web_conferencing/support.html#backup
36
9.2. Set up your HA Servers
The following are sample settings. Make both HA servers have the same virtual IP and
configure your firewall to port forward the ports: 80 (TCP), 443 (TCP), 8889 (TCP &
UDP) to this virtual IP address.
Figure 9.2 HA server settings
9.3. Start or Stop HA Servers
You can start or stop an HA server is just a click of a button.
After an HA server starts, it will remain “Started” until you stop the server by clicking
the “Stop HA Server” button. The HA started/stopped status is not affected by if the
server is powered on or off.
The “Primary Master Server” is the HA server that holds the production database
initially. You must configure and make the primary master server work first.
9.4. Check the HA Server Status
You can check the HA server status by clicking the “Refresh” button on the HA
management page.
The HA running status is independent of the TurboMeeting server’s running status. That
is, a running HA status does not mean that the TurboMeeting server application is
running or is running without issues. A stopped HA status does not mean that the
TurboMeeting server application has stopped running.
37
HA itself is a server application. Its purpose is to keep the high availability of the servers
at the hardware, operating system, power and networking levels. When the master server
is not available due to any issues with hardware, power, operating system, or networking,
HA promotes the slave server as the master server within seconds.
When HA runs, it constantly does two jobs:
1. Detect the health of the peer server
2. Backup the production database from the master server to the slave server when
there are changes to the production database.
You can monitor the HA server status via the following URL:
http://TurboMeetingServerIP:8885/__HA_STATUS__
The above URL shows the master HA server status. To check each HA server status, use
the server’s local IP for the “TurboMeetingServerIP” in the above URL.
Below is a sample output:
<__Return__><__Status__>SUCCEED</__Status__>
<__Reason__>HA has started. It is the SLAVE.</__Reason__>
<__IsDefaultMaster__>Y</__IsDefaultMaster__> </__Return__>
“SUCCEED” is shown if HA started successfully. Otherwise, a failure status is shown
along with a reason for the failure.
9.5. Test if HA Works Properly
After you deploy the HA servers, you should test whether HA works properly. You need
to find a way to access your server outside your firewall in a browser. The following are
two basic test cases.
Case 1. Power failure
Turn off the power on the master HA server. You should be able to access your
TurboMeeting service after 30 - 50 seconds of disruption. After the TurboMeeting
service recovers, turn on the power on the server that was turned off and turn off the
power on the other server.
Case 2. Ethernet connection failure
Unplug the Ethernet cables from one HA server, then after the new Master takes over
plug in the unplugged Ethernet cable and unplug the Ethernet cable from the other server.
You should be able to access your TurboMeeting service after about 30 seconds of
38
disruption. Note that when you plug back in the cables, you will see that the server
reboots. This is by design.
39
Support Contact
If you purchased the TurboMeeting Server from a RHUB value-added reseller, please contact
them for support. If your reseller is not able to provide you adequate support, your reseller will
contact us or you can contact us directly.
RHUB Communications, Inc.
4340 Stevens Creek Blvd.
Suite 282
San Jose, CA 95129
Tel: 408-899-2831 extension 2
Fax: 408-516-9612
support@rhubcom.com
http://www.rhubcom.com
40
Loading...