Avaya 6000 User Manual
Administrator Guide for Avaya Scopia® Elite
6000 for Aura Collaboration Suite
Version 8.3
For Solution 8.3
July 2014
© 2000-2014 Avaya Inc. All intellectual property rights in
this publication are owned by Avaya Inc. and are
protected by United States copyright laws, other
applicable copyright laws and international treaty
provisions. Avaya Inc. retains all rights not expressly
granted.
All product and company names herein may be
trademarks of their registered owners.
This publication is AVAYA Confidential & Proprietary.
Use pursuant to your signed agreement or Avaya policy.
No part of this publication may be reproduced in any
form whatsoever or used to make any derivative work
without prior written approval by Avaya Inc.
No representation of warranties for fitness for any
purpose other than what is specifically mentioned in this
guide is made either by Avaya Inc. or its agents.
Avaya Inc. reserves the right to revise this publication
and make changes without obligation to notify any
person of such revisions or changes. Avaya Inc may
make improvements or changes in the product(s) and/or
the program(s) described in this documentation at any
time.
If there is any software on removable media described in
this publication, it is furnished under a license agreement
included with the product as a separate document. If you
are unable to locate a copy, please contact Avaya Inc
and a copy will be provided to you.
Unless otherwise indicated, Avaya registered trademarks
are registered in the United States and other territories.
All registered trademarks recognized.
For further information contact Avaya or your local
distributor or reseller.
Administrator Guide for Avaya Scopia® Elite 6000 for
Aura Collaboration Suite Version 8.3, July 31, 2014
http://support.avaya.com
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Notices | 2
Table of Contents
Chapter 1: About the Avaya Scopia® Elite 6000
About Avaya Scopia® Elite 6000 ......................................................................................................................6
Minimum Requirements and Specifications ..................................................................................................... 9
Chapter 2: Planning your MCU Deployment
Planning the Topology of the Scopia® Elite 6000 for Aura Collaboration Suite ............................................ 12
Deploying Redundant MCUs ..........................................................................................................................14
Planning a Centralized or Distributed Topology (Cascading) for MCU ..........................................................15
Planning Network Redundancy or IP Separation (Dual NIC) .........................................................................17
Sizing your MCUs and Scopia® Desktop servers for Aura Collaboration Suite ............................................ 18
About the Capacity of the MCU ......................................................................................................................19
Ports to Open for the Scopia® Elite 6000 for Aura Collaboration Suite .........................................................20
Chapter 3: Securing your Scopia® Elite 6000
Securing MCU and Scopia® Management Connection with TLS ..................................................................24
Securing MCU with TLS in a SIP Environment ..................................................................................24
Uploading TLS Certificates to the MCU ............................................................................................. 25
Configuring Security Access Levels for the Scopia® Elite 6000 ....................................................................31
Configuring IP Separation (Dual NIC) on the Device .....................................................................................32
Chapter 4: Maintaining the Scopia® Elite 6000
Adding a License to the MCU .........................................................................................................................38
Configuring MCU Meeting Types ................................................................................................................... 40
Creating a Meeting Type .................................................................................................................... 40
Configuring the Bandwidth of a Meeting Type ................................................................................... 44
Configuring the Auto-Attendant Service .............................................................................................47
Managing Scopia® Elite 6000 User Profiles ...................................................................................................49
Adding a User Profile ..........................................................................................................................49
Changing a User Password ................................................................................................................50
Deleting a User Profile ........................................................................................................................51
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Table of Contents | 3
Managing the Redundant Power Supply of the Scopia® Elite 6000 ..............................................................51
Adding a Power Supply Unit to the MCU ........................................................................................... 52
Removing a Power Supply Unit from the MCU ..................................................................................54
Configuring Ports on the Scopia® Elite 6000 ................................................................................................. 55
Configuring the UDP Port Ranges for RTP/RTCP on the Scopia® Elite 6000 .................................. 56
Configuring the TCP Port Range for H.245 on the Scopia® Elite 6000 .............................................57
Configuring the HTTP Port on the Scopia® Elite 6000 .......................................................................58
Configuring the UDP Port for RAS on the Scopia® Elite 6000 ...........................................................59
Configuring the UDP Port for the Gatekeeper on the Scopia® Elite 6000 .........................................60
Configuring the TCP Port Q.931 on the Scopia® Elite 6000 ..............................................................60
Configuring the TCP/UDP/TLS Port for SIP on the Scopia® Elite 6000 ............................................ 61
Configuring the TCP Port Range for SIP BFCP on the Scopia® Elite 6000 ...................................... 62
Branding your Scopia® Elite 6000 User Interface ..........................................................................................63
Customizing the Logo Displayed in MCU Conferences ..................................................................... 63
Customizing MCU Audio Messages ...................................................................................................66
Upgrading, Backing up and Restoring the Scopia® Elite 6000 ......................................................................67
Backing Up Your Scopia® Elite 6000 Configuration ...........................................................................67
Restoring Your Scopia® Elite 6000 Configuration ..............................................................................68
Upgrading Scopia® Elite 6000 for Aura Collaboration Suite Software ...............................................68
Restoring a Previous Software Version ..............................................................................................69
Monitoring MCU Performance ........................................................................................................................71
Chapter 5: Troubleshooting the Scopia® Elite 6000
Gathering logs on the MCU ............................................................................................................................74
Defining an Advanced Command on the MCU .............................................................................................. 75
Resolving MCU Failure to Register with the Gatekeeper ...............................................................................76
MCU Cannot Start a Videoconference ...........................................................................................................77
MCU Does Not Allow Access an Existing Videoconference .......................................................................... 78
Poor Quality in Cascaded Videoconferences .................................................................................................79
Endpoints Unexpectedly Disconnect from Videoconferences ....................................................................... 79
Videoconference Ends Unexpectedly ............................................................................................................ 79
SIP Call Disconnected Unexpectedly .............................................................................................................79
Resolving Presentation Issues .......................................................................................................................80
Resolving a Video Display Issue ....................................................................................................................82
Resolving Poor Audio Quality .........................................................................................................................83
Resolving Poor Video Quality .........................................................................................................................84
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Table of Contents | 4
Glossary of Terms for Scopia® Solution
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Table of Contents | 5
Chapter 1 | About the Avaya Scopia® Elite
6000
The Scopia® Elite 6000 is Scopia® Solution’s flagship platform for high definition multi-party videoconferencing.
The MCU supports communications in the board room, at the desktop, in the home, or on the road over wireless.
Navigation
•
About Avaya Scopia® Elite 6000 on page 6
•
Minimum Requirements and Specifications on page 9
About Avaya Scopia® Elite 6000
The Scopia® Elite 6000 is Scopia® Solution’s flagship platform for high definition multi-party
videoconferencing.
An MCU, or Multipoint Control Unit, connects several endpoints to a single videoconference. It manages
the audio mixing and creates the video layouts, adjusting the output to suit each endpoint's capabilities.
The Aura Collaboration Suite enables any enterprise to gain full business collaboration utilizing audio,
video or the web. The Aura Collaboration Suite is positioned for organizations which need robust
collaboration capabilities, including industry leading HD video, plus audio and web conferencing.
The Scopia® Solution is a component of the Aura Collaboration Suite. With this unified offering, every
potential Avaya UC customer can access and utilize the Avaya Scopia premium collaboration
experience.
Avaya UC customers can now enjoy the Scopia high-end video experience as one of their collaboration
options within the Collaboration Suite.
The Avaya Scopia® Desktop and Avaya Scopia® Mobile user licenses delivered with the Aura
Collaboration Suite require a unique version of the MCU specifically designed for the Aura Collaboration
Suite: Scopia® Elite 6000.
The MCU is specially tailored to fit this Unified Communications (UC) offering, along with other video
infrastructure devices of the Scopia® Solution such as Scopia® Desktop for Aura Collaboration Suite and
Avaya Scopia® Management for Aura Collaboration. The MCU cannot be re-purposed for other video
solutions which are not part of the Aura Collaboration Suite.
The MCU harnesses revolutionary processing power for the most demanding videoconferencing
applications using the latest DSP technologies. For an uncompromised videoconferencing experience,
the MCU supports dual channels of Full HD 1080p at 60 frames per second for video and content, H.264
High Profile for bandwidth efficiency, H.264 Scalable Video Coding (SVC) for high network error
resiliency, and full support for many telepresence systems.
With the MCU, each videoconference participant receives a quality experience optimized to their
individual capabilities, from wireless mobile devices to HD room systems and immersive telepresence
systems. The MCU leads in video interoperability, working with the broadest range of video systems on
the market from leading UC clients to mobile devices and telepresence systems.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
About the Avaya Scopia® Elite 6000 | 6
The MCU also features a patented, distributed architecture approach known as the Virtual MCU or
cascaded videoconferences, which brings unparalleled scalability to its superb videoconferencing
experience.
The MCU's feature list includes:
•
Revolutionary video processing power
The MCU brings unmatched power and capacity in a single unit, enabling dual-channel Full HD
1080p resolution at 60 frames per second for video and content, simultaneous H.264 High Profile
and H.264 SVC, and support for multi-stream telepresence.
•
Dynamic resource allocation
A meeting can support a mix of SD and HD users, making most efficient use of available
resources. Video and audio processing is carried out per user rather than per meeting, with
resolutions ranging from CIF to 1080p in the same meeting. Each user connects using unique,
optimized audio and video settings to enjoy the best audio and video quality supported by their
endpoint and network, without affecting the other participants in a conference.
•
Intuitive and easy to use
Video menus make it easy to set up or enter a videoconference, and the intuitive web interface
makes administration easy.
•
Massive scalability
The Virtual MCU enables a unique scalability in both local and distributed architectures to combine
the capacity of multiple MCU devices in the same meeting. The number of supported connections
depends on your license.
•
Seamless interoperability
The MCU is built on the solid foundation of our H.323 and SIP software, ensuring full compliance
and broad-ranging interoperability with IP, ISDN, and 3G endpoints. It also enables H.323 and SIP
endpoints to collaborate in the same videoconference. See Figure 1: Endpoints in the same
videoconference on page 8.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
About the Avaya Scopia® Elite 6000 | 7
Figure 1: Endpoints in the same videoconference
The MCU also easily integrates telepresence systems with regular videoconferencing systems,
even within the same meeting. It is compatible with telepresence systems from Cisco, Tandberg,
Polycom, and LifeSize/Logitech.
When used with Scopia® Solution gateways, the deployment can even add ISDN, V.35 and other
endpoints to the same meeting.
•
Video quality
The MCU delivers enterprise quality video and audio processing, using latest industry standards
including state-of-the-art DSP hardware and software. This video quality is supported by:
–
SVC error resiliency for unmanaged networks using Temporal Scalability and Forward Error
Correction (FEC).
Forward Error Correction (FEC) is a proactive method of sending redundant information in
the video stream to preempt quality degradation. SVC extends the H.264 codec standard to
dramatically increase error resiliency and video quality without the need for higher bandwidth.
–
Frame rates can reach 60 frames per second, ensuring smooth video movement.
–
A wide choice of video layouts
–
Bitrate (data speed) of up to 12 megabits per second on each stream without affecting
capacity. Bitrate is the speed of data flow. Higher video resolutions require higher bitrates to
ensure the video is constantly updated, thereby maintaining smooth motion.
•
Audio quality
The MCU integrates Voice Activity Detection (VAD) to determine the active speaker and filter out
background noise from participants. The MCU also improves audio quality with AGC. Automatic
Gain Control (AGC) smooths audio signals through normalization, by lowering sounds which are
too strong and strengthening sounds which are too weak.
•
Personalized video layouts per meeting or per participant
As an administrator you can choose from 26 video layouts for all participants, or each participant
can customize their own view. You can view up to 28 participants on your screen. A video layout is
the arrangement of participant images as they appear on the monitor in a videoconference. If the
meeting includes a presentation, a layout can also refer to the arrangement of the presentation
image together with the meeting participants.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
About the Avaya Scopia® Elite 6000 | 8
The MCU supports sharing presentations and other content via SIP (using the BFCP standard)
and H.323 (using the H.239 standard). A user can connect to a meeting from either type of
endpoint to share content such as presentations, spreadsheets, documents, and movies.
The MCU supports an additional set of layouts to optimize screen space during content sharing on
single-screen endpoints. With this feature, endpoints with proprietary content sharing protocols
such as Avaya Flare Experience or Microsoft Lync can simultaneously display content and
participants.
•
Security and privacy
The MCU can encrypt communications with endpoints to create secure connections with H.235-
based encryption for H.323 endpoints and SRTP and TLS encryption for SIP endpoints.
In addition, the MCU features administrator and operator password protection for accessing the
web interface. It also features optional PIN protection for joining a videoconference, and additional
PIN protection for moderator control.
•
Dual NIC: IP separation or network redundancy
You can use the two network ports of the MCU in one of the following ways:
–
Network redundancy cuts downtime and provides a cost-effective, uninterrupted service. If
the first NIC fails during a videoconference, network traffic is automatically routed to the
second NIC without affecting current calls on the MCU.
–
IP separation enhances security within the enterprise by routing media and management
traffic to two different subnets.
•
Intuitive web-based management
You can configure the MCU through an intuitive web interface offering easy, high-level
administrative flexibility for an enhanced user experience.
•
In-meeting indicators
A range of messages and icons are displayed on the endpoint during meetings as events occur.
For example, participants are notified when someone joins or leaves the meeting.
•
Easy creation of logs for Customer Support
You can easily create a file containing logs and settings which you can send to Customer Support
for troubleshooting.
•
Interactive Voice Response (IVR) messages
The MCU includes pre-recorded greetings to participants and announcements as each new
participant joins a meeting. You can record messages to provide custom greetings and
announcements, but typically Avaya Scopia® Management supplies these messages across all
MCUs in the organization.
•
SIP Firewall traversal compatibilities
The MCU is fully interoperable with third-party Session Border Controllers (SBC), which increases
compatibility and dexterity with SIP endpoints that join remotely.
Minimum Requirements and Specifications
This section details the system specifications of the MCU you purchased. Refer to this data when
preparing system setup and afterwards as a means of verifying that the environment still complies with
these requirements.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
About the Avaya Scopia® Elite 6000 | 9
Hardware requirements
The following lists the device's hardware requirements:
•
System power requirements: 100-240 VAC, 50/60 Hz with hot-swap redundant AC power supply
and feed (optional)
–
AC Input:
1000W output @ 100-120V, 12-10A, 50-60Hz
1200W output @ 120-140V, 12-10A, 50-60Hz
1800W output @ 200-240V, 10-8.5A, 50-60Hz
–
Maximum power consumption at 35°C: 360W, 450VA (1228 BTU/h)
•
Environmental requirements:
–
Operating temperature: 10°C to 35°C (50°F to 95°F)
–
Relative humidity: 5% to 90% non-condensing
–
Storage and transit temperature: -40°C to 70°C (-40°F to 158°F), ambient
–
Acoustics: low noise fan speed control
•
Physical requirements:
–
Dimensions: width: 437mm (17.2"); height: 43mm (1.7"); depth: 790mm (31.1")
–
Approximate net weight: 14.5kg (32lbs) with one power supply
–
Approximate gross weight (with packaging): approx 23kg (50.7lbs)
Software Specifications
The following lists the technical specifications of the protocols and software requirements:
•
Signaling protocols:
–
H.323
–
SIP
–
H.320 (in conjunction with Scopia H.320 Gateways)
•
Audio support:
–
Codecs: G.711. G.722, G.722.1, G.729, G.722.1 Annex C
–
DTMF tone detection (in-band, H.245 tones and RFC2833)
•
Video support:
–
High Definition Continuous Presence video with a resolution of 1080p at up to 60fps
–
Codecs: H.263, H.263+, H.264, H.264 SVC, H.264 High Profile
–
Live video resolutions: CIF up to 1080p
–
Presentation video resolution: VGA, SVGA, SXGA, XGA, 720p, 1080p, WUXGA
–
Video bandwidth: up to 12Mbps for 1080p resolutions and up to 6Mbps for 720p or lower
•
Web browser support:
–
Microsoft Internet Explorer versions 6, 7, 8 and 9
–
Mozilla Firefox version 3.3 and above
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
About the Avaya Scopia® Elite 6000 | 10
–
Google Chrome
–
Apple Safari
•
Call capacity:
For information on the default capacity of your MCU and how to increase it, see About the Capacity
of the MCU on page 19.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
About the Avaya Scopia® Elite 6000 | 11
Chapter 2 | Planning your MCU Deployment
When planning your MCU deployment, it is important to consider both bandwidth usage and port security, as
described in the following sections:
Navigation
•
Planning the Topology of the Scopia® Elite 6000 for Aura Collaboration Suite on page 12
•
Deploying Redundant MCUs on page 14
•
Planning a Centralized or Distributed Topology (Cascading) for MCU on page 15
•
Planning Network Redundancy or IP Separation (Dual NIC) on page 17
•
Sizing your MCUs and Scopia® Desktop servers for Aura Collaboration Suite on page 18
•
About the Capacity of the MCU on page 19
•
Ports to Open for the Scopia® Elite 6000 for Aura Collaboration Suite on page 20
Planning the Topology of the Scopia® Elite 6000 for Aura Collaboration Suite
This section describes the guidelines for deploying this and other Scopia® Solution components in your
video network when you integrate with Aura Collaboration Suite.
You can deploy Scopia® Solution components either in a centralized or distributed solution:
•
In a centralized topology (Figure 2: Centralized Scopia® Solution deployment with Aura
Collaboration Suite on page 13), all the components are installed in the same location.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 12
Figure 2: Centralized Scopia® Solution deployment with Aura Collaboration Suite
When deploying the Scopia® Solution for Aura Collaboration Suite, you gain state-of-the-art
enterprise videoconferencing using Avaya Scopia® Desktop and Avaya Scopia® Mobile, while
enabling these meetings to also include participants on Avaya UC devices such as Flare, One-X,
IP Deskphone and ADVD.
The solution includes these mandatory components:
–
Scopia® Elite 6000 for Aura Collaboration Suite, responsible for combining images from
different endpoints into a single continuous presence image to enable effective
videoconferencing.
–
Avaya Scopia® Management for Aura Collaboration Suite, which sits at the core of your
Scopia® Solution and offers a comprehensive management solution for video
communications where enterprises can efficiently control the videoconferencing network. The
MCU can only function and connect calls when managed and controlled by Scopia
®
Management for Aura Collaboration Suite.
–
Scopia® Desktop server for Aura Collaboration Suite, the desktop videoconferencing system
turning PCs, Macs and mobile devices into videoconferencing endpoints. The Scopia
®
Desktop server brings together meetings with Scopia® Desktop Clients and Scopia® Mobile
devices, passing their media connections to the MCU.
A SIP trunk connects the Aura Session Manager to Scopia® Management, while an H.323 trunk
connects the Aura Communication Manager also to Scopia® Management. Scopia® Management
synchronizes automatically and periodically with the Web License Manager (WebLM) installed on
the Aura System Manager to manage the Collaboration Suite licenses. For detailed information on
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 13
licenses, see Administrator Guide for Avaya Scopia® Management for Aura Collaboration Suite.
You can also optionally add Aura Conferencing (AAC) to transmit media to the MCU.
•
In a distributed topology (Figure 3: Additional components in other locations for a distributed
deployment on page 14), you can add components in other locations to create a scalable and
geographically distributed solution. You can deploy a full set of videoconferencing components in
the headquarters, and distribute additional MCUs and Scopia® Desktop servers over several
branches. Each branch can have one or more of these servers depending on the branch's
requirements for videoconferencing capacity and high availability. To provide scalability and high
availability with service preservation, you can also cluster the Scopia® Desktop servers behind a
load balancer. The Scopia® Desktop servers are typically deployed in the DMZ to provide
connection to participants from both the internal and external networks.
Figure 3: Additional components in other locations for a distributed deployment
For a detailed description of the Scopia® Solution components, refer to Scopia® Solution Guide.
For guidelines on how to assess your MCU and Scopia® Desktop server capacities, see Sizing your
MCUs and Scopia® Desktop servers for Aura Collaboration Suite on page 18.
Deploying Redundant MCUs
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 14
Redundancy is a way to deploy a network component, in which you deploy extra units as 'spares', to be
used as backups in case one of the components fails.
You can achieve MCU redundancy by deploying additional MCUs that are configured with the same
services as the devices which they back up. You can also use the distributed topology of your
deployment where MCUs located in different time zones can cover up for a failing MCU. MCU fallback is
managed by Scopia® Management, as explained in Administrator Guide for Avaya Scopia
Management for Aura Collaboration Suite.
This is different from LAN redundancy, which uses one of the MCU's two network ports as redundant, so
if one fails, the other takes over. For more information, see Planning Network Redundancy or IP
Separation (Dual NIC) on page 17.
®
Planning a Centralized or Distributed Topology (Cascading) for MCU
When your organization has more than one site, like a headquarters and several branches, the Scopia
Solution offers a unique method of cutting video bandwidth costs, known as cascaded meetings.
A cascaded videoconference is a meeting distributed over more than one physical Scopia® Elite 6000,
where a master MCU connects to one or more slave MCUs to create a single videoconference. It
increases the meeting capacity by combining the resources of several MCUs. This can be especially
useful for distributed deployments across several locations, reducing bandwidth usage.
Without cascading, if you choose a centralized MCU deployment, frequent videoconferences between
branches can be expensive (Figure 4: Centralized MCU deployment, where all branches use the HQ
MCU on page 15).
®
Figure 4: Centralized MCU deployment, where all branches use the HQ MCU
To reduce cross-site bandwidth costs, a distributed MCU deployment (Figure 5: Distributed MCU
deployment cascading meetings for reduced WAN bandwidth on page 16) can perform cascaded
conferences. Participants connect to their local MCU, and the conference is cascaded by connecting
between the MCUs using a fraction of the bandwidth compared to the centralized deployment. The same
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 15
principles apply to an MCU in the same location, thus increasing call capacity by cascading conferences
between them.
Figure 5: Distributed MCU deployment cascading meetings for reduced WAN bandwidth
The bandwidth used by a cascaded link is equivalent to only a single client connection in each direction:
upload and download. The bandwidth value is determined by the MCU meeting type (or service), which
is invoked when choosing a dial prefix for the meeting. You define the maximum bandwidth for each
meeting type in the MCU. For more information on defining meeting types, see Configuring the
Bandwidth of a Meeting Type on page 44.
Users do not need to choose a specific MCU. The powerful functionality of virtual rooms enables you to
dial the same number anywhere in the world, while the Scopia® Solution infrastructure transparently
directs you to the correct meeting on the correct MCU.
The maximum supported number of participants in a single videoconference is 270 for both the
centralized and distributed MCU deployment.
Users do not need to manually enable cascading when creating meetings. This is performed
transparently by Avaya Scopia® Management using sophisticated cascading algorithms.
When an endpoint initiates a meeting on an MCU, that MCU becomes the master MCU. Other MCUs
which participate in the meeting are designated as slave MCUs. There are a number of factors that
might influence when the system automatically chooses to cascade to a different MCU. For example, to
avoid reaching the maximum bandwidth threshold, the system would attempt cascading with a different
MCU, a slave MCU. Endpoints would then join the videoconference from the slave MCU. Only one level
of cascading is supported: all slave MCU conferences must cascade to the same master MCU
conference. Administrators can also customize the priority given to cascading in a distributed topology,
as explained in Administrator Guide for Avaya Scopia® Management for Aura Collaboration Suite.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 16
Cascading has the following characteristics:
•
A cascaded connection uses two connections—one connection on the master MCU, and one
connection on the slave MCU.
•
Make sure that the Meeting Type (MCU service), representing the required meeting properties and
accessed with a dial prefix, is available on all participating MCUs. For example, if the meeting uses
MCU service 81, then 81 must exist on the master MCU and on the slave MCUs.
•
Participants connecting to the slave MCU:
–
View only the default meeting layout
–
Can send and receive video with a resolution up to 720p (for Scopia® Elite 5000 Series
MCU)
–
Perform actions (such as joining the meeting) via their endpoint or web interface, and not via
DTMF.
•
Only one participant at a time (typically the active speaker) connecting from each slave MCU can
send video and be seen by other meeting participants in the video layout.
•
The lecturer and any telepresence endpoint always connect to the videoconference from the
master MCU. Connections are reserved on the master MCU to support these features.
•
Endpoints seamlessly join a videooconference according to the cascading logic implemented on
the sites. An endpoint connected to a slave MCU and trying to launch a feature which is not
supported by the slave MCU gets a relevant error message. You can move an endpoint to a
master MCU when scheduling your videoconference. For more information, see User Guide for
Scopia® Management.
•
Scopia® Elite 6000 does not support cascading to a Scopia® MCU.
You can customize the cascading priorities in Scopia® Management in a number of ways:
•
Default to using a local MCU first, and only cascade conferences if required.
•
Prioritize cascading wherever possible, to keep bandwidth costs to an absolute minimum.
•
Avoid cascading as often as possible.
For more information on implementing cascading in Scopia® Management, see Administrator Guide for
Avaya Scopia® Management for Aura Collaboration Suite.
Planning Network Redundancy or IP Separation (Dual NIC)
The device has two network cards (NICs) which can be used in one of the following ways:
•
Use the second NIC as a redundant backup of the first, to provide a cost-effective, uninterrupted
service.
With network redundancy, the primary NIC is actively responsible for all management, media and
signaling traffic, while the secondary NIC is a backup. The NICs are paired, so they are both
connected to the same network switch, and the IP addresses you configure on one NIC are
automatically mirrored to the other NIC, as described in Installation Guide for Scopia® Elite 6000
for Aura Collaboration Suite.
When a failure is resolved, the MCU moves traffic back to the primary NIC and the secondary NIC
returns to its standby state.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 17
You can increase MCU capacity by adding more devices to your existing deployment (see
Deploying Redundant MCUs on page 14).
•
Implement IP separation, to enhance security within the enterprise.
IP separation configures one NIC to handle management traffic (like administrator web access)
while the other controls media (video, audio and presentation) and signaling (call setup). Connect
each network port to a different subnet (Figure 6: IP separation on page 18). For more
information, see Configuring IP Separation (Dual NIC) on the Device on page 32.
Figure 6: IP separation
Sizing your MCUs and Scopia® Desktop servers for Aura Collaboration Suite
About this task
The Scopia® Elite 6000 and the Scopia® Desktop server are two of the central components which
support videoconferencing. As the number of video users (Scopia® User licenses) increases, you need
to add more MCUs and Scopia® Desktop servers.
This section provides basic guidelines to calculate the number of these servers required to support
videoconferencing users in a typical deployment with Avaya Aura Collaboration Suite. This assumes you
already know the number of Scopia® User licenses in your organization. For detailed information on
licenses, see Administrator Guide for Avaya Scopia® Management for Aura Collaboration Suite.
For information on the topologies supported in your deployment, see Planning the Topology of the
Scopia® Elite 6000 for Aura Collaboration Suite on page 12.
To estimate the number of MCUs and Scopia® Desktop servers required in your deployment:
Procedure
1. Consider the number of simultaneous connections supported by each type of server.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 18
•
Each MCU can support up to 80 simultaneous HD connections (720p at 30 frames per
second (fps)), or up to 160 simultaneous connections in standard definition (480p at
30fps).
•
Each Scopia® Desktop server can support up to 250 simultaneous Scopia® Desktop
Client or Scopia® Mobile connections.
2. Estimate the number of simultaneous videoconference connections you expect.
•
For an organization with up to 10,000 Scopia® User licenses, on average ten percent of
users connect simultaneously to a videoconference.
•
Above 10,000 licensed users, on average five percent connect simultaneously to a
videoconference.
This average percentage includes guest user access.
3. Use the formula below to estimate the number of servers (MCUs or Scopia® Desktop
servers) you need in your deployment:
Num of servers = (num of licensed users x proportion of simultaneous connections)
/ max simultaneous connections for this server
For example, in an organization with 8,000 Scopia® User licenses where an MCU in HD
(720p) has a maximum of 80 connections, the number of MCUs required is:
Number of MCUs = (8000 x 0.10) / 80 = 10
The number of Scopia® Desktop servers required, where each server can hold a maximum
of 250 connections, is: :
Number of Scopia® Desktop servers = (8000 x 0.10) / 250 = 3.2 (round up to 4)
Important:
If your current deployment uses more than 80 percent capacity on any server, deploy
additional MCUs and Scopia® Desktop servers.
About the Capacity of the MCU
The MCU's capacity is measured in terms of the maximum number of simultaneous connections to a
videoconference supported by this device.
The impact of a connection on the MCU's capacity depends on the bandwidth of the connection, which
in turn is dependent on the resolution and frame rate of that connection. Therefore the same meeting
can support a mix of HD and SD connections.
For example, a connection at 1080p at 30fps or 720p at 60fps uses half the capacity of a 1080p
connection at 60fps. Similarly, a connection at 480p at 30fps uses a quarter of the resources of a 1080p
connection at 30fps, or one-eighth of the resources of a 1080p 60fps connection.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 19
Figure 7: A connection uses its proportion of resources on the MCU
Table 1: Simultaneous connections available at different video quality settings
Video quality settings
Maximum number of supported simultaneous
connections
1080p at 60fps (Full HD) 20
1080p at 30fps (Full HD) 40
720p at 30fps (HD) 80
480p at 30fps (SD) 160
For information on adding more servers when the number of simultaneous connections exceeds the
MCU capacity, refer to Sizing your MCUs and Scopia® Desktop servers for Aura Collaboration Suite on
page 18.
Important:
Use the 1080p resolution only for room systems such as the XT Series Scopia XT Series or 3rd party
video system. Room system connectivity requires an additional license in Scopia® Management. For
more information, see Administrator Guide for Scopia® Management.
If you want to limit the resolution and frame rate of all connections to a meeting, define a meeting type
(MCU service) in the MCU and place the limit there. For more information, see Creating a Meeting Type
on page 40. Alternatively, you can limit the bandwidth using the global bandwidth policies in Scopia
Management.
®
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 20
Ports to Open for the Scopia® Elite 6000 for Aura
Collaboration Suite
The Scopia® Elite 6000 for Aura Collaboration Suite is typically located in the enterprise network and is
connected to the DMZ. When opening ports on the Scopia® Elite 6000, use the following as a reference:
•
If you are opening ports that are both in and out of the Scopia® Elite 6000 for Aura Collaboration
Suite, see Table 2: Bidirectional Ports to Open on the Scopia® Elite 6000 for Aura Collaboration
Suite on page 21.
•
If you are opening ports inbound to the Scopia® Elite 6000 for Aura Collaboration Suite, see Table
3: Inbound Ports to Open to the Scopia® Elite 6000 for Aura Collaboration Suite on page 23.
Important:
The specific firewalls you need to open ports on depends on where your MCU and other Scopia
Solution products are deployed.
Table 2: Bidirectional Ports to Open on the Scopia® Elite 6000 for Aura Collaboration Suite
Port Range Protocol Destination Functionality
1024-1324 H.245
(TCP)
1719 RAS
(UDP)
Any H.323
device
H.323
gatekeeper
Enables H.245
signaling
Enables RAS
signaling
Result of Blocking
Port
Cannot connect H.323
calls
Cannot communicate
with H.323 gatekeeper
Mandatory
To configure, see
Configuring the TCP Port
Range for H.245 on the
Scopia® Elite 6000 on
page 57
Mandatory
To configure, see
Configuring the UDP Port
for RAS on the Scopia
Elite 6000 on page 59
and Configuring the UDP
Port for the Gatekeeper on
the Scopia® Elite 6000 on
page 60
®
Required
®
1720 Q.931
(TCP)
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Any H.323
device
Enables Q.931
signaling
Cannot connect H.323
calls
Mandatory
To configure, see
Configuring the TCP Port
Q.931 on the Scopia® Elite
6000 on page 60
Planning your MCU Deployment | 21
Port Range Protocol Destination Functionality
3336 XML
(TCP)
Conference
Control web
client
Enables you to
manage the MCU
via the XML API
endpoint,
®
Scopia
Management,
or third-party
controlling
applications
3337 XML
(TCP)
Other MCUs Enables use of
MCU Cascading
XML API
3338 XML
(TCP)
®
Scopia
Management,
or third-party
Enables you to
configure the MCU
via the XML API
configuration
applications
3400-3580 SIP
BFCP
(TCP)
Any SIP video
network
device
Enables SIP
content sharing
Result of Blocking
Port
Cannot use MCU
Conference Control
web user interface.
Cannot use XML API
to control MCU.
Cannot cascade
between two MCUs
Cannot configure
MCU via the XML API
Cannot share SIP
contents
Required
Mandatory as deployed
with Scopia® Management
Mandatory if multiple
MCUs are deployed with
Scopia® Management
Mandatory if deployed with
Scopia® Management
Mandatory if using content
sharing with SIP over TCP
To configure, see
Configuring the TCP Port
Range for SIP BFCP on
the Scopia® Elite 6000 on
page 62
5060 SIP
(TCP/
UDP)
5061 SIP
(TLS)
12000-13200
16384-16984
RTP/
RTCP/
SRTP
(UDP)
Any SIP video
network
device
Any SIP video
network
device
Any H.323 or
SIP mediaenabled video
network
device
Enables SIP
signaling
Enables secure SIP
signaling
Enables real-time
delivery of video
and audio media
Cannot connect SIP
calls
Cannot connect SIP
calls over TLS
Cannot transmit/
receive video media
streams
Mandatory if using SIP
over TCP/ UDP
To configure, see
Configuring the
TCP/UDP/TLS Port for SIP
on the Scopia® Elite 6000
on page 61
Mandatory if using SIP
over TLS
To configure, see
Configuring the
TCP/UDP/TLS Port for SIP
on the Scopia® Elite 6000
on page 61
Mandatory
To configure, see
Configuring the UDP Port
Ranges for RTP/RTCP on
the Scopia® Elite 6000 on
page 56
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 22
Table 3: Inbound Ports to Open to the Scopia® Elite 6000 for Aura Collaboration Suite
Port
Range
Protocol Destination Functionality
21 FTP
(TCP)
22 SSH
(TCP)
80 HTTP
(TCP)
443 HTTPS
(HTTP
over SSL)
Result of Blocking
Port
FTP Server Enables audio stream
recording
Cannot record audio
streams
SSH Client Enables you to view logs Cannot view logs in
real-time (logs are
collected on the
compact flash card)
Web client Provides access to the
MCU Administrator; used
Cannot configure
MCU
for software upgrade
Web client Provides secure access
to the MCU Administrator;
Cannot configure
MCU
used for software
upgrade
Required
Optional
Optional
Mandatory if using
HTTP
To configure, see
Configuring the
HTTP Port on the
Scopia® Elite 6000
on page 58
Mandatory if using
HTTPS
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Planning your MCU Deployment | 23
Chapter 3 | Securing your Scopia® Elite
6000
There are several ways of securing your MCU:
•
You can secure the connection between the MCU and Scopia® Management via TLS.
•
You can secure the MCU by enabling or disabling remote management with the SSH, FTP, ICMP (ping)
protocols.
•
Using the MCU dual-NIC feature, you can enhance security by placing management traffic on a separate
subnet from media and signaling traffic.
Important:
Using encryption is subject to local regulation. In some countries it is restricted or limited for usage. For more
information, consult your local reseller.
Navigation
•
Securing MCU and Scopia® Management Connection with TLS
•
Configuring Security Access Levels for the Scopia® Elite 6000 on page 31
•
Configuring IP Separation (Dual NIC) on the Device on page 32
on page 24
Securing MCU and Scopia® Management Connection with
TLS
TLS is a standard method of authentication and encryption of SIP application signalling, using public-key
cryptographic system. To allow a secure connection between the MCU and Scopia® Management, the
SIP server must be configured to support TLS, and a TLS certificate must be uploaded to the MCU, to
provide TLS public and private keys for an encrypted network connection.
Important:
Using encryption is subject to local regulation. In some countries it is restricted or limited for usage.
For more information, consult your local reseller.
Navigation
•
Securing MCU with TLS in a SIP Environment
•
Uploading TLS Certificates to the MCU on page 25
on page 24
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Securing your Scopia® Elite 6000 | 24
Securing MCU with TLS in a SIP Environment
About this task
The first step to allow a secure connection between MCU and Scopia® Management is to enable TLS support on the MCU SIP server. Once MCU SIP server is TLS enabled, a certificate must be uploaded to the MCU to provide identification and encryption keys (see Uploading TLS Certificates to the MCU on page 25).
Important:
Using encryption is subject to local regulation. In some countries it is restricted or limited for usage.
For more information, consult your local reseller.
Procedure
1. Log in to the MCU.
2. Select Configuration > Protocols > Enable SIP Protocol.
3. Select Specify.
4. Set the IP address as the IP address of the Scopia® Management server.
5. Set Port to the same port defined in Scopia® Management. The default value is 5061.
6. Set Type as TLS.
Figure 8: Enabling the SIP Protocol on the MCU
7. Restart the MCU.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Securing your Scopia® Elite 6000 | 25
Uploading TLS Certificates to the MCU
About this task
TLS certificates, issued by a trusted Certificate Authority (CA) contains the server’s public encryption
keys, that are used over the network to ensure authentication and encryption of the network connection.
Important:
Using encryption is subject to local regulation. In some countries it is restricted or limited for usage.
For more information, consult your local reseller.
Procedure
1. Log in to the MCU.
2. Select Configuration.
3. Select Manage in the Security section.
4. Select Create a new certificate request.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Figure 9: Security section
Securing your Scopia® Elite 6000 | 26
Figure 10: Creating a new certificate request
5. Select Next.
6. Enter the Organization, Organizational Unit, Email and Common name. For example:
•
Organization: Company_Name
•
Organizational Unit: IT
•
Email: joe@companyname.com
•
Common name: video.mycompany.com (unique for each MCU)
7. Select Next.
8. Enter the geographical information as required. For example:
•
Country/Region: US
•
State/Province: New York
•
City/Locality: New York
9. Select Next.
The Certificate Request Summary is displayed.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Figure 11: Organization details
Securing your Scopia® Elite 6000 | 27
Figure 12: Certificate request summary
10. To generate a certificate request, select Next. Copy certificate request text in text area and
paste it to a file (for example, mcu_ca_request.txt). Then select Finish.
Figure 13: Saving the certificate request
11. Submit this file to your Certification Authority (CA) by e-mail or any other method supported
by your organization for your Enterprise CA.
You will receive a signed certificate from the CA, for example and the root certificate, for
example ca_root.cert.
To install the signed certificate:
12. Select Manage.
13. Select Process the pending request and install the certificate.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Securing your Scopia® Elite 6000 | 28
Figure 14: Certificate status
14. Select Next.
15. Open the signed certificate, and copy-paste the content of the signed certificate.
Figure 15: Processing a pending request
16. Select Next.
17. If data is correct, select Finish and the MCU certificate is uploaded successfully. If the data is
not correct, select Back to enter the correct data.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Securing your Scopia® Elite 6000 | 29
Figure 16: Successful certificate upload
18. (Optional) Select Details to view the certificate details like the serial number or the expiry
date.
19. Upload the CA root certificate by selecting Upload from the Security section.
20. Select Browse to select the CA root certificate.
Administrator Guide for Avaya Scopia® Elite 6000 for Aura
Collaboration Suite Version 8.3
Figure 17: Viewing the certificate details
Securing your Scopia® Elite 6000 | 30
Loading...