Bridge Deployment Guide

8/11/2019 Bridge Deployment Guide

1/39

LifeSize Bridge 2200Deployment Guide

August 2013


2/39

LifeSize Bridge 2200 Deployment Guide 2

LifeSize Bridge 2200LifeSize Bridge 2200 is a fixed capacity multipoint control unit (MCU) optimized for HD conferences that

features 8, 12, or 16 ports and expanded conferences that can host up to 48 participants. You can deploy

LifeSize Bridge 2200 standalone or in a cluster.

Related documentation is available from lifesize.com/support.

Terminology

The following terms are used in this document to describe the LifeSize Bridge features. These terms might

differ from terms used with other LifeSize video systems. Familiarize yourself with these terms to best

understand the capabilities of your LifeSize Bridge.

Initial Configuration Describes tasks to enable and configure a LifeSize Bridge 2200.

Clusters You can deploy LifeSize Bridge 2200s of all port capacities as standalone

bridges or as a cluster of bridges to provide more capacity, unified

scheduling, and failover capability.

Conferences

Expanding Your Conference

Configuring Cascaded Conferences

Describes how to create and manage conferences.

To add capacity beyond 8 ports, apply one or more 4-port licenses and an

expanded conference license.

Standalone LifeSize Bridge 2200s support cascaded conferences. One

bridge can host a conference with other bridges as participants.

Managing Your LifeSize Bridge Describes how to administer your bridge and perform diagnostics.

Maintaining Your LifeSize Bridge Provides instructions for backing up, restoring, and resetting the system.

active State of a conference after the first participant has joined.

call Individual participant who joins a conference.

cluster A configuration of multiple MCUs that is controlled by a master MCU that hosts calls and manages

the port resources of subordinate MCUs.

conference Multiple participants, hosted by the MCU.

cascaded

conference

Conference in which an MCU hosts a combination of participant MCUs and single participants.

expanded

conference

Conference hosting up to 48 participants; a license key is required for this feature.

on demand

conference

Conference that is not scheduled in advance, does not have a scheduled start time, and is always

live.

on demand +

conference

On demand + conferences retain all of the attributes of on demand conferences except they are

not always live, not limited to 40 instances, have their own conference ID pool, and can be created

by dialing a valid, unused on demand + conference ID. When prefix dialing is enabled, on demand

conferences are converted to on demand + conferences.

scheduled

conference

Conference that is planned in advance and includes a specific participant capacity for a given start

and end time.
http://www.lifesize.com/supporthttp://www.lifesize.com/support


3/39


temporary

conference

On demand conference that is removed three minutes after the last participant exits the call.

Configure the Virtual Operator to allow users to create temporary conferences. Read more at

Configuring the Virtual Operator.

live State of a scheduled conference when the start time occurs. On demand conferences are always

live. On demand + conferences are never live. Participants need not have joined for the

conference to be live.

master MCU An MCU that controls a cluster of MCUs. All conferences are created and scheduled on the master

MCU. All calls connect through the master MCU, and all port resources are allocated by the

master MCU. The master MCU is also a media server and hosts calls.

media server An MCU hosting conferences in a cluster.

port Refers to both Ethernet ports to which you connect your bridge, as well as conference connection

ports, which determine the number of simultaneous participants that can be hosted on a single

conference.

prefix dialing Configure a prefix for calls to the MCU. The prefix can be provisioned on a gatekeeper to route

calls with the prefix to the bridge. This option converts on demand conferences to on demand +

conferences.

region Logical groupings of MCUs within the cluster.

slave MCU An MCU that functions as a media server in a cluster.

standby

MCU

An MCU configured to take over as master MCU if the master MCU fails. The standby MCU is also

used as a media server by the master MCU.

Virtual

Operator

When enabled, answers calls to the bridge that do not specify a conference ID. You can select a

conference from a menu, or enter the conference ID. Read more at Configuring the Virtual

Operator.


4/39


Section 1: Initial ConfigurationDeploying LifeSize Bridge includes the following tasks:

Installing the LifeSize Bridge Utili ty

Ensure that your system meets the following requirements prior to installing the utility.

To install the utility, enter the IP address of a LifeSize Bridge

in a browser. You are prompted to installAdobe AIR and the LifeSize Bridge Utility. The system on which you are installing the utility must be

connected to the Internet during installation of Adobe AIR. This is only necessary if Adobe AIR is not

installed on your system when you launch the utility for the first time.

When you receive automatic notification of updates to the utility, you can install them immediately or

download and install them at a later time.

Complete the installation of and assign an IP address for each

LifeSize Bridge in your deployment.

LifeSize Bridge 2200 Installation Guide

Install the LifeSize BridgeUtility. Installing the LifeSize Bridge Utility

Update the licenses for each LifeSize Bridge in your deployment. Updating License Keys

Configure each LifeSize Bridge in your deployment. Upgrading your System Software

Optional:Create a cluster. Clusters

Create conferences. Conferences

Optional:Use the SOAP API to control your bridge. Access API documentation at:

http:///docs/soap/

Operating System Hardware Requirements

Microsoft Windows XP Home, Professional, or Tablet PC Edition

with Service Pack 2 or 3

Windows Server 2003

Windows Vista Home Premium, Business, Ultimate, or

Enterprise (including 64-bit editions) with Service Pack 1

Windows 7

Processor: Intel Pentium III or faster

RAM: 1 GB required, 2 GB recommended

Mac OS X v10.5, v10.6, or v10.7 Processor: Intel Core Duo or faster


Linux:

Fedora Core 12

Ubuntu 9.10

openSUSE 11.2

Processor: Intel Pentium III or faster



5/39


6/39


Configuring LifeSize Bridge

You can manage a standalone bridge or a cluster using the LifeSize Bridge Utility from your Mac or PC.

Use the utility to create and manage conferences, configure system and user experience preferences, and

perform diagnostics and maintenance.

NOTE If you plan to use LifeSize Bridge in a cluster, make any configuration

changes before you add the bridge to the cluster. You cannot make changes

to standby and slave bridges after they belong to a cluster, and you must not

change the IP address of the master MCU once it is in a cluster. At a

minimum, ensure the network options are configured properly. Read more at

Configuring Your Networkand Clusters.

License Keys

If your system has HTTP access through port 80 to the LifeSize license key server, it will automatically

attempt to update license keys on your bridge to reflect the version you purchased. From the LifeSize

Bridge Utility, navigate to Maintenance > License Keys andverify that your licenses are updated

properly. For example, if you purchase a 16-port bridge, two 4-port licenses should be listed.

If the licenses listed do not reflect the capacity you purchased, refer to Updating License Keys.

System Date and Time

The system date and time are automatically set if one of the following conditions exists:

The DHCP preference (in Preferences > Network) is enabled, and the DHCP server passes an NTP

server address to your system.

You specify the hostname or IP address of an NTP server in NTP Server Hostname.

NOTE The value you specify for NTP Server Hostname is used in addition to any

NTP server address that a DHCP server passes to your system.

View and configure the systems date and time in Preferences > Date and Time:

System Time Configure the current time on your system relative to the system's configured time

zone.

Time Zone Configure the time zone of your system.

Current NTP Server Shows the currently configured NTP server. This value can be set manually or

specified by DHCP.

NTP Server Hostname Configure the NTP server of your system.


7/39


Configuring the Virtual Operator

Use the Virtual Operator to create and connect to conferences.

1. Access Preferences > Virtual Operator.

2. Select the checkbox to enable the operator.

3. Enter a name for the operator, which appears in the caller ID and redial lists. The default value is

Virtual Operator.

4. Select a language.

5. Select Touch Tonesor Camera Controlas the default navigation method. Touch Tonesuses the

number keys on the remote control and Camera Control uses the arrow keys.

6. To create a temporary conferencefrom the Virtual Operator, select Allow users to create

conferences. This allows users interacting with the Virtual Operator to create an on demand

conference that is removed two minutes after the last participant exits the call.

NOTE If all ports are in use or allocated to scheduled conferences, you cannot

create a new conference from the Virtual Operator.

Configuring Your Network

Configure your network in Preferences > Network.

NOTE Do not change these settings when the MCU is in a cluster. Configure network

preferences on each MCU before adding it to a cluster.

Controlling Ethernet

ports

Enable or disable each of the four Ethernet ports. Disable the ports that you are not

using. Selecting the port shows the status, current IP address, and subnet mask for the

port. You can configure one port at a time or configure up to four network ports for port

redundancy.

Specifying DHCP or a

locally configured IP

address

DHCP dynamically allocates and assigns IP addresses. If you disable DHCP, enter the

locally configured IP address and subnet mask (used to partition the IP address into a

network and host identifier). LifeSize recommends using static IP addresses for bridges

in a cluster to avoid the rare case when the address might change if a bridge fails and

restarts after its IP lease has expired. The virtual IP address in a cluster must be static.

Specifying network

speed

If you do not select Auto negotiate speed and duplex settings, ensure that the values

match the speed and duplex configured on your network switch. LifeSize recommends

that you set Auto negotiate speed and duplex settings unless your network

specifically requires a fixed speed or duplex setting.

NOTE: If your Ethernet switch is configured for half duplex, you might experience poor

quality video when placing calls greater than 512 kb/s. Change your Ethernet switch

configuration to a setting other than Half Duplexwhen selecting Auto negotiate speed

and duplex settings.


8/39


Limitations of IPv6 Support

LifeSize Bridge supports IPv6 with the following limitations:

Clusters do not support IPv6.

SIP calls are not supported with IPv6.

You must restart LifeSize Bridge after configuring a VLAN with IPv6 enabled.

LifeSize systems cannot register to gatekeepers on IPv6.

Adaptive motion control is disabled for IPv6 on LifeSize systems.

You cannot reach LifeSize Bridge through the LifeSize Bridge Utility over IPv6.

Specifying a VLAN ID If you have static VLANs configured, you can configure your LifeSize system to apply a

VLAN tag to outgoing packets and accept incoming tagged packets only if they share

the same VLAN identifier. Specify the VLAN identifier of the VLAN to which the system is

assigned. The value range is 1 through 4094.

IPv6 support Select Enable IPv6to add IPv6 support to the default IPv4 support. Select IPv6 Auto

Configuration to automatically discover the network IPv6 router and be assigned an

IPv6 address, or clear it and provide a static IPv6 address and the address of the IPv6router. Read more at Limitations of IPv6 Support.

Network Port

Redundancy

Select the checkbox to enable redundancy, specify the ports you are using, and specify

the type of port redundancy. The port status, current IP address, and subnet mask for all

enabled ports appear. Read more at Network Port Redundancy.

Default Gateway Specify the default gateway.

Specifying DNS

servers and domain

Enter the IP addresses to configure DNS servers. Enter the domain names to search

when resolving hostnames. DNS translates names of network nodes into addresses;

specify this preference to use DNS to resolve the hostnames to IP addresses.

NOTE:A system cannot detect a change to its IP address from a change in networks

from a wiring closet or through software, such as a change to a router configuration.

Specifying search

domains

Domains are searched in the order you list them, and the search stops when a valid

name is found. To search a name hierarchy, use search domains of varying scope. For

example: building.campus.university.edu, campus.university.edu, university.edu.

Restricting reserved

ports

By default, LifeSize systems communicate through TCP and UDP ports in the range

60000 - 64999. LifeSize recommends that you use the default range. However, you can

restrict the range of UDP and TCP ports that are available for communication. LifeSize

recommends the range you choose, if other than a subset of the default range, begins

with a port number greater than 10000.

The minimum TCP port range is 480, and the minimum UDP port range is 4312.

The utility will not allow you to save a smaller value.

Configuring QoS Set QoS preferences according to the settings in your network. You can specify DiffServ

or IntServ values for audio, video, and data packets. You can also set the IntServ Typeof Service (ToS) preference. By default, Network QoS and IntServ ToS are set to None.

The range for DiffServ values is 0 to 63. The range for IntServ values is 0 to 7.

Adjusting the MTU of

video packets

Video packets that exceed the MTU size for any router or segment along the network

path might be fragmented or dropped, resulting in poor quality video at the receiving

device. You can set the MTU of video packets that your LifeSize system sends. The

default value is 1440 bytes. The valid range is 900 -1500 bytes. LifeSize recommends

you do not change this value unless your network is using a different MTU.


9/39


Network Port Redundancy

Enable network port redundancy to configure and combine up to four Ethernet ports into a single

connection.

1. Click at the top of the utility or navigate to Preferences > Network.

2. Select Enable Network Port Redundancy.

3. Select the type of port redundancy bond.

4. Select the network interface to configure for each of the four redundant ports.

5. Click Save. The icon changes to .

Configuring Your Firewall

If your LifeSize Bridge communicates with other systems through a firewall, configure your firewall to allow

incoming and outgoing traffic to the system through the following ports:

TCP port 1720 for H.323 call setup

UDP port 5060 for SIP call setup

TCP port 5060 for SIP call setup if TCP signaling is enabled for SIP calls

TCP port 5061 for TLS signaling in SIP calls if TLS signaling is enabled

Reserved TCP and UDP ports (default range 60000 - 64999)

80 (HTTP) and 443 (HTTPS) for administration ports

If you are using LifeSize Bridge in conjunction with LifeSize UVC Transit, refer to the LifeSize UVC Transit

Deployment Guidefor more information.

NOTE You must open TCP and UDP ports 5300 through 5305 between the MCUs in

the cluster.

Active Backup The default. Only one port is active. Another port becomes active if the current port

fails.

802.3ad Creates groups that share the same speed and duplex settings.

Balanced Round

Robin

Packets are transmitted in sequential order across available ports.

Balanced XOR Packets are transmitted based on MAC address. The same port is selected for each

destination MAC address.

Broadcast Each port transmits the same signal.


10/39


Configuring Protocols

You can identify the status of H.323 and SIP services, network interface status, and system health from the

system information at the top of the utility. Clicking any of these icons displays the preferences for these

items, which you can then modify.

NOTE If both H.323 and SIP are disabled, a message indicates that calls cannot be

placed or received.

H.323

By default, LifeSize Bridge supports the H.323 protocol for placing and receiving video and voice calls. To

disable support for H.323 calls, clear Enable H.323in Preferences > H.323 > General.

When H.323 is enabled, you can specify an H.323 name or extension to use when placing a call. The

H.323 name and extension identify the device to the gatekeeper. Any registered device can dial anotherregistered device by using this name and extension.

H.323 Name is an optional value that is used when a gatekeeper is configured and requires the system to

register with an H.323 ID. If the gatekeeper administrator assigns an H.323 ID for the system, enter that ID

for H.323 Name.

H.323 Extension is an optional value that is used when a gatekeeper is configured and requires the

system to register with an E.164 number or extension. If the gatekeeper administrator assigns an E.164

number or extension for the system, enter that number for H.323 Extension.

Set the Gatekeeper ID only if the gatekeeper requires it (for example, configurations with multiple

gatekeepers). The Gatekeeper ID must match the gatekeeper ID configured for the gatekeeper to whichthe system is registering. SelectEnable Gatekeeper Authenticationto enable authentication and enter

the authentication username and password.

Set Gatekeeper Mode toAuto to have the system automatically discover a gatekeeper. You can also set

Gatekeeper Mode to Manual to specify the IP address and port for the primary gatekeeper. The

gatekeeper port defaults to the industry standard, 1719.

When you click Save, icons appear in the status bar to indicate the status of the registration process. The

yellow icon appears when your system is attempting to register. If the registration fails, the red icon

appears.

SIP

By default, support for SIP is enabled. To configure SIP as the protocol to use for placing calls, select

Enable SIPin Preferences > SIP > Generaland configure the SIP preferences.

In Preferences > SIP > Identification, enter the username, SIP server authorization name, and password

for the device, if required. The authorization username and password are the values the LifeSize system

uses for authentication. These values are required only if the registrar or proxy require authentication.


11/39


You can enable the SIP registrar or a proxy and configure proxy settings. SIP devices use register settings

to dynamically register their current location.

When you click Save, the status bar indicates the status of the registration process with the SIP server.

SIPappears in yellow when your system is trying to register with the SIP server. If the registration fails, SIP

appears in red. If the registration fails, click Registerto retry.

Ports

By default, UDP and TCP signaling are enabled and cannot be disabled. The default port for each is 5060,

but you can change either to a non-zero value.

By default, the TLS signaling port is 0, which disables TLS signalling. Enter a non-zero value, customarily

5061, to enable TLS signalling. Select Enable the SIP registrarand register to a SIP registrar. Direct SIP

TLS calls are not supported.

If you enable TLS signaling, the system attempts to use Secure Real-time Transport Protocol (SRTP) for

media encryption in SIP calls. If the far side supports SRTP, the media is encrypted.

NOTE The system reboots if you change any port value and click Save.


12/39


Section 2: ClustersA cluster allows you to consolidate all your MCU resources so that you can control all your conferences

through one utility, one IP address, and one scheduler, instead of having to set up and maintain schedules

on multiple MCUs. You can cluster up to 10 LifeSize Bridge 2200s of any capacity.

Each cluster can contain a master MCU, a standby MCU, and up to 8 slave MCUs.

Regions are logical groupings of the MCUs within the cluster. Use regions to group local MCUs, especially

if they reside in the same subnet. You can also specify a region when configuring a conference to influence

which MCU hosts the conference. When a slave MCU fails, the master MCU attempts to reroute calls from

the failed slave MCU to another media server in the same region. If resources are not available within the

region, the master MCU moves the conferences to the next available resource. Participants experience a

brief loss of media before the call resumes. Presentations and recordings must be restarted manually.

At least one region must be specified when creating a cluster, but you can create up to 10.

Required:

Master MCU

Hosts all signaling data for all conferences.

Handles all conference scheduling.

Hosts conferences up to its port capacity.

Recommended:

Standby MCU

A standby MCU is optional but highly recommended to provide signaling failover.

Monitors the health of and periodically clones the data of the master MCU. If the master

MCU fails, the standby MCU takes over as the master MCU, and callers are notified to dial

back into their conferences. Conferences that were hosted on the master MCU are moved to

another MCU in the cluster with available ports.

Must reside in the same subnet as the master MCU.

Requires a virtual IP address for signaling failover. In addition to the static IP addresses that

you assign to each MCU in a cluster, reserve a unique, static IP address to be a virtual IP

address when you designate the standby MCU. The virtual IP becomes the address for the

cluster, initially pointing to the master MCU unless it fails, at which point the virtual IP

address points to the standby MCU.

All calls must use the virtual IP address once you add a standby MCU to the cluster.

Hosts conferences up to its port capacity.

Optional:

Slave MCUs

Act as media servers and host conferences up to their port capacity.

Are protected by failover. If a slave MCU fails, the master MCU attempts to move the

conferences hosted on the failed slave to other MCUs.


13/39


Initially, calls to the virtual IP address are routed to the master MCU, which determines which MCU hosts

each conference. A conference never spans bridges and is always contained on just one bridge.

If a slave MCU fails in the Americas region in the example, the master MCU attempts to move the

conferences to the other slave MCU in the Americas region. Otherwise, conferences are moved to the next

nearest MCU with enough free ports. Participants experience a brief loss of media before the call resumes.

Presentations and recordings must be restarted manually.

The standby MCU monitors the health of the master MCU and clones the master MCUs configuration

when changes to it are detected. In addition to its role as a media server, the standby MCU is prepared to

take over if the master MCU fails. If the master MCU fails, all current conferences fail. However, a

message instructs users to rejoin an interrupted conference by dialing the clusters virtual IP address.

NOTE The message might not appear in some conferences depending on the

behavior of participant video devices.

The virtual IP address reroutes subsequent calls to the standby MCU, which uses available port resources

to recreate the conferences. When the former master MCU recovers, it automatically becomes the standby

MCU.


14/39


Conference failover in a cluster is contingent on available spare resources, and conferences cannot span

bridges. Therefore, if a bridge fails and no other bridge in the cluster has enough spare ports to host the

conferences from the failed bridge, those conferences cannot be preserved or reconnected. In a cluster of

bridges with mixed port capacity, some conferences will never be able to fail over. For example, a 16-

participant conference can never fail over to a 12-port or 8-port bridge, so the conference simply fails.

Cluster Requirements

Before you add bridges to a cluster, ensure you have met the following requirements:

All bridges are licensed for the intended number of ports. You cannot add capacity licenses to bridges

when they belong to a cluster. You must remove them from the cluster, update their capacity license,

and add them to the cluster. Read more at Dismantling a Cluster.

The master and standby bridges reside in the same subnet.

Bridges that you intend to group in regions reside in the same subnet.

All bridges have the same software version and that the software is v.2.0 or later. You can configurethe utility to upgrade MCUs to the master MCU software version as you add them to the cluster. Refer

toAdding the Standby MCUandAdding Slave MCUs.

All bridges for the cluster have IPv6 enabled, or none do.

All bridges for the cluster have FIPS enabled, or none do.

You have reserved a static IP for the master virtual IP address that is not being used as the IP address

of any bridge in the cluster or any other device in the network.

All bridges for the cluster have been properly configured. You cannot configure subordinate bridges

when they belong to the cluster.

If you intend to add an existing bridge to a cluster as a standby or slave MCU:

- Upgrade the software to the latest version. Refer to Upgrading your System Software.

- Move conferences configured on the bridge to the scheduler on the master MCU. Conferences on

standby and slave MCUs are not automatically merged with the master MCU. They remain on the

slave or standby MCU, ready to be used if the MCU ever reverts to standalone, but are unavailable

while the bridge is a standby or slave MCU. LifeSize recommends you save the system

configuration of each MCU before adding it to the cluster. Refer to Saving a System Configuration.

If your cluster elements are separated by firewalls, configure the firewalls to allow incoming and

outgoing traffic. Refer to Configuring Your Firewall.

After you set up a cluster, do not change the following:

Master MCU IP address

Network preferences

Changing these options might result in unexpected behavior or cause the cluster to malfunction.

You cannot change the virtual IP address of a cluster. You must dismantle the cluster and start over. Read

more at Dismantling a Cluster.


15/39


Adding the Master MCU1. From the LifeSize Bridge Utility, log in to the bridge that you want to designate as the master MCU.

2. Navigate to Clustering > Configure.

3. Enter a Regionname. You must name a least one region and can specify up to 10.

4. Click Set Master. The Participation Typechanges to Master.

CAUTION Do not change the IP address of the master MCU after it is in the cluster.

Adding the Standby MCU1. Enter the IP address of the bridge that you want to designate as the standby MCU. It must be in the

same subnet as the master MCU.

2. Select the Region. It must be the same region as the master MCU.

3. Enter the administrator password for the LifeSize Bridge Utility.

4. Optional:Select Cluster Licenseto enter a cluster license key for the standby MCU. Do not perform

this step if you have already applied this license.

5. Optional:Select Allow Upgradeto allow the utility to automatically upgrade the new MCU if its

software version differs from the master MCU.

6. Click to add the MCU to the cluster.

7. Click Set Virtual IP Address.

8. Enter the unused, static IP address you reserved for the virtual IP address. It must reside in the same

subnet as the master MCU and standby MCU. Once set, you cannot change the virtual IP address.

9. In the listing of the MCU you just added, click . The Participation Typechanges to Standby.

10. Log out and log back in using the virtual IP address for the cluster.

Adding Slave MCUs1. Navigate to Clustering > Configure.

2. Enter the IP address of a bridge.

3. Select the Region, or define a new one.

4. Enter the administrator password for the LifeSize Bridge Utility.

5. Optional:Select Cluster Licenseto enter a cluster license key for the standby MCU. Do not perform

this step if you have already applied this license.


16/39


6. Optional:Select Allow Upgradeto allow the utility to automatically upgrade the new MCU if its

software version differs from the master MCU.

7. Click to add the MCU to the cluster.

8. Repeat this process to add up to 8 slave MCUs.

Dismantling a Cluster

LifeSize recommends you save your cluster system configuration before dismantling the cluster. All cluster

scheduler information is lost when you convert a master MCU to standalone. Read more at Saving a

System Configuration.

1. In the utility, navigate to Clustering > Configureand click to remove each MCU, starting with the

slaves. Remove the master MCU last.

2. After you remove the standby MCU, log back in to the utility using the Master MCU IP address.

3. Click to convert the master MCU to standalone.


17/39


Section 3: ConferencesThe following types of conferences are available:

Create and manage conferences from the calendar view of conferences in the Scheduler. You can view all

conferences by day, week, or month.

NOTE If LifeSize UVC Manager manages your bridge, use the scheduler in LifeSize

UVC Manager, not the LifeSize Bridge Utility.

Port Allocation

The Scheduler manages the scheduling of ports and ensures that no conflicts exist. Each participant in a

conference uses one port. On a standalone bridge, you can choose a minimum of 2 and up to the

maximum number of ports licensed on your bridge for the conference. In a cluster, you can allocate up to

the ports per conference of the largest capacity bridge in your cluster. Additionally, when 16 ports are

selected for a conference, you can select Expandto accommodate up to 48 participants.

NOTE Expandis available only for scheduled conferences, if all ports are available,

and if you have licensed this feature. In a cluster, you can schedule as many

48-way conferences as you have licenses, and any 16-port bridge can host

the 48-way call, not just the bridge on which the license resides. Read more

about Expanding Your Conference.

Scheduled conferences take priority over on demand conferences, and port conflicts are always settled in

the scheduled conferences favor. If a scheduled conference becomes active, and on demand conferences

are using ports the scheduled conference needs, the longest running on demand conference terminates to

free the necessary ports for the scheduled conference.

Limit scheduled conferences to 10,000 or fewer for the most efficient operation.

Scheduled A conference with a specific start and end time. Ports are allocated by participant.

On demand

On demand +

A conference with no start or end time and no allocated ports. These conferences use any

unscheduled or active port.

On demand and on demand + conferences include all the attributes of scheduled conferences

except start and end times and recurrence settings. An on demand or on demand + conference

begins if required ports are available when the first participant attempts to join.


18/39


On Demand and On Demand + Conferences

By default, you can create up to 40 on demand conferences, which share the same pool of conference IDs

as scheduled calls. On demand conferences are listed in a separate view in the Scheduler, to the left of the

calendar view. If you have reached the maximum number, the button is disabled.

Alternatively, you can choose to enable prefix dialing, which converts on demand conferences to on

demand + conferences. The converted on demand + conferences are assigned new conference IDs in the

new on demand + ID range. For example, if an on demand conference has an existing conference ID of

1011, and the next available on demand + ID is 10001, the converted on demand + conference will retain

the same conference name but be assigned the new ID of 10001.

The following table compares the two on demand options.

NOTE Conversion of on demand conferences to on demand + conferences is

irreversible. You can choose to disable prefix dialing, but all existing on

demand + conferences disappear and are not converted to on demand

conferences.

Prefix Dialing

Configure a dialing prefix for calls to the bridge in Preferences > Prefix Dialing. By default, Allow

Conference Creationis enabled, allowing you to create on demand + conferences by dialing an unused

ID in the on demand + conference range. The conference settings are taken from the Conference

Template, listed first under On Demand + Conferences in the Scheduler. You can modify the Conference

Template. Although it is listed with on demand + conferences, it is not a conference and you cannot use it

to make calls.

On Demand Conferences On Demand + Conferences

Limited to 40 instances. Up to 10,000 reserved conference templates. The actual

number of conferences is limited only by the conference ID

bounds settings.

Always live. The utility always counts an on

demand conference in On Demand(at the top

of the utility).

Become active when the first participant joins. The utility only

counts an on demand + conference in On Demandwhen the

conference is active.

Can be chosen from the Virtual Operator. Never appear in the Virtual Operator.

Can be created from the Virtual Operator. Can be created by dialing an unused ID in the on demand +

conference range. Conference Template provides settings for

these conferences.

Shares conference ID pool with scheduled

conferences.

Has a separate conference ID pool from scheduled

conferences.

Prefix can be configured on a gatekeeper for call routing.

Both and are

accepted dial strings.


19/39


Configure the bridges dialing prefix on your gatekeeper to make call routing to the bridge easier and

enable up to 10,000 users to use the bridge with unique dial strings. Because some gatekeepers might

strip the prefix before forwarding the call while others might pass it through, LifeSize Bridge accepts a

conference ID with or without a prefix as a valid dial string.

By default, conference IDs are 4 digits and range from 1000 to 9999. On demand + conference IDs default

to 5 digits with a range from 10000 to 99999. The number of digits for these two IDs must be different, andthe IDs cannot have fewer than 4 digits. Navigate to Preferences > Schedulerto change these options.

Because the bridge accepts a conference ID with or without the prefix as a valid dial string, and because

the bridge strips the prefix, the conference ID range you choose cannot produce a conference ID whose

first digits are the same as the prefix. Otherwise, the digits can be mistaken for the prefix and stripped,

resulting in an invalid conference ID. A call with an invalid conference ID defaults to the Virtual Operator

and, because on demand + calls never appear in the Virtual Operator, the caller is never able to join the

call.

Similarly, ensure that the number of digits in the prefix added to the conference ID range does not equal

the on demand + ID range.

For example, default conference IDs are 4 digits, and default On demand + conference IDs are 5 digits. A

two digit prefix ensures that the two ID ranges can never be confused for one another by the addition of a

prefix.

To disable prefix dialing, clear the prefix and click Save.

Creating a Conference1. To create an on demand or on demand + conference, click in the Scheduler.

-or-

To create a scheduled conference, open the Scheduler and double-click the desired date for the

conference, or right-click the date and choose Create Conference.

NOTE Create a cascaded conference or lecture conference by selecting the

appropriate option in Conference Type. Read more at Configuring Cascaded

Conferencesand Lectures.

2. Select Autoto automatically assign an ID to the conference. Clear the checkbox to assign a specific

conference ID.

NOTE If you specify a conference ID that is already in use, the system substitutes an

alternate value. You cannot modify the conference IDs of live conferences.

3. Enter a name for the conference.

4. Optional: Enter a description of the conference.


20/39


5. Optional: Enter a password that users must enter to join the conference. Select Display Passwordto

include the password in the meeting invitation. Passwords must be 20 characters or fewer, numbers

only.

6. Scheduled conference only:Select All Day or adjust the time frame for the start and end date and

time.

7. Scheduled conference only:For recurring conferences, select how often to repeat. Recurringconferences are indicated in the Scheduler by .

8. Scheduled conference only:Choose the number of ports to allocate for the conference. For up to 48

participants in a scheduled conference, choose 16 ports and select Expand.

NOTE Expandis available for scheduled conferences only, if all ports are available,

and if a license for this feature is available. Read more at Expanding Your

Conference.

9. To set additional preferences, click Show Details:

Preference Description Default Value

Conference Type Refer to Configuring Cascaded Conferencesand Lectures. Standard

Time Zone Scheduled conferences only:The time zone in which the conference is

hosted. Automatically adjusts for daylight saving time. Defaults to a

city in your detected time zone.

a city in your

detected time

zone

Language The language of the user interface text and voice prompts. English (US)

Self View The view from a participants camera appears on their screen. Off

Speaker Order The most recent speaker appears in the prominent window. On

Status Indicators Status icons appear on the user interface. On

Announcements Voice prompts and system sounds indicate the current system status

or action required.

On

Navigation Control the interface using touch tones or the far end camera control

buttons on the LifeSize remote control.

Touch tones

Show System

Names

System names of onscreen participants remain visible during the

conference.

Off

Text Inset How far the text is offset from the sides of the screen. 7%

Region (Cluster

only)

The region in which you want the conference media to be hosted, port

resources permitting.

Auto

Default Layout The default layout for the conference. Auto

Participants A list of participants to add to a conference when it becomes live.

In a scheduled conference, these participants are dialed when the

conference becomes live.

In an on demand conference, all participants are dialed when one

participant dials the conference, making it active. You can also trigger

the conference from the Call Manager by clicking . If you preferthat participants must dial in individually, do not define any participants

in this list.

no default


21/39


10. Click Saveto make the changes and close the dialog box.

NOTE Not all options are available during active conferences or for expanded

conferences.

You can also manage conference restrictions from Preferences > Scheduler.

Participant

Bitrate

The bit rate for each participant in the conference. Auto

Security Encryption level used for the conference.Autoallows both encrypted

and unencrypted calls. Strictconnects encrypted calls only.

Auto

Resolution The video resolution used for the conference. The default is 720p60. Auto

Video Codecs Customize the default video codec order, or allow the system to

choose automatically.

Auto

Audio Codecs Customize the default audio codec order, or allow the system to


Auto

Presentations The ability to display data from a PC or secondary input. On

Presentation

Codecs

Customize the default presentation codec order, or allow the system to


Auto

Conference ID Bounds Choose the number of digits the system allows for a conference ID. The

default is 4. Also specify the minimum and maximum allowable numbers.

Minimum default: 1000. Maximum default: 9999.

On Demand + ID Bounds Choose the number of digits the system allows for an on demand +ID.

The default is 5. Also specify the minimum and maximum allowable

numbers. Default minimum: 10000. Default maximum: 99999.

Maximum On Demand Conferences Enter the maximum number of on demand conferences the system can

manage. The default is 40. Does not apply to on demand + conferences

when prefix dialing is enabled.

Expired Conference Removal Time Choose the length of time for the system to store expired conferences.

The default is 3 months.

Preference Description Default Value


22/39


Troubleshooting Scheduling Failures

Expanding Your Conference

NOTE Expanded conferences are supported only on 16-port bridges that have a

license installed for the feature. Contact your LifeSize Partner or LifeSize

Technical Services to obtain the expanded conference license key. Learn how

to apply the license key atUpdating License Keys.

You can add up to 48 participants to a scheduled conference by selecting 16 ports and then selecting

Expand. The Expandcheckbox does not appear if all 16 ports are not available, or if a license key is not

available for this feature. On a standalone 16-port bridge, no other conferences can be created during this

time. Read Creating a Conferencefor specific instructions.

In a cluster, you can schedule as many 48-way conferences as you have licenses, and any 16-port bridge

can host the 48-way call, not just the bridge on which the license resides. Participants of an expanded

conference are unable to control the conference or change the layout. The default layout shows video from

the last 8 active speakers. Change layouts from the Scheduler to show fewer or additional participants.

Using the Virtual Operator in an Expanded Conference

If you dial in to the Virtual Operator during an expanded conference on a standalone bridge and are among

the first 16 callers, you are instructed to use touch tones to navigate the menu. Press the 2 (up) and 8

(down) keys on the remote control to navigate to the conference and press 6 to select it.

Callers 17 and later automatically reach the Virtual Operator, which instructs you to enter the conference

ID directly.

Message Action

The conference has no name. Enter a name for the conference.

No available ports for requested time. Select a time for the conference when the required number of ports

is available.

All conference IDs are in use. Change the range of possible conference IDs in Preferences >

Scheduler to allow the system to assign a unique ID.

Exceeded maximum number of on demand

conferences.

Increase the value for Maximum On Demand Conferencesin

Preferences > Scheduler,or consider enabling prefix dialing.

Scheduler file not found. The system may

be corrupt.

Restart the LifeSize Bridge Utility.


23/39


Configuring Cascaded Conferences

NOTE Clusters do not support cascaded conferences.

On a standalone bridge, you can allow a conference to host other conferences as participants. The host

conference can include MCU and non-MCU participants. Participant MCUs cannot host other MCUs. A

scheduled cascaded conference can host up to 16 participant MCUs. An on demand cascaded conference

can host up to 15 participant MCUs. Configure a cascaded conference as follows:

1. Determine the host MCU and note its IP address.

2. Configure conferences on each participant MCU.

a. From a participant LifeSize Bridge Utility, create a scheduled or on demand conference. Refer to

Creating a Conference.

b. Click Show Details.

c. From Conference Type, select Cascading Participant.

d. Click Add Participant, enter the host MCUs number and change Participant Typeto Host MCU.

e. Add other participants as required.

f. Note the conference ID.

NOTE For third party MCUs, create the conference and add non-MCU participants

only. Configure the layout to full screen and active talker. The participant

conference must be able to accept a call from the host.

3. Configure a conference on the host LifeSize Bridge.

a. From the host LifeSize Bridge Utility, create a conference.

b. Click Show Details.

c. For Conference Type, select Cascading Host.

d. Click Add Participant, add each participant MCU number, and change Participant Typeto

Participant MCU. The dial string you enter as the participant MCU number must specify the

participant conference you created in step 2.

e. Add other participants as required.

Participant MCUs send the last talker on their conference to the host conference, and participants on the

participant conference can view only the layout sent from the host MCU.

NOTE Third party MCUs produce infinitely cascaded video to the host until one of

their participants joins. SIP presentations are not supported on third party

MCUs.


24/39


Lectures

Use the lecture conference type to specify a participant who always appears in the main window,

regardless of who is speaking. Non-lecturer participants see only themselves until the lecturer joins the

conference. Non-lecturer participants see only the lecturer after the lecturer joins. You can adjust the layout

for the lecturer, but no other participant.

When creating the conference, click Show Details > Conference Type > Lecture and change one

participants type to Lecturer.

Presentations

Users can share data during a call, typically from a laptop or personal computer that is connected to the

appropriate input on the participating LifeSize system.

By default, presentation codecs are automatically selected. You can customize the codecs and the order in

which they are attempted in a conference from Create New Conference. Click Show Details, and selectCustomfor Presentation Codecs. Then choose the codecs to add to the custom list, and drag them to the

desired order.

The Call Manager indicates the status of a presentation in progress .

Managing Conferences

The Call Manager automatically updates as conferences become live or expire, and as calls connect and

terminate. The first column in the Call Manager identifies whether the conference is scheduled or on

demand . You manage all the MCUs in a cluster from one IP address. Click next to the conference to

view additional details about the conference:

Options in the second column depend on whether you are viewing a single call or controlling allparticipants in the conference. Following are the actions you can take:

Identifies the participant as a voice call.

Identifies the participant as a video call.

Identifies the participant as an incoming call.

Identifies the participant as an outgoing call.

Identifies the received audio as unmuted or muted. LifeSize devices only.

Identifies the participant or conference as encrypted.

In live conferences with no participants, dial the participants when the conference becomes live.

Toggle the audio transmission.

Toggle the video transmission.

Change the video layout. Refer to Layouts.


25/39


The remaining column in the Call Manager provides detailed information about the conference:

name and ID of the conference

conference state

number of allocated ports

number of participants

start and end time of the conference (scheduled conferences only)

protocol (the registration status for the conference with the respective gateway or registrar)

Individual calls show the following:

call state (for example, dialing, connecting, busy, or unreachable)

system name, IP address, and number

encoder and decoder on standalone bridges; identifies the host bridge in a cluster

protocol used

vendor information for the system (and software version number)

Stateindicates the conferences registration status with the communication protocol. The following values

might appear:

The video layout for a participant or the conference is locked. Locking a layout prevents a participant

from changing the layout. It does not prevent an administrator from changing the layout from the

LifeSize Bridge Utility. Refer to Locking a Video Layout.

Change the user experience settings: language, self view, speaker order, status indicators,

announcements, navigation, persistent system names, and text inset value. Read more at Creating a

Conference.

View the following audio, video, and presentation statistics for a call, including both transmit and

receive data: resolution, codec, bandwidth, frame rate, maximum jitter, average jitter, and packet

loss.

You can increase or decrease the value in Refresh Intervaland click Refresh to update the number

of seconds to refresh the values.

Add a participant to the live conference. (Disabled if the conference has reached full capacity.)

Terminate the call or conference.

expiring The conference is about to exceed its scheduled time.

expired The conference has exceeded its scheduled time and will be removed.

unregistered The conference is currently not registered with an H.323 gatekeeper or SIP server.

registering The conference is attempting to register with the H.323 gatekeeper or SIP server.

registered The conference successfully registered with the H.323 gatekeeper or SIP server.

registration failed The registration failed. Click Registerto retry.

unknown error An unknown error prevented registration. Click Registerto retry.


26/39


Modifying Conferences

You can configure most conference attributes, either through the Scheduler or through the Call Manager.

Changing options from the Scheduler during a conference does not affect participants in the active

conference. Use the Call Manager to make immediate changes to an active conference.

Multiple instances of the LifeSize Bridge Utility (running on separate computers) can manage the same

schedule. If you add, modify, or delete a conference, the change automatically appears in a second

instance of the utility.

You can modify conferences in the following ways:

Set the minimum and

maximum limits for

conference IDs

Preferences > Scheduler Choose the number of digits and the minimum

and maximum range.

Edit or remove an on

demand conference

Scheduler Highlight the conference name you want to

modify or delete and double-click.

NOTE:A limited set of edit options are available foractive conferences to ensure uninterrupted

connectivity.

Add participants to a

conference

Call Manager Click . Enter the participants Number, specify

the call Type, Protocol, and Bitrate. You cannot

add a participant MCU to a cascaded conference

using this method.

NOTE: When the conference has no available

capacity, is disabled.

Move participants from one

conference to another

Call Manager Drag participants from one conference in the Call

Manager to another. The participant immediately

drops from the current conference and joins the

other conference. If you move a participantsharing a presentation, the presentation

immediately ends.

Specify when to remove

expired conferences from

the Scheduler

Preferences > Scheduler The default is 3 months.

Modify or delete recurring

conferences

Scheduler or Call Manager Choose to edit or delete a single instance or all

instances in the series.

Cut, copy, paste, or drag Scheduler Drag a conference to a new time.

Copy and paste a conference to a new date and

time. A new ID is assigned.

Copy and paste an on demand conference to be ascheduled conference and the reverse. By

default, an on demand conference copied to a

scheduled conference becomes an all day

conference; however, you can edit the conference

details to adjust this result.


27/39


Layouts

The following illustrations show the number and order of layouts available for each possible call scenario.

Layout rotation is determined by the maximum number of video participants allocated for the conference.

Participants appear in the order in which they join the conference. When new participants join the

conference after all available spaces in the current layout are filled, the layout changes to the next bestlayout. The layout also changes to the best fit as participants exit the conference, unless manually

changed by the user.

In lecture conferences, you can adjust the lecturers layout only. All other participants see the lecturer full

screen.

With only one participant in a conference, the full screen view becomes the first layout in the rotation.

If up to two maximum participants are allocated for the conference, the following layouts are available:

If three maximum participants are allocated for the conference, the following layouts are available:

If four maximum participants are allocated for the conference, the following layouts are available:

If 5 to 7 maximum participants are allocated for the conference, the following layouts are available:


28/39


If 8-16 maximum participants are allocated for the conference, the following layouts are available:

If only one participant is connected, the setting for Self Viewis ignored until a second caller joins the

conference. Self Viewis disabled by default.

Changing Layouts for an Individual Call1. From the Call Manager, select the call whose layout you want to change.

2. Click .

The available layouts appear for that call. The current layout appears highlighted in green.

3. Choose the desired layout.

4. If speaker order is not disabled, the layout change takes effect immediately. Otherwise click Apply.

5. Click Close.

Customizing How Participants Appear in Layouts

You can choose to disable speaker ordering and instead drag a participant into a window for the duration of

the call. You can customize participant positions in the master layout of the conference or in layouts of

individual participants.

1. From the Call Manager, select the conference or participant whose layout you want to change.

2. Click .

The available layouts appear for that conference or participant.


4. Click Disable Speaker Order.

5. Drag participants from one window in a layout to another or replace participants in layout windows with

participants not currently visible in the layout. Click Clear Allto remove all participants from the layout

and then drag participants into the layout.

6. Click Apply.


29/39


Locking a Video Layout

From the Call Manager, select the conference whose layout you want to change.

1. Click .


3. Choose lock.

4. Click Close.

To ensure new participants joining a call are locked, choose a default layout and lock it for the conference

instead of locking individual callers. Locking a layout prevents a participant from changing the layout. It

does not prevent an administrator from changing the layout from the LifeSize Bridge Utility.

NOTE The layout in lecturer conferences, in expanded conferences, and for

participant MCUs in cascaded conferences is always locked and cannot be

unlocked.


30/39


Section 4: Managing Your LifeSize Bridge

Remote Administration

By default, remote access to a LifeSize system through the web (HTTP) or SSH is enabled. To change

remote access through these mechanisms, configure Preferences > Security.

Disabling HTTP immediately disconnects you from the system, and you are no longer able to manage the

system from the LifeSize Bridge Utility. If you select Disabledfor this preference, you are prompted to

confirm the change. You can re-enable HTTP from the console using the set http enabledcommand.

Refer to the LifeSize Bridge Installation Guidefor more information about running commands from the

console.

FIPS 140-2 Securi ty

LifeSize Bridge 2200 supports the Federal Information Processing Standard (FIPS) 140-2 (Level 1), a US

government computer security standard. By default, FIPS security is disabled. When you enable FIPS

140-2 in Preferences > Security > FIPS, the following events occur:

The system reboots.

FIPSappears at the top of the utility after the system reboots.

System Upgrade, System Save, and System Restoreare disabled in Maintenance.

Add, Delete, and Updatebuttons are disabled on the License Keyspage.

Preferences > SIP > TLS Signaling Port is removed.

In the Add Participantdialog box, the protocol selection is removed.


31/39


Diagnostic Tools

Call Records

LifeSize Bridge 2200 records information about the calls it hosts. You can specify how many call records

you want the bridge to store, and you can download the records in XML format.

Select the maximum number of call records, up to 2000, to store in Preferences > Diagnostics.

From Diagnostics > Call Records, click Download CDRs.

Save the .tgz file, which includes an XML file and an XSL style sheet for viewing in the application of your

choice.

Each call leg is contained on a single line, which contains the following:

system name and IP address

conference ID

start time and duration

call direction

protocol

dialed and actual bandwidths

the reason for disconnection

Possible reasons for disconnection are as follows:

Normal disconnect The call was terminated correctly.

User busy The caller was unreachable.

Unreachable destination The call could not connect to the other party.

Destination rejection The call was rejected and could not connect.

Call deflection The call request was redirected.

In conference Another call is in progress.

No bandwidth The bandwidth necessary for the call is unavailable.

Security denied Incompatible security support.

TCS rejected Terminal Capability Set (TCS) failed.

Local failure The call disconnected due to a subsystem failure.

Unreachable GK The system could not register with the gatekeeper; the gatekeeper was

unavailable or the gatekeeper IP address was invalid.

No GK resource The gatekeeper is unavailable.

No GW resource The system could not register with the gateway.

Invalid address The IP address was invalid.

Called party not registered The called participant is unregistered and unreachable.


32/39


System Health

For a standalone bridge, navigate to Diagnostics > System Healthto view the status of the system,

temperature, and fans, and determine whether the system has experienced critical errors. For a cluster,

navigate to Clustering > Healthto view these parameters for all bridges in the cluster.

The current running temperature is color coded accordingly:

Fan status for the four fans is color coded accordingly:

These values are read only. You cannot adjust fan speed.

System Information

Diagnostics > System Informationdisplays details about your system, including serial numbers and

versions.

Export this data to a text, HTML, or XML file by clicking the corresponding button.

System Logs

From Preferences > Diagnostics, enter the hostname or IP address of your system log server. Then

choose the log level for each of the subsystems.

NOTE Choosing verbose or debug can adversely affect the performance of the

system.

Caller not registered The caller is unregistered and cannot connect to the call.

Max calls exceeded The maximum number of calls has been reached.

Audio resource unavailable Audio is unavailable to complete the call.

Green normal operating temperature

Yellow approaching critical temperature

Red system overheated or shut down due to overheating

Green normal

Red stalled or failed


33/39


From Diagnostics > System Logs you can filter the current log and save the current view to your

computer. Logs are color coded by level:

Select the checkboxes on the left to choose which subsystem data to view or export. Select the levels at

the top to choose which level of the logs to display.

System Reboot

The system reboots when you complete any of the following tasks:

Manually reboot the system in Diagnostics > System Reboot.

Reset the system to its default state in Maintenance > System Reset.

Revert the system to the previous state in Maintenance > System Revert.

Restore the system to a saved state in Maintenance > System Restore.

Change the VLAN ID preference in Preferences > Network > VLAN ID.

Change TCP reserved ports in Preferences > Network > Reserved Ports.

Change the UDP signaling port, enable or disable TCP or TLS signaling, or change the TCP or TLS

signaling ports.

Upgrade the system software in Maintenance > System Upgrade.

Change the IP address.

Change protocol and network preferences; these are disabled if calls are in progress. Schedule a

maintenance window to make these changes by creating a conference that uses all ports and has a

password that is not shared.

You might need to reboot a system that fails to connect calls. To reboot the system, click in

Diagnostics > System Reboot.

If calls are in progress, you are prompted to continue or cancel. Press Continueto disconnect the calls

and complete the reboot.

NOTE If the user interface is not responding and you are unable to reboot the

system, press the Reset button on the front of the system. Do not attempt to

restart your system by unplugging the power cord.

Verbose White

Debug Blue

Info Green

Warning Yellow

Error Orange

Failure, Crit ical, Alert, Panic Red


34/39


Clustering System Health

Navigate to Clustering > Healthto view the status of system health, temperature, and fans, for all bridges

in the cluster. Refer to System Healthfor an explanation of the color codes for each class of information.

System UtilizationNavigate to Clustering > System Utilizationto view information about the master bridges:

active and available ports; click Viewto access the Scheduler

active and scheduled conferences; click Viewto access the Call Manager

number of conferences

number of Virtual Operator conferences

total calls

total voice calls

total video calls

available expanded licenses

Coroner

Support personnel might request that you capture coroners from your system to help identify the cause of

a problem with your system.

When instructed to gather this information, navigate to Clustering > Coroners. You can select a subset of

bridges in the cluster and click Obtain Selected Coroners, or click Obtain All Coronersto capture files

on all bridges in the cluster.


35/39


Section 5: Maintaining Your LifeSize BridgeSystem upgrade, license key, and system reset options are available from the Maintenancepage.

You can schedule a maintenance window in which to manage the system and change preferences that

might require a system reboot. Some preferences are unavailable if calls are in progress.

Create a maintenance window by scheduling a conference that uses all ports and has a password that is

not shared.

Saving a System Configuration

1. Navigate to Maintenance > System Reset.

2. Click .

3. Choose a location to save the configuration file and then click Save.

Restoring a System Configuration

1. Ensure that a current, saved configuration file exists before performing a restore.

NOTE Configuration preferences and options vary across software releases.

Restoring a system configuration by using a file saved from a different

software release can produce unexpected results. Only restore a

configuration that was saved from the same software release.

2. Hang up all calls connected to the system. If calls are connected when you perform a restore, you are

prompted to continue or cancel the restore. If you continue, the system restore process terminates the

calls.


4. Click .

NOTE You must have a current system configuration saved prior to executing the

system restore function or you will be unable to return to the previous state.

5. Click Continueand choose the file to which to restore the system.

The system reboots and a message indicates that the restore succeeded.


36/39


Resetting the System


2. Click .

3. Enter the reason for the reset and clickYesto confirm setting the system to its default state.

The system automatically reboots.

Reverting the System to an Alternate Image


2. Click .

3. Enter the reason for reverting the system.

4. Optionally, select Reset to defaults?to reset the system to default values.

5. ClickYes.

The system automatically reboots.

Updating License Keys

You must have current license keys to enable the following:

12-port or 16-port bridge operation

expanded conferences

clustering

software upgrades

If your system has HTTP access through port 80 to the LifeSize license key server, update your license

keys in the LifeSize Bridge Utility. Otherwise, refer to Installing a License Key Manually.

1. Navigate to Maintenance > License Keys.

2. Click Update.

If the update is successful, Success appears along with the current license keys and their expiration

dates. If the update fails, a message indicates the cause of the failure.

Installing a License Key Manually1. Click Download Software on lifesize.com/support.

2. Log in to your support account. On your first visit, create the account.

3. Follow the instructions to obtain a license key. You may have multiple keys.

4. Download a license key.

5. From the LifeSize Bridge Utility, navigate to Maintenance > License Keys.


37/39


6. Click and paste the license key that you obtained in step 3.

7. Click Add.

8. Repeat steps 3through 7for each license key listed for your bridge.

NOTE Apply two 4-port licenses before attempting to apply the expandedconference license.

Upgrading your System Software

Before you upgrade your system software, ensure that the system meets the following prerequisites:

A current license key for upgrading exists on the system. The expiration date for the upgrade license

appears in Maintenance > License Keys. Read more at Updating License Keys.

An upgrade fails if a current license key does not exist on the system or has expired. Contact your

LifeSize Partner to renew your maintenance agreement.

If the expired license is on a standby or slave MCU in a cluster, remove the bridge from the cluster,

update its license, and return it to the cluster before performing the upgrade.

Terminate all calls prior to upgrading. Create a maintenance window by scheduling a conference that

uses all ports and has a password that is not shared.

LifeSize recommends you save your system configuration before upgrading. Read more at Saving a

System Configuration.

1. Click Download Software on lifesize.com/support.

2. Log in to your support account. On your first visit, create the account.

3. Download the software update image to a local directory on your system.

NOTE Ensure that you use the correct upgrade file. The upgrade files for a

standalone bridge and a bridge in a cluster are not interchangeable.

4. Access the LifeSize Bridge Utility.

5. For standalone bridge, click Maintenance > System Upgrade.

-or-

For a cluster, click Clustering > Upgrade Cluster.

6. Browse for the upgrade file you downloaded in step 3.

The system validates the file. To re-validate the same file or if you manually entered a path to a file,

click Validatefor the verification to occur.

7. If the validation succeeds and your upgrade requires you to reset the system to the original default

settings, select Reset to Default State.


38/39


8. Click Upgrade Nowor Upgrade Cluster Now.

The upgrade can take several minutes; do not disrupt the upgrade process. During an upgrade, a

status screen appears. Keep the utility window open to monitor the upgrade process. If you close the

window before the file upload completes, the upload is cancelled. If you close the window after the file

upload completes, the upgrade process continues, but you are no longer able to monitor the upgrade

process.A system upgrade status message appears when the upgrade is complete and the system

automatically reboots.

If the software you are attempting to install is an older version than what is currently installed,

Downgrade Nowor Downgrade Cluster Now appears.

9. Your system is ready to use. If you selected Reset to Default Statein step 7, you must first

reconfigure your system.

Troubleshooting Upgrade Failures

If attempts to upgrade software fail, follow these steps:

1. Ensure you have a valid upgrade image.

2. Reboot the system.

3. Attempt the upgrade again.

4. If a second attempt fails, note the error code returned.

5. If problems persist, contact LifeSize Technical Services or your LifeSize Partner.

Upgrade Error Codes

Problem Description

Upgrade script failed After the image has been successfully uploaded, the system runs an upgrade script for

final processing. This error indicates a failure in that script.

Unknown error The upgrade failed for undetermined reasons.

Upgrade in progress An upgrade is already in progress. The system supports only one upgrade at a time.

Bad upgrade file format The upgrade image is corrupt and unusable. This typically occurs due to a bad image

or errors during upload to the device.

Invalid signature The encryption signature is invalid. This typically occurs if the image is corrupt or

compromised.

Missing required file The system was unable to run the upgrade script. This typically occurs due to a bad

image or errors during upload to the device.

Upgrade license expired A current license key for upgrading the system software does not exist on the device.

Contact your LifeSize Partner to renew your maintenance agreement.

The system is busy Resources were unavailable to perform the upgrade.

Must reset to defaults to

install this upgrade

The upgrade requires a reset. Select Reset to Default Values before proceeding with

the upgrade.


39/39

Copyright Notice2012-2013Logitech, and its licensors. All rights reserved.

LifeSize, a division of Logitech, has made every effort to ensure that the information contained in this document isaccurate and reliable, but assumes no responsibility for errors or omissions. Information in this document is subject tochange without notice. Companies, names, and data used in examples herein are fictitious unless noted. Thisdocument contains copyrighted and proprietary information which is protected by United States copyright laws andinternational treaty provisions. No part of the document may be reproduced or transmitted, in any form or by anymeans, electronic or mechanical, for any purpose, without the express written permission from LifeSizeCommunications.

Trademark AcknowledgmentsLifeSize, the LifeSize logo and other LifeSize marks, are registered trademarks or trademarks of Logitech. All othertrademarks are the property of their respective owners.

Patent NoticeFor patents covering LifeSize products, refer to lifesize.com/support/legal.

Contacting Technical ServicesLifeSize Communications welcomes your comments regarding our products and services. If you have feedback aboutthis or any LifeSize product, please send it to [email protected]. Refer to lifesize.com/supportfor additional waysto contact LifeSize Technical Services.
http://www.lifesize.com/support/legalmailto:[email protected]://www.lifesize.com/supporthttp://www.lifesize.com/supportmailto:[email protected]://www.lifesize.com/support/legal

Documents

Bridge Deployment Guide