LifeSize Bridge 2200 Deployment Guide

Transcription

1 LifeSize Bridge 2200 Deployment Guide August 2013

2 LifeSize Bridge 2200 Deployment Guide 2 LifeSize Bridge 2200 LifeSize 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. Initial Configuration Describes tasks to enable and configure a LifeSize Bridge Clusters Conferences Expanding Your Conference Configuring Cascaded Conferences Managing Your LifeSize Bridge Maintaining Your LifeSize Bridge 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. 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. Describes how to administer your bridge and perform diagnostics. Provides instructions for backing up, restoring, and resetting the system. 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. active call cluster conference cascaded conference expanded conference on demand conference on demand + conference scheduled conference State of a conference after the first participant has joined. Individual participant who joins a conference. A configuration of multiple MCUs that is controlled by a master MCU that hosts calls and manages the port resources of subordinate MCUs. Multiple participants, hosted by the MCU. Conference in which an MCU hosts a combination of participant MCUs and single participants. Conference hosting up to 48 participants; a license key is required for this feature. Conference that is not scheduled in advance, does not have a scheduled start time, and is always live. 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. Conference that is planned in advance and includes a specific participant capacity for a given start and end time.

3 LifeSize Bridge 2200 Deployment Guide 3 temporary conference live master MCU media server port prefix dialing region slave MCU standby MCU Virtual Operator 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. 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. 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. An MCU hosting conferences in a cluster. 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. 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. Logical groupings of MCUs within the cluster. An MCU that functions as a media server in a cluster. 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. 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 LifeSize Bridge 2200 Deployment Guide 4 Section 1: Initial Configuration Deploying LifeSize Bridge includes the following tasks: Complete the installation of and assign an IP address for each LifeSize Bridge in your deployment. Install the LifeSize Bridge Utility. Update the licenses for each LifeSize Bridge in your deployment. Configure each LifeSize Bridge in your deployment. Optional: Create a cluster. Create conferences. Optional: Use the SOAP API to control your bridge. LifeSize Bridge 2200 Installation Guide Installing the LifeSize Bridge Utility Updating License Keys Upgrading your System Software Clusters Conferences Access API documentation at: Installing the LifeSize Bridge Utility Ensure that your system meets the following requirements prior to installing the utility. Operating System 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 Mac OS X v10.5, v10.6, or v10.7 Linux: Fedora Core 12 Ubuntu 9.10 opensuse 11.2 Hardware Requirements Processor: Intel Pentium III or faster RAM: 1 GB required, 2 GB recommended Processor: Intel Core Duo or faster RAM: 1 GB required, 2 GB recommended Processor: Intel Pentium III or faster RAM: 1 GB required, 2 GB recommended To install the utility, enter the IP address of a LifeSize Bridge in a browser. You are prompted to install Adobe 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.

5 LifeSize Bridge 2200 Deployment Guide 5 Getting Started with the LifeSize Bridge Utility The LifeSize Bridge Utility enables administrators to manage all aspects of conferences and the system. Two types of user accounts are available. The user account, default password of user, can access the Scheduler only. The admin account, default password of admin, can access all areas of the utility. LifeSize recommends that you protect the user and administrator preferences with a secure password. Change passwords from Preferences > Passwords. Passwords must be a minimum of five characters. When logging in, you can select HTTPS from the login screen to enable secure communications. The IP address of the system to which you are logged in appears in the title bar of your browser. System information, including the software version, appears at the top of the utility. Mouse over the text and icons for more information: Scheduled Ports On Demand Active Operator Calls Number of live scheduled conferences. Number of ports in scheduled or active conferences. Number of on demand conferences. With prefix dialing enabled, on demand + conferences are not included in this count unless they are active. Number of live conferences with participants. Number of participants interacting with the Virtual Operator. Total number of connected calls. Number of connected video calls. Number of connected voice calls. Available ports Maximum Size The number of remaining ports, not active or not scheduled. Cluster only: Largest possible size of a new conference. Because conference participants cannot span bridges, Maximum Size is limited to the largest number of available ports on a single bridge. Shortcut to Diagnostics > System Health, providing a quick view of your system, temperature, and fan status. This icon changes color to identify the health of the system. H.323 Shortcut to Preferences > H.323. This text changes color to identify the status of the H.323 connection. SIP FIPS Shortcut to Preferences > SIP. This text changes color to identify the status of the SIP connection. Indicates that FIPS is enabled in Preferences > Security > FIPS. Shortcut to Preferences > Network. This icon changes color to identify the status of the network connection for each configured Ethernet port; the port number also appears on this icon. Shortcut to Preferences > Network. This icon changes color to identify the status of the redundant ports, if network port redundancy is enabled. Click the appropriate tab beneath your system information to schedule and manage calls, set preferences, and perform maintenance. Changes to preferences that might cause a call to disconnect must occur when the system is idle. Schedule a maintenance window by creating a conference that uses all ports and has a password that is not shared.

6 LifeSize Bridge 2200 Deployment Guide 6 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. 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 Network and 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 and verify 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. 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 system s date and time in Preferences > Date and Time: System Time Time Zone Current NTP Server NTP Server Hostname Configure the current time on your system relative to the system's configured time zone. Configure the time zone of your system. Shows the currently configured NTP server. This value can be set manually or specified by DHCP. Configure the NTP server of your system.

7 LifeSize Bridge 2200 Deployment Guide 7 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 Tones or Camera Control as the default navigation method. Touch Tones uses the number keys on the remote control and Camera Control uses the arrow keys. 6. To create a temporary conference from 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. 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. 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 Specifying DHCP or a locally configured IP address Specifying network speed 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. 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. 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. : 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 Duplex when selecting Auto negotiate speed and duplex settings.

8 LifeSize Bridge 2200 Deployment Guide 8 Specifying a VLAN ID IPv6 support Network Port Redundancy Default Gateway Specifying DNS servers and domain Specifying search domains Restricting reserved ports Configuring QoS Adjusting the MTU of video packets 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 Select Enable IPv6 to 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 IPv6 router. Read more at Limitations of IPv6 Support. 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. Specify the default gateway. 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. : 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. 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. By default, LifeSize systems communicate through TCP and UDP ports in the range 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 The minimum TCP port range is 480, and the minimum UDP port range is The utility will not allow you to save a smaller value. 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 Type of 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. 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 bytes. LifeSize recommends you do not change this value unless your network is using a different MTU. 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.

9 LifeSize Bridge 2200 Deployment Guide 9 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. Active Backup 802.3ad Balanced Round Robin Balanced XOR Broadcast The default. Only one port is active. Another port becomes active if the current port fails. Creates groups that share the same speed and duplex settings. Packets are transmitted in sequential order across available ports. Packets are transmitted based on MAC address. The same port is selected for each destination MAC address. Each port transmits the same signal. 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 ) 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 Guide for more information. You must open TCP and UDP ports 5300 through 5305 between the MCUs in the cluster.

10 LifeSize Bridge 2200 Deployment Guide 10 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. 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.323 in 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 another registered 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 which the system is registering. Select Enable Gatekeeper Authentication to enable authentication and enter the authentication username and password. Set Gatekeeper Mode to Auto 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, 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 SIP in Preferences > SIP > General and 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 LifeSize Bridge 2200 Deployment Guide 11 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. SIP appears 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 Register to 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 registrar and 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. The system reboots if you change any port value and click Save.

12 LifeSize Bridge 2200 Deployment Guide 12 Section 2: Clusters A 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. Required: Master MCU Recommended: Standby MCU Optional: Slave MCUs Hosts all signaling data for all conferences. Handles all conference scheduling. Hosts conferences up to its port capacity. 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. 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. 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.

13 LifeSize Bridge 2200 Deployment Guide 13 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 MCU s 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 cluster s virtual IP address. 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 LifeSize Bridge 2200 Deployment Guide 14 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 configure the utility to upgrade MCUs to the master MCU software version as you add them to the cluster. Refer to Adding the Standby MCU and Adding 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 LifeSize Bridge 2200 Deployment Guide 15 Adding the Master MCU 1. 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 Region name. You must name a least one region and can specify up to Click Set Master. The Participation Type changes to Master. CAUTION Do not change the IP address of the master MCU after it is in the cluster. Adding the Standby MCU 1. 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 License to 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 Upgrade to 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 Type changes to Standby. 10. Log out and log back in using the virtual IP address for the cluster. Adding Slave MCUs 1. 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 License to enter a cluster license key for the standby MCU. Do not perform this step if you have already applied this license.

16 LifeSize Bridge 2200 Deployment Guide Optional: Select Allow Upgrade to 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 > Configure and 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 LifeSize Bridge 2200 Deployment Guide 17 Section 3: Conferences The following types of conferences are available: Scheduled On demand On demand + A conference with a specific start and end time. Ports are allocated by participant. 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. Create and manage conferences from the calendar view of conferences in the Scheduler. You can view all conferences by day, week, or month. 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 Expand to accommodate up to 48 participants. Expand is 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 conference s 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.

18 LifeSize Bridge 2200 Deployment Guide 18 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 The following table compares the two on demand options. On Demand Conferences Limited to 40 instances. Always live. The utility always counts an on demand conference in On Demand (at the top of the utility). Can be chosen from the Virtual Operator. On Demand + Conferences Up to 10,000 reserved conference templates. The actual number of conferences is limited only by the conference ID bounds settings. Become active when the first participant joins. The utility only counts an on demand + conference in On Demand when the conference is active. 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 <conference ID> and <prefix><conference ID> are accepted dial strings. 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 Creation is 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.

19 LifeSize Bridge 2200 Deployment Guide 19 Configure the bridge s 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 On demand + conference IDs default to 5 digits with a range from to The number of digits for these two IDs must be different, and the IDs cannot have fewer than 4 digits. Navigate to Preferences > Scheduler to 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 Conference 1. 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. Create a cascaded conference or lecture conference by selecting the appropriate option in Conference Type. Read more at Configuring Cascaded Conferences and Lectures. 2. Select Auto to automatically assign an ID to the conference. Clear the checkbox to assign a specific conference ID. 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 LifeSize Bridge 2200 Deployment Guide Optional: Enter a password that users must enter to join the conference. Select Display Password to 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. Recurring conferences 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. Expand is 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 Conferences and 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 participant s 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 Navigation Show System Names Voice prompts and system sounds indicate the current system status or action required. Control the interface using touch tones or the far end camera control buttons on the LifeSize remote control. System names of onscreen participants remain visible during the conference. On Touch tones 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 prefer that participants must dial in individually, do not define any participants in this list. no default

21 LifeSize Bridge 2200 Deployment Guide 21 Preference Description Default Value Participant Bitrate Security The bit rate for each participant in the conference. Encryption level used for the conference. Auto allows both encrypted and unencrypted calls. Strict connects encrypted calls only. Auto Auto Resolution The video resolution used for the conference. The default is 720p60. Auto Video Codecs Audio Codecs Customize the default video codec order, or allow the system to choose automatically. Customize the default audio codec order, or allow the system to choose automatically. Auto 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 choose automatically. Auto 10. Click Save to make the changes and close the dialog box. Not all options are available during active conferences or for expanded conferences. You can also manage conference restrictions from Preferences > Scheduler. Conference ID Bounds On Demand + ID Bounds Maximum On Demand Conferences Expired Conference Removal Time 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: Maximum default: 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: Default maximum: 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. Choose the length of time for the system to store expired conferences. The default is 3 months.

22 LifeSize Bridge 2200 Deployment Guide 22 Troubleshooting Scheduling Failures Message The conference has no name. No available ports for requested time. Action Enter a name for the conference. 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. Scheduler file not found. The system may be corrupt. Increase the value for Maximum On Demand Conferences in Preferences > Scheduler, or consider enabling prefix dialing. Restart the LifeSize Bridge Utility. Expanding Your Conference 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 at Updating License Keys. You can add up to 48 participants to a scheduled conference by selecting 16 ports and then selecting Expand. The Expand checkbox 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 Conference for 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.

23 LifeSize Bridge 2200 Deployment Guide 23 Configuring Cascaded Conferences 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 MCU s number and change Participant Type to Host MCU. e. Add other participants as required. f. Note the conference ID. 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 Type to 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. 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 LifeSize Bridge 2200 Deployment Guide 24 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 participant s 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 select Custom for 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: 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. Options in the second column depend on whether you are viewing a single call or controlling all participants in the conference. Following are the actions you can take: 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.