Avaya scopia elite 6000 series Service manual

Avaya Scopia® Elite 6000 for Aura
Collaboration Suite
Administrator Guide
Release 8.3.2
For Solution 8.3.2
February 2016
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

© 2014-2016, Avaya, Inc.1
All Rights Reserved.2
Notice3
While reasonable efforts have been made to ensure that the4
information in this document is complete and accurate at the time of5
printing, Avaya assumes no liability for any errors. Avaya reserves6
the right to make changes and corrections to the information in this7
document without the obligation to notify any person or organization8
of such changes.9
Documentation disclaimer10
“Documentation” means information published by Avaya in varying11
mediums which may include product information, operating12
instructions and performance specifications that Avaya may generally13
make available to users of its products and Hosted Services.14
Documentation does not include marketing materials. Avaya shall not15
be responsible for any modifications, additions, or deletions to the16
original published version of documentation unless such17
modifications, additions, or deletions were performed by Avaya. End18
User agrees to indemnify and hold harmless Avaya, Avaya's agents,19
servants and employees against all claims, lawsuits, demands and20
judgments arising out of, or in connection with, subsequent21
modifications, additions or deletions to this documentation, to the22
extent made by End User.23
Link disclaimer24
Avaya is not responsible for the contents or reliability of any linked25
websites referenced within this site or documentation provided by26
Avaya. Avaya is not responsible for the accuracy of any information,27
statement or content provided on these sites and does not28
necessarily endorse the products, services, or information described29
or offered within them. Avaya does not guarantee that these links will30
work all the time and has no control over the availability of the linked31
pages.32
Warranty33
Avaya provides a limited warranty on Avaya hardware and software.34
Refer to your sales agreement to establish the terms of the limited35
warranty. In addition, Avaya’s standard warranty language, as well as36
information regarding support for this product while under warranty is37
available to Avaya customers and other parties through the Avaya38
Support website: https://support.avaya.com/helpcenter/39
getGenericDetails?detailId=C20091120112456651010 under the link40
“Warranty & Product Lifecycle” or such successor site as designated41
by Avaya. Please note that if You acquired the product(s) from an42
authorized Avaya Channel Partner outside of the United States and43
Canada, the warranty is provided to You by said Avaya Channel44
Partner and not by Avaya.45
“Hosted Service” means a hosted service subscription that You46
acquire from either Avaya or an authorized Avaya Channel Partner47
(as applicable) and which is described further in Hosted SAS or other48
service description documentation regarding the applicable hosted49
service. If You purchase a Hosted Service subscription, the foregoing50
limited warranty may not apply but You may be entitled to support51
services in connection with the Hosted Service as described further52
in your service description documents for the applicable Hosted53
Service. Contact Avaya or Avaya Channel Partner (as applicable) for54
more information.55
Hosted Service56
THE FOLLOWING APPLIES IF YOU PURCHASE A HOSTED57
SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA58
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE59
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA60
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO61
UNDER THE LINK “Avaya Terms of Use for Hosted Services” OR62
SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE63
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE64
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED65
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON66
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE67
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY68
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF69
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A70
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT71
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE72
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR
73
IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU74
MUST NOT ACCESS OR USE THE HOSTED SERVICE OR75
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED76
SERVICE. YOUR USE OF THE HOSTED SERVICE SHALL BE77
LIMITED BY THE NUMBER AND TYPE OF LICENSES78
PURCHASED UNDER YOUR CONTRACT FOR THE HOSTED79
SERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTED80
SERVICES IF APPLICABLE, YOU MAY HAVE THE OPPORTUNITY81
TO USE FLEX LICENSES, WHICH WILL BE INVOICED82
ACCORDING TO ACTUAL USAGE ABOVE THE CONTRACT83
LICENSE LEVEL. CONTACT AVAYA OR AVAYA’S CHANNEL84
PARTNER FOR MORE INFORMATION ABOUT THE LICENSES85
FOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITY86
OF ANY FLEX LICENSES (IF APPLICABLE), PRICING AND87
BILLING INFORMATION, AND OTHER IMPORTANT88
INFORMATION REGARDING THE HOSTED SERVICE.89
Licenses90
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA91
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,92
UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya93
Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY94
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,95
USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED96
FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA97
CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL98
AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.99
UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,100
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE101
WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN102
AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA103
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU104
AND ANYONE ELSE USING OR SELLING THE SOFTWARE105
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR106
USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,107
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM108
YOU ARE INSTALLING, DOWNLOADING OR USING THE109
SOFTWARE (HEREINAFTER REFERRED TO110
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO111
THESE TERMS AND CONDITIONS AND CREATE A BINDING112
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE113
APPLICABLE AVAYA AFFILIATE (“AVAYA”).114
Avaya grants You a license within the scope of the license types115
described below, with the exception of Heritage Nortel Software, for116
which the scope of the license is detailed below. Where the order117
documentation does not expressly identify a license type, the118
applicable license will be a Designated System License. The119
applicable number of licenses and units of capacity for which the120
license is granted will be one (1), unless a different number of121
licenses or units of capacity is specified in the documentation or other122
materials available to You. “Software” means computer programs in123
object code, provided by Avaya or an Avaya Channel Partner,124
whether as stand-alone products, pre-installed on hardware products,125
and any upgrades, updates, patches, bug fixes, or modified versions126
thereto. “Designated Processor” means a single stand-alone127
computing device. “Server” means a Designated Processor that128
hosts a software application to be accessed by multiple users.129
“Instance” means a single copy of the Software executing at a130
particular time: (i) on one physical machine; or (ii) on one deployed131
software virtual machine (“VM”) or similar deployment.132
License type(s)133
Designated System(s) License (DS). End User may install and use134
each copy or an Instance of the Software only on a number of135
Designated Processors up to the number indicated in the order.136
Avaya may require the Designated Processor(s) to be identified in137
the order by type, serial number, feature key, Instance, location or138
other specific designation, or to be provided by End User to Avaya139
through electronic means established by Avaya specifically for this140
purpose.141
Concurrent User License (CU). End User may install and use the142
Software on multiple Designated Processors or one or more Servers,143
so long as only the licensed number of Units are accessing and using144
the Software at any given time. A “Unit” means the unit on which145
Avaya, at its sole discretion, bases the pricing of its licenses and can146
be, without limitation, an agent, port or user, an e-mail or voice mail147

account in the name of a person or corporate function (e.g.,1
webmaster or helpdesk), or a directory entry in the administrative2
database utilized by the Software that permits one user to interface3
with the Software. Units may be linked to a specific, identified Server4
or an Instance of the Software.5
Database License (DL). End User may install and use each copy or6
an Instance of the Software on one Server or on multiple Servers7
provided that each of the Servers on which the Software is installed8
communicates with no more than one Instance of the same9
database.10
CPU License (CP). End User may install and use each copy or11
Instance of the Software on a number of Servers up to the number12
indicated in the order provided that the performance capacity of the13
Server(s) does not exceed the performance capacity specified for the14
Software. End User may not re-install or operate the Software on15
Server(s) with a larger performance capacity without Avaya’s prior16
consent and payment of an upgrade fee.17
Named User License (NU). You may: (i) install and use each copy or18
Instance of the Software on a single Designated Processor or Server19
per authorized Named User (defined below); or (ii) install and use20
each copy or Instance of the Software on a Server so long as only21
authorized Named Users access and use the Software. “Named22
User”, means a user or device that has been expressly authorized by23
Avaya to access and use the Software. At Avaya’s sole discretion, a24
“Named User” may be, without limitation, designated by name,25
corporate function (e.g., webmaster or helpdesk), an e-mail or voice26
mail account in the name of a person or corporate function, or a27
directory entry in the administrative database utilized by the Software28
that permits one user to interface with the Software.29
Shrinkwrap License (SR). You may install and use the Software in30
accordance with the terms and conditions of the applicable license31
agreements, such as “shrinkwrap” or “clickthrough” license32
accompanying or applicable to the Software (“Shrinkwrap License”).33
Heritage Nortel Software34
“Heritage Nortel Software” means the software that was acquired by35
Avaya as part of its purchase of the Nortel Enterprise Solutions36
Business in December 2009. The Heritage Nortel Software is the37
software contained within the list of Heritage Nortel Products located38
at https://support.avaya.com/LicenseInfo under the link “Heritage39
Nortel Products” or such successor site as designated by Avaya. For40
Heritage Nortel Software, Avaya grants Customer a license to use41
Heritage Nortel Software provided hereunder solely to the extent of42
the authorized activation or authorized usage level, solely for the43
purpose specified in the Documentation, and solely as embedded in,44
for execution on, or for communication with Avaya equipment.45
Charges for Heritage Nortel Software may be based on extent of46
activation or use authorized as specified in an order or invoice.47
Copyright48
Except where expressly stated otherwise, no use should be made of49
materials on this site, the Documentation, Software, Hosted Service,50
or hardware provided by Avaya. All content on this site, the51
documentation, Hosted Service, and the product provided by Avaya52
including the selection, arrangement and design of the content is53
owned either by Avaya or its licensors and is protected by copyright54
and other intellectual property laws including the sui generis rights55
relating to the protection of databases. You may not modify, copy,56
reproduce, republish, upload, post, transmit or distribute in any way57
any content, in whole or in part, including any code and software58
unless expressly authorized by Avaya. Unauthorized reproduction,59
transmission, dissemination, storage, and or use without the express60
written consent of Avaya can be a criminal, as well as a civil offense61
under the applicable law.62
Virtualization63
The following applies if the product is deployed on a virtual machine.64
Each product has its own ordering code and license types. Note that65
each Instance of a product must be separately licensed and ordered.66
For example, if the end user customer or Avaya Channel Partner67
would like to install two Instances of the same type of products, then68
two products of that type must be ordered.69
Third Party Components70
“Third Party Components” mean certain software programs or71
portions thereof included in the Software or Hosted Service may72
contain software (including open source software) distributed under
73
third party agreements (“Third Party Components”), which contain74
terms regarding the rights to use certain portions of the Software75
(“Third Party Terms”). As required, information regarding distributed76
Linux OS source code (for those products that have distributed Linux77
OS source code) and identifying the copyright holders of the Third78
Party Components and the Third Party Terms that apply is available79
in the products, Documentation or on Avaya’s website at: https://80
support.avaya.com/Copyright or such successor site as designated81
by Avaya. The open source software license terms provided as Third82
Party Terms are consistent with the license rights granted in these83
Software License Terms, and may contain additional rights benefiting84
You, such as modification and distribution of the open source85
software. The Third Party Terms shall take precedence over these86
Software License Terms, solely with respect to the applicable Third87
Party Components to the extent that these Software License Terms88
impose greater restrictions on You than the applicable Third Party89
Terms.90
The following applies if the H.264 (AVC) codec is distributed with the91
product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT92
PORTFOLIO LICENSE FOR THE PERSONAL USE OF A93
CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE94
REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH95
THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC96
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A97
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO98
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS99
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.100
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG101
LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.102
Service Provider103
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S104
HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT105
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS106
SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE107
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY108
FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL109
PARTNER’S HOSTING OF AVAYA PRODUCTS MUST BE110
AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED111
PRODUCTS USE OR EMBED CERTAIN THIRD PARTY112
SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT113
SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS114
REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE115
LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S116
EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY117
SUPPLIER.118
WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL119
PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED120
THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE121
AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES122
THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY123
AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729124
CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE 125
WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC IS126
LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR127
THE PERSONAL USE OF A CONSUMER OR OTHER USES IN128
WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)129
ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD130
(“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS131
ENCODED BY A CONSUMER ENGAGED IN A PERSONAL132
ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER133
LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED134
OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL135
INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS136
MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://137
WWW.MPEGLA.COM.138
Compliance with Laws139
Customer acknowledges and agrees that it is responsible for140
complying with any applicable laws and regulations, including, but not141
limited to laws and regulations related to call recording, data privacy,142
intellectual property, trade secret, fraud, and music performance143
rights, in the country or territory where the Avaya product is used.144

Preventing Toll Fraud1
“Toll Fraud” is the unauthorized use of your telecommunications2
system by an unauthorized party (for example, a person who is not a3
corporate employee, agent, subcontractor, or is not working on your4
company's behalf). Be aware that there can be a risk of Toll Fraud5
associated with your system and that, if Toll Fraud occurs, it can6
result in substantial additional charges for your telecommunications7
services.8
Avaya Toll Fraud intervention9
If You suspect that You are being victimized by Toll Fraud and You10
need technical assistance or support, call Technical Service Center11
Toll Fraud Intervention Hotline at [phone] for the United12
States and Canada. For additional support telephone numbers, see13
the Avaya Support website: https://support.avaya.com or such14
successor site as designated by Avaya.15
Security Vulnerabilities16
Information about Avaya’s security support policies can be found in17
the Security Policies and Support section of https://18
support.avaya.com/security.19
Suspected Avaya product security vulnerabilities are handled per the20
Avaya Product Security Support Flow (https://21
support.avaya.com/css/P8/documents/100161515).22
Downloading Documentation23
For the most current versions of Documentation, see the Avaya24
Support website: https://support.avaya.com, or such successor site25
as designated by Avaya.26
Contact Avaya Support27
See the Avaya Support website: https://support.avaya.com for28
product or Hosted Service notices and articles, or to report a problem29
with your Avaya product or Hosted Service. For a list of support30
telephone numbers and contact addresses, go to the Avaya Support31
website: https://support.avaya.com (or such successor site as32
designated by Avaya), scroll to the bottom of the page, and select33
Contact Avaya Support.34
Trademarks35
The trademarks, logos and service marks (“Marks”) displayed in this36
site, the Documentation, Hosted Service(s), and product(s) provided37
by Avaya are the registered or unregistered Marks of Avaya, its38
affiliates, or other third parties. Users are not permitted to use such39
Marks without prior written consent from Avaya or such third party40
which may own the Mark. Nothing contained in this site, the41
Documentation, Hosted Service(s) and product(s) should be42
construed as granting, by implication, estoppel, or otherwise, any43
license or right in and to the Marks without the express written44
permission of Avaya or the applicable third party.45
Avaya is a registered trademark of Avaya Inc.46
All non-Avaya trademarks are the property of their respective owners.47
Linux® is the registered trademark of Linus Torvalds in the U.S. and48
other countries.49

Contents
Chapter 1: About the Avaya Scopia® Elite MCU.................................................................... 8
About Avaya Scopia® Elite MCU.............................................................................................. 8
Minimum Requirements and Specifications............................................................................. 12
Chapter 2: Planning your MCU Deployment........................................................................ 14
Planning the Topology of the Scopia® Elite 6000 Series MCU................................................... 14
Deploying Redundant MCUs.................................................................................................. 17
Planning a Centralized or Distributed Topology (Cascading) for MCU........................................ 17
Planning Network Redundancy or IP Separation (Dual NIC)..................................................... 20
Sizing your MCUs and Scopia® Desktop servers for Aura Collaboration Suite............................ 21
About the Capacity of the MCU.............................................................................................. 22
Ports to Open for the Scopia® Elite 6000 Series MCU.............................................................. 24
Chapter 3: Securing your Scopia® Elite MCU...................................................................... 27
Securing MCU and Scopia® Management Connection with TLS................................................ 27
Securing MCU with TLS in a SIP Environment................................................................... 28
Uploading TLS Certificates to the MCU............................................................................. 29
Configuring Security Access Levels for the Scopia® Elite MCU................................................. 34
Configuring IP Separation (Dual NIC) on the Device................................................................. 35
Chapter 4: Maintaining the Scopia® Elite MCU.................................................................... 41
Adding a License to the MCU................................................................................................. 41
Configuring MCU Meeting Types............................................................................................ 43
Creating a Meeting Type.................................................................................................. 43
Configuring the Bandwidth of a Meeting Type.................................................................... 47
Configuring the Auto-Attendant Service............................................................................. 50
Managing Scopia® Elite MCU User Profiles............................................................................. 52
Adding a User Profile....................................................................................................... 52
Changing a User Password.............................................................................................. 53
Deleting a User Profile..................................................................................................... 54
Managing the Redundant Power Supply of the Scopia® Elite MCU............................................ 55
Adding a Power Supply Unit to the MCU........................................................................... 55
Removing a Power Supply Unit from the MCU................................................................... 57
Configuring Ports on the Scopia® Elite MCU............................................................................ 59
Configuring the UDP Port Ranges for RTP/RTCP on the Scopia® Elite MCU....................... 59
Configuring the TCP Port Range for H.245 on the Scopia® Elite MCU................................. 60
Configuring the HTTP Port on the Scopia® Elite MCU........................................................ 61
Configuring the UDP Port for RAS on the Scopia® Elite MCU............................................. 62
Configuring the UDP Port for the Gatekeeper on the Scopia® Elite MCU............................. 63
Configuring the TCP Port Q.931 on the Scopia® Elite MCU................................................ 64
Configuring the TCP/UDP/TLS Port for SIP on the Scopia® Elite MCU................................ 65
Configuring the TCP Port Range for SIP BFCP on the Scopia® Elite MCU........................... 66
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 6
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

Branding your Scopia® Elite MCU User Interface..................................................................... 67
Customizing the Logo Displayed in MCU Conferences....................................................... 67
Customizing MCU Audio Messages.................................................................................. 70
Upgrading, Backing up and Restoring the Scopia® Elite MCU................................................... 71
Backing Up Your Scopia® Elite MCU Configuration............................................................ 71
Restoring Your Scopia® Elite MCU Configuration............................................................... 72
Upgrading Scopia® Elite 6000 Series MCU Software......................................................... 73
Restoring a Previous Software Version............................................................................. 74
Monitoring MCU Performance................................................................................................ 75
Chapter 5: Troubleshooting the Scopia® Elite MCU............................................................ 78
Gathering logs on the MCU.................................................................................................... 78
Defining an Advanced Command on the MCU......................................................................... 80
Resolving MCU Failure to Register with the Gatekeeper........................................................... 80
MCU Cannot Start a Videoconference..................................................................................... 81
MCU Does Not Allow Access an Existing Videoconference....................................................... 83
Poor Quality in Cascaded Videoconferences........................................................................... 84
Endpoints Unexpectedly Disconnect from Videoconferences.................................................... 84
Videoconference Ends Unexpectedly...................................................................................... 85
SIP Call Disconnected Unexpectedly...................................................................................... 85
Resolving Presentation Issues................................................................................................ 85
Resolving a Video Display Issue............................................................................................. 87
Resolving Poor Audio Quality................................................................................................. 88
Resolving Poor Video Quality................................................................................................. 90
Scopia® Elite MCU cannot connect when Scopia® Management can be accessed only through
FQDN................................................................................................................................... 96
Glossary................................................................................................................................... 97
Contents
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 7
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

Chapter 1: About the Avaya Scopia® Elite1
MCU2
The Scopia® Elite MCU is Scopia® Solution’s flagship platform for high definition multi-party3
videoconferencing.4
The MCU supports communications in the board room, at the desktop, in the home, or on the road5
over wireless.6
Related links7
About Avaya Scopia® Elite MCU on page 88
Minimum Requirements and Specifications on page 129
About Avaya Scopia® Elite MCU10
The Scopia® Elite MCU is Scopia® Solution’s flagship platform for high definition multi-party11
videoconferencing.12
An MCU, or Multipoint Control Unit, connects several endpoints to a single videoconference. It13
manages the audio mixing and creates the video layouts, adjusting the output to suit each14
endpoint's capabilities.15
The Aura Collaboration Suite enables any enterprise to gain full business collaboration utilizing16
audio, video or the web. The Aura Collaboration Suite is positioned for organizations which need17
robust collaboration capabilities, including industry leading HD video, plus audio and web18
conferencing.19
The Scopia® Solution is a component of the Aura Collaboration Suite. With this unified offering,20
every potential Avaya UC customer can access and utilize the Avaya Scopia premium collaboration21
experience.22
Avaya UC customers can now enjoy the Scopia high-end video experience as one of their23
collaboration options within the Collaboration Suite.24
The Avaya Scopia® Desktop and Avaya Scopia® Mobile user licenses delivered with the Aura25
Collaboration Suite require a unique version of the MCU specifically designed for the Aura26
Collaboration Suite: Scopia® Elite MCU.27
The MCU is specially tailored to fit this Unified Communications (UC) offering, along with other video28
infrastructure devices of the Scopia® Solution such as Scopia® Desktop for Aura Collaboration Suite29
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 8
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

and Avaya Scopia® Management for Aura Collaboration. The MCU cannot be re-purposed for other1
video solutions which are not part of the Aura Collaboration Suite.2
The MCU harnesses revolutionary processing power for the most demanding videoconferencing3
applications using the latest DSP technologies. For an uncompromised videoconferencing4
experience, the MCU supports dual channels of Full HD 1080p at 60 frames per second for video5
and content, H.264 High Profile for bandwidth efficiency, H.264 Scalable Video Coding (SVC) for6
high network error resiliency, and full support for many telepresence systems.7
With the MCU, each videoconference participant receives a quality experience optimized to their8
individual capabilities, from wireless mobile devices to HD room systems and immersive9
telepresence systems. The MCU leads in video interoperability, working with the broadest range of10
video systems on the market from leading UC clients to mobile devices and telepresence systems.11
The MCU also features a patented, distributed architecture approach known as the Virtual MCU or12
cascaded videoconferences, which brings unparalleled scalability to its superb videoconferencing13
experience.14
The MCU's feature list includes:15
• Revolutionary video processing power16
The MCU brings unmatched power and capacity in a single unit, enabling dual-channel Full HD17
1080p resolution at 60 frames per second for video and content, simultaneous H.264 High18
Profile and H.264 SVC, and support for multi-stream telepresence.19
• Dynamic resource allocation20
A meeting can support a mix of SD and HD users, making most efficient use of available21
resources. Video and audio processing is carried out per user rather than per meeting, with22
resolutions ranging from CIF to 1080p in the same meeting. Each user connects using unique,23
optimized audio and video settings to enjoy the best audio and video quality supported by their24
endpoint and network, without affecting the other participants in a conference.25
• Intuitive and easy to use26
Video menus make it easy to set up or enter a videoconference, and the intuitive web interface27
makes administration easy.28
• Massive scalability29
The Virtual MCU enables a unique scalability in both local and distributed architectures to30
combine the capacity of multiple MCU devices in the same meeting. The number of supported31
connections depends on your license.32
• Seamless interoperability33
The MCU is built on the solid foundation of our H.323 and SIP software, ensuring full34
compliance and broad-ranging interoperability with IP, ISDN, and 3G endpoints. It also enables35
H.323 and SIP endpoints to collaborate in the same videoconference. See Figure 1: Endpoints36
in the same videoconference on page 10.37
About Avaya Scopia® Elite MCU
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 9
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

1
Figure 1: Endpoints in the same videoconference2
The MCU also easily integrates telepresence systems with regular videoconferencing systems,3
even within the same meeting. It is compatible with telepresence systems from Cisco,4
Tandberg, Polycom, and LifeSize/Logitech.5
When used with Scopia® Solution gateways, the deployment can even add ISDN, V.35 and6
other endpoints to the same meeting.7
• Video quality8
The MCU delivers enterprise quality video and audio processing, using latest industry9
standards including state-of-the-art DSP hardware and software. This video quality is10
supported by:11
- SVC error resiliency for unmanaged networks using Temporal Scalability and Forward Error12
Correction (FEC).13
Forward Error Correction (FEC) is a proactive method of sending redundant information in14
the video stream to preempt quality degradation. SVC extends the H.264 codec standard to15
dramatically increase error resiliency and video quality without the need for higher16
bandwidth.17
- Frame rates can reach 60 frames per second, ensuring smooth video movement.18
- A wide choice of video layouts19
About the Avaya Scopia® Elite MCU
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 10
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

- Bitrate (data speed) of up to 12 megabits per second on each stream without affecting1
capacity. Bitrate is the speed of data flow. Higher video resolutions require higher bitrates to2
ensure the video is constantly updated, thereby maintaining smooth motion.3
• Audio quality4
The MCU integrates Voice Activity Detection (VAD) to determine the active speaker and filter5
out background noise from participants. The MCU also improves audio quality with AGC.6
Automatic Gain Control (AGC) smooths audio signals through normalization, by lowering7
sounds which are too strong and strengthening sounds which are too weak.8
• Personalized video layouts per meeting or per participant9
As an administrator you can choose from 26 video layouts for all participants, or each10
participant can customize their own view. You can view up to 28 participants on your screen. A11
video layout is the arrangement of participant images as they appear on the monitor in a12
videoconference. If the meeting includes a presentation, a layout can also refer to the13
arrangement of the presentation image together with the meeting participants.14
The MCU supports sharing presentations and other content via SIP (using the BFCP standard)15
and H.323 (using the H.239 standard). A user can connect to a meeting from either type of16
endpoint to share content such as presentations, spreadsheets, documents, and movies.17
The MCU supports an additional set of layouts to optimize screen space during content sharing18
on single-screen endpoints. With this feature, endpoints with proprietary content sharing19
protocols such as Avaya Flare Experience or Microsoft Lync can simultaneously display20
content and participants.21
• Security and privacy22
The MCU can encrypt communications with endpoints to create secure connections with H.23
235-based encryption for H.323 endpoints and SRTP and TLS encryption for SIP endpoints.24
In addition, the MCU features administrator and operator password protection for accessing the25
web interface. It also features optional PIN protection for joining a videoconference, and26
additional PIN protection for moderator control.27
• Dual NIC: IP separation or network redundancy28
You can use the two network ports of the MCU in one of the following ways:29
- Network redundancy cuts downtime and provides a cost-effective, uninterrupted service. If30
the first NIC fails during a videoconference, network traffic is automatically routed to the31
second NIC without affecting current calls on the MCU.32
- IP separation enhances security within the enterprise by routing media and management33
traffic to two different subnets.34
• Intuitive web-based management35
You can configure the MCU through an intuitive web interface offering easy, high-level36
administrative flexibility for an enhanced user experience.37
• In-meeting indicators38
A range of messages and icons are displayed on the endpoint during meetings as events39
occur. For example, participants are notified when someone joins or leaves the meeting.40
About Avaya Scopia® Elite MCU
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 11
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

• Easy creation of logs for Customer Support1
You can easily create a file containing logs and settings which you can send to Customer2
Support for troubleshooting.3
• Interactive Voice Response (IVR) messages4
The MCU includes pre-recorded greetings to participants and announcements as each new5
participant joins a meeting. You can record messages to provide custom greetings and6
announcements, but typically Avaya Scopia® Management supplies these messages across all7
MCUs in the organization.8
• SIP Firewall traversal compatibilities9
The MCU is fully interoperable with third-party Session Border Controllers (SBC), which10
increases compatibility and dexterity with SIP endpoints that join remotely.11
Related links12
About the Avaya Scopia® Elite MCU on page 813
Minimum Requirements and Specifications14
This section details the system specifications of the MCU you purchased. Refer to this data when15
preparing system setup and afterwards as a means of verifying that the environment still complies16
with these requirements.17
Hardware requirements18
.19
The following lists the device's hardware requirements:20
• System power requirements: 100-240 VAC, 50/60 Hz with hot-swap redundant AC power21
supply and feed (optional)22
- AC Input:23
1000W output @ 100-120V, 12-10A, 50-60Hz24
1200W output @ 120-140V, 12-10A, 50-60Hz25
1800W output @ 200-240V, 10-8.5A, 50-60Hz26
- Maximum power consumption at 35°C: 360W, 450VA (1228 BTU/h)27
• Environmental requirements:28
- Operating temperature: 10°C to 35°C (50°F to 95°F)29
- Relative humidity: 5% to 90% non-condensing30
- Storage and transit temperature: -40°C to 70°C (-40°F to 158°F), ambient31
- Acoustics: low noise fan speed control32
• Physical requirements:33
- Dimensions: width: 437mm (17.2"); height: 43mm (1.7"); depth: 790mm (31.1")34
About the Avaya Scopia® Elite MCU
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 12
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

- Approximate net weight: 14.5kg (32lbs) with one power supply1
- Approximate gross weight (with packaging): approx 23kg (50.7lbs)2
Software Specifications3
The following lists the technical specifications of the protocols and software requirements4
• Signaling protocols:5
- H.3236
- SIP7
- H.320 (in conjunction with Scopia H.320 Gateways)8
• Audio support:9
- Codecs: G.711. G.722, G.722.1, G.729, G.722.1 Annex C10
- DTMF tone detection (in-band, H.245 tones and RFC2833)11
• Video support:12
- High Definition Continuous Presence video with a resolution of 1080p at up to 60fps13
- Codecs: H.263, H.263+, H.264, H.264 SVC, H.264 High Profile14
- Live video resolutions: CIF up to 1080p15
- Presentation video resolution: VGA, SVGA, SXGA, XGA, 720p, 1080p, WUXGA16
- Video bandwidth: up to 12Mbps for 1080p resolutions and up to 6Mbps for 720p or lower17
• Web browser support:18
- Microsoft Internet Explorer versions 6, 7, 8 and 919
- Mozilla Firefox version 3.3 and above20
- Google Chrome21
- Apple Safari22
• Call capacity:23
For information on the default capacity of your MCU and how to increase it, see About the24
Capacity of the MCU on page 22.25
Related links26
About the Avaya Scopia® Elite MCU on page 827
Minimum Requirements and Specifications
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 13
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

Chapter 2: Planning your MCU Deployment1
When planning your MCU deployment, it is important to consider both bandwidth usage and port2
security, as described in the following sections:3
Related links4
Planning the Topology of the Scopia® Elite 6000 Series MCU on page 145
Deploying Redundant MCUs on page 176
Planning a Centralized or Distributed Topology (Cascading) for MCU on page 177
Planning Network Redundancy or IP Separation (Dual NIC) on page 208
Sizing your MCUs and Scopia® Desktop servers for Aura Collaboration Suite on page 219
About the Capacity of the MCU on page 2210
Ports to Open for the Scopia® Elite 6000 Series MCU on page 2411
Planning the Topology of the Scopia® Elite 6000 Series12
MCU13
This section describes the guidelines for deploying this and other Scopia® Solution components in14
your video network when you integrate with Aura Collaboration Suite.15
You can deploy Scopia® Solution components either in a centralized or distributed solution:16
• In a centralized topology (Figure 2: Centralized Scopia® Solution deployment with Aura17
Collaboration Suite on page 15), all the components are installed in the same location.18
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 14
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

1
Figure 2: Centralized Scopia® Solution deployment with Aura Collaboration Suite2
When deploying the Scopia® Solution for Aura Collaboration Suite, you gain state-of-the-art3
enterprise videoconferencing using Avaya Scopia® Desktop and Avaya Scopia® Mobile, while4
enabling these meetings to also include participants on Avaya UC devices such as Flare, One-5
X, IP Deskphone and ADVD.6
The solution includes these mandatory components:7
- Scopia® Elite 6000 Series MCU, responsible for combining images from different endpoints8
into a single continuous presence image to enable effective videoconferencing.9
- Avaya Scopia® Management for Aura Collaboration Suite, which sits at the core of your10
Scopia® Solution and offers a comprehensive management solution for video11
communications where enterprises can efficiently control the videoconferencing network.12
The MCU can only function and connect calls when managed and controlled by Scopia® 13
Management for Aura Collaboration Suite.14
- Scopia® Desktop server for Aura Collaboration Suite, the desktop videoconferencing system15
turning PCs, Macs and mobile devices into videoconferencing endpoints. The Scopia® 16
Desktop server brings together meetings with Scopia® Desktop Clients and Scopia® Mobile17
devices, passing their media connections to the MCU.18
Planning the Topology of the Scopia® Elite 6000 Series MCU
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 15
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

A SIP trunk connects the Aura Session Manager to Scopia® Management, while an H.3231
trunk connects the Aura Communication Manager also to Scopia® Management. Scopia® 2
Management synchronizes automatically and periodically with the Web License Manager3
(WebLM) installed on the Aura System Manager to manage the Collaboration Suite licenses.4
For detailed information on licenses, see Administrator Guide for Avaya Scopia® Management5
for Aura Collaboration Suite. You can also optionally add Aura Conferencing (AAC) to transmit6
media to the MCU.7
• In a distributed topology (Figure 3: Additional components in other locations for a distributed8
deployment on page 16), you can add components in other locations to create a scalable and9
geographically distributed solution. You can deploy a full set of videoconferencing components10
in the headquarters, and distribute additional MCUs and Scopia® Desktop servers over several11
branches. Each branch can have one or more of these servers depending on the branch's12
requirements for videoconferencing capacity and high availability. To provide scalability and13
high availability with service preservation, you can also cluster the Scopia® Desktop servers14
behind a load balancer. The Scopia® Desktop servers are typically deployed in the DMZ to15
provide connection to participants from both the internal and external networks.16
17
Figure 3: Additional components in other locations for a distributed deployment18
For a detailed description of the Scopia® Solution components, refer to Scopia® Solution Guide.19
For guidelines on how to assess your MCU and Scopia® Desktop server capacities, see Sizing your20
MCUs and Scopia® Desktop servers for Aura Collaboration Suite on page 21.21
Planning your MCU Deployment
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 16
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

Related links1
Planning your MCU Deployment on page 142
Deploying Redundant MCUs3
Redundancy is a way to deploy a network component, in which you deploy extra units as 'spares', to4
be used as backups in case one of the components fails.5
You can achieve MCU redundancy by deploying additional MCUs that are configured with the same6
services as the devices which they back up. You can also use the distributed topology of your7
deployment where MCUs located in different time zones can cover up for a failing MCU. MCU8
fallback is managed by Scopia® Management, as explained in Administrator Guide for Avaya9
Scopia® Management for Aura Collaboration Suite.10
This is different from LAN redundancy, which uses one of the MCU's two network ports as11
redundant, so if one fails, the other takes over. For more information, see Planning Network12
Redundancy or IP Separation (Dual NIC) on page 20.13
Related links14
Planning your MCU Deployment on page 1415
Planning a Centralized or Distributed Topology16
(Cascading) for MCU17
When your organization has more than one site, like a headquarters and several branches, the18
Scopia® Solution offers a unique method of cutting video bandwidth costs, known as cascaded19
meetings.20
A cascaded videoconference is a meeting distributed over more than one physical Scopia® Elite21
MCU, where a master MCU connects to one or more slave MCUs to create a single22
videoconference. It increases the meeting capacity by combining the resources of several MCUs.23
This can be especially useful for distributed deployments across several locations, reducing24
bandwidth usage.25
Without cascading, if you choose a centralized MCU deployment, frequent videoconferences26
between branches can be expensive (Figure 4: Centralized MCU deployment, where all branches27
use the HQ MCU on page 18).28
Deploying Redundant MCUs
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 17
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

1
Figure 4: Centralized MCU deployment, where all branches use the HQ MCU2
To reduce cross-site bandwidth costs, a distributed MCU deployment (Figure 5: Distributed MCU3
deployment cascading meetings for reduced WAN bandwidth on page 18) can perform cascaded4
conferences. Participants connect to their local MCU, and the conference is cascaded by connecting5
between the MCUs using a fraction of the bandwidth compared to the centralized deployment. The6
same principles apply to an MCU in the same location, thus increasing call capacity by cascading7
conferences between them.8
9
Figure 5: Distributed MCU deployment cascading meetings for reduced WAN bandwidth10
Planning your MCU Deployment
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 18
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

The bandwidth used by a cascaded link is equivalent to only a single client connection in each1
direction: upload and download. The bandwidth value is determined by the MCU meeting type (or2
service), which is invoked when choosing a dial prefix for the meeting. You define the maximum3
bandwidth for each meeting type in the MCU. For more information on defining meeting types, see 4
Configuring the Bandwidth of a Meeting Type on page 47.5
Users do not need to choose a specific MCU. The powerful functionality of virtual rooms enables6
you to dial the same number anywhere in the world, while the Scopia® Solution infrastructure7
transparently directs you to the correct meeting on the correct MCU.8
The maximum supported number of participants in a single videoconference is 500 for both the9
centralized and distributed MCU deployment.10
Users do not need to manually enable cascading when creating meetings. This is performed11
transparently by Avaya Scopia® Management using sophisticated cascading algorithms.12
When an endpoint initiates a meeting on an MCU, that MCU becomes the master MCU. Other13
MCUs which participate in the meeting are designated as slave MCUs. There are a number of14
factors that might influence when the system automatically chooses to cascade to a different MCU.15
For example, to avoid reaching the maximum bandwidth threshold, the system would attempt16
cascading with a different MCU, a slave MCU. Endpoints would then join the videoconference from17
the slave MCU. Only one level of cascading is supported: all slave MCU conferences must cascade18
to the same master MCU conference. Administrators can also customize the priority given to19
cascading in a distributed topology, as explained in Administrator Guide for Avaya Scopia® 20
Management for Aura Collaboration Suite.21
Cascading has the following characteristics:22
• A cascaded connection uses two connection s—one connection on the master MCU, and one23
connection on the slave MCU.24
• Make sure that the Meeting Type (MCU service), representing the required meeting properties25
and accessed with a dial prefix, is available on all participating MCUs. For example, if the26
meeting uses MCU service 81, then 81 must exist on the master MCU and on the slave MCUs.27
• Participants connecting to the slave MCU:28
- View only the default meeting layout29
- Can send and receive video with a resolution up to 720p (for Scopia® Elite 5000 Series30
MCU)31
- Perform actions (such as joining the meeting) via their endpoint or web interface, and not via32
DTMF.33
• Only one participant at a time (typically the active speaker) connecting from each slave MCU34
can send video and be seen by other meeting participants in the video layout.35
• The lecturer and any telepresence endpoint always connect to the videoconference from the36
master MCU. Connection s are reserved on the master MCU to support these features.37
• Endpoints seamlessly join a videoconference according to the cascading logic implemented on38
the sites. An endpoint connected to a slave MCU and trying to launch a feature which is not39
supported by the slave MCU gets a relevant error message. You can move an endpoint to a40
Planning a Centralized or Distributed Topology (Cascading) for MCU
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 19
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)

master MCU when scheduling your videoconference. For more information, see User Guide for1
Scopia® Management.2
• Scopia® Elite MCU does not support cascading to a Scopia® MCU.3
You can customize the cascading priorities in Scopia® Management in a number of ways:4
• Default to using a local MCU first, and only cascade conferences if required.5
• Prioritize cascading wherever possible, to keep bandwidth costs to an absolute minimum.6
• Avoid cascading as often as possible.7
For more information on implementing cascading in Scopia® Management, see Administrator Guide8
for Avaya Scopia® Management for Aura Collaboration Suite.9
Related links10
Planning your MCU Deployment on page 1411
Planning Network Redundancy or IP Separation (Dual NIC)12
The device has two network cards (NICs) which can be used in one of the following ways:13
• Use the second NIC as a redundant backup of the first, to provide a cost-effective,14
uninterrupted service.15
With network redundancy, the primary NIC is actively responsible for all management, media16
and signaling traffic, while the secondary NIC is a backup. The NICs are paired, so they are17
both connected to the same network switch, and the IP addresses you configure on one NIC18
are automatically mirrored to the other NIC, as described in Installation Guide for Scopia® Elite19
6000 Series MCU.20
When a failure is resolved, the MCU moves traffic back to the primary NIC and the secondary21
NIC returns to its standby state.22
You can increase MCU capacity by adding more devices to your existing deployment (see 23
Deploying Redundant MCUs on page 17).24
• Implement IP separation, to enhance security within the enterprise.25
IP separation configures one NIC to handle management traffic (like administrator web access)26
while the other controls media (video, audio and presentation) and signaling (call setup).27
Connect each network port to a different subnet (Figure 6: IP separation on page 21). For28
more information, see Configuring IP Separation (Dual NIC) on the Device on page 35.29
Planning your MCU Deployment
February 2016 Avaya Scopia® Elite 6000 for Aura Collaboration Suite Administrator Guide 20
Avaya - Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy.
DRAFT—February 11, 2016—1:10 AM (UTC)