Avaya Scopia Elite 6000 6105, 6110, 6120, 6140 MCU Administrator Guide

Avaya Scopia

®

Elite 6000 Series MCU

Administrator Guide

Release 8.3.2

For Solution 8.3.2

Issue 2

February 2016

©

2014-2016, Avaya, Inc.

All Rights Reserved.

Notice

While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.

Documentation disclaimer

“Documentation” means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services.

Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End

User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by

Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages.

Warranty

Avaya provides a limited warranty on Avaya hardware and software.

Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product while under warranty is available to Avaya customers and other parties through the Avaya

Support website: https://support.avaya.com/helpcenter/ getGenericDetails?detailId=C20091120112456651010 under the link

“Warranty & Product Lifecycle” or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and

Canada, the warranty is provided to You by said Avaya Channel

Partner and not by Avaya.

“Hosted Service” means a hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner

(as applicable) and which is described further in Hosted SAS or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in connection with the Hosted Service as described further in your service description documents for the applicable Hosted

Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information.

Hosted Service

THE FOLLOWING APPLIES IF YOU PURCHASE A HOSTED

SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA

CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE

FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA

WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO

UNDER THE LINK “Avaya Terms of Use for Hosted Services” OR

SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE

APPLICABLE TO ANYONE WHO ACCESSES OR USES THE

HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED

SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON

BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE

DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY

AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF

YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A

COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT

YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE

TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR

IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU

MUST NOT ACCESS OR USE THE HOSTED SERVICE OR

AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED

SERVICE. YOUR USE OF THE HOSTED SERVICE SHALL BE

LIMITED BY THE NUMBER AND TYPE OF LICENSES

PURCHASED UNDER YOUR CONTRACT FOR THE HOSTED

SERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTED

SERVICES IF APPLICABLE, YOU MAY HAVE THE OPPORTUNITY

TO USE FLEX LICENSES, WHICH WILL BE INVOICED

ACCORDING TO ACTUAL USAGE ABOVE THE CONTRACT

LICENSE LEVEL. CONTACT AVAYA OR AVAYA’S CHANNEL

PARTNER FOR MORE INFORMATION ABOUT THE LICENSES

FOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITY

OF ANY FLEX LICENSES (IF APPLICABLE), PRICING AND

BILLING INFORMATION, AND OTHER IMPORTANT

INFORMATION REGARDING THE HOSTED SERVICE.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA

WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO ,

UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya

Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY

AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,

USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED

FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA

CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL

AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.

UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,

AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE

WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN

AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA

RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU

AND ANYONE ELSE USING OR SELLING THE SOFTWARE

WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR

USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,

YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM

YOU ARE INSTALLING, DOWNLOADING OR USING THE

SOFTWARE (HEREINAFTER REFERRED TO

INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO

THESE TERMS AND CONDITIONS AND CREATE A BINDING

CONTRACT BETWEEN YOU AND AVAYA INC. OR THE

APPLICABLE AVAYA AFFILIATE (“AVAYA”).

Avaya grants You a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to You. “Software” means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. “Designated Processor” means a single stand-alone computing device. “Server” means a Designated Processor that hosts a software application to be accessed by multiple users.

“Instance” means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine (“VM”) or similar deployment.

License type(s)

Designated System(s) License (DS). End User may install and use each copy or an Instance of the Software only on a number of

Designated Processors up to the number indicated in the order.

Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose.

Concurrent User License (CU). End User may install and use the

Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A “Unit” means the unit on which

Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail

account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server or an Instance of the Software.

Database License (DL). End User may install and use each copy or an Instance of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicates with no more than one Instance of the same database.

CPU License (CP). End User may install and use each copy or

Instance of the Software on a number of Servers up to the number indicated in the order provided that the performance capacity of the

Server(s) does not exceed the performance capacity specified for the

Software. End User may not re-install or operate the Software on

Server(s) with a larger performance capacity without Avaya’s prior consent and payment of an upgrade fee.

Named User License (NU). You may: (i) install and use each copy or

Instance of the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use each copy or Instance of the Software on a Server so long as only authorized Named Users access and use the Software. “Named

User”, means a user or device that has been expressly authorized by

Avaya to access and use the Software. At Avaya’s sole discretion, a

“Named User” may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software.

Shrinkwrap License (SR). You may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as “shrinkwrap” or “clickthrough” license accompanying or applicable to the Software (“Shrinkwrap License”).

Heritage Nortel Software

“Heritage Nortel Software” means the software that was acquired by

Avaya as part of its purchase of the Nortel Enterprise Solutions

Business in December 2009. The Heritage Nortel Software is the software contained within the list of Heritage Nortel Products located at https://support.avaya.com/LicenseInfo under the link “Heritage

Nortel Products” or such successor site as designated by Avaya. For

Heritage Nortel Software, Avaya grants Customer a license to use

Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment.

Charges for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice.

Copyright

Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law.

Virtualization

The following applies if the product is deployed on a virtual machine.

Each product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered.

For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered.

Third Party Components

“Third Party Components” mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements (“Third Party Components”), which contain terms regarding the rights to use certain portions of the Software

(“Third Party Terms”). As required, information regarding distributed

Linux OS source code (for those products that have distributed Linux

OS source code) and identifying the copyright holders of the Third

Party Components and the Third Party Terms that apply is available in the products, Documentation or on Avaya’s website at: https:// support.avaya.com/Copyright or such successor site as designated by Avaya. The open source software license terms provided as Third

Party Terms are consistent with the license rights granted in these

Software License Terms, and may contain additional rights benefiting

You, such as modification and distribution of the open source software. The Third Party Terms shall take precedence over these

Software License Terms, solely with respect to the applicable Third

Party Components to the extent that these Software License Terms impose greater restrictions on You than the applicable Third Party

Terms.

The following applies if the H.264 (AVC) codec is distributed with the product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT

PORTFOLIO LICENSE FOR THE PERSONAL USE OF A

CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE

REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH

THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC

VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A

PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO

PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS

GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.

ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG

LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM

.

Service Provider

THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S

HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT

OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS

SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE

PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY

FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL

PARTNER’S HOSTING OF AVAYA PRODUCTS MUST BE

AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED

PRODUCTS USE OR EMBED CERTAIN THIRD PARTY

SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT

SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS

REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE

LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S

EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY

SUPPLIER.

WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL

PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED

THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE

AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES

THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY

AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729

CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE

WWW.SIPRO.COM/CONTACT.HTML

. THE H.264 (AVC) CODEC IS

LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR

THE PERSONAL USE OF A CONSUMER OR OTHER USES IN

WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)

ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD

(“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS

ENCODED BY A CONSUMER ENGAGED IN A PERSONAL

ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER

LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED

OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL

INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS

MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://

WWW.MPEGLA.COM

.

Compliance with Laws

Customer acknowledges and agrees that it is responsible for complying with any applicable laws and regulations, including, but not limited to laws and regulations related to call recording, data privacy, intellectual property, trade secret, fraud, and music performance rights, in the country or territory where the Avaya product is used.

Preventing Toll Fraud

“Toll Fraud” is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services.

Avaya Toll Fraud intervention

If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center

Toll Fraud Intervention Hotline at +1-800-643-2353 for the United

States and Canada. For additional support telephone numbers, see the Avaya Support website: https://support.avaya.com

or such successor site as designated by Avaya.

Security Vulnerabilities

Information about Avaya’s security support policies can be found in the Security Policies and Support section of https:// support.avaya.com/security .

Suspected Avaya product security vulnerabilities are handled per the

Avaya Product Security Support Flow ( https:// support.avaya.com/css/P8/documents/100161515 ).

Downloading Documentation

For the most current versions of Documentation, see the Avaya

Support website: https://support.avaya.com

, or such successor site as designated by Avaya.

Contact Avaya Support

See the Avaya Support website: https://support.avaya.com

for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: https://support.avaya.com

(or such successor site as designated by Avaya), scroll to the bottom of the page, and select

Contact Avaya Support.

Trademarks

The trademarks, logos and service marks (“Marks”) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such

Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the

Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.

All non-Avaya trademarks are the property of their respective owners.

Linux

®

is the registered trademark of Linus Torvalds in the U.S. and other countries.

Contents

Chapter 1: About the Avaya Scopia

®

Elite MCU.................................................................... 8

About Avaya Scopia

®

Elite MCU

.............................................................................................. 8

Minimum Requirements and Specifications

............................................................................. 12

Document changes since last issue

........................................................................................ 14

Chapter 2: Planning your MCU Deployment........................................................................ 15

Deploying Redundant MCUs

.................................................................................................. 15

Planning a Centralized or Distributed Topology (Cascading) for MCU

........................................ 16

Planning Network Redundancy or IP Separation (Dual NIC)

..................................................... 18

About the Capacity of the MCU

Ports to Open for the Scopia

®

.............................................................................................. 19

Elite 6000 Series MCU

.............................................................. 21

Chapter 3: Securing your Scopia

®

Securing MCU and Scopia

®

Elite MCU...................................................................... 25

Management Connection with TLS

................................................ 25

Securing MCU with TLS in a SIP Environment

................................................................... 26

Uploading TLS Certificates to the MCU

............................................................................. 27

Configuring Security Access Levels for the Scopia

®

Elite MCU

................................................. 32

Configuring IP Separation (Dual NIC) on the Device

................................................................. 33

Chapter 4: Maintaining the Scopia

®

Elite MCU.................................................................... 39

Adding a License to the MCU

................................................................................................. 39

Configuring MCU Meeting Types

............................................................................................ 41

Creating a Meeting Type

.................................................................................................. 41

Configuring the Bandwidth of a Meeting Type

.................................................................... 45

Configuring the Auto-Attendant Service

............................................................................. 48

Managing Scopia

®

Elite MCU User Profiles

............................................................................. 50

Adding a User Profile

....................................................................................................... 51

Changing a User Password

.............................................................................................. 52

Deleting a User Profile

..................................................................................................... 53

Managing the Redundant Power Supply of the Scopia

®

Elite MCU

............................................ 53

Adding a Power Supply Unit to the MCU

........................................................................... 54

Removing a Power Supply Unit from the MCU

................................................................... 56

Configuring Ports on All Models of the Scopia

®

Elite MCU

........................................................ 57

Configuring the UDP Port Ranges for RTP/RTCP on the Scopia

®

Elite MCU

....................... 58

Configuring the TCP Port Range for H.245 on the Scopia

®

Elite MCU

................................. 59

Configuring the HTTP Port on the Scopia

®

Elite MCU

........................................................ 60

Configuring the UDP Port for RAS on the Scopia

®

Elite MCU

Configuring the UDP Port for the Gatekeeper on the Scopia

®

............................................. 61

Elite MCU

............................. 62

Configuring the TCP Port Q.931 on the Scopia

®

Elite MCU

................................................ 62

Configuring the TCP/UDP/TLS Port for SIP on the Scopia

®

Elite MCU

Configuring the TCP Port Range for SIP BFCP on the Scopia

®

................................ 63

Elite MCU

........................... 64

Branding your Scopia

®

Elite MCU User Interface

..................................................................... 65

February 2016 Avaya Scopia

®

Elite 6000 Series MCU Administrator Guide

Comments on this document? [email protected]

6

Contents

Customizing the Logo Displayed in MCU Conferences

....................................................... 65

Customizing MCU Audio Messages

.................................................................................. 68

Upgrading, Backing up and Restoring the Scopia

®

Elite MCU

Backing Up Your Scopia

®

Elite MCU Configuration

................................................... 69

............................................................ 69

Restoring Your Scopia

®

Elite MCU Configuration

............................................................... 70

Upgrading Scopia

®

Elite 6000 Series MCU Software

......................................................... 71

Restoring a Previous Software Version

............................................................................. 73

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

.................................................... 85

Videoconference Ends Unexpectedly

...................................................................................... 85

SIP Call Disconnected Unexpectedly

...................................................................................... 86

Resolving Presentation Issues

................................................................................................ 86

Resolving a Video Display Issue

............................................................................................. 88

Resolving Poor Audio Quality

................................................................................................. 89

Resolving Poor Video Quality

Scopia

®

................................................................................................. 90

Elite MCU cannot connect when Scopia

®

Management can be accessed only through

FQDN

................................................................................................................................... 96

Glossary................................................................................................................................... 97


®



7

Chapter 1: About the Avaya Scopia

®

Elite

MCU

The Scopia

®

Elite MCU 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.

Related links

About Avaya Scopia

®

Elite MCU on page 8

Minimum Requirements and Specifications on page 12

About Avaya Scopia

®

Elite MCU

The Scopia

®

Elite MCU is Scopia videoconferencing.

®

Solution’s flagship platform for high definition multi-party

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 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.

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


®



8

About Avaya Scopia

®

Elite MCU

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 10.


®



9

About the Avaya Scopia

®

Elite MCU

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


®



10

About Avaya Scopia

®

Elite MCU

- 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.

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.


®



11


®

Elite MCU

• 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.

Related links


®

Elite MCU

on page 8

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.

Hardware requirements

Table 1: Physical device specifications on page 12 refers to the physical details of the device.

Table 1: Physical device specifications

Scopia

®

Elite MCU 6105, 6110 and 6120

Scopia

®

Elite MCU 6140

System power requirements

Input 100-240 VAC, 50/60 Hz

AC Input

Maximum power consumption at

35°C

600W output @ 100-240V, 7.5A,

50-60Hz

200W, 250VA (682 BTU/h)

100-240 VAC, 50/60 Hz with hotswap redundant AC power supply and feed (optional)

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

360W, 450VA (1228 BTU/h)

Table continues…


®



12

Minimum Requirements and Specifications

Scopia

®

Elite MCU 6105, 6110 and 6120

Scopia

®

Elite MCU 6140

Environmental requirements

Operating temperature

Relative humidity

Storage and transit temperature

Acoustics

Physical requirements

Dimensions

10°C to 35°C (50°F to 95°F)

5% to 90% non-condensing

-40°C to 70°C (-40°F to 158°F), ambient

Low noise fan speed control

Approximate net weight

Approximate gross weight (with packaging)

Rack mounting

Width: 437mm (17.2"); height:

43mm (1.7"); depth 664mm (26.1")

11kg (24.25lbs)

21kg (46.3lbs)

Width: 437mm (17.2"); height:

43mm (1.7"); depth: 790mm

(31.1")

14.5kg (32lbs) with one power supply

23kg (50.7lbs)

19-inch rack-mountable with flanges

Software Specifications

The technical specifications of the protocols and software requirements apply to all Scopia

®

Elite

6000 Series MCU models:

• 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

- Google Chrome

- Apple Safari


®



13


®

Elite MCU

• 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.

Related links


®

Elite MCU

on page 8

Document changes since last issue

The following changes have been made to this document since the last issue:

• Updated the URL of the licensing portal and made minor changes to the procedure steps in the topic about adding licenses to the MCU.


®



14

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:

Related links

Deploying Redundant MCUs

on page 15

Planning a Centralized or Distributed Topology (Cascading) for MCU on page 16

Planning Network Redundancy or IP Separation (Dual NIC) on page 18


on page 19


®

Elite 6000 Series MCU on page 21

Deploying Redundant MCUs

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 .

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 18.

Related links

Planning your MCU Deployment on page 15


®



15

Planning your MCU Deployment

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

MCU, 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 2: Centralized MCU deployment, where all branches use the HQ MCU on page 16).

Figure 2: Centralized MCU deployment, where all branches use the HQ MCU

To reduce cross-site bandwidth costs, a distributed MCU deployment (

Figure 3: Distributed MCU deployment cascading meetings for reduced WAN bandwidth on page 17) 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 principles apply to an MCU in the same location, thus increasing call capacity by cascading conferences between them.


®



16

Planning a Centralized or Distributed Topology (Cascading) for MCU

Figure 3: 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


on page 45.

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 500 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 .


®



17


Cascading has the following characteristics:

• A cascaded connection uses two port s—one port on the master MCU, and one port 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. Port s are reserved on the master MCU to support these features.

• Endpoints seamlessly join a videoconference 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 MCU 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 .

Related links


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.


®



18


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 Series MCU.

When a failure is resolved, the MCU moves traffic back to the primary NIC and the secondary

NIC returns to its standby state.

You can increase MCU capacity by adding more devices to your existing deployment (see

Deploying Redundant MCUs on page 15).

• 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 4: IP separation

on page 19). For more information, see

Configuring IP Separation (Dual NIC) on the Device on page 33.

Figure 4: IP separation

Related links


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.


®



19


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.

Figure 5: A connection uses its proportion of resources on the MCU

Important:

To enable connections at 720p at 30fps to use half the capacity of a 1080p 30fps connection, install the Double Capacity license. For more information, see

Adding a License to the MCU on

page 39.

The following table details the number of simultaneous connections available for each of the devices when all the connections have the same video resolution and frame rate.

Table 2: Number of simultaneous connections available at different video quality settings

Scopia

®

Elite 6000

Series MCU Model

Scopia

Scopia

®

Scopia

Scopia

®

®

®

Elite MCU 6105

Elite MCU 6110

Elite MCU 6120

Elite MCU 6140

1080p at 60fps

3

5

10

20

1080p at 30fps,

720p at 60fps,

720p at 30fps (no double capacity license)

5

10

20

40

720p at 30fps

(with double capacity license)

10

20

40

80

480p at 30fps

20

40

80

160

Important:

You can increase the device's capacity at any resolution (including 1080p at 60fps) to the same capacities listed under 480p by enabling Switched Video in the meeting type (or service).

Switching is the process of redirecting video as-is without transcoding, so you see only one


®



20


®

Elite 6000 Series MCU endpoint's image at a time, usually the active speaker, without any video layouts or continuous

presence (CP). For more information on enabling switching, see Creating a Meeting Type

on page 41.

However, if you encrypt the media and enable switching in the same MCU service, the resolution may be dynamically lowered slightly in some cases, but overall MCU capacity remains constant.

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 41. Alternatively, you can limit the bandwidth using the global bandwidth

policies in Scopia

®

Management.

Related links


Ports to Open for the Scopia

®


The Scopia

®

Elite 6000 Series MCU is typically located in the enterprise network and is connected to the DMZ. When opening ports on the Scopia

®

Elite MCU, use the following as a reference:

• If you are opening ports that are both in and out of the Scopia

®

Elite 6000 Series MCU, see

Table 3: Bidirectional Ports to Open on the Scopia

®


on page 21.

• If you are opening ports inbound to the Scopia

®

Elite 6000 Series MCU, see Table 5: Inbound

Ports to Open to the Scopia

®


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 3: Bidirectional Ports to Open on the Scopia

®


Port Range

1024-1324

1719

Protoc ol

H.245

(TCP)

RAS

(UDP)

Destination

Any H.323

device

H.323

gatekeeper

Functionality

Enables H.245

signaling

Enables RAS signaling

Result of Blocking

Port

Cannot connect H.

323 calls

Cannot communicate with H.

323 gatekeeper

Required

Mandatory

To configure, see

Configuring the TCP Port

Range for H.245 on the

Scopia

®

Elite MCU on

page 59

Mandatory



®



21


Port Range

1720

3336

3337

3338

3400-3580

5060

Protoc ol

Q.931

(TCP)

XML

(TCP)

XML

(TCP)

XML

(TCP)

SIP

BFCP

(TCP)

SIP

(TCP/

UDP)

Destination Functionality Result of Blocking

Port

Required

Any H.323

device

Enables Q.931

signaling

Cannot connect H.

323 calls

To configure, see


®

Elite MCU on page 61

and Configuring the UDP

Port for the Gatekeeper on the Scopia

®

Elite

MCU

on page 62

Mandatory

To configure, see


Q.931 on the Scopia

®


Mandatory if deployed with Scopia

®

Management

Conference

Control web client endpoint,

Scopia

®

Managemen t, or thirdparty controlling applications

Enables you to manage the MCU via the XML API

Other MCUs Enables use of

MCU Cascading

XML API

Scopia

®

Managemen t, or thirdparty configuration applications

Enables you to configure the

MCU via the XML

API

Any SIP video network device

Enables SIP content sharing

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


Enables SIP signaling

Mandatory if multiple

MCUs are deployed with

Scopia

®

Management

Mandatory if deployed with Scopia

®

Management

Cannot connect SIP calls

Mandatory if using content sharing with SIP over TCP

To configure, see


Range for SIP BFCP on the Scopia

®

Elite

MCU

on page 64

Mandatory if using SIP over TCP/ UDP

To configure, see

Configuring the



®



22


®


Port Range

5061

12000-13200

16384-16984

Protoc ol

SIP

(TLS)

RTP/

RTCP/

SRTP

(UDP)

Destination


Any H.323

or SIP mediaenabled video network device

Functionality Result of Blocking

Port

Required

Enables secure

SIP signaling

Enables real-time delivery of video and audio media

Cannot connect SIP calls over TLS

Cannot transmit/ receive video media streams

TCP/UDP/TLS Port for

SIP on the Scopia

®

Elite

MCU

on page 63

Mandatory if using SIP over TLS

To configure, see

Configuring the

TCP/UDP/TLS Port for

SIP on the Scopia

®

Elite

MCU

on page 63

Mandatory

To configure, see

Configuring the UDP Port

Ranges for RTP/RTCP on the Scopia

®

Elite

MCU

on page 58

Table 4: Outbound ports to open from Scopia

®


Port range

162

53

Protocol Destination

SNMP (UDP) Scopia

®

Management or any SNMP manager station

DNS (TCP/UDP) DNS server

Function

Enables sending

SNMP trap events

Result of blocking port

Cannot send

SNMP traps

Enable querying

DNS for FQDN

DNS is disabled

Required

Recommended

Mandatory

Table 5: Inbound Ports to Open to the Scopia

®


Port

Range

21

Protocol Destination

FTP Server

22

80

FTP

(TCP)

SSH

(TCP)

HTTP

(TCP)

SSH Client

Web client

Functionality

Enables audio stream recording

Enables you to view logs

Provides access to the

MCU Administrator and

Conference Control web


Port

Cannot record audio streams

Cannot view logs in real-time (logs are collected on the compact flash card)

Cannot configure

MCU

Required

Optional

Optional

Mandatory if using

HTTP



®



23


Port

Range

Protocol Destination Functionality

user interfaces; used for software upgrade


Port

Required

To configure, see

Configuring the

HTTP Port on the

Scopia

®

Elite

MCU

on page 60

Mandatory if using

HTTPS

443 HTTPS

(HTTP over

SSL)

Web client Provides secure access to the MCU

Administrator and

Conference Control web user interfaces; used for software upgrade

Cannot configure

MCU

Related links



®



24

Chapter 3: Securing your Scopia

®

Elite

MCU

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.

Related links


®


on page 25

Configuring Security Access Levels for the Scopia

®


Configuring IP Separation (Dual NIC) on the Device on page 33

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:


Related links

Securing your Scopia

®


Securing MCU with TLS in a SIP Environment on page 26


®



25


®

Elite MCU


on page 27

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


on page 27).

Important:


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.

7. Restart the MCU.

Figure 6: Enabling the SIP Protocol on the MCU


®



26


®


Related links


®


on page 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:


Procedure

1. Log in to the MCU.

2. Select Configuration.

3. Select Manage in the Security section.

Figure 7: Security section

4. Select Create a new certificate request.


®



27


®

Elite MCU

Figure 8: 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: [email protected]

• Common name: video.mycompany.com(unique for each MCU)

Figure 9: Organization details

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.


®



28


®


Figure 10: 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 11: 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.


®



29


®

Elite MCU

Figure 12: Certificate status

14. Select Next.

15. Open the signed certificate, and copy-paste the content of the signed certificate.

Figure 13: 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.


®



30


®


Figure 14: Successful certificate upload

18. (Optional) Select Details to view the certificate details like the serial number or the expiry date.

Figure 15: Viewing the certificate details

19. Upload the CA root certificate by selecting Upload from the Security section.

20. Select Browse to select the CA root certificate.


®



31


®

Elite MCU

Figure 16: Browsing for the CA Root Certificate

21. Select OK.

22. Copy the certificates to the B2BUA’s CA directory (for example: mcu_ca.cert and

ca_root.cert).

Related links


®


on page 25

Configuring Security Access Levels for the Scopia

®

Elite

MCU

About this task

The Scopia

®

Elite MCU offers configurable security access levels that enable and disable SSH,

FTP, and ICMP (ping) protocols.

By default, the security access level is set to High. It is recommended to set your security access level to Maximum (which disables these protocols), except for the following situations:

• If you are performing either debugging or troubleshooting operations, SSH should be enabled.

• If you are customizing your language settings, FTP should be enabled.

• If you would like control or error response messages to be sent, ICMP (ping) should be enabled.

Important:


Procedure

1. Access the MCU security settings by selecting Configuration > Setup.

2. Locate the Security section.


®



32


3. Select the access level from the Security Mode list (see Figure 17: Security Access Level

Settings on page 33). Table 6: MCU Security Access Levels

on page 33 lists the protocol status when each security access level is applied.

Figure 17: Security Access Level Settings

Table 6: MCU Security Access Levels

FTP Security Access

Level

Standard

High

Maximum

SSH

Enabled

Disabled

Disabled

4. Select Apply.

Related links


®


Enabled

Disabled

Disabled

ICMP (ping)

Enabled

Enabled

Disabled

Configuring IP Separation (Dual NIC) on the Device

About this task

You can configure IP separation on each network port (dual-NIC), improving security by placing the

management data on a separate subnet from the media and signaling traffic ( Figure 18: IP

Separation on page 34).


®



33


®

Elite MCU

Figure 18: IP Separation

Separating these types of data on different subnets improves security because management data typically remains on subnets within the enterprise, while the media of video calls is often required to traverse firewalls and reach endpoints outside the enterprise.

Management refers to the administration messages sent between components of the Scopia

®

Solution as they manage and synchronize data between them. Management also includes front-end browser interfaces configuring server settings on the server. Management messages are usually transmitted via protocols like HTTP, SNMP, FTP or XML. For example, Scopia

®

Management uses management messages to monitor the activities of an MCU, or when it authorizes the MCU to allow a call to proceed.

Media refers to the live audio, video and shared data streams sent during a call. Presentation and

Far end camera control (FECC) are examples of information carried on the data stream. Media is transmitted via the RTP and RTCP protocols in both SIP and H.323 calls. The parallel data stream of both live video and presentation, is known as dual video.

Signaling, also known as call control, sets up, manages and ends a connection or call. These messages include the authorization to make the call, checking bandwidth, resolving endpoint addresses, and routing the call through different servers. Signaling is transmitted via the H.225.0/Q.

931 and H.225.0/RAS protocols in H.323 calls, or by the SIP headers in SIP calls. Signaling occurs before the control aspect of call setup.

Before you begin

• You must choose how you want to deploy the two network ports of this device: network redundancy or IP separation. For more information on this decision, see

Planning Network

Redundancy or IP Separation (Dual NIC) on page 18.

By default, the NICs are paired as a primary NIC and a redundant NIC. To separate them into media and management (IP separation) first define the IP address of both NICs as detailed in

Installation Guide for Scopia

®

Elite 6000 Series MCU, and then perform the IP separation.

• Make sure you have the management interface IPv4 addresses ready for use: Management IP

Address, Management Router, Management Subnet Mask.

• Make sure you have the IPv4 addresses of the media and signaling interface ready for use:

Media/Signaling IP Address, Media/Signaling Router, Media/Signaling Subnet Mask.


®



34


• If you need management access from another branch with its own network, make sure you have the IPv4 address of that branch ready for configuration.

• Make sure no videoconferences are running on the MCU, as you need to restart it at the end of the procedure.

Procedure

1. If you previously had the MCU in a redundant dual-NIC setup and now you want to use to use dual NIC for IP separation, disconnect the network cables from the network switch.

2. Connect the network cable of the management subnet to the left ethernet port (NIC1). See

Figure 19: The device's management connections

on page 35.

Figure 19: The device's management connections

Important:

Do not connect the network cable of the media subnet until you restart the device at the end of this procedure.

3. Access the device's administrator web interface using the management IP you configured via the serial cable (Installation Guide for Scopia

®

Elite 6000 Series MCU).

4. Select the Configuration

tab.

5. Select the IP Separation check box to expand that section of the page

Figure 20:

Configuring IP separation with two network connections

on page 36).


®



35


®

Elite MCU

Figure 20: Configuring IP separation with two network connections

6. Configure the IP addresses of each interface ( Table 7: Configuring the IP addresses of each network interface

on page 36).

Table 7: Configuring the IP addresses of each network interface

Field

Management IP address

Management router

Management subnet mask

Media/Signaling IP address

Media/Signaling router

Media/Signaling subnet mask

Description

IP address of the MCU management interface

(left ethernet port) as configured via serial port.

This is the IP used to access this web interface.

IP address of the management subnet router

IP address of the management subnet mask

IP address of the MCU media and signaling interface (right ethernet port belonging to a different subnet)

IP address of the media and signaling subnet router

IP address of the media and signaling subnet mask

7. Select Apply at the bottom of the page.

8. Select Yes to restart the MCU.

9. Connect the network cable of the media subnet cable to the right ethernet port (NIC2). See

Figure 21: The device's media and signaling connections on page 37.


®



36


Figure 21: The device's media and signaling connections

10. (Optional) Depending on your deployment, you may need to access the MCU management interface from another network.

For example, if your MCU is located on network 123.x.x.x and your browser is on the same network (123.x.x.x), you can access the administrator web interface to reach this web page.

You can then configure IP separation of management and media as detailed in this procedure, where management communications stay in this network (123.x.x.x) while media

is routed to a different network: 456.x.x.x (see Figure 22: Example of additional management network on page 37). However, if you need management access from another branch with

its own network, for example 789.x.x.x, you can configure the 789.x.x.x management traffic to be routed via 123.x.x.x, and then onwards to 789.x.x.x (

Figure 22: Example of additional management network

on page 37).

February 2016

Figure 22: Example of additional management network

Avaya Scopia

®



37


®

Elite MCU

Use the following steps to configure an additional management network:

a. Select More at the bottom of the expanded section ( Figure 20: Configuring IP separation with two network connections on page 36).

The Additional Management Networks section opens.

b. Select Add Management Network.

c. Configure the access to the MCU management subnet (

Figure 23: Adding a new network for management access on page 38 and Table 8: Configuring the additional network interfaces

on page 38).

Figure 23: Adding a new network for management access

Table 8: Configuring the additional network interfaces

Field

IP address

Subnet mask

Description

IP address of the additional network to access the management of the MCU

IP address of the additional management subnet mask d. Select OK.

Related links


®



®



38

Chapter 4: Maintaining the Scopia

®

Elite

MCU

Maintaining the MCU includes tasks like ensuring secure communications, maintaining the hardware chassis performance, user profiles, backup and restore, license management, and standard configurations of the device.

This section includes the following maintenance procedures:

Related links

Adding a License to the MCU on page 39


on page 41

Managing Scopia

®

Elite MCU User Profiles on page 50


®



®



®

Elite MCU User Interface on page 65


®



on page 75

Adding a License to the MCU

About this task

The MCU has several pre-installed licenses. You can purchase more licenses, such as the option to increase the port capacity when you set the video quality to 720p with 30 frames per second (see


on page 19).


Get the LAC (License Authentication Code) file from the Avaya customer email.

Procedure

1. Log in to the MCU administrator web interface.

2. Note the serial number and MAC address of the device in the Product Information window on the main screen.


®



39

Maintaining the Scopia

®

Elite MCU

Figure 24: Locating the serial number of the MCU

3. Go to the licensing portal at https://plds.avaya.com

.

4. Enter the license authentication code and other details of the device, such as the MAC address.

5. Generate the new license key.

Using the license key, you can activate the features that are eligible for your license.

6. Return to the main MCU screen.

7. Click Maintenance

> Licensing and Registration.

The web interface displays the Licensing and Registration window.

Figure 25: Licensing and Registration window

8. Enter the new license key in the Update license key field.

9. Click Update.

10. Activate the features that are eligible for the license.


®



40


For information on the double capacity license, see


on page 19.

Related links


®


Configuring MCU Meeting Types

This section describes how to configure MCU meeting types.

Meeting types (also known as MCU services) are meeting templates which determine the core characteristics of a meeting. For example, they determine if the meeting is audio only or audio and video, they determine the default video layout, the type of encryption, PIN protection and many other features. You can invoke a meeting type by dialing its prefix in front of the meeting ID. Meeting types are created and stored in the MCU, with additional properties in Scopia

®

Management.

After configuring your MCU meeting types, you download them to Scopia

®

Management, which can use Scopia

®

Management them to reserve MCU resources, schedule MCU conferences, and control in-session MCU meetings. If you modify these meeting types later on the MCU, you need to resync with Scopia

®

Management.

Related links


®


Creating a Meeting Type on page 41


on page 45

Configuring the Auto-Attendant Service

on page 48

Creating a Meeting Type

About this task

Meeting types (also known as MCU services) are meeting templates which determine the core characteristics of a meeting.

In organizations deploying multiple MCUs, Scopia

®

Management enables you to define meeting types in one MCU, and then sync this device with the other MCUs in your deployment. For more information, see Administrator Guide for Scopia

®

Management.

To define a meeting type, choose a unique dial prefix in the organization which would invoke this type of meeting, give it a descriptive name, and then define its parameters.

Procedure

1. Access the MCU administrator web interface.

2. Select Configuration > Conferences, then select Add new service (

Figure 26: Defining a new meeting type

on page 42).


®



41


®

Elite MCU

Figure 26: Defining a new meeting type

3. Enter a unique dial prefix to invoke this meeting type ( Figure 27: Defining basic properties of a meeting type

on page 42). You can also modify the current dial prefix from this field.

This prefix precedes the meeting ID when dialing the videoconferencing number. For example if the meeting ID is 9495, and the new service dial prefix is 88, the meeting ID to give participants is 889495.

Figure 27: Defining basic properties of a meeting type

4. Enter a description of the new meeting type.

5. Configure the MCU for bandwidth savings in the Max call rate (Kbps) field. For more information, see

Configuring the Bandwidth of a Meeting Type on page 45.

6. Select More to define more parameters of this meeting type ( Table 9: Detailed properties of a meeting type on page 43).


®



42


Figure 28: Defining detailed properties of a meeting type

Table 9: Detailed properties of a meeting type

Field Name

Default layout

Description

Determines the default video layout of this meeting type. Choose from the following values:

• Dynamically adjusted changes the video layout automatically based on the number of participants in the videoconference.

Choose from Max displayed streams to optionally limit the maximum number of participants simultaneously visible in the same layout. The default value is the device's maximum.



®



43


®

Elite MCU

Field Name

Enable personal layout

Display participant names

Video quality preference

Enable presentation view

Encryption

Description

• Static enables you to fix the default video layout of this meeting type.

Enables moderators to personalize any participant's video layout to be different from others in the same videoconference.

For more information on this functionality , see User Guide for

Scopia

®

Management.

Determines whether the video layout also displays the name under each participant by default. Choose from the following values:

• Constantly always displays the name for the duration of the meeting.

• On location changes for displays the name only for the first few seconds and refreshes whenever the location of the image in the video layout changes.

The videoconference moderator can change this setting in the Inmeeting Control interface of Scopia

®

Management as explained in

User Guide for Scopia

®

Management.

Determines whether the MCU processor power is dedicated to image sharpness or speedy rendering of moving images.

Determines whether this type of meeting can include presentations (data content) alongside the other streams. Choose the protocol which is supported by all endpoints participating in the videoconference:

• Auto automatically selects the data sharing protocol supported by all endpoints in the videoconference.

• H.264 forces data sharing to take place over H.264, supported by newer endpoints for better compression and higher resolutions.

• H.263 forces data sharing to take place over H.263 for legacy endpoints which do not support H.264.

Specifies whether the meeting is encrypted, and the type of encryption used. Choose from:

• Best effort indicates the system will attempt to encrypt the meeting transmissions, provided the encryption is supported by the endpoint. If an endpoint does not support encrypted media, tranmissions to that endpoint are sent unencrypted.

• Strong encryption (AES-128) required indicates the system demands AES-128 strong encryption. Endpoints not supporting this standard would not be able to connect to meetings of this type.



®



44


Field Name

Auto mute joining participants

Auto mute first joining participant

Automatically reconnect dropped participants

Force conference PIN protection

Ask for conference PIN on invite

Description

Important:


Automatically mutes the sound of joining participants. This is helpful in eliminating background noise, like clicking keyboards and other distractions from an endpoint.

When enabled, all conference participants are muted when joining the conference, except for the first participant.

The system automatically tries to reestablish a link if the connection to one of the endpoints has been dropped.

Determines whether meetings of this type always require participants to enter a PIN before gaining access to the meeting.

Moderators setting up a meeting of this type are required to enter the meeting PIN to allow them to send invitations.


Related links


on page 41

Configuring the Bandwidth of a Meeting Type

About this task

This topic describes how to configure the maximum bandwidth (bitrate) used in a connection with the MCU videoconference. The bitrate is the speed of data flow and is one of the meeting type properties which determine the characteristics of a videoconference. See

Creating a Meeting

Type on page 41.

Consider these factors when selecting a bandwidth:

• The MCU capacity is measured by the number of simultaneous connections to a videoconference (


on page 19). A low bandwidth means you need fewer MCU resources to manage the connections to your videconference. A higher bandwidth would require extra resources to accommodate the connections, which depends on the number and capacity of your MCUs.


®



45


®

Elite MCU

Figure 29: MCU Bandwidth considerations

• The purpose of your videoconference

Corporate policy determines when a meeting should use more or less bandwidth.

• The video resolution you want to experience in your videoconference.

Higher video resolutions require higher bitrates to ensure the video is constantly updated, thereby maintaining smooth motion. If you lower the bitrate, you lower the quality of the video.

In some cases, you can select a lower bitrate without noticing a significant drop in video quality; for example during a presentation or when a lecturer is speaking and there is very little motion.

By default, all videoconferences display video in HD continuous presence which enables viewing multiple participants of a videoconference at the same time, including the active speaker.

The MCU provides the following tools for conserving bandwith in a videoconference connection:

• Defining a meeting type (service) with lower bandwidth, which will impact on resolution as

described in Table 10: Bandwidth versus video resolution

on page 46.

Table 10: Bandwidth versus video resolution

Video Resolution

240p at 30fps

352p at 30fps

480p at 30fps

720p at 30fps

720p at 60fps

Bandwidth (Bitrate) with H.264

Baseline Profile

128K

384K

512K

768K

1.5M


High Profile

128K

256K

384K

512K

900K



®



46



1080p at 30fps

1080p at 60fps


Baseline Profile

1.8M

2.5M


High Profile

1.2M

2M

The Scopia

®

Elite 6000 Series MCU supports H.264 High Profile, which is a standard for compressing video by up to 25% over the H.264 Baseline Profile. H.264 High Profile enables high definition calls to be held over lower call speeds. It requires both sides of the transmission

(sending and receiving endpoints) to support this protocol.

• Using an audio-only meeting type (service) where showing participants is not important.

• Using the switched video meeting type (service). Switching is the process of redirecting video as-is without transcoding, so you see only one endpoint's image at a time, usually the active speaker, without any video layouts or continuous presence (CP).

Follow this procedure to define bandwidth limits per meeting type.

Procedure


2.

Select Configuration > Conferences > Services List and select next to the relevant meeting type.

Figure 30: Service List section of the Conferences tab

3. Select the required value from the list under Max call rate (Kbps) while referring to

Table

10: Bandwidth versus video resolution on page 46, which lists the maximum bandwidth

allowed in this meeting type.

Important:

H.264 HP is enabled by default, and activated when the all endpoints support this protocol.


®



47


®

Elite MCU

Figure 31: Service Settings section

4. Select Audio only to conserve bandwidth for this meeting type by making the service audioonly.

5. Select Switched video to conserve bandwidth for this service by viewing only one participant at a time.

Use switched video only when all endpoints participating in the videoconference support the same resolution. If a network experiences high packet loss, switched video might not be displayed properly for all endpoints in the videoconference.

If you do not know the resolution supported by some endpoints, we recommend setting the bitrate to 512K.


Related links


on page 41

Configuring the Auto-Attendant Service

About this task

The Auto-Attendant service provides quick access to meetings hosted on Scopia

®

Elite MCUs.

Participants can dial a preconfigured Auto-Attendant number to access a visual menu and select meeting options using DTMF. The visual menu is also read aloud, enabling both audio and video endpoints to access these options.


®



48


Figure 32: The visual menu

To enable the Auto-Attendant, you first configure a default meeting type on the MCU, and then configure the Auto-Attendant settings in Scopia

®

Management.

This section only describes how to define a meeting type. For more information on developing this meeting type into the Auto-Attendant service, see Administrator Guide for Avaya Scopia

®

Management.

Procedure


2. Select Configuration > Conferences > Services List > Add new service to add a new meeting type with default settings.

This meeting type becomes the Auto-Attendant template later on in Scopia

®

Management.

Figure 33: Adding the Auto-Attendant Service

3. Choose a prefix which you can access in Scopia

®

Management to specify Auto-Attendant settings. This is not the prefix to be used for accessing the Auto-Attendant. This is purely for naming purposes. The dial number to access the Auto-Attendant is defined in Scopia

®

Management. Add a description to the meeting type (or service).


®



49


®

Elite MCU

Figure 34: Configuring the Auto-Attendant

4. Select Apply. The default settings are sufficient for this template of the Auto-Attendant. The remaining settings are defined in Scopia

®

Management.

5. Configure the Auto-Attendant settings in Scopia

®

Guide for Avaya Scopia

®

Management as described in Administrator

Management. This includes configuring the Auto-Attendant number that participants dial to join a meeting.

6. View the Auto-Attendant service in the MCU Services List.

Figure 35: Viewing the configured Auto-Attendant service

Related links


on page 41

Managing Scopia

®

Elite MCU User Profiles

The MCU has two types of users:

• Administrators (up to 10 users)

• Operators (up to 50 users).

As an administrator, you have the following privileges:

• Full access to the MCU administrator interface.


®



50

Managing Scopia

®

Elite MCU User Profiles

• SSH access to the MCU.

• Manage user profiles.

As an operator, your privileges are limited to viewing MCU settings.

Related links


®


Adding a User Profile on page 51

Changing a User Password on page 52

Deleting a User Profile

on page 53

Adding a User Profile

About this task

MCU administrators can create a new user on the MCU.

You can create up to 10 administrator profiles and up to 50 operator profiles.

Procedure


2. Select Users

.

3. Select Add new user.

Figure 36: Authorized Users List

February 2016

Figure 37: Adding a user profile

Avaya Scopia

®



51


®

Elite MCU

4. Choose Administrator or Operator as the type of user.

5. Enter the new username.

6. Enter a password and its confirmation.


Related links

Managing Scopia

®


Changing a User Password

About this task

Only administrators can change a password.

The MCU comes with two preconfigured users: an administrator and an operator. The password for both preconfigured users is password. We highly recommend that you change the default user password for security.

You can change a user password at any time.

Procedure


2. Select Users

.

3.

Select the Review button for the user profile you want to modify.

4. Enter the new password in the Password and the Confirm Password fields.

Figure 38: Changing a user password


Related links

Managing Scopia

®



®



52


®

Elite MCU

Deleting a User Profile

About this task

Only administrators can delete user profiles.

You can delete user profiles at any time.

Procedure


2. Select Users

.

3.

Select the Review button for the user profile you want to remove.

Figure 39: User Profile Section

4. Select Delete.

5. Select Yes in the message that appears.

The user profile is removed from the authorized users list.

Related links

Managing Scopia

®


Managing the Redundant Power Supply of the Scopia

®

Elite MCU

You can add a power supply unit (PSU) to backup the factory delivered power supply of the MCU.

If one of the PSUs fails, the remaining PSU takes the full load of the system to enable continued operation without interruption. PSUs can be hot-swapped, enabling you to replace the power unit without powering down the device.

Important:

This applies to the 6140 model only. For details of replacing a PSU of the Scopia

®

Elite 5200

Series MCU, see the Administrator Guide of Scopia

®

Elite 5200 Series MCU version 7.7.


®



53


®

Elite MCU

Related links


®



on page 54

Removing a Power Supply Unit from the MCU on page 56

Adding a Power Supply Unit to the MCU

About this task

This section details how to set up an additional power supply unit (PSU) of the Scopia

®

Elite MCU, which can house two PSUs.

Important:


®

Elite 5200


®



You can add the PSU when the MCU is functioning. However, Avaya strongly recommends to turn off the MCU when you perform the procedure for the first time.

To remove an existing PSU from the device, see

Removing a Power Supply Unit from the MCU

on page 56.


Verify you have the following equipment:

• The standalone PSU that you can order from your local Avaya representative using these references:

- Scopia

®

Elite MCU Redundant Power Supply

- Part number 55547-00018

• An antistatic wrist strap

Procedure

1. Disconnect the power cord.

2. Remove the cover of the PSU slot if it is there.

The MCU is shipped with only one PSU fitted, while the second slot is covered by a metal grid. Remove the grid by unscrewing the two screws, one above and one below the device.


®



54


®

Elite MCU

Figure 40: Removing the cover of the second PSU slot in Scopia

®

Elite MCU

3. Insert the new PSU into position and secure it by pressing it firmly into place until the release tab clicks.

February 2016

Figure 41: Adding a PSU in Scopia

®

Elite MCU

Avaya Scopia

®



55


®

Elite MCU

4. Reconnect the two power cords.

Related links


®


Removing a Power Supply Unit from the MCU

About this task

This section details how to remove one of the power supply units (PSUs) from the Scopia

®

Elite

MCU, which can house two PSUs.

Important:


®

Elite 5200


®



To add a new PSU, see


on page 54.


Make sure you wear an antistatic wrist strap.

Procedure

1. Disconnect the AC power cord of that PSU.

Important:

If a second PSU is actively powering the MCU, this PSU can be removed without powering down the device. However, if the only active PSU is the one you need to replace, first power down the device, then remove the power cord.

2. Push the release tab sideways towards the handle of the PSU to eject the unit from the device.

Figure 42: Ejecting the PSU with the release tab

3. Use the PSU handle to remove it from the device.


®



56


®

Elite MCU

Figure 43: Removing a PSU from the device

Related links


®


Configuring Ports on All Models of the Scopia

®

Elite MCU

This section provides instructions of how to configure the following ports and port ranges on all models of the Scopia

®

Elite MCU:

Related links


®


Configuring the UDP Port Ranges for RTP/RTCP on the Scopia

®

Elite MCU

on page 58

Configuring the TCP Port Range for H.245 on the Scopia

®

Elite MCU

on page 59

Configuring the HTTP Port on the Scopia

®



®


Configuring the UDP Port for the Gatekeeper on the Scopia

®


Configuring the TCP Port Q.931 on the Scopia

®

Elite MCU

on page 62

Configuring the TCP/UDP/TLS Port for SIP on the Scopia

®

Elite MCU

on page 63

Configuring the TCP Port Range for SIP BFCP on the Scopia

®



®



57


®

Elite MCU

Configuring the UDP Port Ranges for RTP/RTCP on the Scopia

®

Elite MCU

About this task

The Scopia

®

Elite 6000 Series MCU has designated UDP ports 12000-13200 (for video) and

16384-16984 (for audio) for RTP/RTCP.

While the number of ports required for this protocol remain fixed, you can determine the exact port numbers occupied by the MCU by defining the lower end of the port range, known as the base port.

The Scopia

®

Elite 6000 Series MCU uses 360 ports for audio and 1080 ports for video.

Important:

You cannot reduce the number of UDP ports occupied by the MCU for RTP/RTCP.

Procedure

1. Navigate to the MCU Advanced Commands section by doing the following: a.

Select the icon.

b. Select Advanced parameters.

c. Locate Video Base Port or the Audio Base Port entry in the Name column to change the video or audio port values respectively (

Figure 44: Defining the base port for video on page 58).

Figure 44: Defining the base port for video

2. Select the icon in the Review column.

3. Enter the new lower end port value in the field.


5. Select Close.

Related links


®



®



58


®

Elite MCU

Configuring the TCP Port Range for H.245 on the Scopia

®

Elite

MCU

About this task

The Scopia

®

Elite 6000 Series MCU has designated TCP ports 1024-1324 for H.245. You can set the base port, which is the lower end of the port range. H.245 is a Control Protocol used for multimedia communication that enables transferring information about the device capabilities, as well as opening/closing the logical channels that carry media streams.

The Scopia

®

Elite 6000 Series MCU uses 300 ports.

Procedure


Select the icon.


c. Locate the CLI section and select More (

Figure 45: CLI Section on page 59).

Figure 45: CLI Section

2. Enter the h245baseport command in the Command field.

Important:

To see the current port value, select Execute.

3. Modify the port value in the Value field.

4. Select Execute.


Related links


®



®



59


®

Elite MCU

Configuring the HTTP Port on the Scopia

®

Elite MCU

About this task

The Scopia

®

Elite 6000 Series MCU has designated port 80 for HTTP. You can configure a different port to use HTTP if necessary in your environment.

Procedure


Select the icon.


c. Locate the CLI section and select More (

Figure 46: CLI Section on page 60).

Figure 46: CLI Section

2. Enter the webserverport command in the Command field.

Important:

To see the current port value, select Execute.

3. Enter the port value in the Value field.


Important:

After selecting Execute, a warning message appears, notifying you that the unit will be reset and any active conferences will be disconnected.

5. Select Yes to continue.


Important:

After applying the new port value, you must enter it as a suffix to the MCU IP address in order to access the web server.


®



60


®

Elite MCU

For example, if your new HTTP port value is 8080, access the web server by entering

http://<URL>:8080

Related links


®


Configuring the UDP Port for RAS on the Scopia

®

Elite MCU

About this task

The Scopia

®

Elite 6000 Series MCU has designated port 1719 for RAS. You can configure a different port to use RAS (for example, if port 1719 is busy). Port 1719 is also used to communicate

with the gatekeeper (to configure the UDP port for the gatekeeper, see Configuring the UDP Port for the Gatekeeper on the Scopia

®

Elite MCU

on page 62).

Important:

If you close port 1719, you must configure another port for both RAS and the gatekeeper. If you configure a different port for RAS, you do not need to configure a different port for the gatekeeper.

Procedure


Select the icon.


c. Locate the H323 RAS port number in the Name column ( Figure 47: RAS Port

Configuration on page 61).

Figure 47: RAS Port Configuration


3. Enter the port value in the H323 RAS port number field.




®



61


®

Elite MCU

Related links


®


Configuring the UDP Port for the Gatekeeper on the Scopia

®

Elite

MCU

About this task

The Scopia

®

Elite 6000 Series MCU has designated port 1719 for gatekeeper use. You can configure a different port to enable communication with the gatekeeper (for example, if port 1719 is

busy). Port 1719 is also used for RAS (to configure the UDP port for RAS, see Configuring the UDP

Port for RAS on the Scopia

®

Elite MCU

on page 61).

Important:

If you close port 1719, you must configure another port for both the gatekeeper and RAS. If you configure a different port for the gatekeeper, you do not need to configure a different port for

RAS.

Procedure

1. Navigate to the MCU H.323 Protocol section by selecting Configuration > Protocols.

2. Locate the Enable H.323 protocol section (

Figure 48: H.323 Protocol section of the

Protocols tab

on page 62).

Figure 48: H.323 Protocol section of the Protocols tab

3. Enter the port value in the Gatekeeper port field.


Related links


®


Configuring the TCP Port Q.931 on the Scopia

®

Elite MCU

About this task

The Scopia

®

Elite 6000 Series MCU has designated port 1720 for Q.931. You can configure a different port to use Q.931 (for example, if port 1720 is busy). Q.931 is a telephony protocol used for establishing and terminating the connections in H.323 calls.


®



62


®

Elite MCU

Procedure


Select the icon.


c. Locate the H323 SIG port number in the Name column (

Figure 49: H.323 Signaling

Port Configuration on page 63).

Figure 49: H.323 Signaling Port Configuration


3. Enter the port value in the H323 SIG port number field.



Related links


®


Configuring the TCP/UDP/TLS Port for SIP on the Scopia

®

Elite

MCU

About this task

The Scopia

®

Elite 6000 Series MCU has designated ports 5060 and 5061 for SIP. You can configure a different port to use SIP (for example, if port 5060 or 5061 is busy).

Procedure

1. Navigate to the MCU SIP Protocol section by selecting Configuration > Protocols.

2. Locate the Enable SIP protocol section and select More ( Figure 50: SIP Port



®



63


®

Elite MCU

Figure 50: SIP Port Configuration

3. Do one of the following:

• If your SIP server or Registrar is not configured with TLS, enter the port value in the Local

signaling port field.

• If your SIP server or Registrar is configured with TLS, enter the port value in the Local

TLS signaling port field.

Important:

If your SIP server or Registrar is configured with TLS, you can also configure the port value for TCP/UDP traffic by modifying the Local signaling port field.


Related links


®


Configuring the TCP Port Range for SIP BFCP on the Scopia

®

Elite MCU

About this task

The Scopia

®

Elite 6000 Series MCU has designated TCP ports 3400-3580 for SIP BFCP.

BFCP is a protocol which coordinates shared videoconference features in SIP calls, often used by one participant at a time. For example, when sharing content to others in the meeting, one


®



64


®

Elite MCU User Interface participant is designated as the presenter, and is granted the floor for presenting. All endpoints must be aware that the floor was granted to that participant and react appropriately.

While the number of ports required for this protocol remain fixed, you can determine the exact port numbers occupied by the MCU by defining the lower end of the port range, known as the base port.

Procedure

Navigate to the MCU Advanced Commands section by doing the following: a.

Select the icon.

b. Locate SIP BFC Base Port entry in the Name column to change the port value (

Figure 51:

Defining the base port for SIP BFCP on page 65).

Figure 51: Defining the base port for SIP BFCP

c. Select the icon in the Review column.

d. Enter the new lower end port value in the field.

e. Select Apply.

f. Select Close.

Related links


®


Branding your Scopia

®

Elite MCU User Interface

Customers can change logos and audio messages from the Avaya or MCU branding to their own custom branding using the MCU branding feature.

Related links


®


Customizing the Logo Displayed in MCU Conferences

on page 65

Customizing MCU Audio Messages on page 68

Customizing the Logo Displayed in MCU Conferences

About this task

Perform the procedure in this section to customize the default logo displayed in the MCU conference screens (

Figure 52: Locating the logo in conference screens

on page 66).


®



65


®

Elite MCU

Figure 52: Locating the logo in conference screens

Procedure

1. Select Configuration

2. Select Customization.

.

3. Locate the Images pack area ( Figure 53: Customizing the Images Pack

on page 66).

Figure 53: Customizing the Images Pack

4. Select Save and save the .zip file with the current images to your local drive.

5. Navigate to the location where you saved the .zip file.

6. Add your logo image to each folder, as follows:

Tip:

Images are separated into folders according to resolution ( Figure 54: Image Pack Folder

Structure on page 67). You need to save the desired logo with each of the specified

resolutions to the relevant folder.

If any of the images are missing or in the wrong format, the default system logo is used.


®



66


®

Elite MCU User Interface

Figure 54: Image Pack Folder Structure

a. Ensure that your logo image has the correct dimensions (see

Table 11: Logo Image

Dimensions on page 67 for the requirements).

Table 11: Logo Image Dimensions

Resolution

4CIF

1080p

352p

480p

720p

CIF

QCIF

File Dimension (in Pixels)

216 x 44

312 x 64

132 x 24

132 x 24

216 x 44

132 x 24

96 x 16 b. Give your image a filename in the following format (maximum characters allowed in the filename is 32):

logo_XX

7. Update the Image pack file by selecting Browse and navigating to your updated .zip file.


9.

Select the icon.

10. Select Advanced Parameters.

11. Locate the Default vendor logo in the Name column (see

Figure 55: Advanced Commands

Section on page 67).

February 2016

Figure 55: Advanced Commands Section

Avaya Scopia

®



67


®

Elite MCU


13. Enter the filename of the logo you added in

6

on page 66.



Related links


®


Customizing MCU Audio Messages

About this task

You can change the default audio messages in your MCU to have your own wording. You can upload a single customized audio message, or you can upload a zip file containing all the messages customized. You can also download the existing messages pack of the MCU to inspect the naming convention of each filename.

Sound files must be in .wav format, encoded with G.711 (CCITT), 8-bit, 8kHz mono.

Procedure


2. Select Configuration > Customization > Audio messages.

Figure 56: Customizing audio messages

3. To upload a single message, locate the specific message to be customized in the Message

files section and select the icon in the Review column.


®



68


®

Elite MCU

4. To upload a pack of messages, locate the Messages pack section.

Message packs are sound files grouped together in a standard zip file. File uploads must be less than 3Mb.

Before uploading your customized pack of sound files, we recommend first downloading the existing message pack by selecting Save (see

Figure 56: Customizing audio messages

on page 68), then replace the sound files you want to customize from the downloaded zip file.

5. Select Browse and locate the sound file.

6. Select Save.


Related links


®


Upgrading, Backing up and Restoring the Scopia

®

Elite

MCU

You can restore the MCU database and configuration files from a backup copy. You should back up your database and configuration files on a regular basis.

Use backups to protect from:

• Hardware failure

• Software failure

• Data corruption

• User errors

• Data loss before a software upgrade

Related links


®



®

Elite MCU Configuration on page 69

Restoring Your Scopia

®

Elite MCU Configuration on page 70

Upgrading Scopia

®

Elite 6000 Series MCU Software

on page 71

Restoring a Previous Software Version

on page 73

Backing Up Your Scopia

®

Elite MCU Configuration

About this task

You can save MCU configuration settings to a file and then export this file to a storage device on your network. You can use the saved configuration file to restore the settings to the current MCU or to configure a similar MCU.


®



69


®

Elite MCU

The exported file is a .zip file that includes a .val file and a .xml file.

Procedure


2.

Select > Backup configuration.

3. Save the configuration settings file to your chosen location.

The .zip extension is automatically appended to the filename.

Related links


®


Restoring Your Scopia

®

Elite MCU Configuration

About this task

You can import the settings of a saved MCU configuration file from a storage device on your network. You can use the saved configuration file to restore the settings to the current MCU or to configure another MCU.

The imported file is a .zip file that includes a .val file and a .xml file.

Important:

If you are importing a configuration setup from a different MCU that has different login credentials, you will need to enter these new credentials to access the MCU.

Procedure


2.

Select > Restore configuration.

3. Select Browse.

4. Navigate to and select the configuration file (.zip) you want to import.

5. Select Restore.

6. Select Continue to upload the new configuration settings.

The restore procedure causes all current configuration to be permanently lost.

The system restarts automatically.

All active conferences are disconnected.

7. Select OK to complete the restore procedure.

Related links


®



®



70


®

Elite MCU

Upgrading Scopia

®

Elite 6000 Series MCU Software

About this task

This section details the software upgrade procedure for the Scopia

®

Elite 6000 Series MCU. You can upgrade the MCU in one of several ways:

• Upgrade via the MCU administrator web interface, by following the steps in this section.

• Remotely upgrade via Avaya Scopia

®

Management, where you can centralize all MCU upgrades. For more information, see the Administrator Guide for SCOPIA Management.

• Upgrade the device itself by inserting a USB flash drive. Contact your local Avaya representative to receive the upgrade via USB flash drive.

To implement the USB flash drive upgrade, follow the instructions you received with your flash drive.

Upgrading may take up to 40 minutes. The procedure below details how to upgrade via the MCU web interface.


Before starting the upgrade procedure, verify:

• You have backed up the current device configuration (see Backing Up Your Scopia

®

Elite MCU


• You have successfully made video calls via the MCU.

• There are no active conferences hosted on the MCU.

Procedure


2.

Select > Update software.

3. Select Browse and navigate to the required MCU upgrade package.

A message informs you a temporary license is used for the upgrade. After the upgrade, the license is permanent.

4. Select OK.

5. Select Update.

The system shuts down for a few minutes and then restarts automatically. All active conferences are disconnected.

6. Select Continue.

As soon as the update process has finished, the MCU reboots and reloads with the new software version. The upgrade process keeps the existing configuration and you do not need to import the saved configuration.

7. Verify that the MCU functions properly: a. From an endpoint dial the MCU IP address.


®



71


®

Elite MCU

You access the MCU auto attendant service which plays the video and audio prompts.

b. Select 0 to create a new conference.

c. At the prompt, enter the meeting ID and then #.

The MCU creates a new conference and the Conference window is displayed.

d. Exit the conference by disconnecting the call.

8. Verify the device is ready.

a. Configure this MCU in Scopia

®

Management as explained in Administrator Guide for

Scopia

®

Management.

b. Take other MCUs offline (if any) to make sure you hold the videoconference on this

MCU.

c. From an endpoint dial the IP address (or the Auto-Attendant number if configured).

d. Press 0 to create a new conference.

e. At the prompt, enter the meeting ID followed by #.

The MCU creates the videoconference. If it is successful, the MCU is properly installed and configured.

You can view the videoconference status in these pages:

• The MCU's Status Map which shows the connection to Scopia

®

Management and conference use statistics.

Figure 57: The MCU Status Map

• The Scopia

®

Management Dashboard which shows the details of the current videoconference.

Figure 58: The Scopia

®

Management Dashboard status

f. Exit the videoconference by disconnecting the call.

Related links


®



®



72


®

Elite MCU

Restoring a Previous Software Version

About this task

Perform this procedure to downgrade to the previous MCU software version.

Important:

You cannot downgrade the Scopia

®

Elite 6000 Series MCU to a version prior to 8.0.

We highly recommend that you contact Avaya Customer Support prior to restoring a previous software version.


• Verify you have backed up the current device configuration (see Backing Up Your Scopia

®

Elite MCU Configuration on page 69).

• On the Status tab, verify that the MCU is connected to the network by checking the Ethernet

icon ( Figure 59: Status Map Section of the Status Tab

on page 73).

Figure 59: Status Map Section of the Status Tab

• Verify that there are no active videoconferences hosted on the MCU.

Procedure

1. Access the MCU web Administrator interface.

2.

Select > Rollback software.

Restoring the previous version may take up to 15 minutes.

3. After reset, the previous release is installed on the MCU.

The downgrade process returns the MCU configuration back to the previous version, with the values used prior to the last upgrade.


®



73


®

Elite MCU

Important:

Do not import a saved configuration to the MCU after the downgrade. An older version of the MCU configuration might not support the new configuration values.

4. Verify that the MCU functions properly: a. From an endpoint dial the MCU IP address.

You access the MCU auto attendant service which plays the video and audio prompts.

b. Select 0 to create a new conference.

c. At a prompt, enter the meeting ID and then #.

The MCU creates a new conference and the Conference window is displayed.

d. Exit the conference by disconnecting the call.

5. Verify the device is ready.

a. Configure this MCU in Scopia

®

Management as explained in Administrator Guide for

Scopia

®

Management.

b. Take other MCUs offline (if any) to make sure you hold the videoconference on this

MCU.

c. From an endpoint dial the IP address (or the Auto-Attendant number if configured).

d. Press 0 to create a new conference.

e. At the prompt, enter the meeting ID followed by #.

The MCU creates the videoconference. If it is successful, the MCU is properly installed and configured.

You can view the videoconference status in these pages:

• The MCU's Status Map which shows the connection to Scopia

®

Management and conference use statistics.

February 2016

Figure 60: The MCU Status Map

• The Scopia

®

Management Dashboard which shows the details of the current videoconference.

Figure 61: The Scopia

®

Management Dashboard status

f. Exit the videoconference by disconnecting the call.

Avaya Scopia

®



74

Related links


®



Monitoring MCU Performance

About this task

You can monitor Scopia

®

Elite MCU performance in real-time in case of problems. This allows you to see any recent alarms or other events, and to troubleshoot the MCU if there are issues. For example, if a call is rejected due to a lack of available ports on the MCU, this causes MCU performance issues, and generates an alarm.

There are two ways to monitor MCU performance.

• You can monitor an individual MCU directly through the MCU administrator web interface.

• If you need to monitor multiple MCUs, or additional Scopia

Management via XML.

®

Solution components, you can do so through Scopia

®

Management. The MCU generates messages and sends them to Scopia

®

Scopia

®

Management gathers information about the performance of video network devices across the Scopia

®

Solution, including these messages sent from all your MCUs. It then analyzes the information it receives, and generates its own messages (including SNMP traps if your deployment uses SNMP) that allow you to monitor and troubleshoot the MCU.

For more information, see the sections on Real-time Monitoring and Monitoring Network

Devices via Scopia

®

Management in the Administrator Guide for Scopia

®

Management.

Important:

The MCU does not issue its own SNMP traps. SNMP is only available via Scopia

®

Management.

This section details how to monitor performance directly through the MCU administrator web interface.

Procedure


2. Select Events.

3. Select Alarms to view only critical and major events.


®



75


®

Elite MCU

Figure 62: Monitoring MCU performance using the MCU administrator web interface

4. Select for the event you want to see.

The Event information window appears with details of the problem.

Figure 63: Event information window

5. Select OK to close the window.

6. Once you have fixed the problem, the system clears the alarm. You can also manually change the severity of the alarm: a. Select the alarm for which you want to change the severity.

The Manage events window appears.


®



76

Figure 64: Manage events window

b. Select the new severity from the Severity drop-down menu.

c. Select Apply and then Close.

Related links


®




®



77

Chapter 5: Troubleshooting the Scopia

®

Elite MCU

These tips list useful hardware and software troubleshooting solutions. If the MCU still malfunctions, contact your local Avaya support representative for help.

Related links

Gathering logs on the MCU on page 78

Defining an Advanced Command on the MCU on page 80

Resolving MCU Failure to Register with the Gatekeeper

on page 80

MCU Cannot Start a Videoconference on page 81

MCU Does Not Allow Access an Existing Videoconference

on page 83

Poor Quality in Cascaded Videoconferences on page 84


on page 85

Videoconference Ends Unexpectedly on page 85

SIP Call Disconnected Unexpectedly on page 86

Resolving Presentation Issues on page 86

Resolving a Video Display Issue on page 88

Resolving Poor Audio Quality on page 89

Resolving Poor Video Quality on page 90

Scopia

®

Elite MCU cannot connect when Scopia

FQDN on page 96

®

Management can be accessed only through

Gathering logs on the MCU

About this task

You can gather logs to send to Customer Service in case of a problem. There are two ways to gather support logs:

• From Scopia

®

Management, you can gather the customer support package of logs for all video network devices, including the MCU. For more information, see Administrator Guide for

Scopia

®

Management.

• Directly from the MCU administrator web interface.

This section details how to gather logs directly from the MCU administrator web interface.


®



78

Procedure


2.

Select > Contact Customer Support.

Gathering logs on the MCU

Figure 65: Creating log package for Customer Support

3. Select Create to create a log package with the default settings.

4. Select Customize to choose the start date of the log to be included in the package.

Ensure you set the start date to just before the incident occurred so as to capture the logs at the time.

Figure 66: Customizing the dates of the logs in the package

Related links

Troubleshooting the Scopia

®



®



79


®

Elite MCU

Defining an Advanced Command on the MCU

Problem

How to enter an advanced command in the MCU. Often this instruction may come from a conversation with your local customer support representative.

Cause

Advanced configuration of some of the less commonly accessed settings are managed with

Advanced Command settings on the MCU.

Solution

Navigate to the advanced commands entry by performing the following steps.

1.

Select the icon.

2. Select Advanced parameters.

3. Locate the CLI section and select More (see

Figure 67: CLI section in MCU on page 80).

Figure 67: CLI section in MCU

4. Enter the advanced command in the Command field.

5. Enter the value of the command in the Value field.


Related links


®


Resolving MCU Failure to Register with the Gatekeeper

Problem

The Scopia

®

Elite MCU fails to register with the gatekeeper.


®



80

MCU Cannot Start a Videoconference

Incorrect gatekeeper address

The gatekeeper address is set incorrectly.

Solution

If the gatekeeper IP address is incorrect, verify the gatekeeper IP address and reconfigure the gatekeeper IP address on the MCU.

TCP/IP setup issue

There is a TCP/IP setup issue.

Solution

• Verify that the MCU is assigned a unique IP address.

• Verify that the subnet mask and default gateway subnet mask are set correctly.

• Attempt to ping the MCU from the gatekeeper to verify whether the MCU is reachable.

• Ensure the IP address assigned to the MCU is unique and not duplicated anywhere on the network.

LAN or cable issue

There is a LAN or cable issue.

Solution

• Verify the switch port settings.

• Verify that the Ethernet cable is straight through.

• Try another Ethernet cable.

• Verify if the Link and Activity LEDs on the switch port are lit.

Predefined mode

The ECS is in the Predefined mode.

Solution

If the ECS is in Predefined mode, verify that the MCU is predefined on the ECS.

Related links


®


MCU Cannot Start a Videoconference

Problem

Users cannot create new conferences.


®



81


®

Elite MCU

ECS set to reject all calls

In instant meetings, the ECS is set to reject all calls.

Solution

If the problem is caused by the ECS rejecting all calls, verify that the Accept calls option is checked in ECS > Settings > Calls.

MCU needs authorization server configured

The MCU is set to work with an external authorization server, but no authorization server is configured.

Solution

If the MCU is set to work with an authorization server and no authorization server is configured, perform these steps: verify that the External conference authorization policy option is set to

None in Maintenance > Advanced parameters > External conference policy authorization.


2.

Select the Maintenance options button , and then select Advanced parameters.

The Advanced parameters window is displayed.

3. Locate the Allows external authorization servers to connect parameter.

4. Select the Review button .

This parameter section is displayed.

Improper authorization server configuration

The MCU is set to work with an external authorization server, but the authorization server is not configured properly to work with the MCU.

Solution

If the MCU is set to work with an authorization server, but the authorization server is not configured properly, verify that the MCU IP address is correctly configured in the authorization server.

Endpoint interoperability issues

There are endpoint-related interoperability issues.

Solution: proper endpoint registration

1. Verify the MCU and the endpoint are registered properly: a. For SIP endpoints, verify that both the MCU and the SIP endpoint are properly registered with the SIP proxy.


®



82

MCU Does Not Allow Access an Existing Videoconference b. For H.323 endpoints, verify that both the MCU and the H.323 endpoint are properly registered with the ECS.

c. For 3G endpoints, verify that both the MCU and the 3G endpoint are properly registered with the SIP proxy and/or ECS.

2. If the registration is correct, collect logs and wireshark traces and send them to Avaya

Customer Support.

Solution: Initiating endpoint not registered

If the initiating LAN endpoint is not registered with the ECS, verify that the initiating endpoint appears in the ECS Endpoints table correctly.

Service not defined

The MCU service may not be defined in the ECS Services table.

Solution

1. Verify that the service is defined in the MCU.

2. Verify that the MCU service prefix appears in the ECS Services table. If it does not, add it manually.

3. Verify that the service prefix is not a subset of another service prefix.

Insufficient resources

There are not enough MCU resources available for the desired conference.

Solution

There are not enough MCU resources available, verify that current calls are not utilizing all resources by checking the available MCU capacity and then trying to disconnect other calls in order to find the problem.

Related links


®


MCU Does Not Allow Access an Existing Videoconference

Problem

An endpoint cannot be invited to a conference or dial into the conference.

ECS set to reject all calls

The ECS is set to reject all calls.

If the ECS is set to reject all calls, verify that the Accept calls option is checked in ECS >

Settings > Calls.


®



83


®

Elite MCU

Endpoint is not registered

The endpoint is not registered with the ECS.

Solution

If the endpoint is not registered with the ECS, verify that the invited/dialing endpoint appears in the

ECS table of registered endpoints. Also verify that the endpoint is online.

Endpoint not authorized

The MCU is configured to work with an authorization server, but the endpoint is not authorized and therefore the authorization server rejects the call.

Solution

If the MCU is configured to work with an authorization server , verify that the endpoint is authorized in the authorization server.

Endpoint in use

The endpoint is currently in a call.

Solution

If the endpoint is currently in a call, confirm that the endpoint is not busy/in a call.

Insufficient resources

There are not enough MCU resources available for the desired conference.

Solution

If there are not enough MCU resources, remove one of the current participants to verify that the endpoint can join successfully. Then verify whether cascading is enabled and if the meeting is scheduled for cascading.

Related links


®


Poor Quality in Cascaded Videoconferences

Problem

A videoconference using several MCU devices (cascaded videoconference) suffers long delays or bad lip synchronization.

Cause

The topology used for the conference is not suitable; for example, a chain topology is used unnecessarily.


®



84


Solution

One single central MCU should invite all other cascaded MCUs. We recommend that you do not have more than one level of cascaded MCUs. Use a star topology, where the central MCU is in the center of the star, and other cascaded MCU modules are on the arms of the star.

Related links


®


Endpoints Unexpectedly Disconnect from

Videoconferences

Problem

Endpoints unexpectedly drop out of the MCU conference.

Cause

The network connection is unreliable.

Solution

Check network connection quality. Round trip time should be less than 300ms.

Related links


®


Videoconference Ends Unexpectedly

Problem

A conference on the MCU unexpectedly terminates.

Cause

The MCU unexpectedly drops out of the ECS endpoints database.

Solution

1. Uncheck the Check that endpoint is online every n seconds option in ECS > Settings >

Advanced.

2. Uncheck the Check that call is alive every n seconds option in ECS > Settings > Calls.

3. Uncheck the TTL option in ECS > Settings > Advanced.

Related links


®



®



85


®

Elite MCU

SIP Call Disconnected Unexpectedly

Problem

A SIP call unexpectedly disconnects after 30 seconds.

Cause

DNS is not fully configured on the MCU and user agents.

Solution

Make sure that DNS is configured on user agent and MCU.

Related links


®


Resolving Presentation Issues

Problem

A conference participant cannot start or receive a presentation.

H.239 not enabled

H.239 functionality is not enabled on the endpoint.

Solution

If the H.239 functionality is not enabled on the participant’s endpoint, verify that H.239 is enabled on the endpoint. Make a point-to-point call to another endpoint and verify that the participant can start a presentation.

Presentation not configured

Presentation is not configured in the MCU service used in the conference.

Solution


2. Select the Configuration tab

3. Select the Conferences tab.

.

4. In the Services List section, select the service.

5. Select More.

Additional settings for this service are displayed.


®



86

Resolving Presentation Issues

Figure 68: Additional Service Settings Window

6. Select Enable presentation view.

Presentation definitions not supported

MCU presentation definitions in the service are not supported by the endpoint (frame rate, frame size, codec).

Solution

If the problem is caused by inconsistency of presentation definitions, configure the endpoint to that it supports the frame size, frame rate and video codec as defined in the service.

Issue still exists

If the issue still exists, capture the endpoint data logs for Customer Support.

Figure 69: Data logs from the Scopia

®

Management user portal

on page 88 shows an endpoint data log captured from the conference control of the Scopia

®

Management user portal. For more information, see User Guide for Scopia

®

Management.


®



87


®

Elite MCU

Figure 69: Data logs from the Scopia

®

Management user portal

Related links


®


Resolving a Video Display Issue

Problem

The video for a conference participant is not displayed in a conference view.

Interoperability

Interoperability issues: an incorrect video format used by an endpoint or incorrect logical channel negotiation.

Solution

1. Make a point-to-point call without Avaya products to verify that there are no issues related to endpoints used in a conference. In case there are problems related to endpoints, use the endpoint documentation to troubleshoot them.

2. If the problem is not endpoint-related verify that perform verification depending on the kind of endpoint used in the conference:

• For a SIP endpoint, verify that both the MCU and the endpoint are properly registered with the SIP proxy.

• For an H.323 endpoint, verify that both the MCU and the endpoint are properly registered with the ECS.

• For a 3G endpoint, verify that both the MCU and the endpoint are properly registered with

SIP proxy and/or the ECS.

3. If registration is correct, collect logs and wireshark traces to Avaya Customer Support.


®



88

Resolving Poor Audio Quality

Camera of cables

Issues related to a camera or cables.

Solution

Verify that the camera is connected properly.

Firewall blocking ports

The media ports are blocked on the firewall.

Solution

Open the necessary media ports on the firewall. Refer to the Port Security Reference Guide for information about ports.

Related links


®


Resolving Poor Audio Quality

Problem

The quality of a participant’s audio received in a conference is poor.

Cause

Interoperability issues: an incorrect video format used by an endpoint or incorrect logical channel negotiation

Solution

1. Make a point-to-point call without Avaya products to verify that there are no issues related to endpoints used in a conference. In case there are problems related to endpoints, use the endpoint documentation to troubleshoot them.

2. If the problem is not endpoint-related verify that perform verification depending on the kind of endpoint used in the conference:

• For a SIP endpoint, verify that both the MCU and the endpoint are properly registered with the SIP proxy.

• For an H.323 endpoint, verify that both the MCU and the endpoint are properly registered with the ECS.

• For a 3G endpoint, verify that both the MCU and the endpoint are properly registered with

SIP proxy and/or the ECS.

3. If registration is correct, collect logs and wireshark traces for Avaya Customer Support.

This includes capturing the audio log from an endpoint. For example, if you are using the conference control of the Scopia

®

Management user portal, you need to capture the audio

log shown in Figure 70: Audio log from the Scopia

®


on page 90.

For more information, see User Guide for Scopia

®

Management.


®



89


®

Elite MCU

Figure 70: Audio log from the Scopia

®


Related links


®


Resolving Poor Video Quality

Problem

The quality of the video in a videoconference is poor.

Not running the latest software

The MCU is not running the latest software version.

Solution


2. Navigate to the Product Information section in the Status tab ( Figure 71: Software version information

on page 91). If it does not display the latest software version, update as

described in Upgrading Scopia

®

Elite 6000 Series MCU Software on page 71).


®



90


Figure 71: Software version information

Incorrect network speed and duplex mode

The MCU and network switches are not configured to the correct network speed and duplex mode.

Solution

Verify the MCU Ethernet interface is set to 1Gbps and Full Duplex as the preferred values for auto-negotiation. This standard requires that the MCU, router and switch ports are configured to the same transmission settings to avoid compatibility issues.


2. Navigate to Status Map section in the Status tab ( Figure 72: Verifying the Ethernet interface setting

on page 91).

Figure 72: Verifying the Ethernet interface setting

3. If the Ethernet interface is not configured for Auto-Speed/Duplex as shown in

Figure 72:

Verifying the Ethernet interface setting on page 91, select the Configuration tab.

4. In the Network section, set the Port settings field to Auto (Up to 1 Gbps/Full Duplex), and

select Apply ( Figure 73: Network Section of the Setup Tab on page 92).


®



91


®

Elite MCU

Figure 73: Network Section of the Setup Tab

5. Configure the network switch which connects to the MCU to Auto-Speed and Duplex mode.

6. Verify the Status Map section shows the setting in ( Figure 72: Verifying the Ethernet interface setting

on page 91. This indicates the switch and the MCU are communicating at the correct speed and duplex mode.

Figure 74: Verifying the Ethernet interface setting

Bandwidth

The MCU service bandwidth is not set to the optimal value.


®



92


Solution

To return the MCU to the default service bandwidth, proceed as follows:


2. In the Configuration tab, locate Conferences > Services List and select Review.

3. Select the default value 4096 from the list under Max call rate (Kbps).

Figure 75: Selecting the default bandwidth


Incorrect video quality service value

The MCU video quality service is not set to the correct value.

Solution

To verify you configured the video quality to the value required for your conference, proceed as follows:


2. Select Configuration > Conferences > Services List, then select Review next to the service you want to modify.

3. Select More and locate the Video quality preference section.

4. Select Sharpness for a more static videoconference, or Motion if you need a higher frame rate to better support movement.

February 2016

Figure 76: Verifying the video quality setting

Avaya Scopia

®



93


®

Elite MCU

5. Select OK, and then Apply.

Incorrect QoS settings

The QoS settings of the network router do not match the MCU ones.

Solution

Make sure the MCU QoS settings conform with the network QoS settings across the network

(switches, routers, endpoints). To verify the MCU QoS settings, proceed as follows:

1. Access the MCU QoS settings as follows: a. Access the MCU administrator web interface.

b. In the Setup tab, locate the QoS section and select More.

The QoS section displays the current settings (

Figure 77: QoS Section showing the default settings on page 94).

Figure 77: QoS Section showing the default settings

2. Make sure the MCU QoS settings match with the network QoS settings.

3. Check the logs of the endpoint which is farthest from the MCU to make sure it received the correct QoS settings. You can also follow the procedure described in the following step.

4. To verify how QoS settings are propagated across the network, you can also proceed as follows: a. Analyze the network traffic in the switch by using its Switched Port Analyzer (SPAN) feature (if supported). This method allows mirroring network traffic from the source port

to another destination port in the switch for monitoring and analysis ( Figure 78:

Mirroring network traffic at a switch

on page 95).


®



94


Figure 78: Mirroring network traffic at a switch

This includes enabling SPAN in the switch, connecting a computer to the destination port, and installing a network sniffer on your computer.

b. Collect a Wireshark trace at the endpoint farthest from the MCU.

5. Review the tracing logs for changes in the Differentiated Services Code Point (DSCP) value of each IP packet that defines the service priority level. If the values have changed to 0x0, the QoS tagging was stripped and the traffic is no longer prioritized.

Revert to factory defaults

If none of these troubleshooting procedures help solve the video quality issues, revert the MCU to factory defaults.

Procedure

1. Back up the configuration file, as described in


®

Elite MCU

Configuration on page 69.


3.

Select > Restore factory defaults.

4. Make sure to read the alert message and then select Continue.

5. After the MCU reboots, start a test videoconference. If the issue improves or is solved, review your configuration settings.

6. If the issue still exists, capture the endpoint video logs for Customer Support.

Figure 79: Video log from the Scopia

®


on page 96 shows a video log captured from the conference control of the Scopia

®

Management user portal. For more information, see User Guide for Scopia

®

Management.


®



95


®

Elite MCU

Figure 79: Video log from the Scopia

®


Related links


®


Scopia

®

Elite MCU cannot connect when Scopia

®

Management can be accessed only through FQDN

Condition

Scopia

®

Elite MCU cannot connect to Scopia

®

Management.

Cause

If Scopia

®

Management, which is the SIP server, can only be accessed using FQDN, Scopia

®

Elite

MCU cannot connect if the settings contain the IP address of the SIP server.

Solution

1. Log in to Scopia

®

Management.

2. Click Devices > MCUs.

3. Select the Scopia

®

Elite 6000 Series MCU instance.

4. Click Configuration.

5. In SIP Proxy Server, enter FQDN of the SIP server.

Related links


®



®



96

Glossary

1080p

2CIF

2SIF

4CIF

4SIF

720p

AAC

AGC (Automatic Gain

Control)

Alias

Auto-Attendant

Balanced

Microphone

See Full HD

on page 100.

2CIF describes a video resolution of 704 x 288 pixels (PAL) or 704 x 240

(NTSC). It is double the width of CIF, and is often found in CCTV products.

2SIF describes a video resolution of 704 x 240 pixels (NTSC) or 704 x 288

(PAL). This is often adopted in IP security cameras.

4CIF describes a video resolution of 704 x 576 pixels (PAL) or 704 x 480

(NTSC). It is four times the resolution of CIF and is most widespread as the standard analog TV resolution.

4SIF describes a video resolution of 704 x 480 pixels (NTSC) or 704 x 576

(PAL). This is often adopted in IP security cameras.

See HD

on page 102.

AAC is an audio codec which compresses sound but with better results than MP3.

Automatic Gain Control (AGC) smooths audio signals through normalization, by lowering sounds which are too strong and strengthening sounds which are too weak. This is relevant with microphones situated at some distance from the speaker, like room systems. The result is a more consistent audio signal within the required range of volume.

An alias in H.323 represents the unique name of an endpoint. Instead of dialing an IP address to reach an endpoint, you can dial an alias, and the gatekeeper resolves it to an IP address.

Auto-Attendant, also known as video IVR, offers quick access to meetings hosted on MCUs, via a set of visual menus. Participants can select menu options using standard DTMF tones (numeric keypad). Auto-Attendant works with both H.323 and SIP endpoints.

A balanced microphone uses a cable that is built to reduce noise and interference even when the cable is long. This reduces audio disruptions resulting from surrounding electromagnetic interference.


®



97

Glossary

BFCP (Binary Floor

Control Protocol)

Bitrate

Call Control

Cascaded

Videoconference

CIF

Content Slider

Continuous

Presence

Control

CP

BFCP is a protocol which coordinates shared videoconference features in

SIP calls, often used by one participant at a time. For example, when sharing content to others in the meeting, one participant is designated as the presenter, and is granted the floor for presenting. All endpoints must be aware that the floor was granted to that participant and react appropriately.

Bitrate is the speed of data flow. Higher video resolutions require higher bitrates to ensure the video is constantly updated, thereby maintaining smooth motion. If you lower the bitrate, you lower the quality of the video. In some cases, you can select a lower bitrate without noticing a significant drop in video quality; for example during a presentation or when a lecturer is speaking and there is very little motion. In video recordings, the bitrate determines the file size for each minute of recording. Bitrate is often measured in kilobits per second (kbps).

See Signaling

on page 108.

A cascaded videoconference is a meeting distributed over more than one physical Scopia

®

Elite MCU, 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.

CIF, or Common Intermediate Format, describes a video resolution of 352 ×

288 pixels (PAL) or 352 x 240 (NTSC). This is sometimes referred to as

Standard Definition (SD).

The Scopia

®

Content Slider stores the data already presented in the videoconference and makes it available for participants to view during the meeting.

Continuous presence enables viewing multiple participants of a videoconference at the same time, including the active speaker. This graphics-intensive work requires scaling and mixing the images together into one of the predefined video layouts. The range of video layouts depends on the type of media processing supported, typically located in the

MCU.

Control, or media control, sets up and manages the media of a call (its audio, video and data). Control messages include checking compatibility between endpoints, negotiating video and audio codecs, and other parameters like resolution, bitrate and frame rate. Control is communicated via H.245 in H.323 endpoints, or by SDP in SIP endpoints. Control occurs within the framework of an established call, after signaling.

See Continuous Presence

on page 98.


®



98

Dedicated Endpoint

Dial Plan

Dial Prefix

Distributed

Deployment

DNS Server

DTMF

Dual Video

Dynamic Video

Layout

E.164

Endpoint

Dedicated Endpoint

A dedicated endpoint is a hardware endpoint for videoconferencing assigned to a single user. It is often referred to as a personal or executive endpoint, and serves as the main means of video communications for this user. For example, Scopia

®

XT Executive. It is listed in the organization's

LDAP directory as associated exclusively with this user.

A dial plan defines a way to route a call and to determine its characteristics.

In traditional telephone networks, prefixes often denote geographic locations. In videoconferencing deployments, prefixes are also used to define the type and quality of a call. For example, dial 8 before a number for a lower bandwidth call, or 6 for an audio-only call, or 5 to route the call to a different branch.

A dial prefix is a number added at the beginning of a dial string to route it to the correct destination, or to determine the type of call. Dial prefixes are defined in the organization's dial plan. For example, dial 9 for an outside line, or dial 6 for an audio only call.

A distributed deployment describes a deployment where the solution components are geographically distributed in more than one network location.

A DNS server is responsible for resolving domain names in your network by translating them into IP addresses.

DTMF, or touch-tone, is the method of dialing on touch-tone phones, where each number is translated and transmitted as an audio tone.

Dual video is the transmitting of two video streams during a videoconference, one with the live video while the other is a shared data stream, like a presentation.

The dynamic video layout is a meeting layout that switches dynamically to include the maximum number of participants it can display on the screen

(up to 9 on the XT Series, or up to 28 on Scopia

®

Elite MCU). The largest image always shows the active speaker.

E.164 is an address format for dialing an endpoint with a standard telephone numeric keypad, which only has numbers 0 - 9 and the symbols:

* and #.

An endpoint is a tool through which people can participate in a videoconference. Its display enables you to see and hear others in the meeting, while its microphone and camera enable you to be seen and heard by others. Endpoints include dedicated endpoints, like Scopia

Executive, software endpoints like Scopia

®

®

XT

Desktop Client, mobile device endpoints like Scopia

®

Mobile, room systems like XT Series, and telepresence systems like Scopia

®

XT Telepresence.


®



99

Glossary

Endpoint Alias

FEC

FECC

Forward Error

Correction

FPS

Frame Rate

Frames Per Second

FTP

Full HD

Full screen Video

Layout

Gatekeeper

See Alias

on page 97.

Forward Error Correction (FEC) is a proactive method of sending redundant information in the video stream to preempt quality degradation. FEC identifies the key frames in the video stream that should be protected by

FEC. There are several variants of the FEC algorithm. The Reed-Solomon algorithm (FEC-RS) sends redundant packets per block of information, enabling the sender (like the Scopia

®

Elite MCU) to manage up to ten percent packet loss in the video stream with minimal impact on the smoothness and quality of the video.

Far End Camera Control (FECC) is a feature of endpoint cameras, where the camera can be controlled remotely by another endpoint in the call.

See FEC

on page 100.

See Frames Per Second

on page 100.

See Frames Per Second

on page 100.

Frames Per Second (fps), also known as the frame rate, is a key measure in video quality, describing the number of image updates per second. The average human eye can register up to 50 frames per second. The higher the frame rate, the smoother the video.

The File Transfer Protocol (FTP) is a standard network protocol used to transfer computer files from one host to another host over a TCP-based network, such as the Internet. FTP is built on a client-server architecture and uses separate control and data connections between the client and the server. FTP users may authenticate themselves using a clear-text sign-in protocol, normally in the form of a username and password, but can connect anonymously if the server is configured to allow it.

Full HD, or Full High Definition, also known as 1080p, describes a video resolution of 1920 x 1080 pixels.

The full screen view shows one video image. Typically, it displays the remote presentation, or, if there is no presentation, it displays the other meeting participant(s).

A gatekeeper routes audio and video H.323 calls by resolving dial strings

(H.323 alias or URI) into the IP address of an endpoint, and handles the initial connection of calls. Gatekeepers also implement the dial plan of an organization by routing H.323 calls depending on their dial prefixes.

Scopia

®

Management includes a built-in Avaya Scopia

®

Gatekeeper, while

ECS is a standalone gatekeeper.


®



100

H.243

H.245

H.261

H.263

H.264

GLAN

H.225

H.235

H.239

Gateway

H.264 Baseline

Profile

H.264 High Profile

Gateway

A gateway is a component in a video solution which routes information between two subnets or acts as a translator between different protocols.

For example, a gateway can route data between the headquarters and a partner site, or between two protocols like the TIP Gateway, or the Scopia

®

100 Gateway.

GLAN, or gigabit LAN, is the name of the network port on the XT Series. It is used on the XT Series to identify a 10/100/1000MBit ethernet port.

H.225 is part of the set of H.323 protocols. It defines the messages and procedures used by gatekeepers to set up calls.

H.235 is the protocol used to authenticate trusted H.323 endpoints and encrypt the media stream during meetings.

H.239 is a widespread protocol used with H.323 endpoints, to define the additional media channel for data sharing (like presentations) alongside the videoconference, and ensures only one presenter at a time.

H.243 is the protocol used with H.323 endpoints enabling them to remotely manage a videoconference.

H.245 is the protocol used to negotiate call parameters between endpoints, and can control a remote endpoint from your local endpoint. It is part of the

H.323 set of protocols.

H.261 is an older protocol used to compress CIF and QCIF video resolutions. This protocol is not supported by the XT Series.

H.263 is an older a protocol used to compress video. It is an enhancement to the H.261 protocol.

H.264 is a widespread protocol used with SIP and H.323 endpoints, which defines video compression. Compression algorithms include 4x4 transforms and a basic motion comparison algorithm called P-slices. There are several profiles within H.264. The default profile is the H.264 Baseline Profile, but

H.264 High Profile uses more sophisticated compression techniques.

See H.264

on page 101.

H.264 High Profile is a standard for compressing video by up to 25% over the H.264 Baseline Profile, enabling high definition calls to be held over lower call speeds. It requires both sides of the transmission (sending and receiving endpoints) to support this protocol. H.264 High Profile uses compression algorithms like:

• CABAC compression (Context-Based Adaptive Binary Arithmetic

Coding)


®



101

Glossary

H.320

H.323

H.323 Alias

H.350

H.460

HD

High Availability

High Definition

High Profile

HTTP

HTTPS

• 8x8 transforms which more effectively compress images containing areas of high correlation

These compression algorithms demand higher computation requirements, which are offered with the dedicated hardware available in Scopia

®

Solution components. Using H.264 High Profile in videoconferencing requires that both the sender and receiver's endpoints support it. This is different from SVC which is an adaptive technology working to improve quality even when only one side supports the standard.

H.320 is a protocol for defining videoconferencing over ISDN networks.

H.323 is a widespread set of protocols governing the communication between endpoints in videoconferences and point-to-point calls. It defines the call signaling, control, media flow, and bandwidth regulation.

See Alias

on page 97.

H.350 is the protocol used to enhance LDAP user databases to add video endpoint information for users and groups.

H.460 enhances the standard H.323 protocol to manage firewall/NAT traversal, employing ITU-T standards. Endpoints which are already H.460

compliant can communicate directly with the PathFinder server, where the endpoint acts as an H.460 client to the PathFinder server which acts as an

H.460 server.

A HD ready device describes its high definition resolution capabilities of

720p, a video resolution of 1280 x 720 pixels.

High availability is a state where you ensure better service and less downtime by deploying additional servers. There are several strategies for achieving high availability, including deployment of redundant servers managed by load balancing systems.

See HD

on page 102.

See H.264 High Profile

on page 101.

The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web.

Hypertext is structured text that uses logical links (hyperlinks) between nodes containing text. HTTP is the protocol to exchange or transfer hypertext.

HTTPS is the secured version of the standard web browser protocol HTTP.

It secures communication between a web browser and a web server through authentication of the web site and encrypting communication


®



102

Image Resolution

KBps kbps

LDAP

Lecture Mode

Load balancer

Location

Management

Image Resolution between them. For example, you can use HTTPS to secure web browser access to the web interface of many Scopia

®

Solution products.

See Resolution

on page 106.

Kilobytes per second (KBps) measures the bitrate in kilobytes per second, not kilobits, by dividing the number of kilobits by eight. Bitrate is normally quoted as kilobits per second (kbps) and then converted to kilobytes per second (KBps). Bitrate measures the throughput of data communication between two devices.

Kilobits per second (kbps) is the standard unit to measure bitrate, measuring the throughput of data communication between two devices.

Since this counts the number of individual bits (ones or zeros), you must divide by eight to calculate the number of kilobytes per second (KBps).

LDAP is a widespread standard database format which stores network users. The format is hierarchical, where nodes are often represented asbranch location > department > sub-department, orexecutives >

managers > staff members. The database standard is employed by most user directories including Microsoft Active Directory, IBM Sametime and others. H.350 is an extension to the LDAP standard for the videoconferencing industry.

Scopia

®

Desktop's lecture mode allows the participant defined as the lecturer to see all the participants, while they see only the lecturer. All participants are muted except the lecturer, unless a participant asks permission to speak and is unmuted by the lecturer. This mode is tailored for distance learning, but you can also use it for other purposes like when an executive addresses employees during company-wide gatherings.

A load balancer groups together a set (or cluster) of servers to give them a single IP address, known as a virtual IP address. It distributes client service requests amongst a group of servers. It distributes loads according to different criteria such as bandwidth, CPU usage, or cyclic (round robin).

Load balancers are also known as application delivery controllers (ADC).

A location is a physical space (building) or a network (subnet) where video devices can share a single set of addresses. A distributed deployment places these components in different locations, often connected via a VPN.

Management refers to the administration messages sent between components of the Scopia

®

Solution as they manage and synchronize data between them. Management also includes front-end browser interfaces configuring server settings on the server. Management messages are usually transmitted via protocols like HTTP, SNMP, FTP or XML. For example, Scopia

®

Management uses management messages to monitor


®



103

Glossary

MBps

MCU

MCU service

Media

Media Control

Meeting Type

Moderator

MTU

Multi-Point

Multi-tenant

February 2016 the activities of an MCU, or when it authorizes the MCU to allow a call to proceed.

Megabytes per second (MBps) is a unit of measure for the bitrate. The bitrate is normally quoted as kilobits per second (kbps) and then converted by dividing it by eight to reach the number of kilobytes per second (KBps) and then by a further 1000 to calculate the MBps.

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.

See Meeting Type

on page 104.

Media refers to the live audio, video and shared data streams sent during a call. Presentation and Far end camera control (FECC) are examples of information carried on the data stream. Media is transmitted via the RTP and RTCP protocols in both SIP and H.323 calls. The parallel data stream of both live video and presentation, is known as dual video.

See Control on page 98.

Meeting types (also known as MCU services) are meeting templates which determine the core characteristics of a meeting. For example, they determine if the meeting is audio only or audio and video, they determine the default video layout, the type of encryption, PIN protection and many other features. You can invoke a meeting type by dialing its prefix in front of the meeting ID. Meeting types are created and stored in the MCU, with additional properties in Scopia

®

Management.

A moderator has special rights in a videoconference, including blocking the sound and video of other participants, inviting new participants, disconnecting others, determining video layouts, and closing meetings. In

Scopia

®

Desktop Client, an owner of a virtual room is the moderator when the room is protected by a PIN. Without this protection, any participant can assume moderator rights.

The MTU, or Maximum Transmission Unit, is the maximum size of data packets sent around your network. This value must remain consistent for all network components, including servers like the MCU and Scopia

®

Desktop server, endpoints like XT Series and other network devices like LDAP servers and network routers.

A multi-point conference has more than two participants.

Service provider, or multi-tenant, deployments enable one installation to manage multiple organizations. All the organizations can reside as tenants within a single service provider deployment. For example, Scopia

®

Management can manage a separate set of users for each organization,

Avaya Scopia

®



104

Multicast Streaming

NAT

NetSense

Packet Loss

PaP Video Layout

Phantom Power

PiP Video Layout

Point-to-Point

Multicast Streaming separate local administrators, separate bandwidth policies etc. all within a single multi-tenant installation.

Multicast streaming sends a videoconference to multiple viewers across a range of addresses, reducing network traffic significantly. Scopia

®

Desktop server multicasts to a single IP address, and streaming clients must tune in to this IP address to view the meeting. Multicasts require that routers, switches and other equipment know how to forward multicast traffic.

A NAT, or Network Address Translation device, translates external IP addresses to internal addresses housed in a private network. This enables a collection of devices like endpoints in a private network, each with their own internal IP address, can be represented publicly by a single, unique IP address. The NAT translates between public and private addresses, enabling users toplace calls between public network users and private network users.

NetSense is a proprietary Scopia

®

Solution technology which optimizes the video quality according to the available bandwidth to minimize packet loss.

As the available bandwidth of a connection varies depending on data traffic,

NetSense's sophisticated algorithm dynamically scans the video stream, and then reduces or improves the video resolution to maximize quality with the available bandwidth.

Packet loss occurs when some of the data transmitted from one endpoint is not received by the other endpoint. This can be caused by narrow bandwidth connections or unreliable signal reception on wireless networks.

The PaP (Picture and Picture) view shows up to three images of the same size.

Microphones which use phantom power draw their electrical power from the same cable as the audio signal. For example, if your microphone is powered by a single cable, it serves both to power the microphone and transmit the audio data. Microphones which have two cables, one for sound and a separate power cable, do not use phantom power.

The PiP (Picture In Picture) view shows a video image in the main screen, with an additional smaller image overlapping in the corner. Typically, a remote presentation is displayed in the main part of the screen, and the remote video is in the small image. If the remote endpoint does not show any content, the display shows the remote video in the main part of the screen, and the local presentation in the small image.

Point-to-point is a feature where only two endpoints communicate with each other without using MCU resources.


®



105

Glossary

PoP Video Layout

Prefix

PTZ Camera

Q.931

QCIF

Quality of Service

(QoS)

Recordings

Redundancy

Registrar

Resolution

The PoP (Picture out Picture) view shows up to three images of different size, presented side by side, where the image on the left is larger than the two smaller images on the right.

See Dial Prefix on page 99.

A PTZ camera can pan to swivel horizontally, tilt to move vertically, and optically zoom to devote all the camera's pixels to one area of the image.

For example, the XT Standard Camera is a PTZ camera with its own power supply and remote control, and uses powerful lenses to achieve superb visual quality. In contrast, fixed cameras like webcams only offer digital

PTZ, where the zoom crops the camera image, displaying only a portion of the original, resulting in fewer pixels of the zoomed image, which effectively lowers the resolution. Fixed cameras also offer digital pan and tilt only after zooming, where you can pan up to the width or length of the original camera image.

Q.931 is a telephony protocol used to start and end the connection in H.323

calls.

QCIF, or Quarter CIF, defines a video resolution of 176 × 144 pixels (PAL) or 176 x 120 (NTSC). It is often used in older mobile handsets (3G-324M) limited by screen resolution and processing power.

Quality of Service (QoS) determines the priorities of different types of network traffic (audio, video and control/signaling), so in poor network conditions, prioritized traffic is still fully transmitted.

A recording of a videoconference can be played back at any time.

Recordings include audio, video and shared data (if presented). Users can access recordings from the Scopia

®

Desktop web portal or using a web link to the recording on the portal.

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.

A SIP Registrar manages the SIP domain by requiring that all SIP devices register their IP addresses with it. For example, once a SIP endpoint registers its IP address with the Registrar, it can place or receive calls with other registered endpoints.

Resolution, or image/video resolution, is the number of pixels which make up an image frame in the video, measured as the number of horizontal pixels x the number of vertical pixels. Increasing resolution improves video quality but typically requires higher bandwidth and more computing power.

Techniques like SVC, H.264 High Profile and FEC reduce bandwidth usage


®



106

Restricted Mode

Room System

RTCP

RTP

RTSP

Sampling Rate

SBC

Scalability

Scopia

®

Content

Slider

SD

Service

Restricted Mode by compressing the data to a smaller footprint and compensating for packet loss.

Restricted mode is used for ISDN endpoints only, when the PBX and line uses a restricted form of communication, reserving the top 8k of each packet for control data only. If enabled, the bandwidth values on these lines are in multiples of 56kbps, instead of multiples of 64kbps.

A room system is a hardware videoconferencing endpoint installed in a physical conference room. Essential features include its camera's ability to

PTZ (pan, tilt, zoom) to allow maximum flexibility of camera angles enabling participants to see all those in the meeting room or just one part of the room.

Real-time Control Transport Protocol, used alongside RTP for sending statistical information about the media sent over RTP.

RTP or Real-time Transport Protocol is a network protocol which supports video and voice transmission over IP. It underpins most videoconferencing protocols today, including H.323, SIP and the streaming control protocol known as RTSP. The secured version of RTP is SRTP.

RTSP or Real-Time Streaming Protocol controls the delivery of streamed live or playback video over IP, with functions like pause, fast forward and reverse. While the media itself is sent via RTP, these control functions are managed by RTSP

The sampling rate is a measure of the accuracy of the audio when it is digitized. To convert analog audio to digital, it must collect or sample the audio at specific intervals. As the rate of sampling increases, it raises audio quality.

A Session Border Controller (SBC) is a relay device between two different networks. It can be used in firewall/NAT traversal, protocol translations and load balancing.

Scalability describes the ability to increase the capacity of a network device by adding another identical device (one or more) to your existing deployment. In contrast, a non-scalable solution would require replacing existing components to increase capacity.

See Content Slider on page 98.

Standard Definition (SD), is a term used to refer to video resolutions which are lower than HD. There is no consensus defining one video resolution for

SD.

Also known as MCU service. See

Meeting Type on page 104.


®



107

Glossary

SIF

Signaling

Single Sign On

SIP

SIP Registrar

SIP Server

SIP URI

Slider

SNMP

Software endpoint

SQCIF

SRTP

SIF defines a video resolution of 352 x 240 pixels (NTSC) or 352 x 288

(PAL). This is often used in security cameras.

Signaling, also known as call control, sets up, manages and ends a connection or call. These messages include the authorization to make the call, checking bandwidth, resolving endpoint addresses, and routing the call through different servers. Signaling is transmitted via the H.225.0/Q.931

and H.225.0/RAS protocols in H.323 calls, or by the SIP headers in SIP calls. Signaling occurs before the control aspect of call setup.

Single Sign On (SSO) automatically uses your network login and password to access different enterprise systems. Using SSO, you do not need to separately login to each system or service in your organization.

Session Initiation Protocol (SIP) is a signaling protocol for starting, managing and ending voice and video sessions over TCP, TLS or UDP.

Videoconferencing endpoints typically are compatible with SIP or H.323, and in some cases (like Avaya Scopia

®

XT Series), an endpoint can be compatible with both protocols. As a protocol, it uses fewer resources than

H.323.

See Registrar

on page 106.

A SIP server is a network device communicating via the SIP protocol.

See URI on page 110.

See Content Slider on page 98.

Simple Network Management Protocol (SNMP) is a protocol used to monitor network devices by sending messages and alerts to their registered

SNMP server.

A software endpoint turns a computer or portable device into a videoconferencing endpoint via a software application only. It uses the system's camera and microphone to send image and sound to the other participants, and displays their images on the screen. For example,

Scopia

®

Desktop Client or Scopia

®

Mobile.

SQCIF defines a video resolution of 128 x 96 pixels.

Secure Real-time Transport Protocol (SRTP) adds security to the standard

RTP protocol, which is used to send media (video and audio) between devices in SIP calls. It offers security with encryption, authentication and message integrity. The encryption uses a symmetric key generated at the start of the call, and being symmetric, the same key locks and unlocks the data. So to secure transmission of the symmetric key, it is sent safely during call setup using TLS.


®



108

SSO

Standard Definition

Streaming

STUN

SVC

SVGA

Switched video

SXGA

Telepresence

SSO

See Single Sign On

on page 108.

See SD

on page 107.

Streaming is a method to send live or recorded videoconferences in one direction to viewers. Recipients can only view the content; they cannot participate with a microphone or camera to communicate back to the meeting. There are two types of streaming supported in Scopia

®

Solution: unicast which sends a separate stream to each viewer, and multicast which sends one stream to a range of viewers.

A STUN server enables you to directly dial an endpoint behind a NAT or firewall by giving that computer’s public internet address.

SVC extends the H.264 codec standard to dramatically increase error resiliency and video quality without the need for higher bandwidth. It is especially effective over networks with high packet loss (like wireless networks) which deliver low quality video. It splits the video stream into layers, comprising a small base layer and then additional layers on top which enhance resolution, frame rate and quality. Each additional layer is only transmitted when bandwidth permits. This allows for a steady video transmission when available bandwidth varies, providing better quality when the bandwidth is high, and adequate quality when available bandwidth is poor.

SVGA defines a video resolution of 800 x 600 pixels.

Switching is the process of redirecting video as-is without transcoding, so you see only one endpoint's image at a time, usually the active speaker, without any video layouts or continuous presence (CP). Using video switching increases the port capacity of the Scopia

®

Elite MCU only by four times.

Important:

Use switched video only when all endpoints participating in the videoconference support the same resolution. If a network experiences high packet loss, switched video might not be displayed properly for all endpoints in the videoconference.

SXGA defines a video resolution of 1280 x 1024 pixels.

A telepresence system combines two or more endpoints together to create a wider image, simulating the experience of participants being present in the same room. Telepresence systems always designate one of the endpoints as the primary monitor/camera/codec unit, while the remainder are defined as auxiliary or secondary endpoints. This ensures that you can issue commands via a remote control to a single codec base which leads and controls the others to work together as a single telepresence endpoint.


®



109

Glossary

Telepresence - Dual row telepresence room

TLS

Transcoding

UC (Unified

Communications)

Unbalanced

Microphone

Unicast Streaming

URI

URI Dialing

User profile

VFU

VGA

Video Fast Update

(VFU)

Dual row telepresence rooms are large telepresence rooms with two rows of tables that can host up to 18 participants.

TLS enables network devices to communicate securely using certificates, to provide authentication of the devices and encryption of the communication between them.

Transcoding is the process of converting video into different sizes, resolutions or formats. This enables multiple video streams to be combined into one view, enabling continuous presence, as in a typical videoconferencing window.

UC, or unified communications deployments offer solutions covering a wide range of communication channels. These include audio (voice), video, text

(IM or chat), data sharing (presentations), whiteboard sharing (interactive annotations on shared data).

An unbalanced microphone uses a cable that is not especially built to reduce interference when the cable is long. As a result, these unbalanced line devices must have shorter cables to avoid audio disruptions.

Unicast streaming sends a separate stream of a videoconference to each viewer. This is the default method of streaming in Scopia

®

Desktop server.

To save bandwidth, consider multicast streaming.

URI is an address format used to locate a device on a network, where the address consists of the endpoint's name or number, followed by the domain name of the server to which the endpoint is registered. For example,<endpoint name>@<server_domain_name>. When dialing URI between organizations, the server might often be the Avaya Scopia

®

PathFinder server of the organization.

Accessing a device via its

URI

on page 110.

A user profile is a set of capabilities or parameter values which can be assigned to a user. This includes available meeting types (services), access to Scopia

®

Desktop and Scopia

®

Mobile functionality, and allowed bandwidth for calls.

See Video Fast Update (VFU) on page 110.

VGA defines a video resolution of 640 x 480 pixels.

Video Fast Update (VFU) is a request for a refreshed video frame, sent when the received video is corrupted by packet loss. In response to a VFU request, the broadcasting endpoint sends a new intra-frame to serve as the baseline for the ongoing video stream.


®



110

Video Layout


Video Switching

Videoconference

Viewer Portal

Virtual Room

VISCA Cable

Waiting Room

Webcast

WUXGA

Video Layout

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.

See Resolution

on page 106.

See Switched video

on page 109.

A videoconference is a meeting of more than two participants with audio and video using endpoints. Professional videoconferencing systems can handle many participants in single meetings, and multiple simultaneous meetings, with a wide interoperability score to enable a wide variety of endpoints to join the same videoconference. Typically you can also share

PC content, like presentations, to other participants.

The Avaya Scopia

®

Streaming and Recording Viewer Portal is embedded in the Avaya Scopia

®

Desktopuser portal. To access the Viewer Portal, you can select Recordings and Events on the main Scopia

®

Desktop page.

From the Viewer Portal, you can watch recordings and navigate through the categories.

A virtual room in and Scopia

®

Mobile offers a virtual meeting place for instant or scheduled videoconferences. An administrator can assign a virtual room to each member of the organization. Users can send invitations to each other via a web link which brings you directly into their virtual room.

Virtual meeting rooms are also dialed like phone extension numbers, where a user’s virtual room number is often based on that person’s phone extension number. You can personalize your virtual room with PIN numbers, custom welcome slides and so on. External participants can download or Scopia

®

Mobile free to access a registered user's virtual room and participate in a videoconference.

A crossed VISCA cable connects two PTZ cameras to enable you to use the same remote control on both.

A waiting room is a holding place for participants waiting for the host or moderator to join the meeting. While waiting, participants see a static image with the name of the owner's virtual room, with an optional audio message periodically saying the meeting will start when the host arrives.

A webcast is a streamed live broadcast of a videoconference over the internet. Enable Scopia

®

Desktop webcasts by enabling the streaming feature. To invite users to the webcast, send an email or instant message containing the webcast link or a link to the Scopia

®

Desktop portal and the meeting ID.

WUXGA defines a video resolution of 1920 x 1200 pixels.


®



111

Glossary

XGA

Zone

XGA defines a Video resolution of 1024 x 768 pixels.

Gatekeepers like Avaya Scopia

®

ECS Gatekeeper split endpoints into zones, where a group of endpoints in a zone are registered to a gatekeeper. Often a zone is assigned a dial prefix, and usually corresponds to a physical location like an organization's department or branch.


®



112

Avaya Scopia Elite 6000 6105, 6110, 6120, 6140 MCU Administrator Guide

Assistant Bot

Avaya Scopia

Elite 6000 Series MCU

Administrator Guide

Contents

Chapter 1: About the Avaya Scopia

Elite

MCU

About Avaya Scopia

Elite MCU

Minimum Requirements and Specifications

Document changes since last issue

Chapter 2: Planning your MCU Deployment

Deploying Redundant MCUs

Planning a Centralized or Distributed Topology

(Cascading) for MCU

Planning Network Redundancy or IP Separation (Dual NIC)

About the Capacity of the MCU

Ports to Open for the Scopia

Elite 6000 Series MCU

Chapter 3: Securing your Scopia

Elite

MCU

Securing MCU and Scopia

Management Connection with

TLS

Securing MCU with TLS in a SIP Environment

Uploading TLS Certificates to the MCU

Configuring Security Access Levels for the Scopia

Elite

MCU

Configuring IP Separation (Dual NIC) on the Device

Chapter 4: Maintaining the Scopia

Elite

MCU

Adding a License to the MCU

Configuring MCU Meeting Types

Creating a Meeting Type

Configuring the Bandwidth of a Meeting Type

Configuring the Auto-Attendant Service

Managing Scopia

Elite MCU User Profiles

Adding a User Profile

Changing a User Password

Deleting a User Profile

Managing the Redundant Power Supply of the Scopia

Elite MCU

Adding a Power Supply Unit to the MCU

Removing a Power Supply Unit from the MCU

Configuring Ports on All Models of the Scopia

Elite MCU

Configuring the UDP Port Ranges for RTP/RTCP on the Scopia

Elite MCU

Configuring the TCP Port Range for H.245 on the Scopia

Elite

MCU

Configuring the HTTP Port on the Scopia

Elite MCU

Configuring the UDP Port for RAS on the Scopia

Elite MCU

Configuring the UDP Port for the Gatekeeper on the Scopia

Elite

MCU

Configuring the TCP Port Q.931 on the Scopia

Elite MCU

Configuring the TCP/UDP/TLS Port for SIP on the Scopia

Elite

MCU

Configuring the TCP Port Range for SIP BFCP on the Scopia

Elite MCU

Branding your Scopia

Elite MCU User Interface

Customizing the Logo Displayed in MCU Conferences

Customizing MCU Audio Messages

Upgrading, Backing up and Restoring the Scopia

Elite

MCU

Backing Up Your Scopia

Elite MCU Configuration