Avaya one-X® Client Enablement Services
Overview and Specification
Release 6.2
Issue 1.7
November 2015
© 2012-2015, Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves
the right to make changes and corrections to the information in this
document without the obligation to notify any person or organization
of such changes.
Documentation disclaimer
“Documentation” means information published by Avaya in varying
mediums which may include product information, operating
instructions and performance specifications that Avaya may generally
make available to users of its products and Hosted Services.
Documentation does not include marketing materials. Avaya shall not
be responsible for any modifications, additions, or deletions to the
original published version of documentation unless such
modifications, additions, or deletions were performed by Avaya. End
User agrees to indemnify and hold harmless Avaya, Avaya's agents,
servants and employees against all claims, lawsuits, demands and
judgments arising out of, or in connection with, subsequent
modifications, additions or deletions to this documentation, to the
extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked
websites referenced within this site or documentation provided by
Avaya. Avaya is not responsible for the accuracy of any information,
statement or content provided on these sites and does not
necessarily endorse the products, services, or information described
or offered within them. Avaya does not guarantee that these links will
work all the time and has no control over the availability of the linked
pages.
Warranty
Avaya provides a limited warranty on Avaya hardware and software.
Refer to your sales agreement to establish the terms of the limited
warranty. In addition, Avaya’s standard warranty language, as well as
information regarding support for this product while under warranty is
available to Avaya customers and other parties through the Avaya
Support website: http://support.avaya.com/helpcenter/
getGenericDetails?detailId=C20091120112456651010 under the link
“Warranty & Product Lifecycle” or such successor site as designated
by Avaya. Please note that if You acquired the product(s) from an
authorized Avaya Channel Partner outside of the United States and
Canada, the warranty is provided to You by said Avaya Channel
Partner and not by Avaya.
“Hosted Service” means a hosted service subscription that You
acquire from either Avaya or an authorized Avaya Channel Partner
(as applicable) and which is described further in Hosted SAS or other
service description documentation regarding the applicable hosted
service. If You purchase a Hosted Service subscription, the foregoing
limited warranty may not apply but You may be entitled to support
services in connection with the Hosted Service as described further
in your service description documents for the applicable Hosted
Service. Contact Avaya or Avaya Channel Partner (as applicable) for
more information.
Hosted Service
THE FOLLOWING APPLIES IF YOU PURCHASE A HOSTED
SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO UNDER
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR
IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
SERVICE. YOUR USE OF THE HOSTED SERVICE SHALL BE
LIMITED BY THE NUMBER AND TYPE OF LICENSES
PURCHASED UNDER YOUR CONTRACT FOR THE HOSTED
SERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTED
SERVICES IF APPLICABLE, YOU MAY HAVE THE OPPORTUNITY
TO USE FLEX LICENSES, WHICH WILL BE INVOICED
ACCORDING TO ACTUAL USAGE ABOVE THE CONTRACT
LICENSE LEVEL. CONTACT AVAYA OR AVAYA’S CHANNEL
PARTNER FOR MORE INFORMATION ABOUT THE LICENSES
FOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITY
OF ANY FLEX LICENSES (IF APPLICABLE), PRICING AND
BILLING INFORMATION, AND OTHER IMPORTANT
INFORMATION REGARDING THE HOSTED SERVICE.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO, UNDER
THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN
AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
AND ANYONE ELSE USING OR SELLING THE SOFTWARE
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
SOFTWARE (HEREINAFTER REFERRED TO
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
THESE TERMS AND CONDITIONS AND CREATE A BINDING
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
Avaya grants You a license within the scope of the license types
described below, with the exception of Heritage Nortel Software, for
which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
applicable license will be a Designated System License. The
applicable number of licenses and units of capacity for which the
license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the documentation or other
materials available to You. “Software” means computer programs in
object code, provided by Avaya or an Avaya Channel Partner,
whether as stand-alone products, pre-installed on hardware products,
and any upgrades, updates, patches, bug fixes, or modified versions
thereto. “Designated Processor” means a single stand-alone
computing device. “Server” means a Designated Processor that
hosts a software application to be accessed by multiple users.
“Instance” means a single copy of the Software executing at a
particular time: (i) on one physical machine; or (ii) on one deployed
software virtual machine (“VM”) or similar deployment.
License types
Designated System(s) License (DS). End User may install and use
each copy or an Instance of the Software only on a number of
Designated Processors up to the number indicated in the order.
Avaya may require the Designated Processor(s) to be identified in
the order by type, serial number, feature key, Instance, location or
other specific designation, or to be provided by End User to Avaya
through electronic means established by Avaya specifically for this
purpose.
Concurrent User License (CU). End User may install and use the
Software on multiple Designated Processors or one or more Servers,
so long as only the licensed number of Units are accessing and using
the Software at any given time. A “Unit” means the unit on which
Avaya, at its sole discretion, bases the pricing of its licenses and can
be, without limitation, an agent, port or user, an e-mail or voice mail
account in the name of a person or corporate function (e.g.,
webmaster or helpdesk), or a directory entry in the administrative
database utilized by the Software that permits one user to interface
with the Software. Units may be linked to a specific, identified Server
or an Instance of the Software.
CPU License (CP). End User may install and use each copy or
Instance of the Software on a number of Servers up to the number
indicated in the order provided that the performance capacity of the
Server(s) does not exceed the performance capacity specified for the
Software. End User may not re-install or operate the Software on
Server(s) with a larger performance capacity without Avaya’s prior
consent and payment of an upgrade fee.
contain software (including open source software) distributed under
third party agreements (“Third Party Components”), which contain
terms regarding the rights to use certain portions of the Software
(“Third Party Terms”). As required, information regarding distributed
Linux OS source code (for those products that have distributed Linux
OS source code) and identifying the copyright holders of the Third
Party Components and the Third Party Terms that apply is available
in the products, Documentation or on Avaya’s website at: http://
support.avaya.com/Copyright or such successor site as designated
by Avaya. The open source software license terms provided as Third
Party Terms are consistent with the license rights granted in these
Software License Terms, and may contain additional rights benefiting
You, such as modification and distribution of the open source
software. The Third Party Terms shall take precedence over these
Software License Terms, solely with respect to the applicable Third
Party Components to the extent that these Software License Terms
impose greater restrictions on You than the applicable Third Party
Terms.
Named User License (NU). You may: (i) install and use each copy or
Instance of the Software on a single Designated Processor or Server
per authorized Named User (defined below); or (ii) install and use
each copy or Instance of the Software on a Server so long as only
authorized Named Users access and use the Software. “Named
User”, means a user or device that has been expressly authorized by
Avaya to access and use the Software. At Avaya’s sole discretion, a
“Named User” may be, without limitation, designated by name,
corporate function (e.g., webmaster or helpdesk), an e-mail or voice
mail account in the name of a person or corporate function, or a
directory entry in the administrative database utilized by the Software
that permits one user to interface with the Software.
The following applies if the H.264 (AVC) codec is distributed with the
product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT
PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE
REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG
LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.
Shrinkwrap License (SR). You may install and use the Software in
accordance with the terms and conditions of the applicable license
agreements, such as “shrinkwrap” or “clickthrough” license
accompanying or applicable to the Software (“Shrinkwrap License”).
Service Provider
Database License (DL). End User may install and use each copy or
an Instance of the Software on one Server or on multiple Servers
provided that each of the Servers on which the Software is installed
communicates with no more than one Instance of the same
database.
Heritage Nortel Software
“Heritage Nortel Software” means the software that was acquired by
Avaya as part of its purchase of the Nortel Enterprise Solutions
Business in December 2009. The Heritage Nortel Software is the
software contained within the list of Heritage Nortel Products located
at http://support.avaya.com/LicenseInfo under the link “Heritage
Nortel Products” or such successor site as designated by Avaya. For
Heritage Nortel Software, Avaya grants Customer a license to use
Heritage Nortel Software provided hereunder solely to the extent of
the authorized activation or authorized usage level, solely for the
purpose specified in the Documentation, and solely as embedded in,
for execution on, or for communication with Avaya equipment.
Charges for Heritage Nortel Software may be based on extent of
activation or use authorized as specified in an order or invoice.
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, Hosted Service,
or hardware provided by Avaya. All content on this site, the
documentation, Hosted Service, and the product provided by Avaya
including the selection, arrangement and design of the content is
owned either by Avaya or its licensors and is protected by copyright
and other intellectual property laws including the sui generis rights
relating to the protection of databases. You may not modify, copy,
reproduce, republish, upload, post, transmit or distribute in any way
any content, in whole or in part, including any code and software
unless expressly authorized by Avaya. Unauthorized reproduction,
transmission, dissemination, storage, and or use without the express
written consent of Avaya can be a criminal, as well as a civil offense
under the applicable law.
Virtualization
The following applies if the product is deployed on a virtual machine.
Each product has its own ordering code and license types. Note that
each Instance of a product must be separately licensed and ordered.
For example, if the end user customer or Avaya Channel Partner
would like to install two Instances of the same type of products, then
two products of that type must be ordered.
Third Party Components
“Third Party Components” mean certain software programs or
portions thereof included in the Software or Hosted Service may
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S
HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY
FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL
PARTNER’S HOSTING OF AVAYA PRODUCTS MUST BE
AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED
PRODUCTS USE OR EMBED CERTAIN THIRD PARTY
SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT
SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS
REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE
LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S
EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY
SUPPLIER.
WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE
AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES
THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY
AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729
CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE
WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC IS
LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
THE PERSONAL USE OF A CONSUMER OR OTHER USES IN
WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)
ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD
(“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS
ENCODED BY A CONSUMER ENGAGED IN A PERSONAL
ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER
LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS
MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
WWW.MPEGLA.COM.
Compliance with Laws
Customer acknowledges and agrees that it is responsible for
complying with any applicable laws and regulations, including, but not
limited to laws and regulations related to call recording, data privacy,
intellectual property, trade secret, fraud, and music performance
rights, in the country or territory where the Avaya product is used.
Preventing Toll Fraud
“Toll Fraud” is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
company's behalf). Be aware that there can be a risk of Toll Fraud
associated with your system and that, if Toll Fraud occurs, it can
result in substantial additional charges for your telecommunications
services.
Avaya Toll Fraud intervention
If You suspect that You are being victimized by Toll Fraud and You
need technical assistance or support, call Technical Service Center
Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
States and Canada. For additional support telephone numbers, see
the Avaya Support website: http://support.avaya.com or such
successor site as designated by Avaya.
Security Vulnerabilities
Information about Avaya’s security support policies can be found in
the Security Policies and Support section of https://
support.avaya.com/security.
Suspected Avaya product security vulnerabilities are handled per the
Avaya Product Security Support Flow (https://
support.avaya.com/css/P8/documents/100161515).
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support website: http://support.avaya.com, or such successor site as
designated by Avaya.
Contact Avaya Support
See the Avaya Support website: http://support.avaya.com for product
or Hosted Service notices and articles, or to report a problem with
your Avaya product or Hosted Service. For a list of support telephone
numbers and contact addresses, go to the Avaya Support website:
http://support.avaya.com (or such successor site as designated by
Avaya), scroll to the bottom of the page, and select Contact Avaya
Support.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation, Hosted Service(s), and product(s) provided
by Avaya are the registered or unregistered Marks of Avaya, its
affiliates, or other third parties. Users are not permitted to use such
Marks without prior written consent from Avaya or such third party
which may own the Mark. Nothing contained in this site, the
Documentation, Hosted Service(s) and product(s) should be
construed as granting, by implication, estoppel, or otherwise, any
license or right in and to the Marks without the express written
permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners.
Linux® is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Contents
Chapter 1: Introduction............................................................................................................ 7
Purpose.................................................................................................................................. 7
Intended audience................................................................................................................... 7
Related resources................................................................................................................... 7
Documentation.................................................................................................................. 7
Training............................................................................................................................ 8
Avaya Mentor videos......................................................................................................... 8
Support.................................................................................................................................. 9
Warranty................................................................................................................................. 9
®
Chapter 2: Avaya one-X Client Enablement Services overview....................................... 10
Client integration architecture................................................................................................. 11
Communication Manager................................................................................................. 14
Session Manager............................................................................................................ 15
System Manager............................................................................................................. 16
Presence........................................................................................................................ 17
Messaging...................................................................................................................... 20
Conferencing.................................................................................................................. 20
LDAP............................................................................................................................. 21
WebLM........................................................................................................................... 22
SAL Gateway.................................................................................................................. 22
Handset Server............................................................................................................... 23
IHS................................................................................................................................ 23
Security Appliance........................................................................................................... 23
®
Avaya one-X Communicator........................................................................................... 24
®
Avaya one-X Mobile....................................................................................................... 25
Feature description................................................................................................................ 26
User features.................................................................................................................. 27
Administration features.................................................................................................... 29
New in this release................................................................................................................ 30
Feature comparison............................................................................................................... 31
Chapter 3: Interoperability..................................................................................................... 33
Product compatibility.............................................................................................................. 33
Product requirements for features..................................................................................... 33
Third-party product connectivity.............................................................................................. 35
Operating system compatibility............................................................................................... 35
Chapter 4: Performance specifications................................................................................ 36
Capacity and scalability specifications..................................................................................... 36
Dial plan specification............................................................................................................ 37
Chapter 5: Environmental requirements.............................................................................. 39
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
5
Contents
Altitude and air pressure requirements.................................................................................... 39
Hardware dimensions and clearance requirements.................................................................. 40
Physical system protection requirements................................................................................. 44
Regulatory standards............................................................................................................. 45
Chapter 6: Security................................................................................................................. 46
Security specification............................................................................................................. 46
Password cache behavior................................................................................................ 47
Port utilization....................................................................................................................... 48
Chapter 7: Licensing requirements....................................................................................... 49
Glossary................................................................................................................................... 50
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
6
Chapter 1: Introduction
Purpose
This document describes tested product characteristics and capabilities, including product overview
and feature descriptions, interoperability, performance specifications, security, and licensing
requirements.
Intended audience
This document is intended for anyone who wants to gain a high-level understanding of the product
features, functions, capacities, and limitations within the context of solutions and verified reference
configurations.
Related resources
Documentation
You can download the latest copies of these documents from the Avaya Support website at http://
support.avaya.com.
Title
Avaya one-X® Client Enablement Services Overview and Specification
Implementing Avaya one-X® Client Enablement Services
Administering Avaya one-X® Client Enablement Services
Avaya one-X® Client Enablement Services online Help for administrators
Using Avaya one-X® Mobile on Android
Using Avaya one-X® Mobile on Blackberry (touch screen model)
Using Avaya one-X® Mobile on Blackberry (nontouch-screen model)
Table continues…
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
7
Introduction
Title
Using Avaya one-X® Mobile on iPhone
Avaya one-X® Mobile on Android Quick Start Guide
Avaya one-X® Mobile on Blackberry (touch screen model) Quick Start Guide
Avaya one-X® Mobile on Blackberry (nontouch-screen model) Quick Start Guide
Troubleshooting Avaya one-X® Client Enablement Services
Installing the HP DL360 G7 Server
Installing the HP ProLiant DL360p G8 Server
Installing the Dell™ PowerEdge™ R610 Server
Training
The following courses are available on http://www.avaya-learning.com. To search for a course, enter
the course code in the Search field and click Go.
Course code
Course title
5U00070V
Avaya one-X® Client Enablement Services Implementation and Maintenance
5U00070I
Avaya one-X® Client Enablement Services Implementation and Maintenance
3U00044W
Designing Avaya one-X® UC Soft Clients
ASC00266WEN
Selling Avaya one-X® UC Soft Clients
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.
Procedure
• To find videos on the Avaya Support website, go to http://support.avaya.com, select the
product name, and check the videos checkbox to see a list of available videos.
• To find the Avaya Mentor videos on YouTube, go to http://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 site.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
8
Support
Note:
Videos are not available for all products.
Support
Visit 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
Avaya provides a 3-month limited warranty on Avaya one-X® Client Enablement Services. Detailed
terms and conditions contained in the sales agreement or other applicable documentation establish
the terms of the limited warranty. For the standard Avaya warranty description and details of support
under warranty, see the Avaya Support website at http://support.avaya.com. See specifically Avaya
Global Software License Terms.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
9
Chapter 2: Avaya one-X® Client Enablement
Services overview
Client Enablement Services brings Unified Communications (UC) to your desktop and mobile
phones. Use Client Enablement Services to gain access to multiple Avaya UC capabilities, including
telephony, messaging, mobility, conferencing, and presence services.
With Client Enablement Services, you do not need multiple applications to gain access to the
features provided by:
• Avaya Aura® Communication Manager
• Avaya Aura® Communication Manager Messaging or Avaya Modular Messaging or Avaya
Aura® Messaging
• Avaya Aura® Conferencing or Avaya Aura® Meeting Exchange
• Avaya Aura® Presence Services
In Client Enablement Services, the UC clients of Avaya one-X® Communicator and Avaya one-X®
Mobile need a single server. Client Enablement Services supports a thick client and mobile interface
to gain access to the functionality supported on the server. The Client Enablement Services server
delivers continuous user data and provides a consistent user experience across clients.
Avaya one-X® Communicator provides the Softphone capability. The UC features of Avaya one-X®
Communicator include:
• Visual voice mails that help you filter and sort voice messages so that you can respond to the
most important messages quickly.
• Communication History logs that help you trace the history of your enterprise calls and voice
messages.
• Contact management tools that help you find contact information quickly and view the
presence information of corporate contacts.
Use Avaya one-X® Communicator to increase the productivity of your enterprise with tools that
enhance collaboration, improve responsiveness, and lower costs for IT and user support.
Use Avaya one-X® Mobile to enable your mobile phone to gain access to the telephone system of
your company. Using Avaya one-X® Mobile, you can use your office telephone number to make and
receive calls, review voice mail messages, look up your company corporate directory, and even
block selected calls regardless of your location.
Related links
Feature description on page 26
New in this release on page 30
Feature comparison on page 31
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
10
Client integration architecture
Client integration architecture
The architecture diagram shows the relationship between the Client Enablement Services server
and the servers and clients with which Client Enablement Services integrates.
Deployment models
You can use the following deployment models to provide clients both on-premise and remote access
to services offered by Client Enablement Services:
• Handset Server
• Security Appliance
• VPN
The IP address of Client Enablement Services must be routable from any of the following:
• Handset Server: Deployment model 1
• Security Appliance: Deployment model 2
• VPN gateway: Deployment model 3
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
11
Avaya one-X® Client Enablement Services overview
Client Enablement Services does not make outbound connections to servers in the DMZ or clients in
the internet. The Client Enablement Services server only accepts incoming client connections and
makes connections to servers in the enterprise trusted network.
In all the deployments models:
• Avaya one-X® Communicator only uses HTTPS, 443, and does not use the SSL connection,
7777, that is needed by the mobile clients.
• Avaya one-X® Communicator does not have a cellular voice interface.
• All of the Avaya one-X® Communicator traffic that must be considered for a complete Avaya
one-X® Communicator client deployment is not displayed. For example, H.323 or SIP.
Deployment model 1: Handset Server
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
12
Client integration architecture
Deployment model 2: Security Appliance (For example: Reverse Proxy)
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
13
Avaya one-X® Client Enablement Services overview
Deployment model 3: VPN gateway
Communication Manager
Communication Manager is a key component of the Avaya Aura® portfolio and delivers rich voice
and video capabilities. Communication Manager provides a resilient, distributed network for:
• Media gateways
• Analog, digital, and IP-based communication devices
In addition, Communication Manager delivers robust PBX features, high reliability and scalability,
and multiprotocol support. Communication Manager includes advanced mobility features, built-in
conference calling and contact center applications, and E911 capabilities.
Communication Manager is a mandatory component in Client Enablement Services. You can
connect Communication Manager to Client Enablement Services directly or using Avaya Aura®
Session Manager. Communication Manager and Client Enablement Services interact with each
other using Session Initiation Protocol - Transport Layer Security (SIP-TLS) to deliver the UC
functionality and support telephony and IM clients.
Note:
Client Enablement Services does not support the Communication Manager 6.0 Feature Server
(CM-FS) implementation.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
14
Client integration architecture
CM-FS is Communication Manager acting as a SIP feature server. Feature Server is the descriptor
for the option of deploying Communication Manager in the core or branch, in half-call model,
supporting only SIP endpoints with full application sequencing.
Communication Manager Evolution Server (CM-ES) is Communication Manager with minor
changes. Evolution Server is the descriptor for the option of deploying Communication Manager in
the core or branch, in full-call model, supporting both SIP and non-SIP endpoints with limited
application sequencing.
Because of the integration with Communication Manager, Client Enablement Services offers the
following benefits:
• Robust voice and video call processing capabilities
• Advanced workforce productivity and mobility features
• Centralized voice mail and attendant operations across multiple locations
• Support for SIP, H.323, and many industry standard communications protocols over a variety
of different networks
• More than 700 powerful features
• High availability, reliability, and survivability
Session Manager
Companies usually have a diverse set of communications products within their corporate intranet
that cannot communicate with each other. You require a standard signaling protocol to make these
products work together. Avaya has adopted SIP as the signaling protocol for communication.
Session Manager is a SIP routing and integration tool and the core component of the Avaya Aura®
portfolio.
Session Manager integrates all SIP devices across the entire enterprise network within a company
and does not manage individual locations as separate units within the enterprise. Each location,
branch, or application is part of the overall enterprise and is managed as an enterprise.
In Client Enablement Services, Communication Manager interacts with Session Manager to deliver
the UC functionality and support telephony and IM clients. Avaya Aura® System Manager connects
to Session Manager for administration of Session Manager.
The benefits of routing Client Enablement Services traffic through Session Manager are:
• In an Avaya Aura® environment, Session Manager acts as a centralized SIP routing for Client
Enablement Services and other Avaya applications.
• Simplifies the deployment and configuration when customer has multiple Communication
Manager with Client Enablement Services enabled. The customer needs to configure only one
SIP trunk between Client Enablement Services and Session Manager.
• Client Enablement Services leverages the existing SIP trunks connecting from Session
Manager to each Communication Manager without the need to create new SIP trunks between
Communication Manager and Client Enablement Services.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
15
Avaya one-X® Client Enablement Services overview
• The customer can add additional Session Manager in Client Enablement Services to provide
redundancy. If the primary Session Manager fails, SIP routing will failover to next Session
Manager.
• Session Manager acts as a SIP proxy only for Client Enablement Services.
• For TLS link between Client Enablement Services and Communication Manager, you need to
install the certificate on Communication Manager. However, you do not need a certificate for
TLS links between Client Enablement Services and Session Manager, and Communication
Manager and Session Manager.
In Client Enablement Services, Session Manager is not required for using the following features:
• Telephony in Avaya one-X® Mobile where Communication Manager is used as an Access
Element or Evolution Server.
• Telephony in the Avaya one-X® Communicator H.323 mode using a non-Aura implementation.
• Conferencing in the Avaya one-X® Communicator H.323 mode.
Because of the integration with Session Manager, Client Enablement Services offers the following
benefits:
• A simplified network-wide feature deployment
• Centralized routing, SIP trunking, and user profiles
• Cost-effective scalability from small to very large deployments
• High availability with geographic redundancy
• A secure environment that conforms to specific SIP standards and practices
System Manager
System Manager is a central management system that delivers a set of shared management
services and a common console for the components of System Manager in an enterprise.
System Manager is an optional component for implementing Client Enablement Services. Client
Enablement Services communicates with System Manager to obtain the presence provisioning
information.
System Manager supports only one LDAP server. Hence, the Presence Services server does not
support multiple domains. Hence, if you are using multiple Active Directory domains in Client
Enablement Services, users of only one domain can use services provided by the Presence
Services server.
Because of the integration with System Manager, Client Enablement Services offers the following
benefits:
• Licenses: Features for administering licenses for individual components of the Avaya Aura®
portfolio.
• Security: Certificates needed for gaining access to Presence Services.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
16
Client integration architecture
Limitations when you deploy Client Enablement Services without System Manager:
• Client Enablement Services does not support the presence feature.
Presence
Presence is an indication of the availability of an individual at a point in time and readiness to
communicate across a set of services such as telephony and instant messaging. Presence Services
indicates the presence or availability of a person by states like Available, Busy, and Away.
Presence Services supports presence information gathered from a diverse range of sources and
aggregates this information for each user. Presence Services then makes this information available
to applications that include the presence feature.
Applications interested in the presence of a user must first subscribe to receive presence
information. In Client Enablement Services, Session Manager and System Manager are mandatory
for using Presence Services.
Presence Server collects presence information from various sources, such as Avaya Aura®
Application Enablement Services (AES), Microsoft Office™ Communicator Server (OCS), IBM
Lotus™ Sametime Server, and individual devices such as SIP phones, Avaya one-X®
Communicator, and so on. Use the Avaya one-X® Mobile application to view the presence
information from various interfaces in the application such as corporate directory search results, call
history, or visual voice mail.
The Avaya one-X® Mobile application displays the current presence status of the user on the Home
screen as Availability. You can select an availability status, or you can select the Auto-Manage
option to let the application set your availability status.
You can create a custom message to indicate your availability status. The application displays your
current custom message on the Home screen of the application.
Setting presence manually:
Avaya one-X® Mobile does not publish the presence state as Available after you log in unless you
manually set the presence using Avaya one-X® Mobile.
In the manual mode, you must manually set your availability status to one of the following:
• Available
• Busy
• Unavailable
• Out of Office
• Offline
Using Auto-Manage to manage your availability:
If you want the application to set your availability based on the availability status of your deskphone,
you must set your availability status to Auto-Manage.
Presence limitations:
• Client Enablement Services supports only a single Presence Server.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
17
Avaya one-X® Client Enablement Services overview
• If the enterprise directory that you are using with Client Enablement Services is Microsoft
Active Directory Application Mode (ADAM), then Client Enablement Services does not support
presence.
• In a multi-domain configuration, the administrator can configure presence for users only in one
domain.
• In the Auto-Manage mode, Avaya one-X® Mobile does not influence presence in any way.
Hence, if you are using Avaya one-X® Mobile, then you might still appear as offline if your other
devices are offline.
Behavior: Availability:
Availability is the current presence status of the user on the application. Availability is also referred to as selfpresence.
AES
User client configuration
configured
Auto-Manage
Result
No
Single client: 1XCES
Yes
Client always appears as offline.
No
Single client: 1XCES
No: User sets
presence
manually
Client availability always displays whatever
presence state is set manually.
No
Multiple clients: 1XCES and
other presence enabled client
such as iPad Flare
Yes
Client availability always displays whatever
presence state is published by the other
client such as iPad Flare.
No
Multiple clients: 1XCES and
other presence enabled client
such as iPad Flare
User sets
presence
manually on
1XCES
1XCES pushes the manual presence update
to Presence Services. Presence Services
then updates the self-presence state for the
user and all clients of that user must, based
on that update, show the same manual
presence that was set.
Yes
Single client: 1XCES
Yes
Client always appears as Available unless
the user is on a call in which case the client
appears as Busy.
Note:
This result is true and valid until Avaya
Aura® FP3, at which point if 1XCES is
the only client, then the client always
appears as Offline unless the user is on
a call in which case the client appears
as Busy.
Yes
Single client: 1XCES
No: User sets
presence
manually
Client availability always displays whatever
presence state is set manually.
Yes
Multiple clients: 1XCES and
other presence enabled client
such as iPad Flare
Yes
The resultant presence state between AES
and the other presence enabled client is
determined by the Presence Services
aggregation logic.
Table continues…
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
18
Client integration architecture
AES
User client configuration
configured
Auto-Manage
Result
For example, AES publishes available and
the iPad Flare client logs out and goes
offline, then the presence state of the user
always appears as available.
Note:
This result is true and valid until Avaya
Aura® FP3. Else, for Avaya Aura® FP3
AES publishes available if an H.323
device is registered, otherwise AES
publishes Offline.
Yes
Multiple clients: 1XCES and
other presence enabled client
such as iPad Flare
User sets
presence
manually on
1XCES
1XCES pushes the manual presence update
to Presence Services. Presence Services
then updates the self-presence state for the
user and all clients of that user must, based
on that update, show the same manual
presence that was set.
Examples: Availability:
If a user uses only a single Client Enablement Services client and the administrator deploys Client
Enablement Services without AES, then:
• In the Auto-Manage mode, the availability status of the user is always Offline.
• In the manual mode, the availability status displays the presence that the user selects
manually.
If a user uses only a single Client Enablement Services client and the administrator deploys Client
Enablement Services with AES, then:
• In the Auto-Manage mode, the availability status of the user is always Available unless the
user is on a call in which case the availability status appears as Busy.
Note:
The administrator can optionally configure the AES collector timers that automatically set
the presence of a user to Unavailable or Out of Office after a period of time since the last
call was made. This feature is made available in Avaya Aura® FP3.
• In the manual mode, the availability status displays the presence that the user selects
manually.
If the Client Enablement Services user has more than one client that supports presence, that is,
Avaya one-X® Communicator, Flare iPad, etc., then self-presence is subject to the aggregation rules
on Presence Services.
• Without AES, Client Enablement Services does not publish presence. Hence, the availability
status of the user displays the presence that is available on the other client.
• With AES, self-presence is subject to the aggregation rules on Presence Services.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
19
Avaya one-X® Client Enablement Services overview
Messaging
The messaging server is an enterprise-class system that meets flexible deployment options in single
site and multisite environments. The messaging server is flexible, scalable, resilient, and easy to
deploy on standard Linux-based servers.
The messaging server enhances productivity by enabling quick and effective communication and
collaboration across an enterprise. Using the variety of features and capabilities the solution offers,
users can receive and respond to calls and contacts from customers, partners, and co-workers
faster and more efficiently.
The messaging server is an optional component for use with Client Enablement Services. You can
use any of the following messaging servers with Client Enablement Services:
• Modular Messaging
• Avaya Aura® Messaging
• Communication Manager Messaging
Note:
To implement Modular Messaging or Communication Manager Messaging, you do not require
Session Manager and System Manager.
Client Enablement Services integrates with any of the messaging servers using only the Avaya
message store and not any other email message store. Client Enablement Services uses:
• Internet Message Access Protocol Secure (IMAPS) for retrieving voice mails.
• Simple Mail Transfer Protocol (SMTP) for sending email and SMS.
Because of the integration with any of the messaging servers, Client Enablement Services offers the
following benefits:
• Transfers important calls to the right person, at the right time.
• Alerts employees to critical new messages.
• Lowers the cost of acquisition, implementation, and ownership of the messaging servers
through standards-based interfaces for easy integration with the existing networks,
administrative systems, and security processes.
• Provides multiple configuration choices for scalability that significantly lower total cost of
ownership (TCO) while offering new business continuity options.
Conferencing
Avaya Aura® Conferencing is a fully integrated audio and data conferencing solution for your
organization. Avaya Aura® Conferencing consists of a number of components that provide booking
engines, account management utilities, data sharing functionality, billing outputs, directory server
integration capabilities, and audio management for all calls.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
20
Client integration architecture
In the Standard Edition of Avaya Aura® Conferencing, the media server and the application server
reside on a single server making the unit suitable for smaller deployments.
Client Enablement Services also supports another conferencing server called Avaya Aura® Meeting
Exchange Enterprise Edition. Enterprise Edition of Meeting Exchange suits larger, more complex
deployments.
Enterprise Edition of Meeting Exchange supports complicated installations such as those with
multiple application servers, a global distribution of servers, and redundancy requirements.
Enterprise Edition of Meeting Exchange also supports additional functionality, such as selfregistration for conferences, reseller and wholesaler users, and Avaya Web Conferencing recording
and playback.
Client Enablement Services uses BreadCrumb Application Programming Interface (BCAPI) to
communicate with the conferencing server.
LDAP
The LDAP server is a database that contains system data, user data, and Class of Service (CoS)
data that is assigned to a user. Customers must gain access to the user database to administer the
data in bulk. The LDAP server is also known as an authentication server.
Note:
LDAP does not include mailbox data such as messages, greetings, and announcements.
Client Enablement Services sources and authenticates users from LDAP. Client Enablement
Services uses LDAP Secure (LDAPS) to communicate with the LDAP server.
Client Enablement Services supports the following LDAP servers:
• Microsoft Active Directory
• Microsoft ADAM
• IBM Domino Server
• Novell eDirectory
• SUN Directory Server Enterprise Edition
Note:
Client Enablement Services does not support integration with the Presence Services server if
you are using ADAM as the enterprise directory.
Client Enablement Services supports multiple Microsoft Active Directory domains:
• Multiple Active Directory instances with one domain per instance
• Single Active Directory instance with multiple domains
Client Enablement Services supports the following configurations:
• Single Active Directory with single domain
• Single Active Directory with multiple domains
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
21
Avaya one-X® Client Enablement Services overview
• Multiple Active Directories with multiple domains
• Active Directory split domain
• Active Directory split domain plus single Active Directory with single domain
Important:
During the installation of Client Enablement Services, you can configure multiple domains for
use with Client Enablement Services. However, after you complete the Client Enablement
Services installation, to perform any changes in the multiple-domain configuration, you must
reinstall Client Enablement Services.
Note:
The Presence Services server does not support multiple domains as System Manager supports
only one LDAP server. Hence, if you are using multiple Active Directory domains in Client
Enablement Services, users of only one domain can use services provided by the Presence
Services server.
WebLM
Avaya WebLM is a Web-based license manager that runs on both Microsoft Windows and UNIX or
Linux systems. Avaya has designed WebLM to support software products that require licenses. The
WebLM server provides a Web user interface (UI) for license administration. Use a standard Web
browser over a secure SSL link, HTTPS, for administration.
As WebLM is Web-based, WebLM facilitates easy and faster tracking of licenses. Administrators
can use WebLM to track and manage licenses of multiple Avaya software products from a single
location.
Client Enablement Services uses local WebLM or WebLM of remote System Manager to distribute
the software licenses. Use the local WebLM server only if WebLM of System Manager is
unavailable.
SAL Gateway
Avaya SAL Gateway remotely manages and provides service support for a variety of devices and
products. SAL Gateway monitors alarms generated by the managed devices and sends the alarms
to Concentrator Core Server for action. Concentrator Core Server handles alarms and inventory.
The SAL Gateway application provides a UI so that you can configure the interfaces to manage
devices and other settings. Concentrator Remote Server handles remote access configuration.
All communications from SAL Gateway to Concentrator Core Server flow bidirectionally over a
tunnel. The system creates the tunnel through the HTTPS requests initiated from SAL Gateway to
Concentrator Core Server.
The Client Enablement Services server interacts with SAL Gateway using SNMP. SAL Gateway
interacts with the Client Enablement Services server over a secure SSL link, HTTPS.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
22
Client integration architecture
Handset Server
Handset Server routes the TLS traffic sent from the mobile clients to the default listening port on
Handset Server, 7777, and maps this to Handset Services running on Client Enablement Services
on the default port, 8888. Standalone Handset Server is a component that you can optionally deploy
in the DMZ.
Handset Server uses port forwarding to enable the client traffic to pass through the DMZ.
You can use any other DMZ server as an alternative to Handset Server to allow the client TLS traffic
to reach Client Enablement Services. Configurations include but are not limited to:
• Linux iptables
• Reverse Proxy
IHS
IBM HTTP Server (IHS) is a hardened piece of software designed for gaining HTTP access to
WebSphere application servers. When you install the template, the system installs IHS on the Client
Enablement Services server. Client Enablement Services uses IHS for handling internal HTTP traffic
to IHS.
If you install Client Enablement Services, IHS is automatically installed. If you upgrade Client
Enablement Services, IHS is automatically upgraded.
Security Appliance
When the devices used for Avaya one-X® Mobile are remote to the enterprise using the cellular data
network, that is, 3G or LTE, or a public Wi-Fi hotspot, most enterprises will need to provide a
method to allow the clients to connect to the Client Enablement Services server through a firewall or
DMZ.
In addition to remote access when offsite, many enterprises will also have to consider mobile
deployments where devices will also have direct IP access to enterprise services when associated
with the enterprise Wireless LAN (WLAN).
With Client Enablement Services, supporting a combination of remote access via the internet and
local access via an enterprise WLAN can be addressed in a number of ways when using a Security
Appliance in the DMZ. The most straightforward approach is to simply route all internal and external
traffic from the Avaya one-X clients through the security appliance in the DMZ. This ensures a single
point of access for all traffic in all cases.
There are a wide range of security appliances in the market today that can be used to support this
deployment model such as HTTP Reverse Proxies, Unified Threat Management (UTM) Gateways,
or simple firewalls.
Regardless of the chosen security appliance, the main network connectivity requirement for the
clients is that each Avaya one-X client is able to create a TLS connection directly with the Client
Enablement Services server.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
23
Avaya one-X® Client Enablement Services overview
The following techniques can be used to allow traffic to pass through the firewall or DMZ, subject to
the capabilities of your specific security appliance:
• Firewall Pinhole: Open a pinhole for the client traffic to pass directly through the firewall or DMZ
to the Client Enablement Services server.
• Port Forwarding: Inbound traffic can be configured on the clients to be addressed to the
security appliance which will port forward the traffic to the destination Client Enablement
Services server. This configuration adds topology hiding as a feature of the deployment.
Hence, this method does not directly expose the IP address or the port of the Client
Enablement Services server to the untrusted Internet.
Note:
For BlackBerry devices, the BlackBerry Enterprise Server (BES) Mobile Data Service (MDS) is
commonly used to provide IP access to the enterprise network for remote devices in place of a
third-party security appliance. This option is limited to only BlackBerry devices.
Avaya one-X® Communicator
Using Avaya one-X® Communicator, enterprise users can manage communication tasks with a
simple, intuitive access to all of the everyday communications tools.
Enterprises can offer Avaya one-X® Communicator to users in the following ways:
• A standalone client that provides basic and advanced telephony features, Instant Messaging,
and presence support when integrated with Presence Services.
• A UC client that is integrated with Client Enablement Services for 24*7 call logs, with the
conferencing server to provide live audio conference services, and with the messaging server
to provide voice message services. The messaging server uses Avaya message store as the
storage destination. You can integrate the UC client with the Presence Services server and
Microsoft OCS to provide Instant Messaging and presence support across Avaya one-X®
Communicator and MOC.
Use Avaya one-X® Communicator to increase your productivity with tools that:
• Enhance collaboration with assurance of security.
• Improve responsiveness.
• Make high definition video calls.
• Lower costs for IT and user support.
Avaya one-X® Communicator usage modes:
Mode name
Description
H.323 - Standalone
Customers in a H.323 environment deploy this model
to provide users the Softphone capability.
These customers often deploy their first Softphone or
replace their existing IP Softphones. Most customers
Table continues…
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
24
Client integration architecture
Mode name
Description
deploy this model for regular use, but some use the
model only as a business continuity tool.
H.323 - UC Integration
Customers in a H.323 environment who deploy
Avaya applications to gain access to UC capabilities
such as Conferencing, Messaging, Presence
Services, deploy this model to provide users
enhanced capabilities and a single UI.
SIP - Standalone : CM-ES or CM-FS
Customers in a SIP environment deploy this model
to provide users the Softphone capability.
These customers often deploy their first Softphone or
replace their existing IP Softphones. Most customers
deploy this model for regular use, but some use the
model only as a business continuity tool.
SIP - UC Integration Standalone : CM-ES or CM-FS
Customers in a SIP environment who deploy Avaya
applications to gain access to UC capabilities such
as Conferencing, Messaging, Presence Services,
deploy this model to provide users enhanced
capabilities and a single UI.
SIP - Native IM Standalone : CM-ES or CM-FS
Mid-sized companies that want a single source, lowcost offering for their UC and voice centric clients
deploy this model.
SIP - UC Integration + Native IM Standalone : CMES or CM-FS
Customers that want to leverage Avaya applications
and capabilities and want the users of this feature
set to experience a single GUI access to computer
and voice collaboration deploy this preferred model.
Avaya one-X® Mobile
The Avaya one-X® Mobile software offers enterprise voice mail and corporate directory integration
on mobile devices. Use Avaya one-X® Mobile to extend the corporate voice network to employee
mobile phones.
Avaya one-X® Mobile connects to the Client Enablement Services server to provide multiple UC
capabilities, such as:
• Telephony
• Messaging
• Mobility
• Conferencing
• Presence Services
Use Avaya one-X® Mobile to enable your mobile phone to gain access to the telephone system of
your company. Using Avaya one-X® Mobile, you can:
• Use your office telephone number to make and receive calls.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
25
Avaya one-X® Client Enablement Services overview
• Review voice mail messages.
• Search the corporate directory.
• Block selected calls.
Avaya one-X® Mobile Lite connects to the Communication Manager server. Avaya one-X® Mobile
Lite provides the simultaneous ring feature for mobile users. Users can thus remain productive with
a single telephone number and voice mail capabilities.
Mobile users can be provisioned with a SIP station or H.323 station and have full functionality.
Avaya one-X® Mobile client distribution:
The Avaya one-X® Mobile client for Android is available on Google Play, for BlackBerry is available
on BlackBerry App World, and for iPhone is available in iTunes.
Google Play is a digital application distribution platform for Android developed and maintained by
Google. BlackBerry App World is an application distribution service and application for BlackBerry
devices by Research In Motion (RIM). iTunes is a media player and media library application
developed by Apple Inc.
Additionally, Client Enablement Services also uses Product Licensing and Delivery System (PLDS)
to distribute and support the Android and BlackBerry Avaya one-X® Mobile clients. You can
distribute the builds to your enterprise users according to your preference. Distribution methods
might include the use of a Web server and Mobile Device Management (MDM).
The R6.1 and R6.2 versions of the Client Enablement Services server and the Avaya one-X® Mobile
clients are forwards and backwards compatible with each other. That is, the Client Enablement
Services R6.2 server is compatible with the Avaya one-X® Mobile R6.1 clients. Alternatively, the
Client Enablement Services R6.1 server is compatible with the Avaya one-X® Mobile R6.2 clients.
Feature description
The following subsections describe the major features and functionality of Client Enablement
Services. Information includes features for the:
• User of Avaya one-X® Communicator
• User of Avaya one-X® Mobile
• Administrator of Client Enablement Services
Related links
Avaya one-X Client Enablement Services overview on page 10
User features on page 27
Administration features on page 29
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
26
Feature description
User features
Avaya one-X® Communicator
Features are categorized as basic and UC.
Basic features:
• Desktop access to all your communication tools from a single, intuitive UI.
• Telephony features similar to Avaya one-X Desktop Edition and Avaya IP Softphone.
• Usage modes control.
• Multiple levels of security.
• High-definition video calling.
• Viewing and sharing of presence states.
• Scalable instant messaging capability to send messages without requiring any third-party
messaging application.
• Presence to determine the best way to reach a colleague quickly.
• Groups for associating users with particular telephone settings.
• Centralized control and administration.
• Desktop video for Softphones for face-to-face communications to streamline decision-making
and reduce travel expenses.
• Click-to-Dial capability from Microsoft Internet Explorer and Mozilla Firefox.
• Click-to-Dial capability from Microsoft Outlook Contacts.
• Wipe-to-dial, that is, clipboard dialing capability from any application.
• Contact lookup of Microsoft Outlook or IBM Lotus Notes contact from the Avaya one-X®
Communicator UI.
• Contact management tools that help you quickly find contact information.
• Telephone share control that provides telephony functionality from a server to your desktop.
• Enhanced login preferences: Automatic login and Autostart.
• Expanded video options: Full screen option, Always on top feature, and Screen Saver and
Monitor Power Saving feature.
• Customization of the Avaya one-X logo, and the title in the Login window.
UC features:
UC features require integration with Client Enablement Services. These features include:
• The entire Basic feature set.
• Visual voice mail to filter and sort voice messages so you can respond to the most important
messages quickly.
• Visual Audio Bridge Conferencing that is easy to start, join, and manage for improved
collaboration and conference call effectiveness.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
27
Avaya one-X® Client Enablement Services overview
• Communication History logs that help you trace the history of your enterprise calls and voice
messages.
• Contact management tools that help you find contact information quickly and view the
presence information of corporate contacts.
• Presence access requests control.
Some functionalities also require integration with additional products.
Avaya one-X® Mobile
• Use the Speech Access feature to initiate a call to the Avaya one-X® Speech server.
• Use the Status Message feature to add, edit, delete, or select a status message.
• Use the My Phones feature to select telephone numbers that must ring when you receive an
incoming call on your office deskphone extension.
• Use the Call Screening feature to block or allow all incoming calls, or allow only VIP calls on
your phone destination.
• Use the Availability feature to set your presence status.
• Use the History feature to view the list of incoming, outgoing, and missed calls to your office
deskphone extension.
• Use the Contacts feature to search for a contact in the corporate directory. You can add
corporate directory contacts to your local contacts list.
• Use the Call Back feature to route a call from the Avaya one-X® Mobile application to any
telephone using your office deskphone system.
• Use the Messages feature to play or delete voice mail messages.
• Use the VIP feature to choose key contacts in the corporate directory as VIPs. You can use the
VIP feature in association with the Call Screening feature to allow only VIP calls.
• Use the Favorite feature to choose key contacts from the corporate directory of your company
as favorites. For example, you can easily search for the contact you call frequently from the
Favorites tab on the Contacts screen.
• Use the Lost/stolen device feature to enable the Client Enablement Services server to notify
the Avaya one-X® Mobile application to:
- Remove all locally stored data, such as downloaded voice mail.
- Clear the account information.
- Force the user to relogin to gain access to Avaya one-X® Mobile.
To use Avaya one-X® Mobile on any mobile phone, ensure that the administrator enabled your
account. Contact your administrator to enable the Lost/stolen device feature on the Client
Enablement Services server.
Supported languages
Client Enablement Services supports the following languages for users in this release:
• Chinese (Simplified)
• English
• French
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
28
Feature description
• German
• Italian
• Japanese
• Korean
• Lat-Spanish
• Portuguese (Brazilian)
• Russian
Related links
Feature description on page 26
Administration features
The Client Enablement Services administration application includes the administration Web client
and the administration command line client application.
Administration Web client:
• Administer a Client Enablement Services server from any computer.
• Configure the various servers, which are required for different functionalities, on the Client
Enablement Services server.
• Define system and group profiles.
• Create users and assign resources to a user.
• Schedule and administer synchronization, statistics cleanup, and database backup.
• Monitor, suspend, and restart various services of Client Enablement Services.
Administration command line client:
Use the administration command line client as an alternative to the Web-based administration
application for performing some administration tasks. You can use the administration command line
client when the administration Web client is unavailable.
The administration command line client is also useful when you need to perform bulk operations
such as importing users and exporting users.
Related links
Feature description on page 26
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
29
Avaya one-X® Client Enablement Services overview
New in this release
Client Enablement Services 6.2 provides the following features:
• Support for Linux installs in addition to System Platform, so that a significant percentage of
customers use Linux installs.
Note:
You cannot use VMware to deploy Client Enablement Services.
• Support for multiple Microsoft Active Directory domains:
- Multiple Active Directory instances with one domain per instance
- Single Active Directory instance with multiple domains
Important:
During the installation of Client Enablement Services, you can configure multiple domains
for use with Client Enablement Services. However, after you complete the Client
Enablement Services installation, to perform any changes in the multiple-domain
configuration, you must reinstall Client Enablement Services.
Note:
The Presence Services server does not support multiple domains as System Manager
supports only one LDAP server. Hence, if you are using multiple Active Directory domains
in Client Enablement Services, users of only one domain can use services provided by the
Presence Services server.
• For security reasons, the administrator can:
- Prevent enterprise data, specifically voice mail attachments and corporate contacts, from
being downloaded to the mobile device.
- Restrict the use of the Avaya one-X® Mobile application to a single mobile phone.
Every mobile phone has a unique device identifier (ID). When you log in to the Avaya one-X®
Mobile application, the Client Enablement Services server retrieves that ID to authenticate
the user and prevent unauthorized use of the application. If the administrator activates this
feature on the server, the use of the Avaya one-X® Mobile application is restricted to your
mobile phone only. If the administrator does not activate this feature, you can gain access to
the Avaya one-X® Mobile application from any mobile phone.
Note:
Avaya uses your ID, which is your personal data, only for the purpose of authentication,
and not for any other purpose.
- Hide the contact information of selected contacts. For example, companies might not want to
publish the contact information of senior management to each user. When a user searches
for the contact information of such a contact, the client application displays only the name of
that contact.
- Prevent the usage of the Avaya one-X® Mobile application on Android and iPhone mobile
phones if that device is jail broken.
• The administrator can select specific multiple LDAP fields for Corporate Directory queries.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
30
Feature comparison
• The Avaya one-X® Mobile user can selectively forward the bridged call appearances to the
active devices in the ring phones group.
• Client Enablement Services clients use TLS v1.0.
• Avaya one-X® Mobile can be provisioned to the mobile device directly from the mobile markets.
• Simplified Handset Server architecture improves the reliability of Handset Server.
Related links
Avaya one-X Client Enablement Services overview on page 10
Feature comparison
Feature comparison between the Avaya one-X® Mobile UC and Lite modes:
The following table lists the various features that are available in UC mode and in Lite mode. For a
complete list of features available in a mode, see the user guide for that mobile OS.
Features in UC mode
Features in Lite mode
Call modes: Business: Callback, Business: Direct
Dial, and Personal
Call modes: Business: Direct Dial and Personal
Visual voice mail
Call voice mail
My phones: Desk phones, mobile phones, and userdefined numbers
Simultaneous ring
Corporate directory search
Corporate directory search
Client Enablement Services uses Active Directory to
perform search operations in the corporate directory.
BlackBerry mobile phones use BlackBerry Enterprise
Server (BES) to perform search operations in the
corporate directory.
Android mobile phones use ActiveSync to perform
search operations in the corporate directory.
Mark enterprise contacts as Favorites
One touch dial and join Conference Bridge
Mark enterprise contacts as VIPs
Call Forward
Message notification as SMS
Bridge onto active call
Allow VIP calls or Block all calls
Send All Calls
Presence status of self and other enterprise contacts
History in UC mode shows calls of type - Incoming,
outgoing, and missed.
History in Lite mode shows history of only outgoing
calls
However, when a user changes from UC mode to
Lite mode, the application carries over the history of
all calls to Lite mode. After changing to Lite mode,
the application displays the history of only outgoing
calls for calls made after changing to Lite mode. The
Table continues…
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
31
Avaya one-X® Client Enablement Services overview
Features in UC mode
Features in Lite mode
native call log of the mobile phone displays new
incoming and missed calls.
To use the following Lite mode features in UC mode,
the user must change the call settings to Business:
Direct Dial or Business: Callback and configure
the telephony settings using the settings file:
• Conference on Answer
• Transfer on Hang-Up
• Drop Last Added Party
• Exclusion
Differences between controlling SIP and H.323 deskphones:
As an administrator, you observe a difference in functioning when you control the SIP and H.323
deskphones for a Client Enablement Services user.
The main difference between the two types of deskphones when Client Enablement Services is
active and you log in using the This Computer or Other Phone mode is that the:
• H.323 deskphone is unregistered from Communication Manager.
• SIP deskphone remains registered to Session Manager.
Because the SIP and H.323 deskphones can work in parallel, the simultaneous working of
deskphones might be a problem for any software that is trying to control your deskphone by making
third-party requests to Communication Manager, including MOC and Client Enablement Services.
Communication Manager and Client Enablement Services use the following rules to resolve the
problem:
• By default, the user that you configure to use the SIP deskphone in the system controls the SIP
deskphone.
• When a user logs in to Client Enablement Services in the This Computer or Other Phone
mode, the system changes the control to follow the option chosen in Client Enablement
Services.
• When the user logs out of Client Enablement Services, the system changes the control to the
SIP deskphone.
Another difference between the two types of deskphones is that when you use a SIP deskphone in
DeskPhone or Shared Control mode, you must use the deskphone to send DTMF tones. You
cannot send DTMF tones using the Avaya one-X client applications. However, if you use the This
Computer or Other Phone mode, DTMF tones continue to function as before.
Related links
Avaya one-X Client Enablement Services overview on page 10
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
32
Chapter 3: Interoperability
Product compatibility
For the latest and most accurate compatibility information for Avaya one-X® Client Enablement
Services 6.2 SP4, see the Release Notes document or use the Compatibility Matrix tool on the
Avaya Support website at https://support.avaya.com/CompatibilityMatrix/Index.aspx.
Product requirements for features
Client Enablement Services provides multiple features. Depending on the requirement, you can
choose all the features or any combination. Certain features require additional or specific products
to function properly.
For Client Enablement Services to function properly:
• You do not require Session Manager and System Manager to implement Modular Messaging
or Communication Manager Messaging.
• Install Session Manager if you use System Manager.
The following tables list the products that you must install for each feature. To use the feature listed
in the Feature column, you must install the corresponding product indicated by a Yes in the product
column. To check the later versions of a product that Client Enablement Services supports, see the
Release Notes document or use the Compatibility Matrix tool on the Avaya Support website at
https://support.avaya.com/CompatibilityMatrix/Index.aspx.
Avaya one-X® Mobile:
Feature
Communication
Manager
Presence Services
System Manager
Session Manager
Telephony
Access Element.
No
Optional (6.2 and
later)
Optional (6.2 and
later)
No
Optional (6.2 and
later)
Optional (6.2 and
later)
No
Yes (6.2 and later)
Yes (6.2 and later)
Yes (5.2.1)
Evolution Server.
Yes (6.0.1 and later)
Feature Server.
Yes (5.2.1 and later)*
Presence
Yes (5.2.1 and later)
Yes (6.2.3 and later)
Yes (6.2 and later)
Yes (6.2 and later)
Messaging
Yes (5.2.1 and later)
No
Yes (6.2 and later)
Yes (6.2 and later)
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
33
Interoperability
Note:
*Client Enablement Services does not support the CM-FS 6.0 implementation.
Avaya one-X® Communicator - H.323:
For non-Avaya Aura® deployments with Client Enablement Services, you do not require System
Manager and Session Manager. For Avaya Aura® deployments with Client Enablement Services,
you need System Manager and Session Manager as they are mandatory for Communication
Manager.
Presence
Services
System
Manager
Session
Manager
Avaya Aura®
Conferencing
Telephony
Yes (5.2.1 and
(Non - Aura
later)
implementation
)
No
Optional (6.2
and later)
Optional (6.2
and later)
No
Telephony
No
Yes (6.2 and
later)
Yes (6.2 and
later)
No
No
Yes (6.2 and
later)
Yes (6.2 and
later)
No
No
Yes (6.2 and
later)
Yes (6.2 and
later)
No
Feature
Communication
Manager
Access Element.
Yes (5.2.1)
Evolution Server.
Yes (6.0.1 and
later)
Feature Server.
Yes (5.2.1 and
later)*
Presence
Yes (5.2.1 and
later)
Yes (6.2.3
and later)
Yes (6.2 and
later)
Yes (6.2 and
later)
No
Conferencing
Yes (5.2.1 and
later)
No
No
No
Yes (5.2 and
later)
Messaging
Yes (5.2.1 and
later)
No
Yes (6.2 and
later)
Yes (6.2 and
later)
No
Note:
*Client Enablement Services does not support the CM-FS 6.0 implementation.
Avaya one-X® Communicator - SIP:
Feature
Communication
Manager
Presence
Services
System
Manager
Session
Manager
Avaya Aura®
Conferencing
Telephony
Access Element.
No
Yes (6.2 and
later)
Yes (6.2 and
later)
No
No
Yes (6.2 and
later)
Yes (6.2 and
later)
No
Yes (5.2.1)
Evolution Server.
Yes (6.0.1 and
later)
Table continues…
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
34
Third-party product connectivity
Feature
Communication
Manager
Presence
Services
System
Manager
Session
Manager
Avaya Aura®
Conferencing
Feature Server.
No
Yes (6.2 and
later)
Yes (6.2 and
later)
No
Yes (5.2.1 and
later)*
Presence
Yes (5.2.1 and
later)
Yes (6.2.3
and later)
Yes (6.2 and
later)
Yes (6.2 and
later)
No
Conferencing
Yes (5.2.1 and
later)
No
Yes (6.2 and
later)
Yes (6.2 and
later)
Yes (5.2 and
later)
Messaging
Yes (5.2.1 and
later)
No
Yes (6.2 and
later)
Yes (6.2 and
later)
No
Note:
*Client Enablement Services does not support the CM-FS 6.0 implementation.
Third-party product connectivity
For the latest and most accurate compatibility information for Avaya one-X® Client Enablement
Services 6.2 SP4, see the Release Notes document or use the Compatibility Matrix tool on the
Avaya Support website at https://support.avaya.com/CompatibilityMatrix/Index.aspx.
Operating system compatibility
For the latest and most accurate compatibility information for Avaya one-X® Client Enablement
Services 6.2 SP4, see the Release Notes document or use the Compatibility Matrix tool on the
Avaya Support website at https://support.avaya.com/CompatibilityMatrix/Index.aspx.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
35
Chapter 4: Performance specifications
Capacity and scalability specifications
Avaya one-X® Client Enablement Services supports 4,000 administered users and 2,000 active
users. If the administrator provisions a user, the user can use any of the Avaya one-X®
Communicator and Avaya one-X® Mobile UC clients. In Client Enablement Services, the number of
users cannot exceed the maximum limit. For example, Client Enablement Services blocks the login
attempt by the 2,001 user.
Client Enablement Services supports up to 20,000 groups and 100,000 users in the corporate
database. The 100,000 users includes the contacts in additional LDAP contact domains.
Note:
The Device, Media, and Call Control (DMCC) connections and AES connections might limit the
Client Enablement Services server capacity.
A single Client Enablement Services server can integrate with the following maximum number of
Avaya servers:
Server
Maximum supported
®
4
®
Avaya Aura Communication Manager Messaging or
Avaya Modular Messaging or Avaya Aura®
Messaging
4
Avaya Aura® Conferencing or Avaya Aura® Meeting
Exchange
3
Avaya Aura® Presence Services
1
Avaya Aura Communication Manager
®
4
®
1
Avaya Aura Session Manager
Avaya Aura System Manager
Note:
To increase the capacity, you can have multiple Client Enablement Services servers. However,
each Client Enablement Services server must have a specific environment and not
communicate with other Client Enablement Services servers.
In an organization, different levels of users have different system usage. The following table
describers a light, average, and heavy user of Client Enablement Services:
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
36
Dial plan specification
User
Light
Average
Heavy
Calls per day
5
30
100
Calls per hour
1
4
10
Conferences per day
1
3
10
Messaging
2
10
30
Personal Contacts
5
100
1000
Favorite Contacts
5
50
500
History
20
50
100
Percentage of users
10
80
10
Dial plan specification
Most enterprise directories, including Active Directory, store telephone numbers in the standard E.
164 format. For example, the E.164 format is +19788081234. The E.164 format provides a unique
description for each telephone number. Avaya one-X® Client Enablement Services uses a dial plan
to:
• Convert telephone numbers from the E.164 standard format to a sequence of numbers that the
telephony server can dial or use for mobile number or ring also number transformation.
• Convert a sequence of numbers received from the telephony server to the standard E.164
format.
Note:
Although most enterprise directories store telephone numbers in the E.164 format, the E.164
format is not mandatory for dial plan conversions using Client Enablement Services.
Client Enablement Services includes the following dial plan transformations:
• Simple Dial Plan
• Pattern Matching
• Regular Expression
Simple Dial Plan transformation
All dial plans that you configure in Client Enablement Services must use the Simple Dial Plan
transformation. The Simple Dial Plan transformation uses the same number transformation rule that
users use. Users convert a telephone number before dialing the number in the telephony server. For
example, in the United States, many users dial 9 before a telephone number to make the
connection. To call +1(978) 555-1111, the users dial 919785551111.
Pattern Matching transformation
The Pattern Matching transformation is very similar to the algorithm used by Avaya Aura®
Communication Manager. The system evaluates the Pattern Matching rules in the order that you
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
37
Performance specifications
specify in the UI. The system uses the first rule that matches the input as the transformation rule.
The Pattern Matching transformation uses a pattern based on the following values:
• String at the beginning of the number
• Minimum length of the string
• Maximum length of the string
After the dial plan matches the number, the Pattern Matching transformation deletes the specified
number of characters and inserts the configured set of characters.
Regular Expression transformation
The Regular Expression transformation is the most flexible method of transformation and the most
difficult to configure. The Regular Expression transformation uses the syntax defined by Java
Regular Expressions. The Regular Expression transformation uses the list of regular expressions
and replacement patterns that you previously defined and applies these rules to the telephone
number.
For more information, see Administering Avaya one-X® Client Enablement Services.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
38
Chapter 5: Environmental requirements
Altitude and air pressure requirements
The tables in this section include the altitude and air pressure requirements for the HP DL360 G7
and Dell R610 servers that Avaya one-X® Client Enablement Services supports. For an updated list
of requirements, see the section on environmental specifications in Installing the HP DL360 G7
Server and Installing the Dell™ PowerEdge™ R610 Server.
HP DL360 G7 Server
Specification
Value
Temperature range
Note:
All temperature ratings shown are for sea level. An altitude derating of
1 degree Celsius (°C) per 300 meter (m) to 3048 m is applicable. No
direct sunlight must be present.
Operating
10 °C to 35 °C
Shipping
-40 °C to 70 °C
Maximum wet bulb
temperature
28 °C
Relative humidity:
Noncondensing
Note:
The maximum humidity of 95% for storage is based on the maximum
temperature of 45 °C. The maximum altitude for storage corresponds
to a pressure minimum of 70 kilopascal (kPa).
Operating
10% to 90%
Non-operating
5% to 95%
Dell R610 Server
Specification
Value
Temperature range
Operating
10 °C to 35 °C with a maximum temperature gradation of 10 °C per hour
Shipping
-40 °C to 65 °C with a maximum temperature gradation of 20 °C per hour
Relative humidity: Noncondensing
Operating
20% to 80% with a maximum humidity gradation of 10% per hour
Non-operating
5% to 95% with a maximum humidity gradation of 10% per hour
Table continues…
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
39
Environmental requirements
Specification
Value
Altitude
Operating
-16 m to 3,048 m
Non-operating
-16 m to 10,600 m
Hardware dimensions and clearance requirements
This section includes the minimum hardware requirements and partition specifications for the Client
Enablement Services server and Standalone Handset Server. If you expect Client Enablement
Services to handle a high volume of traffic, you must provide hardware with more memory and a
faster processor. Contact your Avaya representative or Avaya BusinessPartner representative for
assistance with sizing a Client Enablement Services system.
Client Enablement Services hardware specifications
If you are performing a Linux installation, the Client Enablement Services server must meet the
following minimum hardware specifications:
CPU
Dual quad-core processors of 2.4 Gigahertz (GHz) at a minimum.
Memory
24 Gigabytes (GB) of RAM (minimum 16 GB).
Hard disk drive
500 GB (minimum 300 GB).
Network card
100 Megabits per second (Mbps) or 1 Gigabits per second (Gbps).
Optical disk drive
The DVD and CD combination drive is optional.
Client Enablement Services supports System Platform 6.3.1 on HP DL360p G8 and HP DL360 G7.
If you installed Client Enablement Services with earlier Avaya Common Server, such as Dell PE
R610, then the setup must remain on System Platform 6.2.2.
If you installed Client Enablement Services 6.1.3 on the S8800 server, to use Client Enablement
Services 6.2 SP4, you must migrate the configuration to a RHEL system. For more information, see
Chapter 5: Installing Avaya one-X® Client Enablement Services on Linux.
Hardware requirements
HP DL360 G7
HP DL360p G8
Dell R610
CPU
Dual quad-core
processors of 2.4 Ghz.
Dual six-core E5-2630 /
2.3 GHz (Sandybridge).
Dual quad-core
processors of 2.4 Ghz.
Memory
24 GB.
8 * 4 GB DDR3 RDIMMs. 24 GB.
Hard Drive
3 * 300 GB RAID 5 or 4 *
146 GB RAID 5.
3 * 300 GB SAS 2.5" 10K 4 * 146 GB RAID 5.
RPM 6G DP Hard Drive.
Network Card
100 Mbps or 1Gbps.
4 integrated ENET
Gigabit NIC ports with
TCP offload engine
100 Mbps or 1Gbps.
Table continues…
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
40
Hardware dimensions and clearance requirements
Hardware requirements
HP DL360 G7
HP DL360p G8
(included on
motherboard)
Dell R610
Optical Drive
The DVD and CD
combination drive is
optional.
The DVD and CD
combination drive is
optional.
The DVD and CD
combination drive is
optional.
Client Enablement Services partition specifications
The system installs Client Enablement Services in the /opt and /home partitions with the individual
components in the following locations:
• IBM WebSphere Application Server in the /opt/IBM/WebSphere directory
• Feature Pack for Communications Enabled Applications in the /opt/IBM/CEA directory
• IBM DB2 in the /opt/IBM/db2 and /home/dbinst/sqllib directories for software and in
the /home/dbinst/ACPDB directory for the database
• IBM HTTP Server in the /opt/IBM/HTTPServer directory
• Oracle JDK in the /opt/sun directory
• Apache Tomcat in the /opt/avaya/3rdparty directory
• Client Enablement Services in the /opt/avaya and /opt/vsp directories
A new installation of Client Enablement Services takes up to 20 GB of hard disk space. However,
the total size on both the /opt and /home partitions must be more than 100 GB to account for the
database growth, incremental DB2 backups, and logs.
Note:
If you configure the /opt and /home partitions to be different physical partitions, then /opt
must be more than 70 GB and /home must be more than 30 GB. Database backups take the
maximum disk space and by default are located in the /opt/avaya/1xp/dbbackup directory.
Hence, the /opt partition requires the majority of the allocated disk space.
HP DL360 G7 Server physical specifications
The following table includes physical specifications for HP DL360 G7 Server. For an updated list,
see Installing the HP DL360 G7 Server.
Type
Description
Height: 4.32 cm, that is, 1.70 in.
Dimensions
Width: 42.62 cm, that is, 16.78 in.
Depth: 69.53 cm, that is, 27.38 in.
Maximum Weight: Two
processors, two power
supplies, and eight hard disk
drives
15.97 kg, that is, 35.20 lb
Table continues…
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
41
Environmental requirements
Type
Description
Minimum Weight: One
processor, one power supply,
and no hard disk drives
14.51 kg, that is, 32.00 lb
Weight: No disk drives
present
14.06 kg, that is, 31.00 lb
HP ProLiant DL360p G8 Server physical specifications
The following table includes physical specifications for HP ProLiant DL360p G8 Server. For an
updated list, see Installing the HP ProLiant DL360p G8 Server.
Type
Description
Dimensions
Height: 4.32 cm, that is, 1.70 in.
Width: 43.47 cm, that is, 11.11 in.
Depth: 69.85 cm, that is, 27.50 in.
Maximum Weight: Two processors, two power
supplies, and eight hard disk drives
19.2 kg, that is, 42.33 lb
Dell R610 Server physical specifications
The following table includes physical specifications for Dell R610 Server. For an updated list, see
Installing the Dell™ PowerEdge™ R610 Server.
Type
Description
Height: 4.26 centimeter (cm), that is, 1.68 inch (in.)
Width:
• 48.24 cm, that is, 18.99 in. with rack latches
Dimensions
• 42.4 cm, that is, 16.99 in. without rack latches
Depth:
• 77.2 cm, that is, 30.39 in. with power supplies and bezel
• 73.73 cm, that is, 29.02 in. without power supplies and bezel
Weight: Maximum
configuration
17.69 kilogram (kg), that is, 39 pound (lb)
Weight: Empty
13.25 kg, that is, 29.2 lb
Standalone Handset Server hardware specifications
The server must meet the following prerequisites for installing Handset Server on Standalone
Server. The Handset Server software that you use for Client Enablement Services must be the
Enterprise Server edition.
Note:
The customer must provide Standalone Handset Server and the Handset Server software.
Operating System
November 2015
RHEL 6.5 (64 bit) and later versions
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
42
Hardware dimensions and clearance requirements
CPU
Dual quad-core processors of 2.4 GHz at a minimum
Memory
4 GB of RAM
Hard drive
4 * 146 GB RAID 1
Network card
1 (maximum) of 100 Mbps or 1 Gbps
Optical disk drive
The DVD and CD combination drive is optional
Handset Server partition specifications
The system installs Handset Server in the /opt and /etc partitions.
The xinetd daemon process is used to perform the port forwarding from the Client Enablement
Services server that is located in the corporate network to the mobile clients in the outside world.
The logs for the xinetd daemon process are by default saved in the /var/log/messages file.
Avaya recommends that you accept the default partition sizes. The following are the minimum
recommended sizes if an administrator wishes to manually configure the partitions. For each
partition, select the larger number from the Size or Percentage of total capacity columns so that all
the partitions add up to the total disk capacity. Otherwise, unpartitioned space will be wasted.
Partition
Size
Percentage of total capacity
/
10 GB
25%
/opt
6 GB
15%
/home
4 GB
10%
/tmp
6 GB
15%
/var
8 GB
20%
/usr
6 GB
15 %
Linux installation:
• RHEL 6.5 64-bit operating system and later versions
• xinetd
Minimal installation of Linux:
Handset server can work with the minimal RHEL installation if you add the packages described in
this section. You must select the xinetd package during the RHEL installation or install using the
RHEL DVD or using the yum install xinetd command.
For an automated kickstart configuration, the following %packages declaration is sufficient:
• %packages
• xinetd
The base and core groups are included by default. For more information on how to perform a
kickstart installation, see RHEL documentation.
If you do not wish to perform a kickstart installation, then you must ensure that the packages in the
%packages declaration are not prefixed with ‘-‘.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
43
Environmental requirements
The minimal installation of Linux does not include X-Windows. Therefore, you must install Handset
Server using the command line rather than the GUI if you install RHEL with minimal required
packages mentioned above.
Physical system protection requirements
Use the following safety guidelines to ensure your personal safety and to protect your system and
working environment from potential damage.
Observe the following precautions for rack stability and safety. For information on specific caution
statements and procedures, see the rack installation documentation accompanying the rack.
Component refers to a system, various peripheral devices, or the supporting hardware.
Danger:
• Before installing systems in a rack, install front and side stabilizers on standalone racks or
the front stabilizer on racks that are joined to other racks. Failure to install stabilizers before
installing systems in a rack could cause the rack to tip over and might result in serious
injury.
• After installing components in a rack, never pull more than one component out of the rack
on the slide assemblies at one time. The weight of more than one extended component
could cause the rack to tip over and might result in serious injury.
• Use caution when pressing the component rail release latches and sliding a component in
to or out of a rack because the slide rails can hurt your fingers.
Note:
• Your system is certified for safety as a freestanding unit and as a component for use in a
rack cabinet using the customer rack kit. Ensure that the final combination of system and
rack complies with all applicable safety standards and local electric code requirements.
• Trained service technicians must install the system rack kits.
Important:
• Two or more people are required to install components that are 2 rack unit (RU) or larger in
a rack cabinet.
• Always load the rack from the bottom, and load the heaviest item in the rack first.
• Ensure that the rack is at an even level and stable before extending a component from the
rack.
• Do not overload the AC supply branch circuit that provides power to the rack. The total
rack load must not exceed 80% of the branch circuit rating.
• Ensure that the system provides proper airflow to components in the rack:
- Do not block any air vents. Usually 15 cm (6 in.) of space provides proper airflow.
- Install the server in a rack cabinet with perforated doors.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
44
Regulatory standards
- Do not leave open spaces around an installed server in your rack cabinet. To prevent
damage to server components, always install a blank filler panel to cover the open
space and to ensure proper air circulation.
• Do not step on or stand on any component when servicing other components in a rack.
• Do not place any object on top of rack-mounted components.
Regulatory standards
Client Enablement Services provides an infrastructure using which the Avaya one-X® Mobile and the
Avaya one-X® Communicator clients comply with all E911 regulations. Enhanced 911, E-911, or
E911 is a system used in North America that links emergency callers with the appropriate public
resources.
In all the markets in which Avaya sells or supports Client Enablement Services, Client Enablement
Services complies with the following:
• The applicable privacy and data security regulations and laws
• The applicable wiretap regulations and laws
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
45
Chapter 6: Security
Security specification
Connections through VPN or internal LAN
Avaya one-X® Client Enablement Services supports connection through VPN or internal LAN.
User authentication through the enterprise directory
Client Enablement Services integrates with the existing enterprise directory. Client Enablement
Services uses the Microsoft Active Directory, Microsoft ADAM, IBM Domino Server, Novell
eDirectory, or SUN Directory Server Enterprise Edition user records for authentication and
authorization.
However, to log in to the standalone mode, Avaya one-X® Communicator uses the extension and
password of Avaya Aura® Communication Manager for user authentication.
Access to Client Enablement Services through secure server connections
Client Enablement Services supports TLS and SSL. Install a secure server certificate obtained from
a certifying authority such as VeriSign, Thawte, or GTE CyberTrust. Users can then connect to
Client Enablement Services without any security concerns.
For H.323 connection
If administered on the call server, the system supports encryption for call signaling messages.
Connections to integrated components through secure ports
You can configure secure ports for integrated components including:
• Enterprise directory application
• Avaya WebLM
• The supported messaging servers
Encryption implemented through the Administration Command Line Client
For information on how to implement the following encryption, see the online Help provided with the
administration application:
• Encryption for sensitive information in the Client Enablement Services database
• Encryption for bulk user import
• Encryption for bulk user export
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
46
Security specification
Security requirements for administrators
To maintain a secure environment for Client Enablement Services:
• Use role assignments and assign security groups for operations.
• For accountability, each user must have a unique login ID. Instruct users not to share their
login ID and password.
• Periodically review and update the list of administered users, roles, and permissions.
• Review administration logs regularly to ensure that the system is operating properly.
• Review audit logs regularly to ensure that the system is operating properly.
• Review security logs and alarms regularly to monitor possible security events.
Additional security information
Additional security information for Client Enablement Services and Avaya components that integrate
with Client Enablement Services is available on the Avaya Support website at http://
support.avaya.com/security. For example, you can find information about the following:
• Avaya Product Security Vulnerability Response Policy
• Avaya Security Vulnerability Classification
• Avaya Product Security Support Flow
• Security advisories for Avaya products
• Software patches for security issues
• Reporting a security vulnerability
• Automatic email notifications of security advisories
You can also find additional information about security practices on the National Security Agency
website at http://www.nsa.gov/snac/.
Password cache behavior
After the administrator changes the password on the enterprise directory, the password is
immediately available for use by the one-X clients. However, as Client Enablement Services caches
the enterprise directory data for up to 60 minutes, the old password might continue to be accepted
for up to 60 minutes after the password is changed on the enterprise directory.
However, if the user is logged in to the client application and the administrator changes the
password, the 60 minutes of time-out settings begins from the time the user logs out of the client
application.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
47
Security
Port utilization
The Avaya one-X® Client Enablement Services 6.2 Port Matrix document lists the ports and
protocols that Client Enablement Services uses. Avaya Direct, BusinessPartners, and customers
can find the port matrix document at http://support.avaya.com/security.
1. On the webpage, click the Avaya Product Port Matrix Documents link.
2. On the Avaya Product Port Matrix Documents webpage, click the Avaya one-X® Client
Enablement Services 6.2 Port Matrix link.
You can gain access to the port matrix document only after you log in to the Avaya Support site
using valid support site credentials.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
48
Chapter 7: Licensing requirements
Avaya one-X® Client Enablement Services is available with the UC All Inclusive (UCAI) offer. The
UCAI offer provides the applications and features of the Avaya Aura® applications in a package
price that enables sales and improves competitiveness.
The UCAI offer simplifies communications by making it easy to acquire and deploy market-leading
UC capabilities as part of moving to the latest version of Avaya Aura®. Using the UCAI offer, the
enterprise users can work from anywhere, connect their applications, get real time information, and
most importantly gives them control over how they communicate.
The applications currently included in the UCAI offer are:
• Avaya one-X® Communicator
• Avaya one-X® Client Enablement Services
• Extension to Cellular (EC500)
• Avaya Aura® Application Enablement Services (AES) for Unified Desktop
The UCAI offer provides customers a cost effective bundle of high value UC products and services:
• User-based pricing, pay as you go for what you need
• Multi-vendor interoperability
• Desktop and Mobile clients provide you access from anywhere
• Integration with Microsoft Office Communicator and IBM Lotus Sametime
• The UCAI applications provide enterprises the functionality they need when they need it
With the UCAI offer, Avaya meets the needs of key audiences:
• End User - Adaptable to enable people wherever they are
• Line of Business - Industry specialized for the environment of the business user
• IT Decision Maker - Creates a reliable virtual enterprise leveraging existing investments
Use PLDS to generate the license for Client Enablement Services. After you obtain the license file,
use Avaya WebLM to install the license file. For more information, see Implementing Avaya one-X®
Client Enablement Services.
You must obtain the end-user license from Avaya to provision users for Client Enablement Services.
Users who are not provisioned cannot gain access to Client Enablement Services. The system uses
an end-user license when you configure and activate a user.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
49
Glossary
Application
Enablement Services
A set of enhanced telephony APIs, protocols, and Web services that are
available to developers. These capabilities support access to the powerful
call processing, media, and administrative features available in
Communication Manager.
Communication
Manager
A key component of Avaya Aura®. It delivers rich voice and video
capabilities and provides a resilient, distributed network for media gateways
and analog, digital, and IP-based communication devices. It includes
advanced mobility features, built-in conference calling, contact center
applications and E911 capabilities.
Lightweight
Directory Access
Protocol
A data store used to store user information such as name, location,
password, group permissions, and pseudo permissions.
Secure Access Link
A centralized method that monitors Avaya equipment and software
remotely. Secure Access Link (SAL) collects inventory information on
equipment and software, and automatically creates service tickets when
there is a problem.
Session Manager
A SIP routing and integration tool that is the core component within the
Avaya Aura® solution.
System Manager
A common management framework for Avaya Aura® that provides
centralized management functions for provisioning and administration to
reduce management complexity.
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
50
Index
A
intended audience ................................................................. 7
administration features ........................................................ 29
architecture .......................................................................... 11
Client Enablement Services ......................................... 11
authentication server ........................................................... 21
Avaya Aura Messaging ........................................................20
Avaya products .................................................................... 33
L
LDAP ................................................................................... 21
licenses ................................................................................49
Lightweight Directory Access Protocol ................................ 21
M
B
business purpose .................................................................10
Meeting Exchange ............................................................... 20
Modular Messaging ............................................................. 20
C
N
Client Enablement Services .................................................10
Communication Manager .....................................................14
Communication Manager Messaging .................................. 20
compatibility
Avaya products .............................................................33
operating system .......................................................... 35
third-party products .......................................................35
Conferencing ....................................................................... 20
connectivity
third-party products .......................................................35
course .................................................................................... 8
new features ........................................................................ 30
new in this release ............................................................... 30
D
documentation ....................................................................... 7
F
feature requirements ............................................................33
features ................................................................................26
administrator .................................................................29
comparison ................................................................... 31
new ............................................................................... 30
one-X Communicator ....................................................27
one-X Mobile ................................................................ 27
user ...............................................................................27
functionality ..........................................................................26
H
Handset Server ....................................................................23
I
IBM HTTP Server ................................................................ 23
IHS .......................................................................................23
November 2015
O
one-X Communicator ...........................................................24
one-X Mobile ........................................................................25
operating system compatibility .............................................35
overview ...............................................................................10
P
password cache ...................................................................47
port forwarder ...................................................................... 23
port matrix ............................................................................48
ports .....................................................................................48
port usage ............................................................................48
port utilization .......................................................................48
Presence Services ...............................................................17
product compatibility ............................................................ 33
product requirements ...........................................................33
R
regulatory standards ............................................................ 45
related documents ................................................................. 7
requirements
air pressure ...................................................................39
altitude .......................................................................... 39
clearance ...................................................................... 40
dimensions ................................................................... 40
hardware .......................................................................40
licensing ........................................................................49
physical system protection ........................................... 44
safety ............................................................................ 44
Reverse Proxy ..................................................................... 23
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
51
Index
S
SAL Gateway .......................................................................22
SAL GW ...............................................................................22
security ................................................................................ 46
security appliance ................................................................ 23
Session Manager .................................................................15
specifications
capacity ........................................................................ 36
dial plan ........................................................................ 37
scalability ...................................................................... 36
security ......................................................................... 46
standards
regulatory ......................................................................45
support
contact ............................................................................ 9
System Manager ..................................................................16
T
third-party product connectivity ............................................35
third-party products ..............................................................35
training ................................................................................... 8
U
user features ........................................................................27
V
videos .................................................................................... 8
W
warranty ................................................................................. 9
Web License Management .................................................. 22
WebLM ................................................................................ 22
November 2015
Avaya one-X® Client Enablement Services Overview and Specification 6.2
Comments on this document? [email protected]
52