Avaya Aura® Conferencing Overview and

Specification Guide for Turnkey

Release 8.0.6
April 2016
© 2015-2016, Avaya Inc. YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
All Rights Reserved. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
Notice SERVICE.
While reasonable efforts have been made to ensure that the Licenses
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
the right to make changes and corrections to the information in this WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,
document without the obligation to notify any person or organization UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
of such changes. Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
Documentation disclaimer USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
“Documentation” means information published in varying mediums FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
which may include product information, operating instructions and CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
performance specifications that are generally made available to users AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
of products. Documentation does not include marketing materials. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
Avaya shall not be responsible for any modifications, additions, or AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
deletions to the original published version of Documentation unless WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
such modifications, additions, or deletions were performed by or on AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
the express behalf of Avaya. End User agrees to indemnify and hold RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
harmless Avaya, Avaya's agents, servants and employees against all AND ANYONE ELSE USING OR SELLING THE SOFTWARE
claims, lawsuits, demands and judgments arising out of, or in WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
connection with, subsequent modifications, additions or deletions to USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
this documentation, to the extent made by End User. YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
Link disclaimer SOFTWARE (HEREINAFTER REFERRED TO
Avaya is not responsible for the contents or reliability of any linked INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
websites referenced within this site or Documentation provided by THESE TERMS AND CONDITIONS AND CREATE A BINDING
Avaya. Avaya is not responsible for the accuracy of any information, CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
statement or content provided on these sites and does not APPLICABLE AVAYA AFFILIATE (“AVAYA”).
necessarily endorse the products, services, or information described Avaya grants You a license within the scope of the license types
or offered within them. Avaya does not guarantee that these links will described below, with the exception of Heritage Nortel Software, for
work all the time and has no control over the availability of the linked which the scope of the license is detailed below. Where the order
pages. documentation does not expressly identify a license type, the
Warranty applicable license will be a Designated System License as set forth
below in the Designated System(s) License (DS) section as
Avaya provides a limited warranty on Avaya hardware and software. applicable. The applicable number of licenses and units of capacity
Refer to your sales agreement to establish the terms of the limited for which the license is granted will be one (1), unless a different
warranty. In addition, Avaya’s standard warranty language, as well as number of licenses or units of capacity is specified in the
information regarding support for this product while under warranty is documentation or other materials available to You. “Software” means
available to Avaya customers and other parties through the Avaya computer programs in object code, provided by Avaya or an Avaya
Support website: https://support.avaya.com/helpcenter/ Channel Partner, whether as stand-alone products, pre-installed on
getGenericDetails?detailId=C20091120112456651010 under the link hardware products, and any upgrades, updates, patches, bug fixes,
“Warranty & Product Lifecycle” or such successor site as designated or modified versions thereto. “Designated Processor” means a single
by Avaya. Please note that if You acquired the product(s) from an stand-alone computing device. “Server” means a set of Designated
authorized Avaya Channel Partner outside of the United States and Processors that hosts (physically or virtually) a software application
Canada, the warranty is provided to You by said Avaya Channel to be accessed by multiple users. “Instance” means a single copy of
Partner and not by Avaya. the Software executing at a particular time: (i) on one physical
“Hosted Service” means an Avaya hosted service subscription that machine; or (ii) on one deployed software virtual machine (“VM”) or
You acquire from either Avaya or an authorized Avaya Channel similar deployment.
Partner (as applicable) and which is described further in Hosted SAS License types
or other service description documentation regarding the applicable
hosted service. If You purchase a Hosted Service subscription, the Designated System(s) License (DS). End User may install and use
foregoing limited warranty may not apply but You may be entitled to each copy or an Instance of the Software only: 1) on a number of
support services in connection with the Hosted Service as described Designated Processors up to the number indicated in the order; or 2)
further in your service description documents for the applicable up to the number of Instances of the Software as indicated in the
Hosted Service. Contact Avaya or Avaya Channel Partner (as order, Documentation, or as authorized by Avaya in writing. Avaya
applicable) for more information. may require the Designated Processor(s) to be identified in the order
by type, serial number, feature key, Instance, location or other
Hosted Service specific designation, or to be provided by End User to Avaya through
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA electronic means established by Avaya specifically for this purpose.
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA Named User License (NU). You may: (i) install and use each copy or
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE Instance of the Software on a single Designated Processor or Server
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA per authorized Named User (defined below); or (ii) install and use
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER each copy or Instance of the Software on a Server so long as only
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH authorized Named Users access and use the Software. “Named
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE User”, means a user or device that has been expressly authorized by
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE Avaya to access and use the Software. At Avaya’s sole discretion, a
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED “Named User” may be, without limitation, designated by name,
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON corporate function (e.g., webmaster or helpdesk), an e-mail or voice
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE mail account in the name of a person or corporate function, or a
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY directory entry in the administrative database utilized by the Software
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF that permits one user to interface with the Software.
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT Heritage Nortel Software
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE “Heritage Nortel Software” means the software that was acquired by
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF Avaya as part of its purchase of the Nortel Enterprise Solutions
Business in December 2009. The Heritage Nortel Software is the HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN
software contained within the list of Heritage Nortel Products located WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE
at https://support.avaya.com/LicenseInfo under the link “Heritage OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING
Nortel Products” or such successor site as designated by Avaya. For BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS,
Heritage Nortel Software, Avaya grants Customer a license to use THE AVAYA CHANNEL PARTNER IS REQUIRED TO
Heritage Nortel Software provided hereunder solely to the extent of INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE
the authorized activation or authorized usage level, solely for the AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE,
purpose specified in the Documentation, and solely as embedded in, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER.
for execution on, or for communication with Avaya equipment.
Charges for Heritage Nortel Software may be based on extent of WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
activation or use authorized as specified in an order or invoice.
THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE
Copyright AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES
THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY
Except where expressly stated otherwise, no use should be made of AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729
materials on this site, the Documentation, Software, Hosted Service, CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE
or hardware provided by Avaya. All content on this site, the WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC IS
documentation, Hosted Service, and the product provided by Avaya
LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
including the selection, arrangement and design of the content is THE PERSONAL USE OF A CONSUMER OR OTHER USES IN
owned either by Avaya or its licensors and is protected by copyright WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE
and other intellectual property laws including the sui generis rights VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC
relating to the protection of databases. You may not modify, copy, VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED
reproduce, republish, upload, post, transmit or distribute in any way BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR
any content, in whole or in part, including any code and software WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO
unless expressly authorized by Avaya. Unauthorized reproduction, PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
transmission, dissemination, storage, and or use without the express IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION
written consent of Avaya can be a criminal, as well as a civil offense FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE
under the applicable law. OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
Virtualization WWW.MPEGLA.COM.
The following applies if the product is deployed on a virtual machine. Compliance with Laws
Each product has its own ordering code and license types. Note, You acknowledge and agree that it is Your responsibility for
unless otherwise stated, that each Instance of a product must be complying with any applicable laws and regulations, including, but not
separately licensed and ordered. For example, if the end user limited to laws and regulations related to call recording, data privacy,
customer or Avaya Channel Partner would like to install two intellectual property, trade secret, fraud, and music performance
Instances of the same type of products, then two products of that rights, in the country or territory where the Avaya product is used.
type must be ordered.
Preventing Toll Fraud
Third Party Components
“Toll Fraud” is the unauthorized use of your telecommunications
“Third Party Components” mean certain software programs or system by an unauthorized party (for example, a person who is not a
portions thereof included in the Software or Hosted Service may corporate employee, agent, subcontractor, or is not working on your
contain software (including open source software) distributed under company's behalf). Be aware that there can be a risk of Toll Fraud
third party agreements (“Third Party Components”), which contain associated with your system and that, if Toll Fraud occurs, it can
terms regarding the rights to use certain portions of the Software result in substantial additional charges for your telecommunications
(“Third Party Terms”). As required, information regarding distributed services.
Linux OS source code (for those products that have distributed Linux
OS source code) and identifying the copyright holders of the Third Avaya Toll Fraud intervention
Party Components and the Third Party Terms that apply is available
If You suspect that You are being victimized by Toll Fraud and You
in the products, Documentation or on Avaya’s website at: https://
support.avaya.com/Copyright or such successor site as designated need technical assistance or support, call Technical Service Center
by Avaya. The open source software license terms provided as Third Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
Party Terms are consistent with the license rights granted in these States and Canada. For additional support telephone numbers, see
Software License Terms, and may contain additional rights benefiting the Avaya Support website: https://support.avaya.com or such
successor site as designated by Avaya.
You, such as modification and distribution of the open source
software. The Third Party Terms shall take precedence over these Security Vulnerabilities
Software License Terms, solely with respect to the applicable Third
Party Components to the extent that these Software License Terms Information about Avaya’s security support policies can be found in
impose greater restrictions on You than the applicable Third Party the Security Policies and Support section of https://
Terms. support.avaya.com/security.

The following applies only if the H.264 (AVC) codec is distributed with Suspected Avaya product security vulnerabilities are handled per the
the product. THIS PRODUCT IS LICENSED UNDER THE AVC Avaya Product Security Support Flow (https://
PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A support.avaya.com/css/P8/documents/100161515).
CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE Downloading Documentation
REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC For the most current versions of Documentation, see the Avaya
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A Support website: https://support.avaya.com, or such successor site
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO as designated by Avaya.
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS Contact Avaya Support
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, See the Avaya Support website: https://support.avaya.com for
L.L.C. SEE HTTP://WWW.MPEGLA.COM. product or Hosted Service notices and articles, or to report a problem
with your Avaya product or Hosted Service. For a list of support
Service Provider telephone numbers and contact addresses, go to the Avaya Support
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S website: https://support.avaya.com (or such successor site as
HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT designated by Avaya), scroll to the bottom of the page, and select
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS Contact Avaya Support.
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
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, its licensors, its suppliers, 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.
Java is a registered trademark of Oracle and/or its affiliates.
 Contents

Chapter 1: Introduction............................................................................................................ 7
Purpose.................................................................................................................................. 7
Intended audience................................................................................................................... 7
Related resources................................................................................................................... 7
Documentation.................................................................................................................. 7
Training.......................................................................................................................... 10
Viewing Avaya Mentor videos........................................................................................... 10
Deploying online help....................................................................................................... 11
Support................................................................................................................................ 13
Warranty............................................................................................................................... 13
®
Chapter 2: Avaya Aura Conferencing Turnkey solution overview................................... 14
New features in this release................................................................................................... 16
Automated security.......................................................................................................... 17
Reverse proxy support..................................................................................................... 18
Enhancements for mobile users........................................................................................ 18
VMWare support............................................................................................................. 19
DCS on Linux.................................................................................................................. 20
Video quality................................................................................................................... 20
Server clusters and bandwidth management..................................................................... 20
Increased codec flexibility................................................................................................ 21
Recording enhancements................................................................................................ 22
Cleaner upgrades............................................................................................................ 22
Licensing........................................................................................................................ 22
New mode of operation.................................................................................................... 23
Call me/call someone else............................................................................................... 23
Private chat..................................................................................................................... 23
Multiple association of telephone numbers........................................................................ 24
Collaboration Agent logs.................................................................................................. 24
Avaya Web Collaboration audio and video plug-in.............................................................. 25
Web Sockets................................................................................................................... 26
Simple deployment.......................................................................................................... 27
Turnkey-specific enhancements....................................................................................... 27
Recording data disk encryption......................................................................................... 28
Conference timeout......................................................................................................... 28
Key product features.............................................................................................................. 28
Audio and video conferencing.......................................................................................... 29
Web collaboration............................................................................................................ 30
Conference recording...................................................................................................... 33
Feature comparison......................................................................................................... 34
Key components................................................................................................................... 35

April 2016 Turnkey Overview and Specification 8.0 5

Comments on this document? [email protected]
Contents

Application Server........................................................................................................... 35
Media Server.................................................................................................................. 36
Web Server..................................................................................................................... 43
Document Conversion Server........................................................................................... 43
Conference Recording Server.......................................................................................... 43
Flash Media Gateway...................................................................................................... 44
Avaya Session Border Controller for Enterprise................................................................. 44
Load balancing................................................................................................................ 45
Application Delivery Controller.......................................................................................... 45
Conference features.............................................................................................................. 49
Audio and video conferences........................................................................................... 49
Conference recording...................................................................................................... 53
Collaboration Agent user types......................................................................................... 59
Lecture mode.................................................................................................................. 62
Conference Lock and Unlock............................................................................................ 62
Fast Start........................................................................................................................ 63
Continuation................................................................................................................... 63
Conference profiles......................................................................................................... 63
Conference controls........................................................................................................ 64
Language support................................................................................................................. 69
SNMP support...................................................................................................................... 70
Chapter 3: Interoperability..................................................................................................... 71
Product compatibility.............................................................................................................. 71
Supported endpoints in a Turnkey solution........................................................................ 72
Interoperability matrix............................................................................................................ 73
Avaya Communicator for Microsoft Lync overview.................................................................... 74
Avaya Communicator for Microsoft Lync features............................................................... 75
Telephony and video services with Avaya Communicator for Microsoft Lync......................... 77
Interoperability................................................................................................................ 81
Avaya Aura® Communicator Integration overview.................................................................... 82
Overview........................................................................................................................ 82
Operating system compatibility............................................................................................... 89
Chapter 4: Capacity................................................................................................................ 90
Introduction to capacity.......................................................................................................... 90
Capacity information for bare-metal systems........................................................................... 90
Capacity information for VMWare systems.............................................................................. 92
Glossary................................................................................................................................... 94
Glossary............................................................................................................................. 0

April 2016 Turnkey Overview and Specification 8.0 6

Comments on this document? [email protected]
Chapter 1: Introduction

Purpose
This document describes tested product characteristics and capabilities, including feature
descriptions, interoperability, performance specifications, security, and licensing requirements.

Intended audience
This document is intended for people who want to gain a high-level understanding of the product
features, functions, capacities, and limitations.

Related resources

Documentation
The following table lists the related documents for Avaya Aura® Conferencing. Download the
documents from the Avaya Support website at http://support.avaya.com.
The Avaya Support website also includes the latest information about product compatibility, ports,
and Avaya Aura® Conferencing releases.
Related links
Overview on page 8
Implementation on page 8
Administration on page 9
Reference on page 9

April 2016 Turnkey Overview and Specification 8.0 7

Comments on this document? [email protected]
Introduction

Overview
Document Title Use this document to: Audience
number
04-604343 Avaya Aura® Conferencing Understand the high-level features Customers,
Overview and Specification for and functionality of the product. business
Avaya Aura® partners, and
services and
support personnel
04-604344 Avaya Aura® Conferencing Understand the high-level features Customers,
Overview and Specification for and functionality of the product. business
Turnkey partners, and
services and
support personnel
04-604323 Avaya Aura® Conferencing Understand the high-level features Customers,
Solution Description for Small and functionality of the solution. business
and Medium Enterprises partners, and
services and
support personnel
04-604328 Avaya Aura® Conferencing Understand the high-level features Customers,
Solution Description for and functionality of the solution. business
Medium Enterprises partners, and
services and
support personnel
04-604333 Avaya Aura® Conferencing Understand the high-level features Customers,
Solution Description for Large and functionality of the solution. business
Enterprises partners, and
services and
support personnel

Related links
Documentation on page 7

Implementation
Document Title Use this document to: Audience
number
04-604418 Deploying Avaya Aura® Perform installation and configuration Partners,
Conferencing: Basic tasks. Services, and
Installation Support
personnel
04-604363 Deploying Avaya Aura® Perform installation and configuration Partners,
Conferencing: Advanced tasks. Services, and
Installation and Configuration Support
personnel
04-604353 Upgrading Avaya Aura® Perform upgrading and configuration Partners,
Conferencing tasks. Services, and
Table continues…

April 2016 Turnkey Overview and Specification 8.0 8

Comments on this document? [email protected]
 Related resources

Document Title Use this document to: Audience

number
Support
personnel
04-604403 Migrating Avaya Aura® Perform migration and configuration Partners,
Conferencing tasks. Services, and
Support
personnel

Related links
Documentation on page 7

Administration
Document Title Use this document to: Audience
number
04-604378 Administering Avaya Aura® Perform system-wide administration System
Conferencing tasks. administrators
04-604403 Migrating Avaya Aura® Perform system-wide security System
Conferencing administration and backup/restore administrators
tasks.
04-604398 Maintaining and Perform maintenance and System
Troubleshooting Avaya Aura® troubleshooting tasks. administrators
Conferencing
Understand logs and fault tracking. Partners,
Services, and
Support
personnel
— Avaya Aura® Conferencing Perform system-wide security-related System
Security administration tasks. administrators

Related links
Documentation on page 7

Reference
Document Title Use this document to: Audience
number
04–604423 Avaya Aura® Conferencing Collect information about accounting System
Accounting Records Reference records administrators
Customers,
Partners,
Services, and
Support
personnel
Table continues…

April 2016 Turnkey Overview and Specification 8.0 9

Comments on this document? [email protected]
Introduction

Document Title Use this document to: Audience

number
04-604443 Avaya Aura® Conferencing Collect information about alarms and System
Alarms and Logs Reference logs, including the alarms and logs administrators
families
Customers,
Partners,
Services, and
Support
personnel
04-604444 Avaya Aura® Conferencing Collect information about operational System
Operational Measurements measurements administrators
Reference
Customers,
Partners,
Services, and
Support
personnel

Related links
Documentation on page 7

Training
The following courses are available at http://www.avaya-learning.com. In the Search field, type the
course code, and click Go to search for the course.
Course code Course title
2U00110O Selling Avaya Aura® Conferencing Solution Learning Bytes
2U00325O Avaya Aura® Conferencing 7 L1 Customer Scenario
3U00260W Designing Avaya Aura® Conferencing
5U00120E Avaya Aura® Conferencing
3204 Avaya Aura® Conferencing Implementation and Maintenance Exam

Viewing Avaya Mentor videos

Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya
products.
About this task
Videos are available on the Avaya Support website, listed under the video document type, and on
the Avaya-run channel on YouTube.

April 2016 Turnkey Overview and Specification 8.0 10

Comments on this document? [email protected]
 Related resources

Procedure
• To find videos on the Avaya Support website, go to http://support.avaya.com and perform one
of the following actions:
- In Search, type Avaya Mentor Videos to see a list of the available videos.
- In Search, type the product name. On the Search Results page, select Video in the
Content Type column on the left.
• To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and
perform one of the following actions:
- Enter a key word or key words in the Search Channel to search for a specific product or
topic.
- Scroll down Playlists, and click the name of a topic to see the available list of videos posted
on the website.
Note:
Videos are not available for all products.

Deploying online help

Avaya Aura® Conferencing contains a number of online help files and online manuals to guide you
through the process of installing, configuring, and maintaining your conferencing system. These
online help files include:
• Online help for Element Manager
• Online help for the Provisioning Client
• Online help for Reports
• Online help for users of Collaboration Agent
By default, each of these online help packages is fully integrated with the component which it
describes. So, for example, if you view help on Element Manager, you can access the Element
Manager online help. The Element Manager online help file describes each of the Element Manager
fields and describes many of the common procedures that you can perform using the Element
Manager interface.

April 2016 Turnkey Overview and Specification 8.0 11

Comments on this document? [email protected]
Introduction

Figure 1: Online Help for Element Manager

Figure 2: Online Help for the Provisioning Client

In the case of the online help for users of Collaboration Agent, Avaya has translated the online help
into several languages. The list of available languages conforms with the i18n and L10n
(internationalization and localization standards). When users install the Collaboration Agent
application, it chooses which language to display based on the computer's locale.
The online help files are packaged within the Avaya Aura® Conferencing software application
bundle.

April 2016 Turnkey Overview and Specification 8.0 12

Comments on this document? [email protected]
 Support

Support
Go to the Avaya Support website at http://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you to a
support team if an issue requires additional expertise.

Warranty

April 2016 Turnkey Overview and Specification 8.0 13

Comments on this document? [email protected]
Chapter 2: Avaya Aura® Conferencing
Turnkey solution overview

The Avaya Aura® Conferencing Turnkey solution is a meet me conferencing solution which provides
audio, video, and Web conferencing. The Avaya Aura® Conferencing Turnkey solution provides the
ability to deploy Avaya Aura® Conferencing without the Avaya Aura® stack. The Avaya Aura® PBX
stack refers to staging and management software such as System Platform and System Manager.
With the Avaya Aura® Conferencing Turnkey solution, Avaya Aura® Conferencing can be deployed
with a Private Branch eXchange (PBX) such as Avaya Aura® Communication Manager and Avaya
Communication Server 1000 with a SIP trunk between Avaya Aura® Conferencing and the PBX.
Users can connect to the conference using audio and/or video by way of any of the PBX clients, by
way of Audio Video in Collaboration Agent embedded in Collaboration Agent, or by way of the
Avaya Aura® Conferencing mobile clients. Additionally, users can join Web collaboration using the
Collaboration Agent interface.
Administrators can manage the Avaya Aura® Conferencing components and users using the
Element Manager and Provisioning interfaces. In addition, administrators can bulk provision users
by way of Lightweight Directory Access Protocol (LDAP).
Administrators can deploy the Avaya Aura® Conferencing Turnkey solution on bare metal servers. A
bare metal environment refers to the installation of a server directly on to hardware rather than
within the host operating system. Alternatively, the Avaya Aura® Conferencing Turnkey solution
supports virtualization through VMWare.
This solution is available for all deployment models and so is suited to small to medium (SMB),
medium, and large enterprises.
The installation, upgrade, and patching of the Avaya Aura® Conferencing Turnkey solution is almost
the same as the process of installing, upgrading, and patching the Avaya Aura® Conferencing for
Avaya Aura® solution. Moreover, the Avaya Aura® Conferencing user interfaces are identical. End
users will be unaware of whether their conference bridge is powered by Avaya Aura® or an
alternative PBX.
Note:
Avaya Aura® Conferencing is a conferencing feature server. It is not a registrar or a proxy and
does not provide proxy functions.
Support for cascading
Media cascading reduces the number of media streams travelling across the WAN by consolidating
these streams based by location. This technique is applied to both audio and video streams. Media

April 2016 Turnkey Overview and Specification 8.0 14

Comments on this document? [email protected]
 cascading provides bandwidth optimization with no significant reductions in the quality of audio or
video. Conferences are scalable with proper configuration and management which is fully
transparent to end users. Media cascading is available for event conferences. The combination of
these two features — event conferencing and media cascading — provides a very compelling
solution for very large global conferences.
If the media cascading location and the location of the hosting media server are different, bandwidth
is allocated for the audio media stream to allow for participants joining the conference from other
locations without blocking. Network bandwidth is used to transmit/receive audio media streams to/
from the Hosting Media Server location, although silence suppression significantly reduces the
actual bandwidth received from the hosting location. Video bandwidth for media cascading is only
allocated and consumed when it is required in the conference. When all of the participants have
joined from a single cascading location, video bandwidth between the Cascading Media Server and
the Hosting Media Server is only allocated and consumed if a participant from another location joins
the conference.
Cascading capacity
The following table shows the supported capacity for cascading Avaya Aura® Media Servers for
Avaya Aura® Conferencing.
Capacity Capacity CPUs Memory Storage CPU Speed CPU
(Audio (Video (GB) (GB) (GHZ) Reservatio
Sessions) Sessions n (GHZ)
)
VMware system: 540 160 6 16 150 2.893 17.358
Cascading
Avaya Aura®
Media Servers
(6 vCPUs)
Bare-metal 600 180 6 16 150 6 (12 with N/A
system: hyperthread
ing)
Cascading
Avaya Aura®
Media Servers

April 2016 Turnkey Overview and Specification 8.0 15

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Figure 3: Network Architecture

Related links
New features in this release on page 16
Key product features on page 28
Key components on page 35
Conference features on page 49
Language support on page 69
SNMP support on page 70

New features in this release

These sections describe the new features in this release of Avaya Aura® Conferencing.
Related links
Avaya Aura Conferencing Turnkey solution overview on page 14
Automated security on page 17
Reverse proxy support on page 18
Enhancements for mobile users on page 18
VMWare support on page 19
DCS on Linux on page 20
Video quality on page 20
Server clusters and bandwidth management on page 20
Increased codec flexibility on page 21

April 2016 Turnkey Overview and Specification 8.0 16

Comments on this document? [email protected]
 New features in this release

Recording enhancements on page 22

Cleaner upgrades on page 22
Licensing on page 22
New mode of operation on page 23
Call me/call someone else on page 23
Private chat on page 23
Multiple association of telephone numbers on page 24
Collaboration Agent logs on page 24
Avaya Web Collaboration audio and video plug-in on page 25
Web Sockets on page 26
Simple deployment on page 27
Turnkey-specific enhancements on page 27
Recording data disk encryption on page 28
Conference timeout on page 28

Automated security
In this release, the process of creating and importing security certificates is largely automated. In
previous releases, the process was completely manual and required a large number of steps before
you could provide single sign-on or secure conferencing. If you install Avaya Aura® Conferencing in
an Avaya Aura® deployment, the various Avaya Aura® Conferencing network elements are already
associated with certificates from System Manager. So, initially, System Manager is the certificate
authority (CA). For most deployments, you will not have to perform any additional tasks.
However, if you expand your system with additional network elements after initial installation, you
must create and import certificates for these new network elements. Similarly, if you re-install or
upgrade, you may be required to re-create and re-import certificates. Similarly, if you would like to
use a different Certificate Authority (CA), you must perform some configuration tasks. If you would
like to use a CA other than System Manager, you can easily configure an alternative CA after initial
Avaya Aura® Conferencing installation and verification. The adoption of an alternative CA is
appropriate for certain network elements such as the Web Conferencing Server (WCS) or if any
network elements communicate with another external node such as an LDAP Directory Server that
uses certificates signed by a third party. If you install Avaya Aura® Conferencing in a Turnkey
deployment, you always use an alternative CA because there is no System Manager in your
deployment.
Note:
For more information about Avaya Aura® System Manager, see Administering Avaya Aura®
System Manager, which is available from the Avaya Support website: http://support.avaya.com.
Related links
New features in this release on page 16

April 2016 Turnkey Overview and Specification 8.0 17

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Reverse proxy support

Avaya Aura® Conferencing 8.0 supports reverse proxy servers. Avaya has tested the following
reverse proxies for the 8.0 release.
• The A10 Network AX Series Application Delivery Controller (ADC) provides advanced load
balancing as well as reverse proxy support for Web Collaboration and the Audio/Video in
Collaboration Agent clients.
• The Barracuda Load Balancer Application Delivery Controller (ADC) provides advanced load
balancing and reverse proxy support for Web Collaboration as well as for the Audio/Video in
Collaboration Agent clients.
• Many customers prefer the option of an All-Avaya solution and for this reason, Avaya supports
the deployment of the Avaya Session Border Controller for Enterprise as a reverse proxy
server. When acting as a reverse proxy server, the Avaya Session Border Controller for
Enterprise is limited to 300 calls (for example, 50 conferences with 6 participants in each
conference with 50% screen-sharing and 50% slide-sharing). For this configuration, standard
and advanced session licensing is required for each simultaneous session invoked. In addition,
a mid-range server is required as a minimum, such as the Dell R210 II mid-range server.
This configuration assumes that Avaya Aura® Conferencing is configured with transport layer
security (TLS) enabled for all Web interfaces using server certificates signed by an internal
Certificate Authority (CA). Typically, the internal CA is Avaya Aura® System Manager, or, as in the
case of Turnkey deployments, an alternative CA. For the external side of the ADC, Avaya assumes
that a third party CA, such as Verisign, is used to authenticate external clients.
Related links
New features in this release on page 16

Enhancements for mobile users

Avaya has improved the functionality available to Android and iPhone users. In Avaya Aura®
Conferencing Release 8.0, users can now start or join audio or video conferences from their
smartphones. In addition, they can access a greater number of in-conference features, such as full
roster control.
Note:
Video access is only available for registered users and is not available for guests who have not
registered.
Related links
New features in this release on page 16

April 2016 Turnkey Overview and Specification 8.0 18

Comments on this document? [email protected]
 New features in this release

VMWare support
Virtualization is becoming more prevalent within enterprise business data centers and is seen as a
way to reduce both capital expenditure (capex) and total cost of ownership (TCO). VMware™ is a
leader in virtualization technology and seen as an important platform for Avaya to adopt for its
enterprise solutions. VMware provides centralized management of virtualized hosts and virtual
machines from a single console. It provides a comprehensive suite of tools to help the administrator
monitor and manage their data center.
The Avaya Aura® Conferencing on VMware feature creates images with pre-configured and fully
functional Avaya Aura® Conferencing software which is packaged in the standard template format
(OVA - Open Virtualization Achive) for deploying into the customer’s VMware virtual
infrastructure. Avaya refers to the virtualized Avaya Aura® Conferencing solution as “vAAC”.
In this release, multiple OVAs support the various deployment scenarios:
• vAAC Medium Simplex OVA: AAC RHEL platform + Pre-installed/deployed/configured
application bundle (EM, DB, PROV, WCMS, WCS, AS, AMS, AM, DCS, FMG)
- All NEs are deployed & started automatically.
• vAAC Medium Redundant Primary OVA: AAC RHEL platform + Pre-installed/deployed/
configured Medium Primary application bundle (EM, DB, PROV, WCMS, WCS, AS, AMS, AM,
DCS, FMG)
- All NEs (on Primary instances) are deployed & started automatically.
• vAAC Medium Redundant Secondary OVA: AAC RHEL platform + Pre-installed/deployed/
configured medium secondary application bundle (EM, DB, PROV, WCMS, WCS, AS, AMS,
AM, DCS, FMG)
- All NEs are deployed & started automatically.
• vAAC Platform: AAC RHEL platform + Application Bundle ISO file.
- Avaya Aura® Conferencing platform is installed and started.
- Admin has to run “mcpInstaller” to install AAC NEs.
- During the vAAC Platform OVA deployment, you, as the customer, can select large platform
resources or small platform resources.
Note:
VMware is only supported on medium and large deployments and is not supported on SMB
deployments.
Note:
Use of vMotion for automatic disaster recovery (ADR) is not supported. Instead, you must use
the ADR feature of Avaya Aura® Conferencing.
Note:
For certain deployment configurations, the VMware capacity does not match the bare-metal
capacity. For more information, see Introduction to capacity on page 90.

April 2016 Turnkey Overview and Specification 8.0 19

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Related links
New features in this release on page 16

DCS on Linux
For this release, Avaya is deploying the Document Conversion Server (DCS) as a Network Element
on the Linux platform.
The DCS is required for sharing documents during Avaya Aura® Conferencing conferences. Linux is
a UNIX-like, open-source, operating system. Linux is the leading operating system on most servers.
For this release, Avaya will no longer support the DCS on a Windows operating system. As a result,
if you have an existing older Avaya Aura® Conferencing system, you must migrate the DCS from the
Windows operating system to the Linux operating system.
You can repurpose/reuse the existing Windows server by installing the Linux operating system and
Avaya Aura® Conferencing on it. You can now use this server as a DCS. For SMB and medium
deployments, you have the choice of placing the DCS on the same server hosting the other network
elements, or having it on its own server. For large deployments, the DCS must always be on its own
server.
HTTPS
Currently, Avaya only supports HTTPS connections to the DCS. As a result, you must generate and
assign a certificate for each DCS Network Element.
Automatic migration
Avaya has automated most of the DCS migration tasks. All existing DCS data elements
automatically convert to new DCS Network Elements data objects. Similarly, all current configuration
settings, such as location mapping, automatically convert to the new platform.
Related links
New features in this release on page 16

Video quality
In Avaya Aura® Conferencing Release 8.0, there are a number of significant improvements related
to video quality. The new architecture optimizes bandwidth management which results in a higher
video quality for all users.
Related links
New features in this release on page 16

Server clusters and bandwidth management

Within the Avaya Aura® Conferencing environment, the concept of a ‘cluster’ provides a mechanism
for Avaya Aura® Conferencing administrators to provision a collection of servers as one single

April 2016 Turnkey Overview and Specification 8.0 20

Comments on this document? [email protected]
 New features in this release

server. This mechanism reduces the number of configuration tasks but also maximizes load
balancing between the servers. In this release, Avaya Aura® Conferencing supports the concept of a
media server (MS) cluster and a Web Conferencing Server (WCS) cluster. In this Avaya Aura®
Conferencing release, WCS clusters replace WCS groups from previous releases.
When Avaya Aura® Conferencing chooses which WCS cluster to use for a particular conference, it
uses the following process:
• Avaya Aura® Conferencing checks if there is a WCS cluster provisioned to serve the user
(conference owner) in their location.
• If there are no WCS clusters available in the same location as the user, Avaya Aura®
Conferencing searches for WCS clusters serving the user’s location, and selects the least
loaded WCS from amongst those clusters.
• If there are still no WCS available, Avaya Aura® Conferencing uses the default WCS cluster.
There are additional options available if you wish to ensure that users from a particular location use
the system resources in another location.
Avaya Aura® Conferencing follows this process:
• When it chooses which WCS to use for hosting a conference.
• When it chooses which WCS to use for recording a conference.
• When it chooses which WCS to use for playing back a conference.
• When it chooses which WCS to use for encoding a conference that does not include web
collaboration.
Encoding, within this context, refers to the process of processing a conference recording to convert
it to a playable format. If the conference contains web collaboration, Avaya Aura® Conferencing
uses the hosting server for the encoding process.
Related links
New features in this release on page 16

Increased codec flexibility

In Avaya Aura® Conferencing, the recording function operates by establishing a trunk between the
conferencing media server and the recording media server. You can specify the audio codec for this
trunk.
In addition to the ability to specify the audio codec for the recording trunk, you can now implement
the G.726 codec in your deployment of Avaya Aura® Conferencing. The G.726 codec is also
available for cascading trunks.
Related links
New features in this release on page 16

April 2016 Turnkey Overview and Specification 8.0 21

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Recording enhancements
Codecs
The Increased codec flexibility on page 21 contributes to an improved recording experience for
users. In addition, Avaya Aura® Conferencing Release 8.0 provides increased storage capacity for
recordings and improved contingency in the event of any hardware failures.
Expiration date
Administrators can now set an expiration date for conference recordings. In previous releases,
administrators could set a size threshold for the recordings folder. When the recordings folder
exceeded this threshold, Avaya Aura® Conferencing deleted the recordings. This option is still
available in the current release. In addition, administrators can specify a time period, in days, for the
retention of recordings. When recordings exceed this retention period, Avaya Aura® Conferencing
deletes the recordings. As in previous releases, administrators can choose to backup the recordings
prior to deletion.
Related links
New features in this release on page 16

Cleaner upgrades
In Avaya Aura® Conferencing Release 8.0, Avaya introduces the HP ProLiant DL360p G8. This new
server provides performance improvements and increased redundancy. In this release, Avaya also
introduces a number of new deployment models. These deployment models replace the existing
deployment models and have been designed to simplify the process of installation and upgrade. For
installations and upgrades, customers can now also avail of virtualization which means that they can
perform remote maintenance on their servers. Avaya Aura® Conferencing Release 8.0 includes a
large number of staging files that help to automate some of the more complex configuration tasks,
such as security certificate management.
Related links
New features in this release on page 16

Licensing
Licensing enforcement is a new feature in the Avaya Aura® Conferencing Release 8.0. The
enforcement rules are identical for the Avaya Aura® Conferencing for Turnkey solution and the
Avaya Aura® Conferencing for Avaya Aura® solution.
Avaya uses an application called Web License Manager (WebLM) to manage licenses for Avaya
products. For the Avaya Aura® Conferencing for Turnkey solution, WebLM is installed directly on the
Avaya Aura® Conferencing application server. For the Avaya Aura® Conferencing for Avaya Aura®
solution, WebLM is installed on System Manager. WebLM is managed as a Linux service.

April 2016 Turnkey Overview and Specification 8.0 22

Comments on this document? [email protected]
 New features in this release

For both solutions, a grace period of 30 days exists for upgrades and new installations. Additionally,
new upgrades and installations include a number of default licenses. If the licensing limits are
exceeded, Avaya Aura® Conferencing displays full explanatory error messages to users. Licenses
must be periodically renewed. If they are not renewed, they expire.
The license monitors:
• Maximum number of provisioned audio, video, and web users
• Maximum number of media servers allowed in the Avaya Aura® Conferencing system
• Maximum number of recording Avaya Aura® Conferencing systems
Related links
New features in this release on page 16

New mode of operation

In all previous releases of Avaya Aura® Conferencing, only moderators could start the Web
Collaboration component of a conference. For Avaya Aura® Conferencing 8.0, customers can
choose to retain this mode of operation for their Avaya Aura® Conferencing deployment.
Alternatively, customers can choose to enable a mode of operation in which all participants can start
the Web Collaboration component of a conference. In this alternative mode, typically called
Presentation Mode, all participants have the presenting privileges that were previously available
only after a moderator manually promoted a participant to presenter.
Related links
New features in this release on page 16

Call me/call someone else

The Avaya Aura® Conferencing 8.0 server can dial out to participants and enable them to join the
conference without entering a passcode. This feature enables participants to bring other people into
the conference rapidly. It also enables participants who join a conference online to call their own
telephone from the Collaboration Agent interface. For example, if participants are attending a
standalone web conference (SWC), they can introduce an audio component without separate
verification of credentials. If a participant already has an audio connection to a conference, they can
only dial out to other participants. They cannot dial their own line. This feature is available for all
types of users, including guest users.
Related links
New features in this release on page 16

Private chat
The Messages window contains a list of messages exchanged by conference participants. The
window has a field where you can type or paste text messages with maximum 1024 characters.

April 2016 Turnkey Overview and Specification 8.0 23

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Collaboration Agent displays the participant name and time stamp with each message. You can
send public messages to all participants in conferences or private messages to specific participants.
Avaya Aura® Conferencing does not send historical private messages again if a user rejoins a
conference or joins the conference from another device.
Related links
New features in this release on page 16

Multiple association of telephone numbers

Avaya Aura® Conferencing 8.0 supports multiple association of telephone numbers. This feature
means that users can associate up to 10 numbers with their Avaya Aura® Conferencing profile. This
feature is useful if a user uses several different devices each with different numbers to attend
conferences. Administrators can view the list of associated telephone numbers for each user using
the Avaya Aura® Conferencing Provisioning Manager interface. Administrators can also search this
list and can delete numbers.
Related links
New features in this release on page 16

Collaboration Agent logs

Collaboration Agent can automatically send logs to Avaya when Collaboration Agent detects a
network connectivity issue during a conference. Avaya uses these logs to troubleshoot issues faced
by users.
Collaboration Agent displays a dialog box for users to select whether to send the logs. If users
choose to send the logs, Collaboration Agent opens an email in Microsoft Outlook that contains an
attachment of the Collaboration Agent plug-in logs, which includes all conference events. The email
also contains a list of questions which the users must answer before sending the email.
You can also manually send the logs using the Send logs option in the Information menu on the
Collaboration Agent GUI.
Limitations
• Collaboration Agent supports only Windows-based computers to send logs.
• Collaboration Agent displays a message for Mac-based computers to again log in to the
conference.
• Collaboration Agent supports only Microsoft Outlook to send the email with the details of the
issue.
• Users must install the Collaboration Agent plug-in for the logs feature.
For more information, see Using Avaya Aura® Conferencing Collaboration Agent at the Avaya
Support website: http://support.avaya.com/.

April 2016 Turnkey Overview and Specification 8.0 24

Comments on this document? [email protected]
 New features in this release

Related links
New features in this release on page 16

Avaya Web Collaboration audio and video plug-in

In this release of Avaya Aura® Conferencing, there is a new Web-based audio and video client. This
client is a browser plug-in which executes within the Web Collaboration Agent client. It enables
users to receive their audio and video through the Web. This functionality means that users do not
have to dial into the conference using a phone connection. The client is available for all deployment
types and can operate seamlessly with other supported clients. Avaya are delivering this feature as
a browser plug-in. In previous releases, Avaya delivered a similar but inferior feature using a Flash-
based client. The newly enhanced browser plug-in offers an improved audio and video experience
and a more intuitive user interface. The older client is still available as part of the software bundle
and existing installations can still continue to use the older client. However, Avaya recommends
upgrading to the new client for a superior user experience.
For Avaya Aura® Conferencing turnkey deployments, it is likely that most users will receive their
audio and video using the new client.
You can control access to the plug-in at a system level. Using this system parameter, you can
enable or disable access for all users in your deployment. In addition to this system-wide setting,
you can also control access to the Avaya Web Collaboration audio and video plug-in at a user level,
by configuring a class of service. For example, you may want to offer the plug-in to some users but
not to others. If you enable access to the Avaya Web Collaboration audio and video plug-in, you can
choose to inform users of its availability immediately after they join the conference or you can
choose not to inform them. If you choose to inform them, Avaya Aura® Conferencing displays a
menu and if you choose not inform them, Avaya Aura® Conferencing hides this menu.
If you wish to offer this form of integrated audio and video to external users who reside outside of
the enterprise, you must install and configure a Session Border Controller (SBC).
Related links
New features in this release on page 16
Web browsers and operating systems that the audio and video conferencing plug-in supports on
page 25
Ability to modify the post-login user experience on page 26

Web browsers and operating systems that the audio and video
conferencing plug-in supports
Web browsers
Web browsers supported Web browsers not supported
• Mozilla Firefox version 10 and later on Apple OS X • Microsoft Internet Explorer for Microsoft Metro
and Windows • Microsoft Edge
• Microsoft Internet Explorer 8 and later on Windows • Opera
• Any 64–bit version of browsers

April 2016 Turnkey Overview and Specification 8.0 25

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Web browsers supported Web browsers not supported

• Apple Safari latest version for Apple OS X • All other mobile browsers
• Google Chrome on Apple OS X and Windows

Operating systems
Operating systems supported Operating systems not supported
• Windows 7, 32–bit and 64–bit • Older versions of Windows, such as Windows XP
• Windows 8, 32–bit and 64–bit • Android
• Windows 10, 32–bit and 64–bit • iOS
• Apple OS X 10.7 and later • Linux
• Windows Mobile

Limitations of the audio and video conferencing plug-in

• The audio and video conferencing plug-in supports only the 32–bit version of web browsers.
• The enterprise network must have a session border controller deployed to support participants
who log in to an integrated audio and video conference from outside the network.
Related links
Avaya Web Collaboration audio and video plug-in on page 25

Ability to modify the post-login user experience

You can control the experience for users immediately after they login, using a conference class of
service parameter. By default, immediately after they enter a conference, Avaya Aura® Conferencing
displays an alert pop-up to users. This pop-up displays a number of access options for users. Using
this pop-up, users can choose to connect to the conference using the Avaya Web
Collaboration audio and video plug-in, or they can prompt the Avaya Aura® Conferencing system to
dial them, or if they are already dialed into the system, they can associate their online identifier with
their telephone identifier. As an administrator, you can control whether this pop-up is displayed or
hidden.
Related links
Avaya Web Collaboration audio and video plug-in on page 25

Web Sockets
Avaya Aura® Conferencing 8.0 supports the Web Socket standard. Previous versions of Avaya
Aura® Conferencing used HTTP-based request/response support using standard and non-standard
HTTP and HTTPS based ports. The HTTP approach had limited scalability, excessive resource
load, and response latencies. To address these limitations, Avaya Aura® Conferencing 8.0 uses
Web Sockets to provide a new mechanism for client-server interaction that provides a full-duplex
communication channel that starts off as a HTTP connection that is then upgraded to a regular TCP

April 2016 Turnkey Overview and Specification 8.0 26

Comments on this document? [email protected]
 New features in this release

channel. Web Sockets also supports cascading by communicating with remote servers. Web
Sockets provides the following collaboration benefits:
• Remote control during document sharing in Collaboration Agent
• Live drawing on the whiteboard, rather than ‘mouse-up’ updates
• Improvements in screen sharing performance
• Whiteboard and meeting minutes functionality for mobile devices
Related links
New features in this release on page 16

Simple deployment
Flexible deployment: Large platform resources or small platform resources
For this release, Avaya created two platform OVAs (vAAC_LargePlatform and
vAAC_SmallPlatform):
• vAAC_LargePlatform OVA‘s vCPU and memory resources: 12 vCPUs (100% reserved), 30 GB
Memory (100% reserved)
• vAAC_SmallPlatform OVA’s vCPU and memory resources: 6 vCPUs (100% reserved), 16 GB
Memory (100% reserved)
With the exception of the OVA vCPU and memory resource configuration and reservation, all other
parameters were the same for these OVAs. These two OVAs were two different entities, which the
customer had to download.
For this release, Avaya simplified the two platform OVAs by introducing a flexible deployment
feature. Now, there is a single platform OVA. During the platform OVA deployment, the wizard
prompts customers to select the deployment configuration. There are two deployment configuration
options:
• Large Platform Resources
• Small Platform Resources
With this feature, customers can choose difference resource configuration during the OVA
deployment. The Large Platform Resources option is compatible with the Large Platform OVA
deployment from previous releases. The Small Platform Resources option is compatible with the
Small Platform OVA deployment from previous releases.
Related links
New features in this release on page 16

Turnkey-specific enhancements
Avaya Aura® Conferencing now supports the use of mobile devices and enhanced Audio Video in
Collaboration Agent in a Turnkey deployment. Specifically, users on mobile devices located outside
of the enterprise network can attend Avaya Aura® Conferencing conferences on their devices. In
addition, users located outside of the enterprise network can access the enhanced Audio Video in

April 2016 Turnkey Overview and Specification 8.0 27

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Collaboration Agent plug-in. This offering requires the installation and configuration of a Session
Border Controller (SBC).
Related links
New features in this release on page 16

Recording data disk encryption

Avaya Aura® Conferencing 8.0.6 now supports the ability to encrypt the recording data disk. If the
recording data disk is stolen, the recordings will be inaccessible.
Related links
New features in this release on page 16

Conference timeout
Conferences consume Avaya Aura® Conferencing system resources. If conferences are left open,
and there are no participants in attendance, Avaya Aura® Conferencing system resources are still
being consumed. For this reason, administrators can configure a conference timeout. This setting
prompts the system to check for empty or low-attendance conferences and to close them. Using the
Element Manager interface, administrators can configure X and Y. X is the number of hours after
which a conference closes if there are fewer than Y participants still in the conference.
Related links
New features in this release on page 16

Key product features

Avaya Aura® Conferencing comprises the following key features:
• Audio and video conferencing
• Web collaboration
Related links
Avaya Aura Conferencing Turnkey solution overview on page 14
Audio and video conferencing on page 29
Web collaboration on page 30
Conference recording on page 33
Feature comparison on page 34

April 2016 Turnkey Overview and Specification 8.0 28

Comments on this document? [email protected]
 Key product features

Audio and video conferencing

Avaya Aura® Conferencing works in tandem with Avaya Aura® Media Server to support different
audio codecs, such as G.711, G.722, G.726, and G.729, and video codecs, such as H.264 SVC and
AVC for conferencing. Avaya Aura® Conferencing also supports different classes of service for audio
and video conferencing to ensure that the best quality of audio and video classes are chosen for a
conference based on the available bandwidth.
Avaya Aura® Conferencing supports single stream and continuous presence video conferences. In
continuous presence video conferences, users can receive up to eight video streams of the last four
active speakers on the conference. Avaya Aura® Conferencing also supports conferencing features
and events such as muting audio, muting video, muting audio and video, and muting all participants
except Presenter.
Language support
The audio message prompts are available in a number of languages.
SIP signaling and a Locale setting for conference access numbers are used to determine the
primary language for audio prompting.
When the accept-language attribute is present in the SIP signaling of a call to Avaya Aura®
Conferencing, the language specified in this attribute is used, if it matches one of the supported
languages. Otherwise, the Locale setting determines the language to be used. Note that the
language used for web browser content is determined by the user’s browser locale settings.
After the conference has started, the language of general announcements is determined by the
Locale provisioned for the conference moderator.
This Locale can be one of the G13 language set, which includes the following languages:
• English (United States)
• Chinese (Simplified)
• Japanese (Japan)
• Korean (Korea)
• French (France)
• German (Germany)
• Italian (Italy)
• Russian (Russia)
• English (United Kingdom)
• Spanish (Mexico)
• Portuguese (Brazil)
• French (Canada)
• English (Canada)
The following sections describe the different type of conferences that Avaya Aura® Conferencing
supports based on the requirements of users.

April 2016 Turnkey Overview and Specification 8.0 29

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Related links
Key product features on page 28
MeetMe conferencing on page 30
Event conferencing on page 30

MeetMe conferencing
MeetMe conferencing supports audio, video, and Web collaboration. MeetMe conferencing is used
for planned meetings where the meeting owner distributes the conference number and the
participant access code before the scheduled conference.
With MeetMe conferencing, a user can host a conference call using pre-configured conference
access codes. The system administrator provisions one or more MeetMe SIP addresses and
telephone numbers.
Conference participants can join a MeetMe conference by dialing the MeetMe SIP address or the
telephone number. Each conference participant dials a participant access code to connect to the
conference. This access code is unique for each conference. Moderator has a unique moderator
access code for the MeetMe conference which identifies Moderator as the host of the conference.
Related links
Audio and video conferencing on page 29

Event conferencing
Event conferencing is used by enterprises to conduct large conferences that involve a large number
of participants. Event conferences have the following unique characteristics:
• The audio of all participants in the conference are always muted. Moderator enables the audio
of a participant who requests permission to speak by virtually raising a hand.
• The conference stays active until a Presenter is logged in to the conference.
• Presenters join the conference with a separate access code which identifies these participants
as Presenters. This access code ensures that the audio of Presenters is not muted.
• Participants view a limited roster that lists Presenters and the participants who have speaking
privileges. Moderator views the entire roster. Presenters can view requests to speak from the
participants who virtually raise a hand.
• Entry and exit tones are disabled.
Related links
Audio and video conferencing on page 29

Web collaboration
Web collaboration tools support management of Web conferences and participation in these Web
conferences. Through Web conferencing tools, you can:
• Join a Web conference by clicking the Collaboration Agent URL and entering your
authentication credentials.

April 2016 Turnkey Overview and Specification 8.0 30

Comments on this document? [email protected]
 Key product features

• Join only the audio conference of a Web conference through a telephone by dialing the
MeetMe conference number.
• View the roster of conference participants in Collaboration Agent.
• Use conference controls, such as virtually raising a hand, to seek permission to ask a question
or talk to the presenter.
Avaya Aura® Conferencing supports Web collaboration through Collaboration Agent.
For more information about Collaboration Agent, see Using Avaya Aura® Conferencing
Collaboration Agent at the Avaya Support website: http://support.avaya.com.
Related links
Key product features on page 28
Collaboration Agent on page 31

Collaboration Agent
Collaboration Agent is an application that provides web collaboration and conferencing tools. Users
with Avaya Aura® Conferencing accounts and invited guests can use the tools to manage
conferences and participate and collaborate in conferences.
Conference participants can join conferences by logging in to Collaboration Agent and dialing in to
the audio bridge assigned to the conference. Participants can also use the integrated audio and
video feature of Collaboration Agent. Participants can use the Collaboration Agent tools to boost
productivity and track action items even after the conference ends. Conference moderators can:
• Record all aspects of conferences.
• Record and edit meeting minutes.
• Create and distribute meeting reports based on the meeting minutes.
Collaboration Agent features
In Collaboration Agent, the participants and moderators can perform multiple tasks such as:
• View a list of other participants.
• Virtually raise a hand and seek permission to speak.
• Send messages.
• Annotate shared content.
• Record or edit minutes.
• Set the entry and exit tones.
• Dial out to other users and the users to the conference.
• Disconnect participants.
• Promote participants to the moderator role.
• Invite more participants to join an active conference.

April 2016 Turnkey Overview and Specification 8.0 31

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

During the conference, participants can view the following information in Collaboration Agent:
• The participants who joined only on the audio bridge
• The participants active on web collaboration
• The participant currently speaking
• The current presenter
Optional features
The following features are optional and must be enabled by the system administrator:
• Starting conferences before moderators join.
• Integrated video
• Promoting all participants to the presenter role so that all participants can share content
• Dialing out from Collaboration Agent to connect users to conferences
• Conference recording
Related links
Web collaboration on page 30
Collaboration Agent Permanent Association on page 32
Collaboration Agent customization on page 32
Collaboration Agent plug-in on page 33

Collaboration Agent Permanent Association

Collaboration Agent displays two entries in the roster for users logging in through Collaboration
Agent and a PSTN phone. With the Collaboration Agent Permanent Association feature, users
associate Collaboration Agent and the number of the PSTN phone to appear as a single entry.
This association also applies to actions such as muting. The muting feature in Collaboration Agent
does not mute the audio of the PSTN phone.
Related links
Collaboration Agent on page 31

Collaboration Agent customization

Enterprise users can choose to customize the login screens of Collaboration Agent with the
enterprise brand and colors.
Avaya can customize Collaboration Agent by replacing:
• The Avaya log with the enterprise logo.
• The Avaya Aura® brand in the Collaboration Agent name with the enterprise brand.
• The background color with the color of the enterprise brand.
Related links
Collaboration Agent on page 31

April 2016 Turnkey Overview and Specification 8.0 32

Comments on this document? [email protected]
 Key product features

Collaboration Agent plug-in

The Web collaboration feature of Collaboration Agent requires a Java applet for desktop sharing.
Because of the recent modifications to Web browsers by developers to resolve security
vulnerabilities, your Web browser might block Collaboration Agent from invoking the Java applet.
With the Collaboration Agent plug-in, Collaboration Agent does not require the Java applet for
desktop sharing.
Collaboration Agent prompts you to install the plug-in when you share your desktop for the first time.
If you do not install the plug-in, Collaboration Agent prompts you to install the plug-in again when
you share your desktop the next time, and continues to use the Java applet for desktop sharing. If
you face issues with desktop sharing without the plug-in, you have the option to resolve the Java-
related issues on your computer or install the plug-in.
You can also manually install the plug-in by clicking Download Collaboration Plugin from the
Begin sharing options. For more information about installing the Collaboration Agent plug-in, see
Using Avaya Aura® Conferencing Collaboration Agent at the Avaya Support website: http://
support.avaya.com.
Related links
Collaboration Agent on page 31

Conference recording
Capacity
How many hours of storage do the recording server(s) provide?
In terms of recording hours, capacity is a function of what is being recorded. The best case is audio-
only and the worst case is audio with screen sharing with lots of movement. The table below defines
the recording capacity per recording server. You can deploy multiple recording servers. The key
here is that one recording server is permitted per location (physical or virtual). Users are assigned to
a particular recording server based on their location as defined within Avaya Aura® System Manager
or a Turnkey equivalent. Older releases of Avaya Aura® Conferencing supported the 900Gbyte
server. Newer releases of Avaya Aura® Conferencing introduce optional support for a 1.8Tbyte
server.
Table 1: Capacity

Type of Media Format Size (MB/Hour) Capacity on the Capacity on the

1.8Tbyte system 900Gbyte system
(Hours) (Hours)
Audio Only Recording mp3 40 45000 22000
Audio + Web (50% slides swf 72 25000 12000
50% screen share)
Audio + Web (100% screen swf 105 17000 8000
share, with movement)

April 2016 Turnkey Overview and Specification 8.0 33

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Archives
How are archived recordings, that are stored to external storage, accessed and
retrieved? Through the application, directly from the external storage?
In terms of archiving and playback:
• Users can view recordings using the Avaya Aura® Conferencing playback infrastructure, by
reaching the recording by way of the URL
• Administrators can configure the backup schedule to automatically backup the recordings daily
to the external system.
• Administrators can restore the recordings by choosing from several options: Restore a single
recording, all recordings for a given user, or all recordings in the backup folder
• Users can download the recording as audio (.mp3) or audio+web (.swf) and store it anywhere.
• You cannot view recordings that are not in the recording media server, even if they are
archived. To view them again, you must restore them.
Note:
These downloads don’t have the robust playback capabilities of the native Avaya Aura®
Conferencing playback experience e.g. time line, activity stream, and so on.
Related links
Key product features on page 28

Feature comparison
Visually, for end users, there is no difference between the Avaya Aura® Conferencing for Turnkey
and Avaya Aura® Conferencing for Avaya Aura® solutions. The graphic user interfaces (GUIs) are
identical, in terms of branding and screen layout.
For the most part, a parity of features exists across the Avaya Aura® Conferencing for Turnkey and
Avaya Aura® Conferencing for Avaya Aura® solutions. Both solutions provide access to a wide
variety of conference-related features which have evolved over a number of releases. However, the
Avaya Aura® Conferencing for Turnkey solution is unable to support a limited number of features.
These features are as follows:
• Advanced bandwidth management (call admission control is not supported in this context)
• Disaster recovery
Adhoc conferencing, in this context, refers to the ability to book conferences using the Dual Tone
Multi-frequency (DTMF) keys on the telephone keypad. The Avaya Aura® Conferencing for Turnkey
supports meet me conferencing, event conferencing, and standalone web conferencing.
Switching to an Avaya Aura® solution
It is possible to migrate from a Turnkey solution to an Avaya Aura® solution by changing some
settings. There is no need to re-install the system or to upgrade it. The full steps for this migration
are available on https://support.avaya.com/. To complete the migration, some additional provisioning
will be required on System Manager.

April 2016 Turnkey Overview and Specification 8.0 34

Comments on this document? [email protected]
 Key components

Related links
Key product features on page 28

Key components
Avaya Aura® Conferencing consists of the following key components:
• Application Server
• Avaya Aura® Media Server
• Web Server
• Document Conversion Server
• Conference Recording Server
• Flash Media Gateway
• Session Border Controller
Depending on the deployment layout of an enterprise, some or all of these components might be co-
resident on one server or deployed on separate servers.
Related links
Avaya Aura Conferencing Turnkey solution overview on page 14
Application Server on page 35
Media Server on page 36
Web Server on page 43
Document Conversion Server on page 43
Conference Recording Server on page 43
Flash Media Gateway on page 44
Avaya Session Border Controller for Enterprise on page 44
Load balancing on page 45
Application Delivery Controller on page 45

Application Server
Application Server is a functionally-rich SIP collaboration server which provides an audio, video, and
Web collaboration session control software engine. Application Server is highly scalable and
supports high availability and:
• Hosts the MeetMe, Adhoc, and Event conference applications.
• Processes the SIP signals from clients.
• Supports advanced client integration for the SIP events defined in RFC 4579, RFC 4575, and
CCMP.

April 2016 Turnkey Overview and Specification 8.0 35

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

The functions of Application Server also include management and optimization of bandwidth usage
and selection of the Media Server for cascading.
Related links
Key components on page 35

Media Server
Avaya Aura® Media Server processes the audio and the video media streams of a conference,
including voice mixing. Media Servers can be distributed across different enterprise locations to
provide bandwidth optimization that is aligned with the enterprise network topology. Application
Server controls Media Server.
Media Server supports the following codecs:
• Audio: G.711, including the μ-law and the A-law algorithms, G.722, G.729, and G.726.
• Video: H.264, including AVC and SVC.
Related links
Key components on page 35
Avaya Aura Media Server selection on page 36

Avaya Aura® Media Server selection

Avaya Aura® Media Servers are deployed in Media Server clusters that are associated with physical
locations. All Avaya Aura® Media Servers within a cluster have identical capabilities. These
capabilities include IVR and hosting and cascading functions that Avaya Aura® Conferencing
controls through MSML and SIP signaling.
Session Manager (or your Turnkey equivalent) and Avaya Aura® Conferencing must be provisioned
with all the locations in a network. All conference sessions must be associated with a location in the
network either through network address mapping or by provisioning the SIP Entity Location field in
Session Manager.
Note:
Avaya Aura® Conferencing cannot manage the sessions that are not associated with a location.
If bandwidth management is enabled, Avaya Aura® Conferencing blocks these sessions.
Related links
Media Server on page 36
Avaya Aura Media Server algorithms on page 36

Avaya Aura® Media Server algorithms

Use Avaya Aura® Media Server selection algorithms to select Media Servers for the various roles in
a conference. A Media Server can have different roles for various conferences at any time. For
example, an Avaya Aura® Media Server can act as an IVR Media Server for one conference, a
Hosting Media Server for another conference, and also a Cascading Media Server for another. You

April 2016 Turnkey Overview and Specification 8.0 36

Comments on this document? [email protected]
 Key components

create Media Server clusters from the Avaya Aura® Conferencing Element Manager Server and
assign a physical location, one or more serving locations and hosting locations in the Avaya Aura®
Conferencing Provisioning Client. During conference creation, the user location and Avaya Aura®
Media Server configuration and state are examined to determine the appropriate Media Server
cluster for Avaya Aura® Conferencing to use. Server selection can be one of the following:
• Media Server selection by location
• IVR Media Server selection
• Hosting and cascading Media Server selection
Related links
Avaya Aura Media Server selection on page 36
Avaya Aura Media Server selection by location on page 37
Avaya Aura Media Server by load factor on page 38
IVR Media Server selection on page 39
Hosting and cascading Media Server selection on page 40

Avaya Aura® Media Server selection by location

There can be numerous scenarios that require consideration for optimal selection of a Media Server
for a given location while allowing the pooling of server resources between locations.
For example, it is preferable from a bandwidth utilization perspective for a new participant to use the
Media Server that is physically located at the same location. However, if local resources are not
available, a Media Server with the lowest load factor that is servicing the location of the participant is
selected. This is a common selection algorithm for finding the optimal Media Server for a specified
location.
The following flowchart shows the logic used to select the optimal Media Server for a specified
location during IVR and hosting Media Server selection.

April 2016 Turnkey Overview and Specification 8.0 37

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Figure 4: Media Server selection by location

Related links
Avaya Aura Media Server algorithms on page 36

Avaya Aura® Media Server by load factor

Avaya Aura® Conferencing uses the Avaya Aura® Media Server load factor and the number of
sessions on the Avaya Aura® Media Server to determine the optimal server to host a conference.
Any Avaya Aura® Media Server that meets the following criteria is a candidate:
• operational
• unlocked
• has a load factor of less than 70
• is available to the cluster at the target location
Avaya Aura® Conferencing maintains an ordered list of Avaya Aura® Media Servers by issuing an
OPTIONS request to the Avaya Aura® Media Server every five seconds to request the load factor to
keep the order up to date.
Avaya Aura® Conferencing uses the following algorithm to select the Avaya Aura® Media Server: For
load factors greater than zero, the algorithm is (70 / [load factor] * [number of sessions]) - [number of
sessions]. The results are stored against the Avaya Aura® Media Server from high to low.

April 2016 Turnkey Overview and Specification 8.0 38

Comments on this document? [email protected]
 Key components

Note:
The first Avaya Aura® Media Server in this list is the least loaded.
For example, to determine the least loaded Avaya Aura® Media Server see the following table.

Table 2: Example calculation to determine load factor

Avaya Aura® Media Server A Avaya Aura® Media Server B

Sessions: 1000 900
Load Factor: 35 33
Calculation: (70 / [35] * [1000]) - [1000] = [1000] (70 / [33] * [900]) - [900] = [1009]
®
Therefore, Avaya Aura Media Server B is the least loaded

Related links
Avaya Aura Media Server algorithms on page 36

IVR Media Server selection

The IVR Media Server is selected from the current location of the caller which is extracted from the
initial INVITE message.
Note:
If the initial INVITE from a participant already has the conference access code embedded, the
IVR Media Server is not required and the participant is redirected to a Hosting Media Server or
Cascading Media Server.
The following figure shows the algorithm used to select the IVR Media Server upon arrival of a new
client or participant.

April 2016 Turnkey Overview and Specification 8.0 39

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Figure 5: IVR Media Server selection

Related links
Avaya Aura Media Server algorithms on page 36

Hosting and cascading Media Server selection

A hosting Media Server is a logical role for mixing audio, selection of the current Active Speaker and
top-level handling of SVC video media streams/layers for the overall conference call.
The target conference is identified after the IVR session. Selection of the hosting Media Server is
based on the configuration of the conference moderator. For example:
• The hosting Media Server for an existing conference is found by entering the participant or
moderator code and running a search for an existing conference with the participant or
moderator code information. If media cascading is disabled for the domain, location, or
conference number of the new participant then the new participant is redirected to the existing
hosting Media Server.

April 2016 Turnkey Overview and Specification 8.0 40

Comments on this document? [email protected]
 Key components

• The hosting Media Server for a new conference is based on the provisioned location of the
conference moderator. This can be different than the moderator's current physical location due
to the moderator being at a different physical location than usual or because centralized Media
Servers are configured due to site bandwidth limitations.
To select the hosting Media Server, determine the preferred hosting location. This location is then
used to select a Media Server using the Media Server selection algorithm.
The following figure shows the algorithm used to select the hosting Media Server upon arrival of a
new client or participant.

Figure 6: Hosting Media Server selection flow

After the hosting Media Server has been selected, a cascading Media Server can be required.

April 2016 Turnkey Overview and Specification 8.0 41

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

The following figure shows the algorithm used to select the cascading Media Server upon arrival of
a new client or participant to a conference.
Note:
The cascading Media Server selected must be at the same physical location as the participant
in order to minimize WAN bandwidth. If there is no available local server, cascading cannot
occur. The participant is redirected to the hosting Media Server.

Figure 7: Cascading Media Server selection

Related links
Avaya Aura Media Server algorithms on page 36

April 2016 Turnkey Overview and Specification 8.0 42

Comments on this document? [email protected]
 Key components

Web Server
Web Server is a solution component that supports content sharing through Collaboration Agent or
from supported clients such as Avaya Web Collaboration Agent, Avaya Web Collaboration Agent for
iOS, and Avaya Web Collaboration Agent for Android.
Related links
Key components on page 35

Document Conversion Server

Document Conversion Server is a Linux-based server that converts Microsoft Word, Microsoft Excel,
Microsoft PowerPoint, PDF, and TXT files into a format for content sharing through Web
collaboration.
The administrator sets up Document Conversion Server as a network element. The administrator
can also create clusters of Document Conversion Server which improves the scalability of the
server.
In a large Avaya Aura® Conferencing deployment, the Document Conversion Server is deployed for
each location and there is no default server or failover support. In an SMB or medium deployment,
the Document Conversion Server is bundled in the offer as a network element.
Related links
Key components on page 35

Conference Recording Server

The Conference Recording Server is a Media Server which records conferences and stores these
recordings. You can have either one or two servers for recordings. You cannot have more than two
servers. You can configure these server clusters for the conferencing function, for the recording
function, or for the combined function of conferencing and recording.
• The SMB and medium deployment layouts support the Media Server clusters for conferencing
and recording conferences.
• The large deployment layout requires a dedicated Media Server for recording conferences to
ensure enhanced storage capacity.
Note:
Conference Recording Server is an optional server with the optional Conference Recording
feature.
Related links
Key components on page 35

April 2016 Turnkey Overview and Specification 8.0 43

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Flash Media Gateway

Flash Media Gateway supports the Audio/Video in Collaboration Agent feature to provide integrated
audio and video in Collaboration Agent to users located outside the enterprise network. These users
can log in to a conference through a Web browser and use the Flash-based features of the browser
that support audio and video in Collaboration Agent.
Flash Media Gateway supports communications between the clients in the Flash domain using
RTMP and the network elements in the multimedia domain using SIP and RTP.
Note:
Flash Media Gateway is an optional server with the optional Audio/Video in Collaboration Agent
feature.
Related links
Key components on page 35

Avaya Session Border Controller for Enterprise

Avaya Aura® Conferencing supports the deployment of a session border controller (SBC) between
the enterprise network and the endpoints. You must deploy the SBC only at the edge of the
enterprise network between the Avaya Aura® Conferencing network and Session Manager or
Turnkey equivalent. In the case of a Turnkey deployment, the SBC communicates directly with the
Avaya Aura® Conferencing (AAC) server. Avaya has tested and recommends the Avaya Session
Border Controller for Enterprise (also known as the Sipera SBC) for use with Avaya Aura®
Conferencing.
Avaya Aura® Conferencing supports the deployment of the SBC as a client application on the
enterprise network. In this scenario, you do not need to administer Session Manager through
System Manager, but you must add the IP address of the internal interface of SBC to the SIP
firewall of Session Manager.
Avaya Aura® Conferencing supports the following different options to deploy the SBC. These
deployment methods are not specific to the SBC, but are similar to administering a SIP entity. You
can:
• Deploy the SBC as a client application on the enterprise network. In this scenario, you do not
need to administer Session Manager through System Manager, but you must add the IP
address of the internal interface of the SBC to the SIP firewall of Session Manager.
• Administer a SIP trunk between the SBC and Session Manager. In this scenario, you must
administer the SIP trunk on Session Manager, and add the SBC SIP entity to the SIP firewall of
Session Manager. For a Turnkey deployment, in which there is no Session Manager, Avaya
Aura® Conferencing (AAC) communicates directly with the SBC by way of a SIP trunk.

April 2016 Turnkey Overview and Specification 8.0 44

Comments on this document? [email protected]
 Key components

Turnkey deployments
In an Avaya Aura® deployment, the SBC communicates with Session Manager and System
Manager. In a Turnkey deployment, the SBC communicates directly with the Avaya Aura®
Conferencing (AAC) server. The configuration of a Turnkey solution is largely the same as the
configuration for an Avaya Aura® solution. Instead of pointing towards Session Manager and System
Manager, the SBC in a Turnkey deployment points directly to the AAC and the AAC points directly
to the SBC.
Use the links above to see the steps involved.
Related links
Key components on page 35

Load balancing
For Avaya Aura® Conferencing, load-balancing is supported through the use of more than one
server for a particular purpose. For example, you could have more than one Web Conferencing
Server (WCS) or you could have more than one Document Conversion Server (DCS) or you could
have more than one media server. The WCS hosts web conferences. The DCS converts files for
sharing online. The media server provides a number of functions, such as, audio/video mixing, Dual
Tone Multi Frequency (DTMF) detection, and message playing. In times of heavy system usage, a
single WCS might become overloaded. Similarly, if large numbers of users are converting files at the
same time, a single DCS might reach capacity. The same is true for a single media server. For these
situations, it is a good idea to share the load across multiple WCSs or multiple DCSs or multiple
media servers. If the first server is full, the traffic can automatically go to another available server.
Related links
Key components on page 35

Application Delivery Controller

Avaya recommends an ADC for providing external access as well as for providing load balancing for
redundant and large deployments. Figure 1 shows an example deployment with redundancy.

April 2016 Turnkey Overview and Specification 8.0 45

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Figure 8: External ADC Deployment

You can deploy an additional ADC in the enterprise network if further traffic separation is required as
shown in Figure 2.

Figure 9: Internal/External ADC Deployment

One of the key benefits of using an ADC in the solution is that the number of firewall rules required
is greatly reduced, simplifying configuration and maintenance of the solution. Additional features
such as DDoS protection and Web Application Firewalls (WAF) common on ADCs can be used to

April 2016 Turnkey Overview and Specification 8.0 46

Comments on this document? [email protected]
 Key components

enhance the defense-in-depth security of the deployment. Please refer to the specific ADC vendor
documentation on how to tune these features for your deployment such that service is not impacted.
Minimum Requirements
The follow are the minimum requirements when choosing an ADC to use with Avaya Aura®
Conferencing:
• 1 Gigabit throughput
• Minimum of 10 real servers
• Layer 4 (TCP) load balancing
• Layer 7 (HTTPS) load balancing
• Web Socket support (recommended)
• HTTP Header/URL Rewriting
• Connection Persistence
Avaya Aura® Conferencing Virtual IP Addresses
The following table lists the Virtual IP Addresses (VIP) required on the ADC for Avaya Aura®
Conferencing.
Table 3: Virtual IP Addresses (VIP)

Server Role Port VIP Type Description

Collaboration Agent (CA) 443 HTTPS A single VIP represents a
pool of CA servers on the
back-end. Persistence is
required for connections
such that once a client
connects, the connection
to the specific back-end
server is maintained
through the duration of
the session.
Web Conferencing 443 HTTPS | SSL-Proxy If the ADC supports Web
Server (WCS) Sockets, the a single
HTTPS VIP represents a
single WCS cluster. Note
that the ADC does not do
the load balancing but
routes to a specific back-
end WCS based on the
URL. For ADC's that do
not support Web
Sockets, an SSL-Proxy
VIP must be configured
for each WCS in the
cluster.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 47

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Server Role Port VIP Type Description

WCS Flash Policy Server 843 TCP A single VIP represents a
pool of Flash Policy
Servers on the back-end.
This is required for the
client to retrieve the
Flash policy file on initial
connection. This
connection does not
require persistence.
Audio Video in 443 | 80 SSL-Proxy | HTTP Prior to ADC support, the
Collaboration Agent primary FMG for an
Audio/Video in
Collaboration Agent
deployment did the load
balancing. If this
configuration is
maintained, then there
must be a one-to-one
mapping of VIPs to back-
end FMG servers.
Otherwise, if each back-
end FMG is configured
individually, then only a
single VIP is required
and the ADC will provide
the load-balancing. If
AViCA is configured to
use RTMPT, the VIP type
should be HTTP, or SSL-
Proxy if configured for
RTMPS.
Provisioning Manager 8443 HTTPS A single VIP representing
(Prov) a pool of Provisioning
Manager servers on the
back-end. For
deployments that have
an internal ADC for traffic
from within the
Enterprise, it is
recommended to not
include on the external
ADC. Regardless, this
interface should not be
exposed to the Internet.

Related links
Key components on page 35

April 2016 Turnkey Overview and Specification 8.0 48

Comments on this document? [email protected]
 Conference features

Conference features
The following sections describe the supported:
• Conference features.
• User roles in Collaboration Agent.
• Conference controls.
Related links
Avaya Aura Conferencing Turnkey solution overview on page 14
Audio and video conferences on page 49
Conference recording on page 53
Collaboration Agent user types on page 59
Lecture mode on page 62
Conference Lock and Unlock on page 62
Fast Start on page 63
Continuation on page 63
Conference profiles on page 63
Conference controls on page 64

Audio and video conferences

Avaya Aura® Conferencing supports the following technologies for integrated audio and video:
• The Flash-based audio and video in Collaboration Agent.
• The web browser-based audio and video conferencing using the audio and video conferencing
plug-in.
Collaboration Agent supports streaming audio and video in conferences using the camera,
speakers, and microphone of the computer. If you use the integrated audio and video feature, you
do not have to associate and dissociate your phone number with your account on Collaboration
Agent. This feature is for guest users and participants who are located outside the enterprise
network. The integrated audio and video is an optional feature. The system administrator must
enable this feature for users.
Use the integrated audio feature of Collaboration Agent instead of separately dialing in to the audio
bridge. Speak through your computer microphone and hear other participants through speakers.
Mute and enable your microphone using the Collaboration Agent interface.
Use the integrated video feature of Collaboration Agent to join video conferences. Stream your
video through your camera and view the live video of other participants on the computer. Pause and
start video using the Collaboration Agent interface. In video conferences, Collaboration Agent
constantly transmits the video of the active speaker. Collaboration Agent also displays a self-view
from your camera. If you do not have a camera, you can receive video, but you cannot stream
video.
Collaboration Agent provides a tuning wizard to optimize the audio and video settings.

April 2016 Turnkey Overview and Specification 8.0 49

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Related links
Conference features on page 49

Collaboration Agent window components

№ Button Description
1 Start sharing... Starts web collaboration.
Participants can share information, such as the desktop, an
application, or a virtual whiteboard. All participants logged in to
Collaboration Agent can view the shared information.
2 Conference Information Opens the Conference Information window with the following
options:
• Dial-in and invite details
• Participation Reports
• Operator
• Touch-tone commands
• Help
• Reports
• Recordings
• Audio and Video Statistics
• Send logs
• Download Sharing Plugin
• Download Audio/Video Plugin
3 Default Settings Opens the Settings window to configure the default conference
settings for:
• Fast Start

• Continuation

• Entry Tone

• Video

• Auto Record

• Presentation Mode

You cannot configure the default settings in active conferences.

4 Exit Exits Collaboration Agent.
If you exit Collaboration Agent, you can still stay connected to the
conference on the audio bridge.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 50

Comments on this document? [email protected]
 Conference features

№ Button Description
5 Add Audio or Video Adds audio or video or both to the web collaboration session on
Collaboration Agent.
6 Conference recording Records conferences.
7 Adjust audio volume button Adjusts the volume of the audio on Collaboration Agent, or mutes
the speakers.

Collaboration Agent displays Adjust audio volume button only

if you use the integrated audio and video feature.
8 Pause video Pauses and starts the video on Collaboration Agent.

Collaboration Agent displays Pause video only if you use the

integrated audio and video feature.
9 Mute myself Mutes and enables your microphone.
10 Mode bar Displays the status of Lecture mode, conference lock, secure
conferences, conference recording, and error messages.
Collaboration Agent displays the Mode bar only when you enable
and disable settings.

Note:
Avaya Aura® Conferencing can establish secure conferences
only if the endpoints of all participants support SRTP.
11 Participants Sorts the list of participants to display:
• All Participants
• Participants In Collaboration
• Recent Talkers
• Dropped participants
Collaboration Agent updates Recent Talkers when other
participants speak. Collaboration Agent displays Active speaker
next to the names of the participants who speak.
12 Filter By Participant Name Filters and searches for conference participants by name.

13 Sort Participants By Roles Sorts and displays the participants in the participants list according
to their roles, such as moderator, participant, and presenter.
14 Add Participants Opens the Add Participants window to add participants to the
conference.
When you enter the phone number of a participant to add to the
conference, Avaya Aura® Conferencing calls the participant and
connects the participant to the conference.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 51

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

№ Button Description
15 Conference Controls Opens the Conference Controls window to enable and disable the
following settings for the conference:
• Lecture

• Entry Tone

• Continuation

• Presentation Mode

• Lock

• End Conference

Ending the conference from the Conference Controls window

immediately disconnects the conference.
16 Participant Controls Displays the following moderator and participant actions:
• Identify my phone

• Mute

• Pause video

• Promote to moderator

•
• Raise Hand

• Drop from Call

17 Participants list Displays the list of participants.
In Event conferences, the participants list displays only the
moderator, presenters, the participants whose microphones are
enabled, and the participants with raised hands. With the name or
the phone number of participants, the participants list also displays
icons next to each participant indicating:
• The status of the microphone of the participant. If the conference
is secure, the audio icon contains an embedded lock icon.
• The status of the video of the participant. If the conference is
secure, the video icon contains an embedded lock icon.
• That the participant virtually raised a hand.
• That web collaboration of the participant is in progress.
• That the participant is the moderator on the audio bridge or
Collaboration Agent or both.

Web Collaboration components

The following figure show the components of the Web Collaboration window. In this example, the
moderator is sharing a whiteboard.

April 2016 Turnkey Overview and Specification 8.0 52

Comments on this document? [email protected]
 Conference features

No. Name Description

1 Annotation tools Annotate the whiteboard or shared document.
2 Zoom tools Changes the size of the screen content.
3 Auto fit Auto fits the web collaboration interface to the window size.
4 Screenshot Send a screen shot of the current screen to all participants in a
message as a JPG file that participants can download.
5 Navigation tools Navigate the shared content. The buttons change according to the
content being shared.
6 Stop Sharing Stop sharing current content.
7 Hide or show roster Hides or shows the conference roster.

Conference recording
The Conference Recording feature, which is an optional feature of Conferencing, provides the
capability to record conferences. These conference recordings capture:
• Audio and information about the active speaker
• Library items such as presentation slides.
• Whiteboard.
• Conference notes, including questions, comments, and actions items, along with details about
the author and the time when these events occurred.
• Conference events, including messages that the participants send, shared documents, and
screen captures.
• The roster and the time when each participant enters and exits the conference along with
information about the active speaker.
The recording feature requires a separate license. The system administrator enables or disables the
conference recording permissions for users through the Allow Conference Recording parameter in

April 2016 Turnkey Overview and Specification 8.0 53

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

the user communication profile. The administrator can also set the preferred codec for the trunk
between the conferencing Media Server and the recording Media Server.
The recording capacity is up to 1800 GB for each recording media server cluster. Recording audio
consumes approximately 40 MB of storage capacity per hour, while recording the Web conference
and audio consumes up to 105 MB per hour.
The owner of a conference and a delegated moderator can record a conference. The owner can
also administer Conferencing to automatically start recording when a conference starts.
Conferencing automatically assigns a name to each recording. This name is the time when the
recording starts.
When the owner or the moderator starts a conference recording, Conferencing plays a notification to
inform the participants that the conference is being recorded. Participants joining the conference
also hear the message that the conference is being recorded.
Users can play these conference recordings from a URL that the owner sends.
Conferencing captures the following recording metrics:
• The number of recordings in progress.
• The total number of recordings.
• The total minutes of recordings.
Collaboration Agent
Collaboration Agent supports the Conference Recording feature. Users can play the conference
recording in a Web browser through a URL for the recording that the owner sends.
The following figure illustrates the conference Auto Record default setting of the Conference
Recording feature in Collaboration Agent:

April 2016 Turnkey Overview and Specification 8.0 54

Comments on this document? [email protected]
 Conference features

Figure 10: Conference default settings

TUI
The owner and the moderator of a conference can start and stop a conference recording through
the phone keypad using TUI. Collaboration Agent displays the conference recording menu
instructions through the keypad in the information tab.
For example, by default, the owner can gain access to the recording menu by pressing *2 and start
the recording by pressing 1.
Conference recording components
Multiple components are involved in recording a conference.
• Application Server manages a recording, including the conference events in the recording.
• Media Server is the primary server for media recording and content storage.
- If the host Media Server fails, the conference recording stops and the content storage
contains the recording till the Media Server fails.
- If the recording Media Server fails, the recording fails.
• The Web conferencing media server stores the metadata of the recordings.
- If the Web conferencing media server fails, the Web conference recording fails. A new Web
conference recording starts in the secondary server.

April 2016 Turnkey Overview and Specification 8.0 55

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

- If the Web conferencing media server fails and there is no provision of a secondary server,
saving the recording depends on when the server fails. If the server fails before the
recording starts, the recording does not start. If the server fails when the recording is
stopped, the conference owner can manually encode the recording if the audio recording file
and Web recording file is available.
• The Web collaboration server records the Web conferencing media and stores this media in
the content storage of Media Server. Web collaboration server also contains the recording
playback service.
- If the Web collaboration server fails, the Web conference recording fails. A new Web
conference recording starts in the secondary server.
- If the Web collaboration server fails and there is no provision of a secondary server, the
audio recording continues but the Web conference recording fails. The conference owner
can manually encode the recording from the playback service interface. If the encoding
service fails, the owner can again try to encode the recording from the recording
management interface.
- The database stores recordings, the metadata of the recordings, and the information
required to play these recordings.
Conference recording sharing
In Collaboration Agent, the conference owner can view a list of recordings.
• For audio conferences, the recording is in the form of a .mp3 file.
• For audio and Web conferences, the recording is in the form of an .swf file which contains the
audio and the Web content.
The owner can delete, rename, and share these recordings. The owner can also download a copy
of the recordings.
The following figure illustrates the Recording window in Collaboration Agent:

April 2016 Turnkey Overview and Specification 8.0 56

Comments on this document? [email protected]
 Conference features

Figure 11: Conference recordings

Playback panel
The Playback panel uses a Flash-based application to display a timeline of the events in a
conference recording.
Backup and restoration of a conference recording
Conferencing performs a backup of the conference recordings daily. The system administrator can
configure the time of this backup process.
The backup process only updates the existing backup with the new recordings that Conferencing
generates since the previous backup process.
The system administrator can restore a conference recording or gain access to a subset of the
recording. The administrator can search for a particular recording of a user to restore in the
conference recording folder. This folder is named with the date of the recording.
Automatic disk management
An automatic disk management process on Media Server deletes old recordings to ensure
availability of disk space for new recordings.
This process runs daily after the backup process.

April 2016 Turnkey Overview and Specification 8.0 57

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Conference recording limitations

The Conference Recording feature has the following limitations:
• There is no recording limit for each user. A single user can record a large number of
conferences which might consume a large amount of storage capacity.
• The recording conference controls do not have pause and resume buttons. The moderator can
only stop and restart a recording.
• Conferencing does not correlate multiple recordings from a single conference. The owners
must perform this correlation manually.
• The conference owners cannot share a recording with specific users. If the owners enable a
recording for sharing, the recording is visible to all users. The owners can send a copy of the
recording through email.
• The delete process deletes all the old recordings. There is no provision to mark a recording to
be excluded from the delete process.
• Users cannot search or annotate recordings.
Conference recording feature permissions
The following table lists the conference recording feature permissions for each user role in
Conferencing.
Table 4: Conference recording feature permissions

User roles Permissions

Participant and Participants and viewers can play the recorded conferences and navigate by:
viewer
• A slide and play only the relevant sections.
• A contributor by browsing through messages and documents.
• An event by browsing each action item, question, or note.
• The moderator, a participant, a subject, date and time, and a key word.
• An element in the conference recording.

Note:
Participants and viewers can only play a conference recording if the owner of the
conference sends a URL of the conference recording. A viewer might not be a
participant of the conference but can still view the conference recording through
the URL.
Owner Owner has all the permissions that a participant or a viewer has along with the
following additional permissions:
• Start and stop the conference recording.
• Control whether the conference is recorded. Conferencing records the audio, Web,
roster, and the minutes of a conference.
• Gain access to all conference recordings that an owner owns, and delete, rename,
or replay these recordings.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 58

Comments on this document? [email protected]
 Conference features

User roles Permissions

• Obtain a link to a conference recording or a link to an excerpt of a conference
recording and distribute these links.
Administrator Administrator has all the permissions that Owner has along with the following
additional permissions:
• Edit and maintain user accounts.
• Enable and disable the Conference Recording feature for the entire system or for
individual users.

Related links
Conference features on page 49

Collaboration Agent user types

Within the Collaboration Agent environment, there are two types of users. These types are:
• Member
• Guest
During a conference, the user type is constant. It does not change.
Members require a password and an account on Avaya Aura® Conferencing. Members have access
to a large number of privileges within the Collaboration Agent environment.
Guests do not require a password and do not have an account on Avaya Aura® Conferencing. If a
guest wishes to become a member, an administrator must create a conferencing profile for them in
Avaya Aura® System Manager. Guests have fewer privileges than members. For example, guests
can log in to a conference, raise their hands, send messages, enter minutes, associate their audio
line, and be promoted to a presenter. However, they cannot be promoted to a moderator. Guests
can also mute themselves if their Collaboration Agent log-in is associated with their phone in the
participant list.
A guest must know the collaboration code to join the Collaboration Agent. Participants, including
guests, who receive the Microsoft Outlook meeting invitation can also join the conference through
Collaboration Agent by clicking the conference link in the invitation, which automatically opens
Collaboration Agent.
Related links
Conference features on page 49
User roles on page 59

User roles
Collaboration Agent supports the following user roles:
• Conference owner
• Moderator

April 2016 Turnkey Overview and Specification 8.0 59

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

• Presenter
• Participant
• Operator
During a conference, user roles are dynamic and mutually exclusive.
• Participants can become moderators.
• Conference owners can be moderators and presenters simultaneously.
• Conference owners can promote participants to the moderator or presenter role.
Conference owner
Members are owners of the conferences that are associated with their Avaya Aura® Conferencing
accounts. Conference owners have complete control over their own conference for which
conference owners function as the owner, moderator, and presenter.
Moderator
Moderators have most of the privileges of conference owners, but cannot gain access to conference
recordings and meeting reports. Moderators enter the moderator code to join conferences.
Moderators can promote participants to the presenter or moderator roles. Moderators can also
share content using web collaboration.
Members can be moderators on:
• Collaboration Agent and the audio bridge.
• Collaboration Agent only.
• The audio bridge only.
Avaya Aura® Conferencing links the login action of users who log in to Collaboration Agent and the
audio bridge with the moderator code. Avaya Aura® Conferencing then assigns the moderator role to
the same user on Collaboration Agent and the audio bridge. However, conferences can also have
different moderators on Collaboration Agent and the audio bridge. Collaboration Agent assigns the
moderator role to the first user to log in with the moderator code. If multiple users log in with the
moderator code, one user might become the moderator on Collaboration Agent, while another user
might become the moderator on the audio bridge. The Collaboration Agent moderator has access to
all moderator features on Collaboration Agent, but the audio bridge moderator has access only to
the moderator features that the dial pad commands support on the audio bridge.
Certain features, such as Lecture mode, are unavailable when moderators are in Collaboration
Agent–only mode because Lecture mode is disabled if the conference has no audio.
Presenter
Presenters have limited control in conferences, but can share content. Presenters can share:
• Desktop, a part of the desktop, or an application.
• Virtual whiteboards, using which conference participants can collaborate through drawings.
• Documents.
Presenters can annotate the shared content, take screen shots, and send the screen shots to all
participants. Avaya Aura® Conferencing provides a private library for members with accounts.
Members can upload material, such as documents, presentation slides, and graphics, to their
private library.

April 2016 Turnkey Overview and Specification 8.0 60

Comments on this document? [email protected]
 Conference features

Moderators can only promote participants who are logged in to Collaboration Agent to the presenter
role. Moderators can also demote presenters to participants.
Participant
Participants in conferences have limited control. Participants can view other participants in
conferences, view shared content, and mute their own microphones if the participants associate
their Collaboration Agent instance with their phone number in the participants list. Participants can
dial in to the audio bridge and log in to Collaboration Agent for web collaboration or use the
integrated audio and video feature to use Collaboration Agent for audio and web collaboration.
Participants join conferences using the participant code. Participants can log in to:
• Collaboration Agent only.
• Collaboration Agent and the audio bridge.
• The audio bridge only.
Participants can annotate whiteboards, but cannot open new whiteboards. Participants can virtually
raise a hand, send messages, view participation reports, enter meeting minutes, and edit the
meeting minutes they entered. Participants cannot add users to conferences.
Participants can be Avaya Aura® Conferencing members or guest users.
Audio–only participant
Audio-only participants join conferences by dialing in to the audio bridge. Moderators can also dial
out to users and add the users to conferences as participants.
Operator
Operators control all aspects of conferences. Operators can:
• Mute and enable the microphones of participants.
• Disconnect specific participants or all participants.
• Enable and disable entry and exit tones.
• Lock and unlock conferences.
• Start and stop conference recording.
• Enable and disable conference continuation after the moderator leaves the conference.
• Promote self to presenter.
Operators cannot:
• Change the default settings of conferences where the operator is not assigned the operator
role.
• Start and end web collaboration.
Related links
Collaboration Agent user types on page 59

April 2016 Turnkey Overview and Specification 8.0 61

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Lecture mode
All participants of a conference are muted when the Lecture mode is enabled. Moderator can enable
the Lecture mode. Event conferences start in the Lecture mode.
When the Lecture mode is enabled:
• There can be more than one Presenter.
• Presenters are not automatically muted.
• Audio of Participant who is promoted to Presenter is enabled.
• Audio of Presenter who is demoted to Participant is automatically muted.
• Audio of Presenter joining an active conference in the Lecture mode is automatically muted but
Presenter can mute or enable audio.
• Moderator can mute and enable the audio of Participant.
- If Moderator enables the audio of a Participant, the Participant can mute and enable audio.
- Moderator can return Participant to the Lecture mode by muting the audio of Participant.
Audio of Participants in a conference that is in the Lecture mode or in an Event conference is
automatically muted. Participants virtually raise a hand to indicate to Moderator that they want to
talk. Audio of Participants in Adhoc or MeetMe conferences is not muted, but these Participants can
virtually raise a hand to indicate that they want to talk. Moderator can lower a virtually raised hand of
Participant.
Related links
Conference features on page 49

Conference Lock and Unlock

The Conference Lock feature is used only by Moderator to block new participants from joining a
conference. This feature does not lock the bandwidth or other resources the conference is locked.
Moderator can lock a conference through Collaboration Agent, Avaya Equinox™, or through the
telephone dial pad. A conference is unlocked by default, but Moderator can lock or unlock the
conference after joining the conference. After the conference is locked or unlocked, an audible
message is played to notify participants of the change in the conference state. If a participant
attempts to join the locked conference, an audible message plays to indicate that the conference is
locked.
Moderator can unlock the conference at any time. If the conference is in a locked state, Moderator
must dial out to add participants in the conference. Moderator can rejoin the conference if the
conference is locked. Participants can disconnect from the locked conference but cannot rejoin the
locked conference. Participants cannot dial out to add participants to a locked conference.
Moderator can promote a user to Moderator during a locked conference. If the moderator leaves the
conference, the conference is unlocked.

April 2016 Turnkey Overview and Specification 8.0 62

Comments on this document? [email protected]
 Conference features

Participant in a locked conference can:

• Upgrade from audio-only to audio and video or downgrade from audio and video to audio-only.
• Enter or exit Collaboration Agent.
• Disable or pause video.
MeetMe and Adhoc conferences support the Conference Lock feature.
Related links
Conference features on page 49

Fast Start
With the Fast Start feature, participants can join a conference before Moderator joins. MeetMe
conferences support the Fast Start feature. The Fast Start must be enabled before the start of a
conference.
If Moderator does not join the conference, a participant can assume the Moderator control by joining
with the Moderator code. Participants can also assume the Moderator control through Collaboration
Agent, Avaya Equinox™, or by dialing *51 on the telephone dial pad.
Related links
Conference features on page 49

Continuation
With the Continuation feature, participants can continue a conference even after Moderator
disconnects. By default, a conference ends after Moderator disconnects and the grace period
expires. If Moderator rejoins the conference before the grace period expires or another participant
assumes Moderator control, the conference continues.
Moderator can enable the Continuation feature through Collaboration Agent, Avaya Equinox™, or by
dialing *98 on the telephone dial pad. During a conference, Moderator can disable the Continuation
feature for the conference even if the Continuation feature is enabled in the default settings of the
conference.
MeetMe and Adhoc conferences support the Continuation feature.
Related links
Conference features on page 49

Conference profiles
With the Microsoft Office Outlook delegate feature, you can create different conference profiles that
contain the conference details of other users. You can use these conference profiles to set up
conferences for other users who delegate this activity to you.

April 2016 Turnkey Overview and Specification 8.0 63

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

For example, a senior executive in a company might delegate the activity of setting up conferences
to an assistant. The executive provides the conference details to the assistant, and the assistant
enters these details while creating a conference profile in Conferencing Manager. If the executive
has more than 1 set of conference details, the assistant can create up to 20 conference profiles that
contain a different set of conference details in each profile.
While creating a conference for another user, you can select a conference profile that contains the
relevant conference details. Conferencing Manager automatically adds these conference details in
the body of the conference invitation. If you want to join a conference that you set up for another
user, Conferencing Manager provides you with the Join as Moderator and Join as Participant
drop-down options in the Join button. The Join as Moderator option is available only if you enter
the Moderator code while creating the conference profile. Also, if the conference requires an
additional passcode, you must enter the passcode in the conference profile.
Related links
Conference features on page 49

Conference controls
Conference users can use a supported audio or video endpoint to use the call functions. Users can
gain access to a conference through:
• The dial pad of an audio or video endpoint
• A supported client, such as Collaboration Agent, and advanced clients, such as Avaya
Equinox™ for Windows and Avaya Equinox™ for iOS.
Through Collaboration Agent users can use the advanced conference controls for scheduled
conferences such as MeetMe and Event conferences.
The following tables describes the advanced and integrated conference control features available to
Moderator, Participant, and Guest through a supported client user interface:

Table 5: Conference controls for a supported client

Feature Description Moder Particip Guest

ator ant
Continuation Toggle this control on or off. This control is disabled by yes no no
default.
• If you enable this control, the conference continues even
after Moderator leaves the conference.
• If you disable this control and Moderator leaves the
conference, Conferencing notifies the participants on the
number of minutes remaining until the conference ends.
If Moderator joins the conference again or a Participant
assumes the Moderator role, the conference returns to the
normal conference state.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 64

Comments on this document? [email protected]
 Conference features

Feature Description Moder Particip Guest

ator ant
For more information about continuation, see
Continuation on page 63.
Lock and unlock The moderator can lock the conference to block new yes no no
conference participants from joining. The moderator can dial out to add
new participants at any time or unlock the conference.
For more information about lock and unlock, see Lock and
unlock on page 62.
Lecture mode The moderator becomes a lecturer and is the only one who yes no no
can speak or be seen in video on the conference. All other
participants are considered passive participants and in a
mute for audio and paused for video state.
For more information about lecture mode, see Lecture
mode on page 62.
Fast start Toggle this control on or off. This control is disabled by yes no no
default.
• If you enable this control, Participants can start the
conference even if Moderator does not join first.
• If you disable this control, Participants must wait till
Moderator joins for the conference to start.
For more information about fast start, see Fast start on
page 63.
Display dropped Displays participants who have left the conference. yes yes yes
participants
Sort participants Displays participants by role (moderator, participant, guest, yes yes yes
by roles and presenter).
Dial out The moderator can invite a new participant to the yes no no
conference.
Dial out to Contacts the operator. yes yes no
operator (if
provisioned by
the
administrator)
End conference All participants are released from the conference even if yes no no
conference continuation is enabled.
Entry and exit Toggle on or off. Disabled by default. If enabled, an audible yes no no
tones entry or exit tone plays when a participant joins or leaves a
conference. If disabled, no audible entry or exit tone plays.
Audio mute or Individual participants: A moderator can mute or unmute yes yes, yes,
unmute the audio of an individual conference participant. The only self only
moderator cannot self mute. A participant can mute audio self
for self only.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 65

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Feature Description Moder Particip Guest

ator ant
Audio mute or unmute all participants: If enabled, only the yes no no
moderator can speak and all other participants have the
audio muted.
Video pause or Individual participants: A moderator can pause or unpause yes yes, yes,
unpause the video for an individual conference participant. The only self only
moderator cannot self pause. A participant can pause self
video for self only.
Video pause or unpause all participants: If enabled, only yes no no
the moderator can send video and all other participants
have the video paused.
Move user Move a participant from one conference to another. yes no no
Drop user Remove a participant from the conference. yes no no
Promote to Promote participant to moderator. yes no no
moderator
Promote to Promote participant to presenter. yes no no
presenter
Silence or Silence or unsilence all participants. yes no no
unsilence
See the See the number of participants in the meeting. yes yes yes
participant count
Raise and lower To signal to the moderator and others in the conference no yes yes
hand that you wish to speak.
Record and stop Start and stop a conference recording yes no no
recording
List feature keys Show a list of the available feature keys. yes yes yes

The following tables describes the advanced and integrated conference control features available to
Moderator, Participant, and Guest through a the dial pad of an audio or video endpoint:

Table 6: Conference controls using the dialpad of an audio or video endpoint

Key Feature Description Moder Particip Guest

ator ant
** Help Plays an audio list of the commands available. This is yes yes yes
played only to the issuer.
*# Count Audio indication of the number of active users in a yes yes yes
participant conference. This is played only to the issuer.
s
## End Stops the conference even if conference continuation is yes no no
conference enabled.
*0 Dial out to The administrator must provision to allow dial out to yes yes no
operator operator.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 66

Comments on this document? [email protected]
 Conference features

Key Feature Description Moder Particip Guest

ator ant
*1 Dial out Joins a new participant to the conference. yes no no
*4 Entry or Enable or disable the play entry and exit tones to yes no no
exit tone participants. If enabled, tones are played to participants
upon entering or exiting a conference.
*21 Record Start and stop a conference recording yes no no
and stop
recording
*41 Raise Signal to moderator and others in the conference that no yes yes
hand you wish to speak.
Audio only participants receive audio feedback for a raise
hand request. The audio feedback is:
• your hand is raised
• your hand could not be raised
Video endpoint users can see a raised hand icon next to
the user in the roster list.
*42 Lower The moderator can lower the hand of participants. The yes- yes, yes,
hand participant can lower hand for self only. partici only self only
pants self
Audio only participants receive audio feedback for a
only
lower hand request.
• your hand is lowered
• the moderator lowered your hand
• Note:
For event conferences, the moderator must use a
user interface such as Collaboration Agent to
lower the hand of participants.
Video endpoint users can see the hand request has been
lowered as the raise hand icon next to the user in the
roster list is no longer visible.
*5 Lecture Enable or disable lecture mode for a specific conference. yes no no
mode The moderator becomes a lecturer and is the only one
who can speak or be seen in video on the conference. All
other participants are considered passive participants
and are in a mute for audio and paused for video state.
For more information about lecture mode, see Lecture
mode on page 62
*51 Assume Assume the Moderator role if Moderator does not join the no yes yes
moderator conference.
Enter the Moderator code and the Pound key (#) to
assume the Moderator role.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 67

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

Key Feature Description Moder Particip Guest

ator ant
Note:
If Moderator does not join a conference or
Moderator for a conference is not identified, the first
user to dial in with the Moderator code or the first
user to assume the Moderator role becomes
Moderator. If you join a conference as a participant,
you must disconnect and again join the conference
with the Moderator code or press *51 on the dial
pad to assume the Moderator role. After a user is
established as Moderator for a conference, all the
users who join the conference with the Moderator
code subsequently are added as participants.
*6 Mute or Mute or unmute audio and video. yes, yes, yes,
unmute only only self only
audio and self self
video
*61 Mute or Mute or unmute audio. yes, yes, yes,
unmute only only self only
audio self self
*62 Pause or Pause or unpause video. yes, yes, yes,
unpause only only self only
video self self
*7 Lock or The moderator can lock the conference to block new yes no no
unlock participants from joining. The moderator can dial out to
conference add new participants at any time or unlock the
conference.
For more information about lock and unlock, see Lock
and unlock on page 62.
*71 Disable Turns off video for the conference for the duration of the yes no no
video conference. New participants join without video
functionality.
*81 Audio Silences or unsilences all participants in the conference. yes no no
mute all
(on or off)
*82 Video Turn video on or off for all participants in the conference. yes no no
mute all
(on or off)
*96 Silence all Silences all participants in the conference; however, yes no no
participant participants have the ability to unsilience.
s
*98 Continuati Enable or disable. If enabled, conference continues after yes no no
on the moderator leaves the conference.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 68

Comments on this document? [email protected]
 Language support

Key Feature Description Moder Particip Guest

ator ant
If disabled and the moderator leaves the conference,
participants are notified of the number of minutes
remaining until the conference ends. The conference
returns to a normal conference state if the moderator
rejoins the conference or one of the participants
assumes moderator control.
For more information about continuation, see
Continuation on page 63.

Note:
Operator has the same privileges as Moderator and Presenter has the same privileges as
Participant with some exceptions.
Related links
Conference features on page 49

Language support
Avaya Aura® Conferencing is available in the following languages:
• English (United States)
• Chinese (Simplified)
• Japanese (Japan)
• Korean (Korea)
• French (France)
• German (Germany)
• Italian (Italy)
• Russian (Russia)
• English (United Kingdom)
• Spanish (Mexico)
• Portuguese (Brazil)
• French (Canada)
• English (Canada)
This means that users in each of these locations can access the following Avaya Aura®
Conferencing interfaces in their native language:
• Avaya Aura® Conferencing Collaboration Agent (for Desktop)

April 2016 Turnkey Overview and Specification 8.0 69

Comments on this document? [email protected]
Avaya Aura® Conferencing Turnkey solution overview

• Avaya Web Collaboration Agent for Android

• Avaya Web Collaboration Agent for iOS
• Avaya Aura® Conferencing Conference Manager for Microsoft Outlook
To support these users, Avaya has produced audio prompts, online help, and user manuals in each
of these languages. The audio prompt language is determined by the browser locale. The online
help is integrated with each of the user interfaces. The user manuals are as follows:
Document Title Use this document to: Audience
number
04-604359 Using Avaya Aura® Manage and participate in Customers
Conferencing Collaboration conferences using Collaboration
Agent Agent.
04-604428 Avaya Aura® Conferencing Manage and participate in Customers
Collaboration Agent Quick conferences using Collaboration
Reference Agent.
04-604383 Using Avaya Web Manage and participate in Customers
Collaboration Agent for Android conferences using Avaya Web
Collaboration Agent for Android.
04-604388 Using Avaya Web Manage and participate in Customers
Collaboration Agent for iOS conferences using Avaya Web
Collaboration Agent for iOS.
04-604408 Using Avaya Aura® Manage and participate in Customers
Conferencing Conference conferences using Conference
Manager for Microsoft Outlook Manager.

These documents are available on https://support.avaya.com/documents/.

Related links
Avaya Aura Conferencing Turnkey solution overview on page 14

SNMP support
In terms of Simple Network Management Protocol (SNMP) support, Avaya Aura® Conferencing
supports the SNMP v1 and SNMP v2c protocols.
Related links
Avaya Aura Conferencing Turnkey solution overview on page 14

April 2016 Turnkey Overview and Specification 8.0 70

Comments on this document? [email protected]
Chapter 3: Interoperability

Product compatibility
The Avaya Aura® Conferencing for Turnkey solution is deployed without the Avaya Aura® Private
Branch eXchange (PBX) stack, which refers to the staging and management software such as
System Platform and System Manager. Instead, this solution can be deployed with the following
alternative PBXs:
• Avaya Aura® Communication Manager 5.2.1
• Avaya Aura® Communication Manager 6.0.1
• Avaya Aura® Communication Manager 6.2
• Avaya Communication Server 1000 6.0
• Avaya Communication Server 1000 7.5
• Avaya IP Office 9.0
In a Avaya Aura® Conferencing for Turnkey solution, each of these PBXs is configured as a SIP
entity which connects to Avaya Aura® Conferencing by way of a SIP trunk. Most end user clients
connect to Avaya Aura® Conferencing using this SIP trunk. However, the mobile clients connect
directly to Avaya Aura® Conferencing. The mobile clients are the Avaya Aura® Conferencing for
Android application and the Avaya Aura® Conferencing for iPhone application.
Note:
A single deployment of Avaya Aura® Conferencing is either a Turnkey deployment or an Avaya
Aura® deployment. A mixed deployment, consisting of flavors of both solutions, is not supported.
Virtualization
Like the Avaya Aura® Conferencing for Avaya Aura® solution, the Avaya Aura® Conferencing for
Turnkey solution supports VMWare. This means that you can install and configure the servers
remotely. Alternatively, you can install and configure the solution directly, on-site. This is also called
a bare metal installation.
Clients
Like the Avaya Aura® Conferencing for Avaya Aura® solution, the Avaya Aura® Conferencing for
Turnkey solution supports the Avaya Aura® Conferencing Collaboration Agent, the Avaya Aura®
Conferencing for Android application, the Avaya Aura® Conferencing for iPhone application, as well
as a number of clients that are supported by the various PBXs. These clients depend on the clients
that the PBX supports. For example, CS1K soft phone/client. The Turnkey solution can provide
either Enhanced Audio/Video in Collaboration Agent or regular Audio/Video in Collaboration Agent.

April 2016 Turnkey Overview and Specification 8.0 71

Comments on this document? [email protected]
Interoperability

Conference controls
Like the Avaya Aura® Conferencing for Avaya Aura® solution, the Avaya Aura® Conferencing for
Turnkey solution supports all conference controls. Users can control their conferences using the
DTMF telephone keypad controls, the Avaya Aura® Conferencing Collaboration Agent interface, or
the Avaya Aura® Conferencing for Android/iPhone applications interface.
Audio
The Avaya Aura® Conferencing for Turnkey solution supports all audio codecs that are currently
supported by the Avaya Aura® Conferencing for Avaya Aura® solution.
Video
Currently, the Avaya Aura® Conferencing for Turnkey solution supports video for clients running one-
X-Communicator in H.323 mode in a deployment with Communication Manager 6.2. The solution
also supports the Audio/Video in Collaboration Agent, including the Enhanced Audio/Video in
Collaboration Agent feature. In addition, the solution supports video for the Avaya Aura®
Conferencing for Android/iPhone applications because they are not located behind a PBX.
Collaboration
Like the Avaya Aura® Conferencing for Avaya Aura® solution, the Avaya Aura® Conferencing for
Turnkey solution supports the full web collaboration experience.
LDAP
Like the Avaya Aura® Conferencing for Avaya Aura® solution, the Avaya Aura® Conferencing for
Turnkey solution supports local user passwords or enterprise user passwords. If the deployment
uses local passwords, users can update their passwords using the Avaya Aura® Conferencing
Collaboration Agent interface. If the deployment uses enterprise user passwords, the solution is fully
compatible with the Lightweight Directory Access Protocol (LDAP).
Administration
Like the Avaya Aura® Conferencing for Avaya Aura® solution, the Avaya Aura® Conferencing for
Turnkey solution supports the Element Manager console and the Provisioning Manager client. This
means that administrators can configure, maintain, and troubleshoot their deployment uses these
rich interfaces. In addition, using the Element Manager console, administrators can administer
themselves and other administrators. The audit trail and reporting functionality are identical in both
types of solution. In other words, the accounting records, operational metrics, alarms, logs, and Key
Performance Indicators (KPIs) are fully supported in the Turnkey solution.
Related links
Supported endpoints in a Turnkey solution on page 72

Supported endpoints in a Turnkey solution

Endpoints supported with Audio SRTP
• Avaya one-X Communicator Release 6.1
• Avaya one-X Communicator Release 6.1.1
• Avaya one-X Communicator Release 6.1.6

April 2016 Turnkey Overview and Specification 8.0 72

Comments on this document? [email protected]
 Interoperability matrix

Limitations
With a number of minor exceptions, these endpoints support each of Avaya Aura® Conferencing
features. In most cases, where there are support limitations related to an endpoint, there are
engineering fixes in place to enable the feature to behave as users expect. For example, the Avaya
Communicator endpoint does not recognize a conference with Presentation Mode enabled. This
limitation is due to the fact that Avaya Communicator cannot interpret the Presentation Mode
property in the SIP NOTIFY request that Avaya Aura® Conferencing sends. However, Avaya has
implemented an engineering fix to ensure that the conference behaves like a Presentation Mode
conference for all users, including Avaya Communicator users. When Avaya Communicator users
join a Presentation Mode conference, Avaya Aura® Conferencing signals to them that the
collaboration session has already begun. This means that they can share files in the absence of a
moderator.
Related links
Product compatibility on page 71

Interoperability matrix
Prior to the release of Avaya Aura® Conferencing, Avaya tested the compatibility of Avaya Aura®
Conferencing with each of the SIP entities:
• Avaya Aura® Communication Manager 5.2.1
• Avaya Aura® Communication Manager 6.0.1
• Avaya Aura® Communication Manager 6.2
• Avaya Communication Server 1000 6.0
• Avaya Communication Server 1000 7.5
• Avaya IP Office 9.0
For each SIP entity, Avaya tested the following features and documented the results of the testing
process in an Avaya Aura® Conferencing Interoperability Matrix, which is available from https://
support.avaya.com/. Please download the Avaya Aura® Conferencing Interoperability Matrix for
more detailed information.
Tested features
Meet Me conferencing:
• Basic audio
• Features:
- Transfer
- Hold/Retrieve
- Mute/Unmute (audio and video) – Local and network (if client supports it)
- All telephone keypad commands (moderator/participant/guest)

April 2016 Turnkey Overview and Specification 8.0 73

Comments on this document? [email protected]
Interoperability

• Slow start and fast start calls

• Anonymous/Guest meet me dial in
• Dial out to a user – using the SIP gateway
Security
For these SIP entities, Avaya Aura® Conferencing will enforce a best effort approach, which will
depend on the network and the capabilities of the PBX. For example, TLS, SIPS, and SRTP.

Avaya Communicator for Microsoft Lync overview

Avaya Communicator for Microsoft Lync is intended for a network environment where the Microsoft
Lync Server is deployed. Avaya Communicator for Microsoft Lync is a client side add-in to the
Microsoft Lync 2010 and 2013, and Skype for Business 2015 and 2016. Avaya Communicator for
Microsoft Lync can be used to control an H.323 or SIP desk phone or a VDI Communicator client.
Avaya Communicator for Microsoft Lync joins Avaya Aura® communications with the Lync or Skype
for Business client using Microsoft supported APIs. The result is industry leading Avaya
communications integrated into the look and feel of Microsoft Lync. Avaya Communicator for
Microsoft Lync can interwork with a desk phone or a VDI Communicator client. Using Computer
Telephony Integration (CTI), you can integrate the telephone with the computer for managing
telephone calls. Using a Virtual Desktop Infrastructure (VDI) soft client, you can enhance the audio
quality of voice calls by processing the audio locally on your VDI endpoint. The VDI endpoint can be
a thin client or a Windows personal computer.
Avaya Communicator for Microsoft Lync provides the following operational modes:
• Desk Phone or Shared Control mode.
• Computer mode.
Note:
Computer mode is not supported when Avaya Communicator for Microsoft Lync is
deployed with a VDI client.
• Other Phone mode.
For a detailed description of Avaya Communicator for Microsoft Lync functionality, see Telephony
and video services with Avaya Communicator for Microsoft Lync on page 77.
Avaya Communicator for Microsoft Lync interacts with Lync 2010, Lync 2013, or Skype for Business
2015 and 2016 directly using Microsoft supported APIs. All telephony capabilities are integrated
directly between Avaya Communicator for Microsoft Lync and the Microsoft Lync or Skype for
Business client. You only require a Standard CAL (license), eliminating the need for a Microsoft
voice infrastructure and the Microsoft Lync Enterprise CAL. Remote Call Control and Enterprise
Voice must be disabled on the Lync server.
Related links
Avaya Communicator for Microsoft Lync features on page 75

April 2016 Turnkey Overview and Specification 8.0 74

Comments on this document? [email protected]
 Avaya Communicator for Microsoft Lync overview

Telephony and video services with Avaya Communicator for Microsoft Lync on page 77
Interoperability on page 81

Avaya Communicator for Microsoft Lync features

The Avaya Communicator for Microsoft Lync solution uses the Lync 2010 and 2013 user interface to
provide voice services.
Note:
For a detailed description of each voice service and a list of the services supported by each
service provider, see Telephony and video services with Avaya Communicator for Microsoft
Lync on page 77.
The solution supports the following functionality:
• Support for Computer (soft client), Desk Phone (CTI control of Desk phone), and Other Phone
modes when Avaya Communicator for Microsoft Lync is interworking with a desk phone. When
Avaya Communicator for Microsoft Lync is working with a VDI Communicator client, only the
Desk Phone (Shared Control) and Other Phone modes are supported.
- Using Computer Telephony Integration (CTI), you can integrate the telephone with the
computer for managing telephone calls.
- Using Virtual Desktop Infrastructure (VDI) soft client, you can enhance the audio quality of
voice calls by processing the audio locally on your VDI endpoint (a thin client or a Windows
personal computer).
• Make calls from Dialpad, Contact list, or search dialog box utilizing contacts published
numbers.
• With Avaya Collaboration Services, make calls or send IMs from Microsoft Office applications
or a web browser. For more information, see Administering Avaya Collaboration Services
(NN10850-031).
• Translation of E.164 numbers to customer dial plan including insertion or deletion of
appropriate digits.
• Publish Telephony Presences on behalf of the user when their client is signed in and on a call.
• Display a Conversation window with the following mid-call functionality:
- Release/End call.
- Place call on Hold and Retrieve call.
- Insert DTMF digit in to an established call.
- Speaker volume control and speaker mute function (Computer mode).
- Microphone mute function (Computer mode).
- Escalate to a video call.

April 2016 Turnkey Overview and Specification 8.0 75

Comments on this document? [email protected]
Interoperability

• Handling multiple calls:

- Support for multiple Consult calls.
- While on a Consult call, instigate a Call Transfer.
- While on a Consult call, merge another call to form a Conference call.
- Add additional Consult calls to this Conference call.
- Call Waiting pop-up display.
• Display an incoming call window with the following functionality:
- Indicate the Incoming Caller line ID or Caller name.
- Allow the user to answer or ignore the call.
- While on a call, indicate that another call is waiting. Answering this call places the first call
on Hold.
• Using EC500, you can answer Avaya Communicator for Microsoft Lync calls on your mobile
device. You can also extend calls to your mobile device.
• Access the Share My Bridge feature:
- Dial in to your conference bridge or launch web collaboration from the Avaya Communicator
for Microsoft Lync bar or from a Conversation window.
- Share conference bridge and web conference details with another user via instant message
or email.
• With Bridged Line Appearance, the incoming call notification in Avaya Communicator for
Microsoft Lync also indicates whether the call is intended for you or for your boss.
• Set Call Forward options.
- Send All Calls
• Check for and access new voice mail messages.
• Make a video call when Avaya Communicator for Microsoft Lync is working with a desk phone:
Important:
The desk phone should only be H.323.
- Escalate an existing call to a video call.
- Start a video call.
- Mid call control ability to block and unblock camera, and undock the Video window from the
Conversation bar.
- Incoming video call prompting to accept, or ignore incoming video and reply with an instant
message.

April 2016 Turnkey Overview and Specification 8.0 76

Comments on this document? [email protected]
 Avaya Communicator for Microsoft Lync overview

Note:
Avaya Communicator for Microsoft Lync interworking with a VDI Communicator client does
not currently support video call functionality.
• Access to call history records for incoming, outgoing, and missed calls.
• With Multiple Device Access (MDA), log in to your extension, answer calls, and join calls from
multiple devices.
• With dual registration, log in to an H.323 endpoint and a SIP endpoint at the same time. You
can also join calls from both devices with dual registration and extend call to a mobile device.
Related links
Avaya Communicator for Microsoft Lync overview on page 74

Telephony and video services with Avaya Communicator for

Microsoft Lync
Avaya Communicator for Microsoft Lync controls a single line, based on your primary line. If your
desk phone supports multiple lines, non-primary lines will not be represented by Avaya
Communicator for Microsoft Lync.
Note:
The following features are not supported:
• Single Step Transfer or Blind Transfer.
• Video when Avaya Communicator for Microsoft Lync interworks with a VDI Communicator
client.
The following table lists supported functionality:

Table 7: Telephony feature descriptions

Capability Description
Make Call You can make a call on your phone by:
• Clicking a contact in the contact list, and then clicking the icon in Lync
2010.
• Hovering over the picture of a contact and clicking the icon in Lync
2013 or Skype for Business 2015 and 2016.
• Using Dialpad in Avaya Communicator for Microsoft Lync 2013 and the
persona menu.
• Entering a number in the Lync 2010, Lync 2013, or Skype for Business
2015 and 2016 dialog box.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 77

Comments on this document? [email protected]
Interoperability

Capability Description
Note:
With Avaya Collaboration Services, you can also make calls or send
IMs from Microsoft Office applications or web browsers. For more
information, see Administering Avaya Collaboration Services
(NN10850-031).
Release Call You can release a phone call by clicking End Call in the Avaya
Communicator for Microsoft Lync Conversation bar.
Answer Call You can accept an incoming call that is presented to you through an
Incoming Call Notification window.
You can disable incoming call notifications when you are in Desk Phone
mode. To do this, navigate to Settings > General, select Disable Incoming
Call Notifications (Phone Mode) from the Call Notifications area, and then
click OK. The Conversation window minimizes to the toolbar when you
answer the call from a desk phone.
Ignore Call You can ignore a phone call by clicking Ignore Call in the Incoming Call
Notification window.
Escalate to a video call You can escalate an existing audio call to a video call in the Conversation
bar. The call can be in undocked or full screen mode.

Note:
• When an Avaya Communicator for Microsoft Lync H.323 endpoint is a
party on a call, only the originator of the call can escalate an audio
call to a video call. This behavior occurs regardless of whether the
originator of the call is using an H.323 or SIP endpoint.
• In an ad-hoc conference where the moderator has a SIP endpoint
and the participants have H.323 endpoints, the participants might see
a Video window.
Reply to a video call with an You can accept or ignore an incoming video call, and reply with an IM.
IM
Block and unblock camera Using the Mid-call control functionality, you can:
• Block or unblock camera from the Video window menu.
• Undock the Video window from the Conversation bar.
Stop video You can stop video from the Video window menu. Stopping video does not
end the call.
Telephony Presence Avaya Communicator for Microsoft Lync automatically publishes telephony
presence on behalf of you when you are on a call. You can still choose to
manually update their presence status.
Caller ID You receive Calling Party Name or Caller line ID in the Incoming Call
Notification window.
Call forward to another You can activate Call Forward on your PBX line for incoming calls by clicking
phone line or voice mail Call Forward in the Avaya Communicator for Microsoft Lync bar. When the
call forwarding feature is activated, you do not receive incoming call
Table continues…

April 2016 Turnkey Overview and Specification 8.0 78

Comments on this document? [email protected]
 Avaya Communicator for Microsoft Lync overview

Capability Description
notifications. The callee that the call is forwarded to receives an incoming
call notification, and after answering the call, a video request also appears.

Note:
When Avaya Communicator for Microsoft Lync is in Other Phone mode,
call forwarding functionality is disabled.
EC500 Using EC500, you can answer Avaya Communicator for Microsoft Lync calls
on your mobile device. You can also extend calls to your EC500 mobile
device if the Extend Calls capability is enabled in your Avaya Aura® network.
Send All Calls Using Send All Calls, you can route calls to your EC500 device within your
coverage area.
Call Hold and Retrieve Using the Hold button, you can put a call on hold. Click the button again to
retrieve the call.
Generate Digits (DTMF) You can send DTMF digits through the PBX system by selecting the Dialpad
button on the Conversation bar.
This feature is disabled when:
• The call is on hold.
• Avaya Communicator for Microsoft Lync is in SIP Other Phone mode.
In Lync 2013 or Skype for Business 2015 and 2016, the dial pad is dimmed
when disabled. In Lync 2010, the dial pad is invisible when disabled.
Consult Call When on an active call, you can:
• Answer a call.
• Start a second call by:
- Clicking a contact in your contact list.
- Entering a number in the Lync 2010, Lync 2013, or Skype for Business
2015 and 2016 search box.
- Using the Avaya Communicator for Microsoft Lync Dialpad.
When another call is answered or started, the previously active call is put on
hold.
You can create multiple consult calls.
Consult Transfer When one or more consult calls are established, you can select the call you
want to transfer from the list of calls on hold.
Consult Conference When one or more consult calls are established, you can select the call you
want to merge into a Conference call from the list of calls on hold.
Call Waiting When on an active call, an Incoming Call Notification window displays,
indicating that another call is waiting. If you answer this call, then current
active call is put on hold. The new call becomes the active call.
Receiver Mute You can mute or un-mute your PC speakers or headset receivers in
Computer mode.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 79

Comments on this document? [email protected]
Interoperability

Capability Description
Receiver Volume Control You can adjust the volume of the PC speakers or headset receivers in
Computer mode.
Audio Devices Mute You can mute or un-mute your PC speakers or headset microphones in
Computer mode.
Make Video Call You can make a video call by:
• Selecting a contact in your contact list and then clicking Make Video Call.
• Using the dial pad Lync persona menu in Lync 2013 or Skype for Business
2015 and 2016.

Note:
When making a video call or escalating an audio call to a video call, the
IM pane does not appear in Avaya Communicator for Microsoft Lync
2013. This issue does not apply to Avaya Communicator for Microsoft
Lync 2010.
Share My Bridge With Avaya Communicator for Microsoft Lync 2013, you can send dial-in
details and conference details to another user through IM.
This feature is not available in Avaya Communicator for Microsoft Lync
2010.
Launch My Collaboration With Avaya Communicator for Microsoft Lync 2013, you can start a web
collaboration session.
This feature is not available in Avaya Communicator for Microsoft Lync
2010.
Bridged Line Appearance Incoming Call Appearance:
Bridged Line Appearance enhances the experience of incoming calls with
bridged lines. The incoming call notification displays the name or phone
number of the bridged line owner.
Make Call As:
You can also use Make Call As to make a call from another line.

Note:
Exclusion is not supported.
Message Waiting Indication With Avaya Communicator for Microsoft Lync, the Message Waiting
Indicator button on the Avaya Communicator for Microsoft Lync bar lights
up to indicate when you have a new voice mail message. You can click this
button any time to dial in to voice mail.
Call History Call history records for calls made or answered through Avaya
Communicator for Microsoft Lync are saved. Avaya Communicator for
Microsoft Lync also generates call history records for missed calls.
Multiple Device Access MDA provides the following capabilities:
(MDA)
• Ability to log on to the same extension from multiple SIP devices
• Ability to answer a call from multiple devices
Table continues…

April 2016 Turnkey Overview and Specification 8.0 80

Comments on this document? [email protected]
 Avaya Communicator for Microsoft Lync overview

Capability Description
• Ability to join an existing call from other logged in devices
All logged in devices ring simultaneously when an incoming call is made to
the extension.
The Avaya Aura® network configuration, which your administrator
configures, determines:
Dual Registration Using Dual Registration, you can register Avaya Communicator for Microsoft
Lync as an H.323 endpoint and simultaneously register a single SIP
endpoint.

Related links
Avaya Communicator for Microsoft Lync overview on page 74

Interoperability
Avaya Communicator for Microsoft Lync requires certain key components to work. Avaya
Communicator for Microsoft Lync can also optionally interoperate with Avaya applications including:
• Avaya Collaboration Services
• Avaya Aura® Conferencing and Collaboration Agent
Tip:
For easy access to Collaboration Agent web conferencing, you can select the Remember Me
check box on the login page to save your username and password. With this option selected,
you can automatically log in to your web conference without entering your credentials every
time.
For additional information about Avaya Collaboration Services, see Administering Avaya
Collaboration Services (NN10850–031).
For information about Avaya Aura® Conferencing and Collaboration Agent, see:
• Deploying Avaya Aura® Conferencing
• Administering Avaya Aura® Conferencing
• Using Avaya Aura® Conferencing Collaboration Agent

April 2016 Turnkey Overview and Specification 8.0 81

Comments on this document? [email protected]
Interoperability

Avaya Aura® Communicator Integration overview

Overview
Avaya Equinox™ for Windows enables you to log into your company's server, and make and receive
voice or video calls from your telephone extension using your computer. Using the Avaya Equinox™
for Windows client, you can also send instant messages, access your call history, access your
Avaya Aura® contacts and Microsoft Outlook contacts, share information with web collaboration,
perform an enterprise search, and manage your presence status. Avaya Equinox™ for Windows
provides enterprise users with simple access to all the communication tools in a single interface.
Avaya Equinox™ for Windows provides automatic integration with Avaya Aura® Conferencing. When
you log in to a MeetMe conference on Avaya Aura® Conferencing or Avaya Scopia® with Avaya
Equinox™ for Windows, you can:
• Access the Web Collaboration features by clicking the Collaboration button in the main
window. If you are the moderator or have presenter privileges, you can host the web
collaboration session and share documents, presentations, pictures, a whiteboard, your entire
screen, a portion of your screen, or an application window.
• View a graphical representation of the conference and its participants.
• Manage the conference using the built-in moderator controls when you are logged in as the
moderator.
If you have Avaya Aura® Conferencing, you can also start Adhoc conferences with Avaya Equinox™
for Windows.
You must have access to your company's network to use Avaya Equinox™ for Windows.
Related links
Main window on page 82
Button descriptions on page 87
Multiple Device Access overview on page 88

Main window
The following figure shows the components of the main window of Avaya Equinox™ for Windows.
This is the compact view with no tabs expanded.

April 2016 Turnkey Overview and Specification 8.0 82

Comments on this document? [email protected]
 Avaya Aura® Communicator Integration overview

Figure 12: Compact window

No. Name Description

1 User Status area Use this area to log in and log out of the client, and to view your
extension number and presence status. From this area, you can:
• log in and out of the client
• set your presence status or enter a custom presence status
message
2 Message Waiting Lights up to indicate when you have a new voice mail message. You
Indicator can click this button at any time to dial in to your voice mail.
3 Options and Settings You can adjust the volume from Volume.
button
Click Other Settings to configure your servers, dialing rules,
enterprise directory search settings, contacts search settings, audio
settings, video settings, conference settings, preferences, and
messaging settings. Other Settings also displays the software
release and support information.
4 Contacts tab Displays the Contacts fan. The Contacts fan displays cards for all of
your Avaya Aura® contacts and Microsoft Outlook contacts (if
Microsoft Outlook is running). When the Contacts fan is expanded,
you can hover over a contact to see buttons for voice call, video call,
IM, and additional options.
If you have configured the enterprise search settings, you can also
search for Communicator contacts from the Contacts tab.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 83

Comments on this document? [email protected]
Interoperability

No. Name Description

Note:
You must be logged into the server to view your Avaya Aura®
contacts and Microsoft Outlook contacts. Microsoft Outlook must
be running for you to view your Microsoft Outlook contacts.
5 History tab Click to display the History fan and the History tab buttons. The
History fan displays the associated contacts for all the calls you made
and received using the Avaya Equinox™ for Windows client. Using the
History tab buttons, you can view:
• all calls you received using the Avaya Equinox™ for Windows client
• all calls you missed while you were using the Avaya Equinox™ for
Windows client
• all calls you answered using the Avaya Equinox™ for Windows client
• all calls you made using the Avaya Equinox™ for Windows client
A red badge appears on the History tab to indicate the number of calls
you missed since the last time you viewed the History fan.
6 IM tab Displays the Instant Messaging fan. The Instant Messaging fan
displays your instant messaging conversations.
When Avaya Multimedia Messaging is selected, the IM fan displays all
the Avaya Multimedia Messaging IM conversations.
7 Conference tab Click to display the Conference fan or roster fan and the Conference
tab buttons. The roster fan displays the contact cards for the
participants in the conference. The Conference tab buttons enable
you to filter the conference participants in the roster fan. Using the
Conference tab buttons, you can view:
• all participants in the conference
• all participants who are viewing the web collaboration session
• all participants who dropped from the call
You can sort the cards in the Conference fan by most recent
conference entry or alphabetically (from A to Z).
8 Conversation stage Provides a graphical representation of the selected call. A
conversation setup appears for each call you start or join. All calls in
progress (active and held) are displayed in the conversation stage.
You can use the New conversation + button in this area to start a
new conversation.
You can have a maximum of three conversations at a time.
9 Quick dial field Allows you to enter a phone number to make a voice or video call.
You can also use the dialpad in this field to re-dial a phone number.

The following figures show the Avaya Equinox™ for Windows client with the Contacts, History, IM,
and Conference tabs expanded. You must be logged in to the Avaya Equinox™ for Windows client to
access these tabs.

April 2016 Turnkey Overview and Specification 8.0 84

Comments on this document? [email protected]
 Avaya Aura® Communicator Integration overview

Click on the Contacts tab to view your list of contacts. You can also hover over a contact, as shown
in the image, to access channel buttons for voice call, video call, IM, and additional options.

Figure 13: Avaya Equinox™ for Windows with Contacts fan expanded

Click on the History tab to view call history. Missed calls are shown in red.

Figure 14: Avaya Equinox™ for Windows with History fan expanded

Click on the IM tab to view active and missed IM conversations.

April 2016 Turnkey Overview and Specification 8.0 85

Comments on this document? [email protected]
Interoperability

Figure 15: Avaya Equinox™ for Windows with Instant Messaging fan expanded

Click on the Conference tab to view conference call participants and manage your conference calls.

Figure 16: Avaya Equinox™ for Windows with Conference fan expanded

April 2016 Turnkey Overview and Specification 8.0 86

Comments on this document? [email protected]
 Avaya Aura® Communicator Integration overview

Related links
Overview on page 82

Button descriptions
The following table shows the main buttons in the Avaya Equinox™ for Windows client. Buttons are
grayed out when unavailable.

Button Name Purpose

Call To make a voice call.

Video To make a video call.

Instant Message To send an instant message.

Collaboration To start or join a Web

Collaboration session.

Settings To open the Settings dialog box

where you configure your servers,
dialing rules, enterprise directory
search settings, contacts search
settings, audio settings, video
settings, conference settings,
messaging, and preferences. The
Settings dialog box also displays
the software release information
and support information.
You can also access volume
control options from the Settings
dialog box.
End To hang up a voice or video call.

Answer To answer or join an unanswered

active call (bridged, EC500, or
Ignored) on the conversation
setup stage.
Cancel To remove all cards from the
conversation setup stage.

Mute To mute or unmute audio. When

the call is muted, the button is
blue.
Table continues…

April 2016 Turnkey Overview and Specification 8.0 87

Comments on this document? [email protected]
Interoperability

Button Name Purpose

Tip:
Use the Mute functionality in
Avaya Equinox™. Muting on
your desktop or through a
headset is reflected on the
Avaya Equinox™ interface.
Dialpad To open the dialpad. You can
enter touch-tone digits during a
call from the dialpad. You can also
use the dialpad to enter or re-dial
a phone number.
Hold To place the current call on hold or
resume a call on hold. When the
call is on hold, the button is blue.
More To open the More controls panel,
which contains the Moderator
controls tab and the Call controls
tab. The Moderator controls tab is
only available to the moderator.
The Call controls tab is available
to the moderator and participants
of the selected call.

Related links
Overview on page 82

Multiple Device Access overview

Avaya Equinox™ supports Multiple Device Access (MDA), which you can use to:
• Log on to the same extension from multiple devices, including mobile EC500 devices.
• Answer a call from multiple devices.
• Join an existing call from other logged in devices.
• Hear simultaneous ringing on all logged in devices when a call is made to your extension.
The Avaya Aura® network configuration, which your administrator configures, determines:
• The number of devices that you can log in to at the same time.
• Whether the first or last logged in device is denied login access when you reach the maximum
simultaneous device limit.
For more information, see Planning for and Administering Avaya Equinox™ for Android, iOS, Mac,
and Windows.

April 2016 Turnkey Overview and Specification 8.0 88

Comments on this document? [email protected]
 Operating system compatibility

MDA limitations
Support on other devices
• Some devices do not support MDA. You might be able to log in to these devices using the
same extension that you used to log in to your Avaya Equinox™ client. However, other MDA
functionality, such as the ability to answer a new call or join an existing call, might not work
properly.
If you have configured Avaya Multimedia Messaging and Avaya Aura® Presence Services, then
log in to the devices using the same messaging protocol. Else, the Forking feature might not
work properly and you cannot exchange messages with the same user from multiple devices.
• If you simultaneously subscribe MDA devices for Presence Services and publish to the
presence state, Presence Services aggregates the presence state across multiple devices. In
the MDA group, Avaya Aura® Presence Services supports only one IM-capable device to send
and receive IMs to other users.
Video escalation
• When more than one device is on a call, you cannot escalate the call to video. If additional
devices drop from the call and only one device remains on the call, you can escalate that call to
a video call.
• When a second device joins a video call, the video screen becomes blank.
• An EC500 device cannot escalate to a video call at any time even if the EC500 device is the
only device on the call.

Operating system compatibility

April 2016 Turnkey Overview and Specification 8.0 89

Comments on this document? [email protected]
Chapter 4: Capacity

Introduction to capacity
All traffic capacities quoted use the following assumptions for traffic pattern
• 100% of the sessions are using audio
• 35% use web collaboration with screen sharing
• 35% use web collaboration with library sharing
• 30% use video
• 10% of conferences are being recorded
All codecs and resolutions from Avaya Aura® Conferencing 7.2 are supported although capacity
targets were modelled using G.722+H.264 SVC 360p30@515kbps only.
Values provided here are guidelines only. System quotes should be generated using the normal
Avaya processes and tools.
A single audio conference can support up to 250 audio participants in a Meet Me Conference type,
and between 1,750 and 2,000 audio and 1,500 web conferencing participants in an Event
Conference.
There is a significant difference between bare-metal and virtual (VMWare OVA) performance. For a
VMWare solution to offer parity with a bare-metal solution requires a significant increase in resource
reservation once the OVA is installed.

Capacity information for bare-metal systems

Comparison
Parameters SMB Medium Large
Maximum concurrent 150 500 15000 (no web collab)
sessions
7500 (w/ web collab)
Minimum number of 1 1 3
servers
Table continues…

April 2016 Turnkey Overview and Specification 8.0 90

Comments on this document? [email protected]
 Capacity information for bare-metal systems

Parameters SMB Medium Large

Maximum number of 5 10 System cannot have
media cascade servers more than 64 media
servers in total
Maximum number of 1500 5000 150000
provisioned users

Breakdown of large servers

Server configurations Max concurrent audio Max concurrent video Max concurrent web
®
1 Mgmt, 1Avaya Aura 1500 450 1050
Media Server (AMS), 1
Document Conversion
Server (DCS)
Maximum Large 7500 2250 5250
Configuration (focus is
the Mgmt server)
AMS on 12x2.9Ghz CPU 2000 600 n/a
server
AMS on 6x2.3Ghz CPU 600 180 n/a
server
Event conference AMS 2000 600 n/a
WCS on dedicated n/a n/a 2100
server
DCS on dedicated server n/a n/a 200
Flash Media Gateway 525 525 n/a
(FMG) on dedicated
server
Collaboration Agent (CA) 525 525 1050
Manager + Flash Media
Gateway on dedicated
server
CA Manager + Web n/a n/a 1500
Collaboration Server
(WCS) + Web
Collaboration
Management Server
(WCMS) on dedicated
server
CA Manager + WCS + 225 225 600
WCMS + Flash Media
Gateway on dedicated
server

April 2016 Turnkey Overview and Specification 8.0 91

Comments on this document? [email protected]
Capacity

Capacity information for VMWare systems

Our VMWare capacity targets and resource requirements are based on testing on the HP ProLiant
DL360 G7 server platform with Intel® Xeon® X5670 2xHEX core @ 2.93 GHz. You can use this
information to make an informed decision about what to expect when choosing a different platform
on which to run. Avaya expects that the performance may vary depending on CPU chipset, memory,
number of cores, clock speed, hyper threading, and other factors. This means that Avaya cannot be
held to the capacity targets when other platforms are used. In such cases, our capacity targets
should then be used for general planning only. In some cases, you may have to deploy additional
virtual resources to reach their expected capacity targets. As a specific example, where the use of
the Xeon E5-2697 v3 @ 2.60GHz processor is desired, this processor is known to be faster at
2.6GHz than the Avaya-benchmarked processor at 2.9GHz and as such, should be acceptable for
use (in other words, Avaya supports our application on VMware on such a system).
Comparison
Parameters SMB Medium with Medium with Large
default OVA modified OVA
settings (8 vCPU) settings (12 vCPU)
Maximum Not supported 200 500 15000 (no web
concurrent sessions collab)
7500 (with web
collab)
Minimum number of Not supported 1 1 3
OVAs
Maximum number Not supported 10 10 System cannot
of media cascade have more than 64
servers media servers total
Maximum number Not supported 5000 5000 150000
of provisioned
users

Breakdown of OVA capacities in large OVA

Server configurations Max Concurrent audio Max Concurrent video Max Concurrent web
®
1 Mgmt, 1 Avaya Aura 1000 300 700
Media Server (AMS), 1
Document Conversion
Server (DCS) on single
large OVA
Maximum Large 7500 2250 5250
Configuration (focus is on
the Mgmt server)
AMS on 12x2.9Ghz CPU 800 240 n/a
server
Table continues…

April 2016 Turnkey Overview and Specification 8.0 92

Comments on this document? [email protected]
 Capacity information for VMWare systems

Server configurations Max Concurrent audio Max Concurrent video Max Concurrent web
AMS on 6x2.3Ghz CPU 540 160 n/a
server
Event conference AMS 1750 525 n/a
Web Collaboration n/a n/a 1800
Server (WCS) on
dedicated server
DCS on dedicated server n/a n/a 100
Flash Media Gateway on 525 525 n/a
dedicated server
Collaboration Agent (CA) 525 525 1050
Manager + Flash Media
Gateway on dedicated
server
CA Manager + WCS + n/a n/a 1500
WCMS on dedicated
server
CA Manager + WCS + 225 225 600
WCMS + Flash Media
Gateway on dedicated
server

April 2016 Turnkey Overview and Specification 8.0 93

Comments on this document? [email protected]
Glossary

Accounting Manager 1. Configures and manages (deploy/undeploy/start/stop) the various

(AM) network elements.

Application Server 1. SIP Application Server which is the focus point of all conferences.
(AS)

Avaya Media Server 1. Processes all audio/video streams under the supervision of the
(AMS) application server (AS).

Collaboration Agent 1. Hosts the Collaboration Agent and provides the portal for end user
(CA) driven service configuration changes. It is embedded in Provisioning
Manager for SMB/Medium deployments

Document 1. Converts uploaded presentations (Microsoft Powerpoint, and so on)

Conversion Server into a displayable format for sharing.
(DCS)

Element Manager 1. Configures and manages (deploy/undeploy/start/stop) the various

(EM) network elements.

April 2016 Turnkey Overview and Specification 8.0 94

Comments on this document? [email protected]
Index
Numerics components (continued)
Application Server ........................................................ 35
8.0.6 Conference Recording Server ...................................... 43
flexible deployment .......................................................27 Document Conversion Server ...................................... 43
Flash Media Gateway ...................................................44
Media Server ................................................................ 36
A overview ....................................................................... 35
ADCs ................................................................................... 45 SBC .............................................................................. 44
algorithms ............................................................................ 36 Web Server ...................................................................43
Application Server conference
components .................................................................. 35 profiles .......................................................................... 63
servers ..........................................................................35 conference controls ............................................................. 64
audio .................................................................................... 25 Conference Lock
audio and video features .........................................................................62
conferencing ................................................................. 29 conference owners overview ............................................... 59
audio and video conferences conference profiles
overview ....................................................................... 49 overview ....................................................................... 63
audio and video conferencing conference recording
features .........................................................................29 features .........................................................................53
overview ....................................................................... 29 Conference Recording Server
audio and video conferencing plug-in components .................................................................. 43
limitations ......................................................................25 servers ..........................................................................43
supported operating systems ....................................... 25 Conference Unlock
supported web browsers .............................................. 25 features .........................................................................62
audio conferences conferencing
overview ....................................................................... 49 audio and video ............................................................ 29
avaya media server Event
cascading ..................................................................... 36 Lecture mode ........................................................ 62
hosting .......................................................................... 36 features .........................................................................49
selection ....................................................................... 36 MeetMe .........................................................................30
recording .......................................................................53
Continuation
B features .........................................................................63
customization
button descriptions ...............................................................87
Collaboration Agent ...................................................... 32
buttons
main window navigation ............................................... 50
D
C delegate
Microsoft Outlook ..........................................................63
call me ................................................................................. 23
Document Conversion Server
capacity ..........................................................................33, 90
components .................................................................. 43
bare metal .....................................................................90
servers ..........................................................................43
VMWare ........................................................................92
cascading
avaya media server ...................................................... 36 E
Collaboration Agent
customization ................................................................32 encryption ............................................................................ 28
logs ............................................................................... 24 endpoints ............................................................................. 72
Permanent Association .................................................32 Event
Web collaboration ......................................................... 30 conferencing ................................................................. 30
compatibility ......................................................................... 71 Event conferencing
components features .........................................................................30
overview ....................................................................... 30

April 2016 Turnkey Overview and Specification 8.0 95

Comments on this document? [email protected]
Index

F Media Server (continued)

servers ..........................................................................36
Fast Start MeetMe
features .........................................................................63 conferencing ................................................................. 30
features MeetMe conferencing
audio and video conferencing .......................................29 features .........................................................................30
Conference Lock .......................................................... 62 overview ....................................................................... 30
conference recording ....................................................53 member ................................................................................59
Conference Unlock ....................................................... 62 Microsoft Outlook
conferencing ................................................................. 49 delegate ........................................................................63
Continuation ................................................................. 63 mode of operation ................................................................23
Event conferencing .......................................................30 moderators
Fast Start ...................................................................... 63 overview ....................................................................... 59
Lecture mode ................................................................62 multiple association ............................................................. 24
MeetMe conferencing ................................................... 30
overview ....................................................................... 28
Web collaboration ......................................................... 30
N
features overview .................................................................31 navigating
Flash Media Gateway main window .................................................................50
components .................................................................. 44 navigation tools
servers ..........................................................................44 main window .................................................................50
new features ........................................................................ 16
G
guest .................................................................................... 59
O
online help ............................................................................11
H operating systems
supported by audio and video conferencing plug-in ..... 25
hosting operators
avaya media server ...................................................... 36 overview ....................................................................... 59
OVAs ....................................................................................27
overview ...............................................................................82
I audio and video conferencing .......................................29
interoperability ............................................................... 73, 81 components .................................................................. 35
conference profiles ....................................................... 63
Event conferencing .......................................................30
L features .........................................................................28
MeetMe conferencing ................................................... 30
languages ............................................................................ 69
Multiple Device Access .................................................88
Lecture mode
Web collaboration ......................................................... 30
features .........................................................................62
licensing ...............................................................................22
limitations P
MDA ..............................................................................89
limitations of audio and video conferencing plug-in ............. 25 participants
load balancing ......................................................................45 overview ....................................................................... 59
logs Permanent Association
Collaboration Agent ...................................................... 24 Collaboration Agent ...................................................... 32
pop-up ..................................................................................26
presentation mode ............................................................... 23
M presenters
overview ....................................................................... 59
main window ........................................................................ 82
private chat .......................................................................... 23
navigating ..................................................................... 50
profiles
navigation tools .............................................................50
conference ....................................................................63
MDA .....................................................................................88
Media Server
components .................................................................. 36

April 2016 Turnkey Overview and Specification 8.0 96

Comments on this document? [email protected]
 Index

R V
recording video .................................................................................... 25
conferencing ................................................................. 53 features .........................................................................77
release 8.0 video conferences overview ................................................ 49
call me .......................................................................... 23 videos .................................................................................. 10
cleaner upgrades ..........................................................22
codec flexibility ............................................................. 21
DCS on Linux ............................................................... 20
W
enhancements for mobile users ................................... 18 web browsers
mode of operation .........................................................23 supported by audio and video conferencing plug-in ..... 25
multiple association ...................................................... 24 Web collaboration
private chat ................................................................... 23 Collaboration Agent ...................................................... 30
recording enhancements .............................................. 22 features .........................................................................30
reverse proxy ................................................................18 overview ....................................................................... 30
server clusters .............................................................. 20 Web Collaboration components ...........................................52
video quality ..................................................................20 Web Server
VMWare ........................................................................19 components .................................................................. 43
servers ..........................................................................43
S
SBC
components .................................................................. 44
security certificates .............................................................. 17
selection
avaya media server ...................................................... 36
servers
Application Server ........................................................ 35
Conference Recording Server ...................................... 43
Document Conversion Server ...................................... 43
Flash Media Gateway ...................................................44
Media Server ................................................................ 36
Web Server ...................................................................43
sockets .................................................................................26
support .................................................................................13

T
telephony
features .........................................................................77
timeout ................................................................................. 28
turnkey ................................................................................. 14
turnkey features ................................................................... 34

U
universal .............................................................................. 14
universal features ................................................................ 34
user roles overview
conference owners ....................................................... 59
moderators ................................................................... 59
operators ...................................................................... 59
participants ................................................................... 59
presenters .....................................................................59
user types ............................................................................ 59

April 2016 Turnkey Overview and Specification 8.0 97

Comments on this document? [email protected]