Brother OmniJoin Installation guide

Brand: Brother

Model: OmniJoin

Type: Installation guide

OmniJoin Private Cloud

Installation and Planning

Guide

Version 0

ENG

Legal Notice

Microsoft, Windows, Active Directory, ActiveX, Windows Server and Windows Vista are either registered

trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Intel and Intel Xeon are registered trademarks or trademarks of Intel Corporation in the United States and/or

other countries.

Any trade names and product names of companies appearing on Brother products, related documents and any

other materials are all trademarks or registered trademarks of those respective companies.

W3C Software Notice and License

his work (and included software, documentation such as READMEs, or other related items) is being provided

by the copyright holders under the following license.

icense

By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will

comply with the following terms and conditions.

Permission to copy, modify, and distribute this software and its documentation, with or without modification, for

any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies

of the software and documentation or portions thereof, including modifications:

The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.

Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C

Software Short Notice should be included (hypertext is preferred, text is permitted) within the body of any

redistributed or derivative code.

Notice of any changes or modifications to the files, including the date changes were made.

(We recommend you provide URIs to the location from which the code is derived.)

Disclaimers

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO

REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,

WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE

USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS,

COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.

CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the

software without specific, written prior permission. Title to copyright in this software and any associated

documentation will at all times remain with copyright holders.

otes

This version: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231

This formulation of W3C's notice and license became active on December 31 2002. This version removes the

reflects that ERCIM is now a host of the W3C, includes references to this specific dated version of the license,

and removes the ambiguous grant of "use". Otherwise, this version is the same as the previous version and is

written so as to preserve the Free Software Foundation's assessment of GPL compatibility and OSI's

certification under the Open Source Definition.

iii

Table of Contents

troduction 1

Target Users of This Guide ............................................................................................................................. 1

Related Documentation .................................................................................................................................. 1

OVERVIEW ..................................................................................................................................................... 1

Requirements 3

Server Requirements ...................................................................................................................................... 3

Client Requirements........................................................................................................................................ 5

Host Name Requirements ............................................................................................................................... 6

Important Notes Regarding Host Names ................................................................................................. 6

Installation Planning 9

Network Readiness Assessment .................................................................................................................... 9

Installation Checklist ..................................................................................................................................... 10

Network Topology .......................................................................................................................................... 11

Network Planning – Determining the Best Server Locations ........................................................................ 15

Host Domain Name Services ........................................................................................................................ 15

Background ................................................................................................................................................... 16

Before starting the installation ....................................................................................................................... 17

Assumptions .......................................................................................................................................... 17

Example Settings ................................................................................................................................... 17

Settings to Determine in Advance.......................................................................................................... 17

DNS Settings ......................................................................................................................................... 18

Acquiring a Certificate ............................................................................................................................ 19

External Use Configuration ........................................................................................................................... 27

Configure NAT to the APS and VCS ...................................................................................................... 27

Firewall NAT mappings .......................................................................................................................... 28

IMPORTANT .......................................................................................................................................... 29

Installation 30

Setting Up the Configurator .......................................................................................................................... 30

Installing ........................................................................................................................................................ 31

Settings of VCS ............................................................................................................................................. 36

Verifying Basic Installation (IMPORTANT) .................................................................................................... 39

Trouble Shooting ........................................................................................................................................... 40

Frequently asked questions (FAQs) ...................................................................................................... 40

Caveats: ........................................................................................................................................................ 42

Deploying the Conferencing Client

Deploying OmniJoin Conferencing Client via dynamic load ......................................................................... 43

ClickOnce (alternative manual install) ................................................................................................... 43

Launcher (alt. ActiveX

/ Add-on) .......................................................................................................... 48

Alternative.... ActiveX

/ Add-on install .................................................................................................. 48

Via electronic deployment (MSI) ................................................................................................................... 49

Methods of deployment ......................................................................................................................... 49

Create a distribution point ...................................................................................................................... 49

Create a Group Policy Object ................................................................................................................ 49

Assign a MSI package ........................................................................................................................... 52

Publish a MSI package .......................................................................................................................... 54

Redeploy a MSI package ....................................................................................................................... 57

Remove a MSI package ........................................................................................................................ 59

Other methods .............................................................................................................................................. 61

Deploying the Live Contact List/OmniJoin IM 62

Via electronic deployment ............................................................................................................................. 62

Server Management 63

About log files ................................................................................................................................................ 63

What are the private cloud server log files? .......................................................................................... 63

WPC ................................................................................................................................................. 63

APS ................................................................................................................................................. 64

VCS ................................................................................................................................................. 64

Keeping Backups .......................................................................................................................................... 65

Backup and Restore .............................................................................................................................. 65

Uninstalling 67

SPECIAL TOPICS 68

Special Considerations for Backup and Restore .......................................................................................... 68

Special Considerations for Single-Site, Hot Standby Facilities (Manual Cut Over, Not HA) ........................ 69

High Availability Systems & Redundancy (not available in beta release / in development) ......................... 70

General Recommendations and Best Practices ........................................................................................... 70

General ................................................................................................................................................. 71

Best Practices ........................................................................................................................................ 71

IP Address Settings ....................................................................................................................................... 72

Setting 3 IP addresses on one NIC ....................................................................................................... 72

Introduction

Target Users of This Guide

This Guide has been written for readers with the following basic knowledge:



Individuals with IT networking knowledge (i.e., who are capable of setting up ActiveDirectory

and DNS

servers)



Individuals who are generally familiar with certificates and public and private keys



Individuals who are generally familiar with OmniJoin license terms



Individuals with knowledge of OmniJoin products

Related Documentation

he complete OmniJoin Private Cloud documentation set includes the PDF files listed below. These files are

available via OmniJoin public website and the administrator’s console download tab (appears in the left-hand

navigation bar).

 P

roduct brochure (varies by country)

 Systems Requirements Document

 Installation & Planning Guide (this document)

 Administrator’s Guide

OVERVIEW

mniJoin web and video conferencing provides a high-quality

online meeting experience including multipoint HD video,

synchronized wideband audio, and an extensive list of live

collaboration tools. These features support internal meetings,

training, sales, and a wide variety of specialty applications

including boardroom video conferencing, telemedicine,

distance learning, and more.

mniJoin software and online services have been adopted in

financial services, healthcare, government, and many other security conscious environments. First and foremost,

OmniJoin was designed to meet IT manageability and security requirements.

OmniJoin Private Cloud deployments

provide for customer on-premise

installation of virtual conference serv

(VCS), access point server (APS), and

web proxy cache (WPC) content storage

server software. These network services

can be installed on one physical server,

separate servers, or in virtualized server

environments as further described

below. The OmniJoin Private Cloud

backend manages licensing, account

authentication, central process functions

and staging software updates.

n addition, the strategic placement of one

or more virtual conference servers (VCSs)

on the customer’s own network can

provide routing, bandwidth, and video

conferencing performance benefits not

achievable using the public cloud.

Ther

e are several components needed to

complete an OmniJoin Private Cloud

installation, including on-premise servers

and the OmniJoin backend, which is the

managed by the OmniJoin team in our secure datacenter. Here is an overview of the major

server components:



The OmniJoin backend (managed by OmniJoin corporation).

 As an OmniJoin administrator, you will need an OmniJoin administrative account and login credentials.



The Access Point Server (APS) – optional

 Intended for users with the Live Contact List/OmniJoin IM, which is a Windows

application

 Allows users to manage and enter meetings without using their web browser

 Lets users view others status in their Live Contact List/ OmniJoin IM (similar to an address list)

 Send meeting invites

 This is the server component for the Live Contact List/ OmniJoin IM and presence application



The Virtual Conferencing Server (VCS) – required

 The VCS is the central point where meetings are hosted when active. Users who join meetings will connect

directly to a VCS.



The Web Proxy Cache (WPC) Server – required

 The WPC handles all content caching and storage

The t

hree OmniJoin server components (APS, VCS & WPC) are available in the same setup program. The

server administrator decides which component to install when the installation starts.

The a

dministrator can decide to install three components on the same physical server or split the OmniJoin

servers onto separate Windows

servers.

This is one of many possible configurations. In this example the

APS, VCS, and WPC are installed on three separate servers at

one location behind a firewall. Both internal and “external”

conference participants are supported.

Requirements

Server Requirements

• O

mniJoin Private Cloud systems requirements for server resources

 Windows Server

operating system requirements

 Windows Server

2008 & later, 64 bit, capable of 1 Gbps connection minimum

 Server must NOT be a Windows Domain Controller!

NOTE

See also port binding requirements below.

 .Net 4.0 & later

 Microsoft

Office 2013 (32 bit version) is required on the VCS for sharing Microsoft

Office documents

 Minimum and recommended hardware requirements (APS, VCS, WPC)

 For internal meetings where all users are located behind the corporate firewall, we recommend

5 – 15 M

bps of bandwidth to the VCS

 For meetings where there are a mix of users, some behind the firewall and others connecting over t

nternet, we recommend at least 6 Mbps of upstream bandwidth to the Internet.

SERVER H/W APS VCS WPC

SMALL

Minimum hardware

requirements for

bench test and up to

50 users

Intel

Xeon

quad-core

processor at 2.0+ GHz, 4

GB RAM available to this

service, 8 GB of available

hard disk space

Intel

Xeon

quad-core

processor at 2.0+ GHz, 4

GB RAM available to this

service, 8 GB of available

hard disk space

Intel

quad-core processor at 2.0+

GHz, 4 GB RAM available to this

service, 8 GB of available hard disk

space AND at least 500 GB of

available storage capacity for

content (can be direct-attached

storage, DAS, or Microsoft UNC

network path to NAS or SAN)

MEDIUM

Recommended

server for up to 4,000

LCL users and 250

concurrent

conferencing users

Intel

Xeon

quad-core

processor at 2.0+ GHz, 4

GB RAM available to this

service, 8 GB of available

hard disk space

Dual Intel

Xeon

quad-

core processor at 2.0+ GHz

or better, 8 GB RAM

available to this service, 8

GB of available hard disk

space

Dual Intel

Xeon

quad-core

processor at 2.0+ GHz, 8 GB RAM

available to this service, 8 GB

system hard disk space AND at

least 2 TB of available storage

capacity for content (can be direct-

attached storage, DAS, or

Microsoft UNC network path to

NAS or SAN)

LARGE

Recommended

server for up to 4,000

LCL users and 500

concurrent

conferencing users

Intel

Xeon

quad-core

processor at 2.0+ GHz, 4

GB RAM available to this

service, 8 GB of available

hard disk space

Dual Intel

Xeon

quad-

core processor at 2.0+ GHz

or better, 16 GB RAM

available to this service, 8

GB of available hard disk

space

Dual Intel

Xeon

quad-core

processor at 2.0+ GHz, 16 GB RAM

available to this service, 8 GB

system hard disk space AND at

least 2 TB of available storage

capacity for content (can be direct-

attached storage, DAS, or

Microsoft UNC network path to

NAS or SAN)

Requirements

NOTE

The chart above is intended as a guideline. For installation-specific recommendations, please contact

OmniJoin technical support services.

 Po

rts

Required Ports Recommended Ports

WPC 80, 443

APS 80, 443

VCS 80, 443 22, 23, 1270, 37000

Note assigned ports must be bound to the OmniJoin service,

they cannot be shared

 1 Et

hernet port required, 2 redundant Ethernet ports recommended

NOTE

USB, Wi-Fi, and connection types other than Ethernet are NOT supported.

 Ade

quate symmetric bandwidth at each server, 100 Mbps recommended

 Host / Domain Name Services (DNS) resolution

 Administrative access to internal domain controller is required

 Administrative access to customer’s public DNS may be required

 OmniJoin Private Cloud requires a private zone on the customer internal domain called

“Dedicated” and several public (for external participants, if any) or private host names that

successfully resolve to each assigned server resource.

 For a more complete discussion of DNS requirements including the public or private host/domain

name for each server, please refer to the “Host Name Requirements” in this guide.

 Static IP address for all server resources

 Each service (APS, VCS, WPC) requires its own IP address

 IP addresses must be static (can be mapped or “forwarded”, but must be static)

 Network topology



Internet ac

cess to OmniJoin Private Cloud backend

 Network access for internal conference participants to all server resources (APS, VCS, WPC);

see also Network Topology section in this guide.

 Network access for external conference participants, if any, to all server resources (APS, VCS,

WPC); see also Network Topology section in this guide.

 SSL TLS security certificates

 Security certificates issued by a recognized Certificate Authority are required for each server

hosting an OmniJoin service

 Three Web server certificates are available.

Requirements

• Using OmniJoin internally: the Active Directory

’s enterprise certificate authority has

already been configured, or public certificate authority already been configured.

Alternatively, three Web server certificates are available.

• Using OmniJoin externally: Public certificate authority already been configured.

Alternatively, three Web server certificates are available.

 Customers may use OmniJoin self-signed, automatically generated certificates. This is

recommended for quick bench tests only, otherwise network users may receive browser

security warnings after clicking private cloud conference URLs. Please note:

• Self-signed certificates do NOT work for Apple OS X

• Self-signed certificates do NOT work in FIPS mode settings

 Customers may use wildcard certificates, for example *.somedomain.com

 Customers may use separate certificates for internally accessible cloud resources versus

externally accessible resources. For example internal.somedomain.com and

external.somedomain.com.

 Directory services

 Optional, for directory integration (ADS) and/or single sign-on (SSO) implementation

 Customer must have access to directory service administration sufficient to add and edit a

directory service group for OmniJoin

 Clock settings

 SSO implementation (SAML 2.0) requires accurate date, time, and time zone clock settings

(at WPC server)

Client Requirements

• OmniJoin desktop and laptop client requirements

NOTE

The client systems requirements listed below are identical to OmniJoin public online services.

 Windows

 Windows Vista

and later

 Minimum hardware required: Core2Quad, Intel i3, i5 or i7 equivalent; 4 GB RAM; 100 MB

free disk space

 Web browsers

• Internet Explorer

7.0 or later

• Mozilla Firefox v27 or later (note Firefox is self-updating)

• Google Chrome™ v33 or later (note Chrome is self-updating)

 Microsoft

DirectX

9.1 or later (for audio/video peripherals and media processing)

 Audio and video peripherals

• Most Windows

selectable audio and video devices, including USB 2.0+ and PCI

adapter card inputs

 OS X

 OS X 10.6 or later

 Minimum hardware required: Pentium

4, Core2 Duo or Quad, Intel i3, i5 or i7 equivalent; 2

GB RAM; 100 MB free disk space

Requirements

 Web browsers

• Safari v6.1 or later

• Mozilla Firefox v27 or later (note Firefox is self-updating)

• Google Chrome™ v33 or later (note Chrome is self-updating)

 Audio and video peripherals

• Most Apple built-in audio/video devices

 Minimum client bandwidth availability (for desktops and laptops, see above for mobile)

 For hosts or presenters: High-speed broadband internet access (minimum 1 Mbps upstream /

4 Mbps downstream)

 High-speed broadband internet access (minimum 512 Kbps upstream / 4 Mbps downstream)

Network access to private cloud resources – all client components must have DNS resolution (described

above) and ROUTING ACCESS to all OmniJoin Private Cloud resources installed on the customer’s network

(APS, VCS, and WPC servers). Customer IT contacts must have network infrastructure access sufficient to

implement IP address, NAT-port forwarding (NAT-PMP), and possibly proxy settings as may be required for

users to access servers behind the firewall.

Host Name Requirements

OmniJoin Private Cloud requires one internal zone and the following public and private host names as listed

below:



Deployment Host Name – Public – The “Deployment Host Name” must resolve to the WPC server IP

address. The Deployment Host Name must match the SSL certificate bound to that address. This host

name is used for the web portal domain name.



OmniJoin.Dedicated – Private – OmniJoin requires a new zone on the customer’s DNS called “Dedicated”

and a host name called OmniJoin. OmniJoin.Dedicated must resolve to the WPC server IP address (i.e.,

the same IP address as above). Note that this host name can only be registered privately and determines

the customer’s OmniJoin Private Cloud address within the customer’s domain. The OmniJoin.Dedicated

host name is used during the installation process and for on-going server-to-server purposes.



VCS Host Name(s) – If external online meeting participants are required, then this is a public host

name(s) otherwise private – The VCS host name must resolve to the VCS server IP address. The VCS

Host Name must match the SSL certificate bound to that address. The VCS Host Name is required for join

conference links to function.



APS Host Name(s) – If external Live Contact List / OmniJoin IM users are required, then this is a public

host name, otherwise private – The APS host name must resolve to the APS server IP address. The APS

Host Name must match the SSL certificate bound to that address. The APS Host Name is used by the

OmniJoin Live Contact List / OmniJoin IM.

Important Notes Regarding Host Names

Note there is only one ‘Deployment Host Name’ per deployment. VCS and APS host names are associated

with each individual server. All the host names above must be unique, including host names for individual

VCS and APS servers.

For multisite installations as shown in the Network Topologies section, care must be taken to ensure that the

private OmniJoin.Dedicated host name resolves internally across all locations where server resources are

located. Please consult OmniJoin technical support services for multi-site deployments.

Requirements

DNS / IP Address / Server Mapping Summary

APS

VCS

WPC

Live Contact List / OmniJoin IM

Route

—

Route, DNS

Conferencing clients

—

Route, DNS

Web browsers (portal access)

—

Route, DNS

Storage applet

—

Route, DNS

Host/Domain Name

Type

IP Address

Open Ports

Summary Description

Deployment Host Name

(e.g., Conferencing.Xyz.com)

PUBLIC

Static

80, 443

This maps to the primary

WPC Server.

OmniJoin.Dedicated

PRIVATE

Static

80, 443 (same

as Deploying

Host Name)

This also maps to the

primary WPC Server.

VCS Host Name(s)

(e.g., VCS.Xyz.com)

*Public or

private

(see

details

above)

Static

80, 443

required, 22,

23, 1270,

37000

recommended

This maps to one or

more VCSs as may be

required, the host/domain

name must resolve

publicly if external

conference participants

are planned.

APS Host Name(s)

(e.g., APS.Xyz.com)

*Public or

private

(see

details

above)

Static

80, 443

This maps to one or

more APSs as may be

required, the host/domain

name must resolve

publicly if external Live

Contact List / OmniJoin

IM users are planned.

Note assigned ports must be bound to the OmniJoin service, they cannot be shared.

Requirements

Planning Guide for Your Installation:

Host/Domain Name

Type

IP Address

Planning Notes

Deployment Host Name:

PUBLIC

OmniJoin.Dedicated

PRIVATE

VCS Host Name:

APS Host Name:

Installation Planning

Software is being updated without any notice, so please keep in mind that some of the description may differ

from the actual software.

Network Readiness Assessment

The following paragraphs are a simplified readiness assessment sufficient for an OmniJoin Private Cloud

installation at a single location. It is recommended that customers considering a multi-site installation contact

OmniJoin technical support services for a more in-depth readiness assessment, capacity planning, and

determining best server locations.



Client operating environment. OmniJoin client agents require Windows

. Please refer to the Systems

Requirements document for more details regarding operating systems, browsers, mobile devices an

evision levels.



Familiarity with client-side network access, proxy settings, browser security settings, application loaders, user

access rights, and so on.



Server operating environment. OmniJoin server components require a Windows Server

operating

env

ironment. In addition to the hardware and operating system revision levels stated in the Systems

Requirements Document, successful installation requires administrator-level access for software installation



Administrator rights for software installation



Experience acquiring and installing customer SSL security certificates



Ability to set and bind static IP addresses and ports to specific services



Microsoft

.Net readiness. The on-premise components as shown in the architectural overview at the beginning

of this Planning Guide are .Net-based server software resources. For configurations, your organization must

have, or be willing to install .Net 4.0 and later.



Bandwidth. Providing web and video conferencing services on one’s own network requires adequate bandwidth.

In particular, it is recommended the VCS have at least 100 Mbps bandwidth.



Network reliability. In addition to bandwidth, uninterrupted connections are generally required for successful

video conferencing. In general, higher network reliability and fewer interrupted connections means better

network readiness. Customers familiar with QoS controls can often further improve and refine their

conferencing performance. Customers with Wi-Fi to desktops, saturated Internet access, devices and services

that intentionally interrupt connections on a timed basis, and otherwise impeded network routes between t

onferencing users and the server resources shown in the diagrams above will not see the performanc

mprovements normally provided by on-premise server installation. Such networks are NOT ready for privat

cloud deployments.



Access and control over firewalls, routers, and proxies. The installation of all server resources and the

tablishment of the network routes as shown in the architecture diagram above requires customer contacts

that are familiar with ports, NAT port mapping (NAT-PMP), firewall settings, proxy settings, and general

network routing topics. The faster and easier various settings can be reviewed, approved, and set, the more

enable the private cloud environment. Customers without access to and control over firewalls, proxies

and

outers are not ready for private cloud deployment.



Ability to get static IP addresses. Private Cloud deployments require static IP addresses for all server resources.

Certain host/domain names require publicly routable IP addresses (see below).



Expertise with DNS resolution and direct access to one’s own Domain Controller. Private Cloud deployments

require an understanding of private and public host/domain name resolution and administrator access to one’s

own domain controller. In particular, an understanding of fully qualified name resolution as required for internal

users and, optionally, external users, is essential. It should be noted that if external conference participants are

ntended (see diagram), than at least two domain names (see Host Domain Name Services in Installatio

ection of this Guide) must resolve via the public Internet. Customers without full-time staff familiar with DNS

topics, IP addresses, and network routing should not attempt private cloud installation.

Installation Planning

Installation Checklist

In addition to the staff contacts, network expertise, and physical network readiness is good, the following

specific items are also required. It is recommended that the preparation phase of private cloud deployment

include rounding up all the items below.



Completed deployment plan



Capacity plan (for over 50 concurrent users) including server sizing (small, medium, large)



Network topology diagram illustrating server placement



Completed table with host name, IP address and ports (see Installation section on page 9)



Physical or virtualized server resources ready



Administrator access on all required servers for server software installation, SSL certificate installation,

and IP address and port bindings



Custody of desired customer SSL certificate (can use self-signed certificates for bench testing)

NOTE

If purchasing a specific certificate is required, this may be time consuming for some customers.



Administrator access to firewalls for NAT port mapping rules (NAT-PMP)



Administrator access to internal and external DNS server to register private host names and, if separately

managed, access to customer’s method for registering public host/domain names



[Optional, for directory integration and SSO implementation] Administrator access to internal directory

service (ADS)

Installation Planning

Network Topology

In this section we explore various private cloud deployment configurations and how they map to various

customer network topologies. The simplified diagrams on the following pages are intended to conceptually

illustrate server placement, routing, Internet access, and host/domain name resolution requirements for each

scenario.

Please note these generalizations that apply to all scenarios below:



Server-to-OmniJoin backend communications. In all cases, the server resources must have Internet

access and routing sufficient to connect to the OmniJoin Private Cloud backend (for license and account

validation, software update staging, invite-email services, and so on).



Online meeting participant-to-server routing and domain name resolution. The public ‘OmniJoin

Deployment Name’ (a host/domain name) must resolve to the appropriate IP address over the public

Internet; and the OmniJoin.Dedicated host name must resolve to the appropriate IP address over the

customer’s private network (“internal domain”); of course, once DNS returns the correct IP address, it

must be routable for all desired internal and external meeting participants.



In addition to routing and DNS resolution requirements for internal and external participants, server-to-

server communications require successful routing and DNS resolution services between each other (in

particular, using the OmniJoin.Dedicated host name). Note that this requirement becomes more important

when planning advanced, multi-site and HA configurations.

pical Installation – Single Site, Single Server

Installation Planning

Typical Installation – Single Site, Multiple Servers (Adds Capacity)

This is also a very typical installation. This setup can handle more users and heavier conference loads than a

single physical server. Details shown previously are omitted here for simplicity.

Installation Planning

Advanced Scenarios – Single Data Center, More Servers

This is also a very typical installation. This setup can handle more users and heavier conference loads than a

single physical server.

Installation Planning

Advanced Scenarios – Single Data Center, But Located at a 3rd-Party Hosting Facility

This configuration may also be useful for large customer organizations that already have a major hosted data

center location. The benefit of this configuration is the use of a contract hosted data center that may have

more sophisticated physical and environmental controls than the customer’s own locations.

Depending on application, there may be bandwidth and performance benefits too, especially for distributed

operations or lots of external participants.

Installation Planning

Network Planning – Determining the Best Server Locations

It is impossible to reduce the network experience of over 1,000 private network web and video conferencing

installations onto a few pages of an Installation and Planning Guide. However, we can provide some

guidelines that have proven helpful for many customers.

It should be noted that in many cases a single-site installation is planned. In others, the customer already has

pre-determined facilities for new server installation, including virtualized data centers. These factors tend to

dictate where servers are placed. Regardless, the guidelines below should be reviewed, as special

requirements for good bandwidth and public/private domain name resolution are important considerations in

server placement and cannot be overemphasized. Furthermore, some application-specific guidelines are

offered below.



Bandwidth. As mentioned in previous sections, servers require 100 Mbps +, continuous, symmetric

bandwidth. Facilities that are unable to meet this requirement should not be considered.



Name Resolution. Server-to-server communications require successful resolution of the private host

name OmniJoin.Dedicated at all server locations. For a complete discussion of this requirement and

internal/external online meeting attendee-to-server communications, please refer to Host Domain Name

Services in the next section of this Guide.



User Populations. In general, the VCS server or servers should be close to large user populations.



Favor Hosts and Presenters. When considering server locations, the hops and performance for meeting

hosts and presenters versus meeting participants often comes up. In general, it is better to locate the

server closers to hosts and presenters. The fewer hops between those that generate online meeting data

and the VCS the better overall performance.



Video Conferencing Performance. For many customers, the impetus for OmniJoin Private Cloud

installation is improving the routing and performance between the VCS and conferencing users over the

customer’s own LAN, VPN, or private wide-area network. The improved performance can yield multipoint

HD video conferencing equivalent to any telepresence installation. However, in some cases, routing traffic

over the internal network, particularly saturated network segments or already-slow VPNs, may generate

poor results.



Special Considerations for Large Meetings. When planning an installation for large meeting

applications, the VCS bandwidth requirements already mentioned become critical. For this reason,

locating a VCS for this application at a hosting facility may be a consideration.



Special Considerations for Heavy Use of Record-to-Cloud Features. Applications that make heavy

use of the OmniJoin record-to-cloud feature require excellent bandwidth between the VCS and WPC

(content caching and management) servers. WPC performance becomes more critical in these

applications. Under this scenario, we also recommend installing the VCS and WPS on separate servers

in order to decrease CPU load.



Routing, Proxies, Packet Inspection. Latency introduced by excessive routing hops, slow proxy servers,

and slow deep packet inspection will adversely affect online meeting quality, especially VoIP audio quality.

For best results, select server locations that avoid these sources of latency.

Host Domain Name Services

OmniJoin Private Cloud deployments require both PUBLIC and PRIVATE host names. In both cases, the

host name must successfully resolve to the IP address of the appropriate server resource as further

described in the paragraphs below.

It should be noted that domain name resolution must be successful from all server, internal online meeting

attendee, and external online meeting attendee (if any) locations.

This section provides more information on these requirements and the actual host names used.

Page is loading ...

Brother OmniJoin Installation guide

Brother OmniJoin Installation guide

Brother OmniJoin Installation guide

Related papers

Other documents