Sie sind auf Seite 1von 47

Administering Avaya Collaboration

Services

Release 6.6.2
NN10850-031
Issue 5
September 2016
© 2012-2016, Avaya, Inc. IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
All Rights Reserved. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
Notice SERVICE.
While reasonable efforts have been made to ensure that the Licenses
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
the right to make changes and corrections to the information in this WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,
document without the obligation to notify any person or organization UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
of such changes. Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
Documentation disclaimer USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
“Documentation” means information published in varying mediums FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
which may include product information, operating instructions and CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
performance specifications that are generally made available to users AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
of products. Documentation does not include marketing materials. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
Avaya shall not be responsible for any modifications, additions, or AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
deletions to the original published version of Documentation unless WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN
such modifications, additions, or deletions were performed by or on AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
the express behalf of Avaya. End User agrees to indemnify and hold RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
harmless Avaya, Avaya's agents, servants and employees against all AND ANYONE ELSE USING OR SELLING THE SOFTWARE
claims, lawsuits, demands and judgments arising out of, or in WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
connection with, subsequent modifications, additions or deletions to USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
this documentation, to the extent made by End User. YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
Link disclaimer SOFTWARE (HEREINAFTER REFERRED TO
Avaya is not responsible for the contents or reliability of any linked INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
websites referenced within this site or Documentation provided by THESE TERMS AND CONDITIONS AND CREATE A BINDING
Avaya. Avaya is not responsible for the accuracy of any information, CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
statement or content provided on these sites and does not APPLICABLE AVAYA AFFILIATE (“AVAYA”).
necessarily endorse the products, services, or information described Avaya grants You a license within the scope of the license types
or offered within them. Avaya does not guarantee that these links will described below, with the exception of Heritage Nortel Software, for
work all the time and has no control over the availability of the linked which the scope of the license is detailed below. Where the order
pages. documentation does not expressly identify a license type, the
Warranty applicable license will be a Designated System License. The
applicable number of licenses and units of capacity for which the
Avaya provides a limited warranty on Avaya hardware and software. license is granted will be one (1), unless a different number of
Refer to your sales agreement to establish the terms of the limited licenses or units of capacity is specified in the documentation or other
warranty. In addition, Avaya’s standard warranty language, as well as materials available to You. “Software” means computer programs in
information regarding support for this product while under warranty is object code, provided by Avaya or an Avaya Channel Partner,
available to Avaya customers and other parties through the Avaya whether as stand-alone products, pre-installed on hardware products,
Support website: https://support.avaya.com/helpcenter/ and any upgrades, updates, patches, bug fixes, or modified versions
getGenericDetails?detailId=C20091120112456651010 under the link thereto. “Designated Processor” means a single stand-alone
“Warranty & Product Lifecycle” or such successor site as designated computing device. “Server” means a Designated Processor that
by Avaya. Please note that if You acquired the product(s) from an hosts a software application to be accessed by multiple users.
authorized Avaya Channel Partner outside of the United States and “Instance” means a single copy of the Software executing at a
Canada, the warranty is provided to You by said Avaya Channel particular time: (i) on one physical machine; or (ii) on one deployed
Partner and not by Avaya. software virtual machine (“VM”) or similar deployment.
“Hosted Service” means an Avaya hosted service subscription that License type(s)
You acquire from either Avaya or an authorized Avaya Channel
Partner (as applicable) and which is described further in Hosted SAS Designated System(s) License (DS). End User may install and use
or other service description documentation regarding the applicable each copy or an Instance of the Software only on a number of
hosted service. If You purchase a Hosted Service subscription, the Designated Processors up to the number indicated in the order.
foregoing limited warranty may not apply but You may be entitled to Avaya may require the Designated Processor(s) to be identified in
support services in connection with the Hosted Service as described the order by type, serial number, feature key, Instance, location or
further in your service description documents for the applicable other specific designation, or to be provided by End User to Avaya
Hosted Service. Contact Avaya or Avaya Channel Partner (as through electronic means established by Avaya specifically for this
applicable) for more information. purpose.

Hosted Service Concurrent User License (CU). End User may install and use the
Software on multiple Designated Processors or one or more Servers,
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA so long as only the licensed number of Units are accessing and using
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA the Software at any given time. A “Unit” means the unit on which
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE Avaya, at its sole discretion, bases the pricing of its licenses and can
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA be, without limitation, an agent, port or user, an e-mail or voice mail
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO account in the name of a person or corporate function (e.g.,
UNDER THE LINK “Avaya Terms of Use for Hosted Services” OR webmaster or helpdesk), or a directory entry in the administrative
SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE database utilized by the Software that permits one user to interface
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE with the Software. Units may be linked to a specific, identified Server
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED or an Instance of the Software.
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE Database License (DL). End User may install and use each copy or
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY an Instance of the Software on one Server or on multiple Servers
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF provided that each of the Servers on which the Software is installed
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A communicates with no more than one Instance of the same
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT database.
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE CPU License (CP). End User may install and use each copy or
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, 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 software. The Third Party Terms shall take precedence over these
Server(s) does not exceed the performance capacity specified for the Software License Terms, solely with respect to the applicable Third
Software. End User may not re-install or operate the Software on Party Components to the extent that these Software License Terms
Server(s) with a larger performance capacity without Avaya’s prior impose greater restrictions on You than the applicable Third Party
consent and payment of an upgrade fee. Terms.
Named User License (NU). You may: (i) install and use each copy or The following applies only if the H.264 (AVC) codec is distributed with
Instance of the Software on a single Designated Processor or Server the product. THIS PRODUCT IS LICENSED UNDER THE AVC
per authorized Named User (defined below); or (ii) install and use PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
each copy or Instance of the Software on a Server so long as only CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE
authorized Named Users access and use the Software. “Named REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
User”, means a user or device that has been expressly authorized by THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
Avaya to access and use the Software. At Avaya’s sole discretion, a VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
“Named User” may be, without limitation, designated by name, PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
corporate function (e.g., webmaster or helpdesk), an e-mail or voice PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
mail account in the name of a person or corporate function, or a GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
directory entry in the administrative database utilized by the Software ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG
that permits one user to interface with the Software. LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.
Shrinkwrap License (SR). You may install and use the Software in Service Provider
accordance with the terms and conditions of the applicable license
agreements, such as “shrinkwrap” or “clickthrough” license THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S
accompanying or applicable to the Software (“Shrinkwrap License”). HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
Heritage Nortel Software SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY
“Heritage Nortel Software” means the software that was acquired by FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL
Avaya as part of its purchase of the Nortel Enterprise Solutions PARTNER’S HOSTING OF AVAYA PRODUCTS MUST BE
Business in December 2009. The Heritage Nortel Software is the AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED
software contained within the list of Heritage Nortel Products located PRODUCTS USE OR EMBED CERTAIN THIRD PARTY
at https://support.avaya.com/LicenseInfo under the link “Heritage SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT
Nortel Products” or such successor site as designated by Avaya. For SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS
Heritage Nortel Software, Avaya grants Customer a license to use REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE
Heritage Nortel Software provided hereunder solely to the extent of LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S
the authorized activation or authorized usage level, solely for the EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY
purpose specified in the Documentation, and solely as embedded in, SUPPLIER.
for execution on, or for communication with Avaya equipment.
Charges for Heritage Nortel Software may be based on extent of WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
activation or use authorized as specified in an order or invoice. PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE
Copyright AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES
Except where expressly stated otherwise, no use should be made of THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY
materials on this site, the Documentation, Software, Hosted Service, AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729
or hardware provided by Avaya. All content on this site, the CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE
documentation, Hosted Service, and the product provided by Avaya WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC IS
including the selection, arrangement and design of the content is LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
owned either by Avaya or its licensors and is protected by copyright THE PERSONAL USE OF A CONSUMER OR OTHER USES IN
and other intellectual property laws including the sui generis rights WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)
relating to the protection of databases. You may not modify, copy, ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD
reproduce, republish, upload, post, transmit or distribute in any way (“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS
any content, in whole or in part, including any code and software ENCODED BY A CONSUMER ENGAGED IN A PERSONAL
unless expressly authorized by Avaya. Unauthorized reproduction, ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER
transmission, dissemination, storage, and or use without the express LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
written consent of Avaya can be a criminal, as well as a civil offense OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
under the applicable law. INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS
MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
Virtualization WWW.MPEGLA.COM.
The following applies if the product is deployed on a virtual machine. Compliance with Laws
Each product has its own ordering code and license types. Note that
each Instance of a product must be separately licensed and ordered. You acknowledge and agree that it is Your responsibility for
For example, if the end user customer or Avaya Channel Partner complying with any applicable laws and regulations, including, but not
would like to install two Instances of the same type of products, then limited to laws and regulations related to call recording, data privacy,
two products of that type must be ordered. intellectual property, trade secret, fraud, and music performance
rights, in the country or territory where the Avaya product is used.
Third Party Components
Preventing Toll Fraud
“Third Party Components” mean certain software programs or
portions thereof included in the Software or Hosted Service may “Toll Fraud” is the unauthorized use of your telecommunications
contain software (including open source software) distributed under system by an unauthorized party (for example, a person who is not a
third party agreements (“Third Party Components”), which contain corporate employee, agent, subcontractor, or is not working on your
terms regarding the rights to use certain portions of the Software company's behalf). Be aware that there can be a risk of Toll Fraud
(“Third Party Terms”). As required, information regarding distributed associated with your system and that, if Toll Fraud occurs, it can
Linux OS source code (for those products that have distributed Linux result in substantial additional charges for your telecommunications
OS source code) and identifying the copyright holders of the Third services.
Party Components and the Third Party Terms that apply is available Avaya Toll Fraud intervention
in the products, Documentation or on Avaya’s website at: https://
support.avaya.com/Copyright or such successor site as designated If You suspect that You are being victimized by Toll Fraud and You
by Avaya. The open source software license terms provided as Third need technical assistance or support, call Technical Service Center
Party Terms are consistent with the license rights granted in these Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
Software License Terms, and may contain additional rights benefiting States and Canada. For additional support telephone numbers, see
You, such as modification and distribution of the open source
the Avaya Support website: https://support.avaya.com or such
successor site as designated by Avaya.
Security Vulnerabilities
Information about Avaya’s security support policies can be found in
the Security Policies and Support section of https://
support.avaya.com/security.
Suspected Avaya product security vulnerabilities are handled per the
Avaya Product Security Support Flow (https://
support.avaya.com/css/P8/documents/100161515).
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support website: https://support.avaya.com, or such successor site
as designated by Avaya.
Contact Avaya Support
See the Avaya Support website: https://support.avaya.com for
product or Hosted Service notices and articles, or to report a problem
with your Avaya product or Hosted Service. For a list of support
telephone numbers and contact addresses, go to the Avaya Support
website: https://support.avaya.com (or such successor site as
designated by Avaya), scroll to the bottom of the page, and select
Contact Avaya Support.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation, Hosted Service(s), and product(s) provided
by Avaya are the registered or unregistered Marks of Avaya, its
affiliates, its licensors, its suppliers, or other third parties. Users are
not permitted to use such Marks without prior written consent from
Avaya or such third party which may own the Mark. Nothing
contained in this site, the Documentation, Hosted Service(s) and
product(s) should be construed as granting, by implication, estoppel,
or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners.
Linux® is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Contents

Chapter 1: Introduction............................................................................................................  7
Purpose.................................................................................................................................. 7
Intended audience................................................................................................................... 7
Terminology............................................................................................................................ 7
Document changes since last issue..........................................................................................  7
Related resources...................................................................................................................  8
Documentation.................................................................................................................. 8
Viewing Avaya Mentor videos............................................................................................. 8
Support............................................................................................................................  9
Chapter 2: New in this release............................................................................................... 10
Chapter 3: Avaya Collaboration Services overview............................................................  11
Avaya Collaboration Services features....................................................................................  11
Support for Google and Office 365 applications.................................................................  13
System requirements and interoperability................................................................................  14
Avaya Collaboration Services installation requirements......................................................  14
Collaboration Services Outlook add-in Interoperability requirements.................................... 16
Chapter 4: Collaboration Services installation....................................................................  17
Installation parameters........................................................................................................... 17
Extracting the MSI installer from the Avaya Collaboration Services exe file................................  19
Installation options................................................................................................................. 20
Installing Avaya Collaboration Services on the desktop......................................................  20
Installing Collaboration Services on multiple machines from a remote server........................ 21
Installing and uninstalling Collaboration Services in a virtualized application environment.....  22
Chapter 5: Collaboration Services configuration................................................................  23
Smart Tags or Actions configuration........................................................................................ 23
Actions and Smart Tag limitations..................................................................................... 23
Enabling Smart Tags in Outlook 2007...............................................................................  24
Enabling Smart Tags in Microsoft Word, Excel, or PowerPoint in the Office 2007 suite.........  24
Enabling Actions in Outlook 2010 and later........................................................................ 25
Enabling Actions in Word, Excel, and PowerPoint 2010 and later........................................  25
Activating Avaya Collaboration Services in the Microsoft Office suite...................................  26
Enabling Avaya Collaboration Services in web browsers..........................................................  26
Activating Avaya Collaboration Services in Internet Explorer............................................... 27
Chapter 6: Collaboration Services administration..............................................................  28
Uninstalling Collaboration Services from the Windows Control Panel......................................... 28
Uninstalling Collaboration Services through the Windows command console.............................  28
Upgrading Collaboration Services........................................................................................... 29
Upgrading Collaboration Services to support a new version of Microsoft Office....................  29
Setting the debug log levels for Collaboration Services............................................................. 30

September 2016 Administering Avaya Collaboration Services 5


Comments on this document? infodev@avaya.com
Contents

Browser administration..........................................................................................................  30


Disabling Collaboration Services in Google Chrome........................................................... 30
Blocking websites to stop highlighting telephone numbers..................................................  31
Unblocking websites using the group policy....................................................................... 31
Chapter 7: Troubleshooting Collaboration Services........................................................... 32
Assembly loading fails during an upgrade................................................................................ 32
Avaya Collaboration Services installation fails.......................................................................... 32
Avaya Collaboration Services reminder does not display all Outlook reminders..........................  33
Avaya Collaboration Services is unable to use Unified Communication clients............................ 33
Avaya Collaboration Services does not work in Google Chrome................................................ 34
Avaya Collaboration Services does not display Outlook presence.............................................  34
Collaboration Services highlights all the E.164 numbers and locally formatted telephone
numbers in the browser window.............................................................................................. 35
Click-to-call and click-to-IM are unavailable in the Outlook contact card.....................................  35
Conference bridge numbers are marked as normal telephone numbers..................................... 36
Invitation text is not removed from the meeting invitation..........................................................  36
Log file uninstallation error.....................................................................................................  36
Meeting template does not appear in the meeting invitation......................................................  37
Microsoft Internet Explorer changes the position of the contact card in a remote computer..........  37
Nationally formatted numbers are not highlighted when Office 365 is running in Google
Chrome................................................................................................................................  38
Numbers are not highlighted in the search results of web browsers...........................................  38
Number recognition does not work in Internet Explorer.............................................................  39
Outlook does not display the Join Conference and Host Conference menu options .................... 39
Outlook freezes when using the click-to-call feature on an email signature................................. 40
Outlook and Avaya Collaboration Services contact cards show different user capabilities............ 40
Outlook add-in fails to open .msg files.....................................................................................  40
Other email clients do not support reporting a problem in localized languages............................ 41
Unable to use Outlook IM and Presence functionality from Collaboration Services...................... 42
Unable to re-enable Avaya Collaboration Services in Google Chrome.......................................  42
Unable to close Microsoft Outlook when adding contacts from the global address book..............  43
Unable to start a web collaboration session in a Citrix XenApp environment in Google Chrome...  43
Glossary................................................................................................................................... 45

September 2016 Administering Avaya Collaboration Services 6


Comments on this document? infodev@avaya.com
Chapter 1: Introduction

Purpose
This document provides information about how to perform Avaya Collaboration Services
administration tasks including some troubleshooting procedures.

Intended audience
This document is intended for administrators who install, configure, upgrade, and troubleshoot the
Avaya Collaboration Services application.

Terminology
Product names
The following names are used to refer to the Avaya Collaboration Services application:
• Avaya Collaboration Services
• Collaboration Services
Application names
The following names are used to refer to the Collaboration Services Office and Browser applications
when one of these applications is called out separately:
• Collaboration Services Office and Browser applications
• Office and Browser applications
• Office and Browser Add-ins

Document changes since last issue


The following changes have been made to this document:
• Added information about blocking and unblocking websites.

September 2016 Administering Avaya Collaboration Services 7


Comments on this document? infodev@avaya.com
Introduction

• Added information about uninstalling Collaboration Services through the Windows command
console.
• Updated troubleshooting chapter with a new section on opening .msg files.
• Added a procedure about extracting the MSI installer from the Collaboration Services .exe file.

Related resources

Documentation
You can download related documents from the Support website at http://support.avaya.com.

Title Use this document to: Audience


Administration
Administering Avaya Communicator Deploy, install, configure, upgrade, and System
for Microsoft Lync on Avaya Aura® troubleshoot Avaya Communicator for administrators and
Microsoft Lync. support personnel
Administering Avaya Communicator Perform server administration of Avaya System
for Android, iPad, iPhone, and Communicator for Android, iPad, iPhone, administrators and
Windows and Windows. support personnel
Using
Using Avaya Collaboration Services Understand the overview, installation, and
Enterprise users
feature usage information.
Using Avaya Communicator for Understand the overview, installation, and Enterprise users
Windows feature usage information.

Viewing Avaya Mentor videos


Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya
products.
About this task
Videos are available on the Avaya Support website, listed under the video document type, and on
the Avaya-run channel on YouTube.
Procedure
• To find videos on the Avaya Support website, go to http://support.avaya.com and perform one
of the following actions:
- In Search, type Avaya Mentor Videos to see a list of the available videos.

September 2016 Administering Avaya Collaboration Services 8


Comments on this document? infodev@avaya.com
Related resources

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

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

September 2016 Administering Avaya Collaboration Services 9


Comments on this document? infodev@avaya.com
Chapter 2: New in this release

Avaya Collaboration Services Release 6.6 and 6.6.x service packs and feature packs include the
following new features and enhancements:
Compatibility updates
Avaya Collaboration Services now supports the following:
• Windows 8.1
• Mozilla Firefox
Instant messaging and presence enhancements
Instant messaging (IM) and presence have been enhanced to work on all Unified Communications
(UC) desktop clients that interwork with Avaya Collaboration Services.
Configurator moved to Avaya Communicator for Microsoft Lync product
The Configurator component is no longer part of Collaboration Services. The Configurator has been
rebranded to Avaya Communicator for Microsoft Lync Configurator.
New configuration parameters
A new configuration parameter has been added to enable or disable integration of Collaboration
Services IM with the Outlook contact card.

September 2016 Administering Avaya Collaboration Services 10


Comments on this document? infodev@avaya.com
Chapter 3: Avaya Collaboration Services
overview

The Avaya Collaboration Services application provides click-to-call, click-to-IM, and click-to-join and
host conference functionality.
Click-to-call functionality is supported on:
• Microsoft Office applications, such as Word, Excel, PowerPoint, and Outlook.
• Web browsers, such as Google Chrome, Internet Explorer, and Mozilla Firefox.
Click-to-IM and click-to-join and host conference functionality are supported on Outlook and web
browsers. You can send IM from web browsers only if the presence status of a contact is known.
Avaya Collaboration Services interoperates with the following UC desktop clients:
• Avaya Communicator for Microsoft Lync
• Avaya Communicator for Windows
• Avaya one-X® Communicator
Note:
You must have only one UC desktop client installed on your computer at a time.
Related links
Avaya Collaboration Services features on page 11

Avaya Collaboration Services features


Click-to-join or host a conference
Using the Avaya Conference Configuration wizard, you can add, modify, and delete your bridge and
web conference details. Use click-to-join and host a conference to:
• Schedule a meeting with a contact from Outlook.
• Join or host a conference from a web browser or Outlook.
Click-to-call
You can make a voice or video call from a Microsoft Office application or web browser. Use Smart
Tags or Actions to detect phone numbers of a contact within Microsoft Office applications. You must

September 2016 Administering Avaya Collaboration Services 11


Comments on this document? infodev@avaya.com
Avaya Collaboration Services overview

enable Smart Tags or Actions to use click-to-call in Microsoft Office applications, such as Word,
Excel, and PowerPoint.
Click-to-call or IM from a contact card
• From a contact card in Outlook, you can:
- View contact information.
- Make a voice or video call to a contact.
- View presence status and status messages.
- Send an instant message.
- Schedule a meeting.
Note:
You can also call a contact using Additional Actions in Outlook.
• From a contact card in a web browser, you can:
- Make a voice or video call to a contact.
- Schedule a meeting.
- Send an instant message.
- View presence.
- Access contact information.
- Create and send emails.
Other call options
Using the Avaya Collaboration Services Outlook add-on application, you can access the following
additional features:
• Forced Authorization Code (FAC) calling: You can call a number with the pound sign (#). You
can use this feature to dial a conference bridge number and passcode, such as
1866-123-1234 123456#. If the number starts with the pound sign (#), the system
processes the number as a Forced Authorization Code. If the pound sign (#) is before a
comma or at the end of the dial string, the system processes the string as a complete string.
• Extension calling: You can call a telephone number and extension. You can only use the
extension sign (x) in the telephone number. For example: +16135552000 X 1234.
• Conference calling: You can dial a conference call with the contacts in your Outlook client. For
example: 13035382200,123456#, 13035382200,123456,1234,
13035382200,123456,1234#.
Related links
Avaya Collaboration Services overview on page 11
Support for Google and Office 365 applications on page 13

September 2016 Administering Avaya Collaboration Services 12


Comments on this document? infodev@avaya.com
Avaya Collaboration Services features

Support for Google and Office 365 applications


You can use Collaboration Services click-to-call, and click to join or host a conference functionality
within:
• Google applications, such as Gmail, Calendar, Sheets, Documents, Contacts, and Forms.
• Office 365 applications, such as Word, Excel, Outlook, Calendar, SharePoint, People, and
OneNote.

Figure 1: Support matrix for Google and Office 365 Applications

September 2016 Administering Avaya Collaboration Services 13


Comments on this document? infodev@avaya.com
Avaya Collaboration Services overview

System requirements and interoperability

Avaya Collaboration Services installation requirements


System privileges Administrator

Software • Microsoft.NET Framework 3.5 and 4.0


prerequisites
• Microsoft Visual Studio 2010 Tools for Office Runtime x64 and x86
• Microsoft Visual C++ 2010 Service Pack 1 Runtime Libraries x86
When you install Avaya Collaboration Services for the first time, ensure
that all prerequisites are installed on your computer. If not, connect your
computer to the internet to automatically download all prerequisites,
except Microsoft.NET Framework 3.5 that must be downloaded manually.

Supported • Microsoft Windows 7


operating system
• Microsoft Windows 8.1
Ensure that the operating system is fully updated with all Microsoft
patches.

Supported browsers • Internet Explorer 8, 9, 10, and 11


• Firefox 17 ESR and later
• Google Chrome 27 and later

Supported versions • Office 2007


of Microsoft Office
• Office 2010
• Office 2013

Minimum disk 380 MB


space
Note:
Minimum 100 MB of disk space is required for installation.

Related links
Avaya Collaboration Services overview on page 11
VDI requirements on page 14

VDI requirements
The following table summarizes VDI product and server requirements. For detailed information
about VDI requirements, including Virtual Desktop versions, see https://support.avaya.com/
CompatibilityMatrix/Index.aspx.

September 2016 Administering Avaya Collaboration Services 14


Comments on this document? infodev@avaya.com
System requirements and interoperability

Table 1: VDI requirements

Virtual Desktop versions Latest versions of Citrix Xen Desktop, Citrix Xen Applications, and VMWare
Horizon View
Virtual Desktop servers Windows 2008 R2 Enterprise for Citrix Xen Desktop, Citrix Xen
Applications, Microsoft Terminal Server, and VMWare Horizon View
VDI Communicator Version 2.0

The following table lists the VDI specifications for various types of resources:
Table 2: VDI specifications

Resource type Operating vCPU RAM per user RAM per Users per
system (in GB) system (in GB) virtual
machine
Xen Desktop Personal or Windows 7 2 2 N/A 1
Pooled desktop Windows 8.1 2 2 N/A 1
VMware Horizon Windows 7 2 2 N/A 1
Windows 8.1 2 2 N/A 1
XenApp - Hosted Apps or Windows 2008 8 N/A 24 12 to 18
Shared desktop R2
Windows 2012 8 N/A 24 12 to 18
Windows 2012 8 N/A 24 12 to 18
R2
Microsoft Terminal Server Windows 2008 8 N/A 24 12 to 18
Microsoft Remote R2
Desktop Services Windows 2012 8 N/A 24 12 to 18
Windows 2012 8 N/A 24 12 to 18
R2

Note:
• The recommended specifications are for a normal workload of an office-based user.
• With additional memory, you can add more users per virtual machine.
The following table summarizes the server specifications:
Table 3: Server and system memory specifications

Server type CPU System Hard Disk Drive Operation system


memory (in (in GB)
GB)
IBM BladeCenter HS22- Intel Xeon CPU 40 552 Windows 2012
[7870AC1] E5540 @ 2.53 GHz
Table continues…

September 2016 Administering Avaya Collaboration Services 15


Comments on this document? infodev@avaya.com
Avaya Collaboration Services overview

Server type CPU System Hard Disk Drive Operation system


memory (in (in GB)
GB)
Dell R620 Intel Xeon CPU 80 900 XenServer 6.2
E5-2640 @ 2.50
GHz

Related links
Avaya Collaboration Services installation requirements on page 14

Collaboration Services Outlook add-in Interoperability


requirements
You can improve the overall performance of Outlook by removing the following Outlook add-ins:
• Avaya one-X® Communicator Outlook Integrator
• Avaya Aura® Conferencing Conference Manager
When deploying Collaboration Services with Avaya Communicator for Microsoft Lync and Avaya
Communicator for Windows, remove the following Outlook add-ins:
• Microsoft Office Communicator 2007
• Lync Meeting
You must also remove any other Outlook add-ins that you are not using.
Related links
Avaya Collaboration Services overview on page 11

September 2016 Administering Avaya Collaboration Services 16


Comments on this document? infodev@avaya.com
Chapter 4: Collaboration Services
installation

Installation parameters
The following tables describe the main installation parameters for Collaboration Services:
Table 4: Installation parameters

Parameter Description
ENABLECUSTOMIMPROVIDERS Use this parameter to enable or disable integration of
Collaboration Services IM with the Outlook contact card. You
can set one of the following values:
• true to enable integration
• false to disable integration
The default value is false.
DISABLECCEREMINDERWINDOW Enter this parameter in the Command window to disable
Collaboration Services Reminder window in Outlook.
The default value is false.
SILENTSHOWOPENAPPSDLG Enter this parameter in the Command window to start a silent
installation. During the installation, you receive a warning to
close applications, such as Internet Explorer.
The default value is true.
USELDAPCONFIGFROMREGISTRY Enter this parameter to configure a secondary Active Directory.
By default, Collaboration Services configures Active Directory
by using the domain that the user is logged in to.
The default value is false.
ISCITRIX Enter this parameter in the Command window to install
Collaboration Services in a Citrix environment.
The default value is false.
CONFIG Enter this parameter to apply custom configuration by providing
the custom configuration file name and file location to the
Collaboration Services installer.

September 2016 Administering Avaya Collaboration Services 17


Comments on this document? infodev@avaya.com
Collaboration Services installation

These parameters are based on Install Shield. For more information about Install Shield, see http://
helpnet.installshield.com/.
The following table describes MSI parameters. The parameters can vary for .exe and .msi
deployments.
Table 5: Installation parameters for CollaborationServices.msi .

Parameter Description
/x Enter this parameter in the Command window to uninstall
Collaboration Services. The complete command line must be
CollaborationServices.exe /x.
/s /v"/qn" Enter this parameter in the Command window to start a silent
installation. With this parameter, you can complete the
installation with applications such as Internet Explorer running
in the background. Collaboration Services appears the next
time you restart the application.
The complete command line must be
CollaborationServices.exe /s /x /v"/qn". When
you add /x to the command line, the system starts silent
uninstallation.
SILENTSHOWOPENAPPSDLG Enter this parameter in the Command window to start a silent
installation. With this parameter, you receive a warning to close
applications, such as Internet Explorer during the installation.
The complete command line must be
CollaborationServices.exe /s /
v"SILENTSHOWOPENAPPSDLG=TRUE /qn".
-ISCITRIX Enter this parameter in the Command window to install
Collaboration Services in a Citrix environment. The complete
command line must be CollaborationServices.exe /
v"ISCITRIX=TRUE".
ENABLECUSTOMIMPROVIDERS Use this parameter to enable or disable integration of
Collaboration Services IM with the Outlook contact card. You
can set one of the following values:
• true to enable integration
• false to disable integration
The complete command line to enable integration of IM with the
Outlook contact card must be
CollaborationServices.exe /
v"ENABLECUSTOMIMPROVIDERS=TRUE".

Note:
Use ENABLECUSTOMIMPROVIDERS instead of -
disableIMIntegration.
Table continues…

September 2016 Administering Avaya Collaboration Services 18


Comments on this document? infodev@avaya.com
Extracting the MSI installer from the Avaya Collaboration Services exe file

Parameter Description
DISABLECCEREMINDERWINDOW Enter this parameter in the Command window to disable the
Reminder window in Outlook.
The complete command line must be
CollaborationServices.exe /
v"DISABLECCEREMINDERWINDOW=TRUE".
USELDAPCONFIGFROMREGISTRY Enter this parameter to configure a secondary Active Directory.
By default, Collaboration Services configures Active Directory
by using the domain that the user is logged in to.
The complete command line must be
CollaborationServices.exe /
v"USELDAPCONFIGFROMREGISTRY=TRUE". You need not set
the default value as true or false. The default value is
false.
CONFIG Enter this parameter to apply custom configuration by providing
custom configuration file name and file location to Collaboration
Services installer. The complete command line must be
CollaborationServices.exe /v"CONFIG=\"C:
\testing\Default.Collaboration.config"".

Related links
Avaya Collaboration Services installation requirements on page 14
VDI requirements on page 14

Extracting the MSI installer from the Avaya Collaboration


Services exe file
About this task
Use this procedure to extract the MSI installer from the Avaya Collaboration Services .exe file
provided with Avaya one-X® Communicator.
Procedure
1. Open the Windows command console as an administrator.
2. In the Command window, type the path of the folder where the installation file is stored.
3. Run the following command:
Avaya one-X Communicator Suite.exe /stage_only

4. Press Enter on your keyboard.


5. Click Next when you see the Avaya one-X® Communicator – InstallShield Wizard.
6. Click Change .

September 2016 Administering Avaya Collaboration Services 19


Comments on this document? infodev@avaya.com
Collaboration Services installation

7. Navigate to the staging location.


8. Click Install to stage or extract the installation package.
Avaya Collaboration Services is staged in the {2B664BD7-3F93-41D1-
BF4F-038553CC778B} folder.
9. Click Finish to exit the InstallShield Wizard.
10. To stage the Avaya Collaboration Services MSI, do the following:
a. In the Command window, type the staged folder path.
b. Run the following command:
CCE_<build number>.exe /stage_only

For example:
CCE_6.6.2.18.exe /stage_only

11. Press Enter on your keyboard.


12. Click Next when you see the Avaya Collaboration Services – InstallShield Wizard.
13. Repeat steps 6 on page 19 and 7 on page 20.
14. Click Install to stage or extract the installation package.
The CollaborationServices.exe file is staged in the {D9588C7B-1E2A-491C-B225-
CF85D90C264C} folder.
15. Double-click the CollaborationServices.exe file to extract the
CollaborationServices.msi file.
The CollaborationServices.msi file is extracted into the C:\ProgramData
\Downloaded Installations{1CFAC5C6-BF6B-4108-BD23-C2108E1CD156} folder.

Installation options
As an administrator, you can install Collaboration Services locally or using a command line. The
following procedures describe the different installation options.

Installing Avaya Collaboration Services on the desktop


Before you begin
Ensure that:
• You have the Avaya.CollaborationServices.Setup.exe or
Avaya.CollaborationServices.Installer.exe file.
• You have administration privileges.

September 2016 Administering Avaya Collaboration Services 20


Comments on this document? infodev@avaya.com
Installation options

• Your system meets the hardware and software requirements. See Avaya Collaboration Service
installation requirements on page 14.
• You close the open web browsers and Microsoft Outlook running on your computer.
Procedure
1. Open the Avaya Collaboration Services folder, and navigate to the
Avaya.CollaborationServices.Setup.exe or
Avaya.CollaborationServices.Installer.exe file.
2. Double-click the setup.exe file and follow the instructions.
You can use the Avaya.CollaborationServices.Setup.exe -silent or
Avaya.CollaborationServices.Installer.exe -silent command to perform a
silent installation.
Next steps
• Enable the Office and Browser add-ins.
• If the Office add-in is deployed with Avaya Communicator for Microsoft Lync, disable the
Telephone (XML) feature in Microsoft Outlook. If you do not disable this feature, you will
receive a redundant Telephone Number menu option when using the click-to-call feature.
• If you are using IE 10 or 11 with Windows 8.1, disable Enhanced Protected Mode for Avaya
Collaboration Services to work.
• If you are using proxy internet connection, add the following sites to the white list in the settings
of proxy connection:
• http://download.microsoft.com/
• http://software77.net/

Installing Collaboration Services on multiple machines from a


remote server
Before you begin
Ensure that:
• You have the Avaya.CollaborationServices.Setup.exe or
Avaya.CollaborationServices.Installer.exe file.
• Your system meets the hardware and software requirements. See Avaya Collaboration Service
installation requirements on page 14.
Procedure
1. Include all the output files other than the registry files (.reg) from the build.
2. Zip the files so that you can use the files in a software distribution system, such as Microsoft
System Center Configuration Manager (MSCCM).
3. Run the following command: Avaya.CollaborationServices.Setup.exe —silent or
Avaya.CollaborationServices.Installer.exe -silent.

September 2016 Administering Avaya Collaboration Services 21


Comments on this document? infodev@avaya.com
Collaboration Services installation

Next steps
• Enable the Office and Browser add-ins.
• If the Office add-in is deployed with Avaya Communicator for Microsoft Lync, disable the
Telephone (XML) feature in Microsoft Outlook. If you do not disable this feature, you will
receive a redundant Telephone Number menu option when using the click-to-call feature.
• If you are using IE 10 or 11 with Windows 8.1, disable Enhanced Protected Mode for Avaya
Collaboration Services to work.
• If you are using proxy internet connection, add the following sites to the white list in the settings
of proxy connection:
• http://download.microsoft.com/
• http://software77.net/

Installing and uninstalling Collaboration Services in a virtualized


application environment
About this task
Use this procedure to install Avaya Collaboration Services in a Citrix or VDI environment. In a Citrix
environment, you can deploy up to 200 Collaboration Services instances.
Note:
Virtual applications support Internet Explorer or Google Chrome, not Mozilla Firefox.
Before you begin
Ensure that:
• You have administration privileges.
• You have the Avaya.CollaborationServices.Setup.exe or
Avaya.CollaborationServices.Installer.exe file.
Procedure
1. Navigate to the folder where the Collaboration Services installation file is stored.
2. In the Command window:
a. Switch to the directory containing the Collaboration Services installation file.
b. Type Avaya.CollaborationServices.Setup.exe -ISCITRIX=true or
Avaya.CollaborationServices.Installer.exe -ISCITRIX=true.
c. (Optional) Type Avaya.CollaborationServices.Setup.exe -remove -
ISCITRIX=true or Avaya.CollaborationServices.Installer.exe -remove
-ISCITRIX=true to uninstall Collaboration Services.
3. To complete the installation, follow the instructions.
4. Restart your computer if prompted.

September 2016 Administering Avaya Collaboration Services 22


Comments on this document? infodev@avaya.com
Chapter 5: Collaboration Services
configuration

Smart Tags or Actions configuration


By enabling Smart Tags or Actions in your Microsoft Office applications, you can make calls from
Microsoft Office applications. Smart Tag is available in Microsoft Office 2007. Actions is available
in Microsoft Office 2010 and later.
Smart Tag and Actions only support dialing local and E.164 numbers and not conference numbers.
Smart Tag and Actions highlight conference numbers as normal numbers with out the passcode.
Smart Tag normalizes the number to the E.164 format based on the locale of the current text. For
example, if the locale of your Office document is UK, a local UK number that appears on the
document is marked, normalized into the E.164 format, and then presented in the Call menu item.
Related links
Actions and Smart Tag limitations on page 23
Enabling Smart Tags in Outlook 2007 on page 24
Enabling Smart Tags in Microsoft Word, Excel, or PowerPoint in the Office 2007 suite on page 24
Enabling Actions in Outlook 2010 and later on page 25
Enabling Actions in Word, Excel, and PowerPoint 2010 and later on page 25
Activating Avaya Collaboration Services in the Microsoft Office suite on page 26

Actions and Smart Tag limitations


Valid telephone numbers are not recognized in Microsoft PowerPoint
PowerPoint can pass numbers to the Smart Tag recognizer incorrectly. Even if the number is in the
correct E.164 format, Collaboration Services might not be able to read the phone number properly.
For example, if the number entered in PowerPoint is +8482010541, PowerPoint might send the
number to the Smart Tag recognizer as 8482010541. PowerPoint might append another country
code, such as +1 to the beginning of the number. Due to the absence of the plus sign (+),
Collaboration Services cannot recognize the phone number. Therefore, when you right-click the
phone number and select Additional Actions, Collaboration Services does not provide a Call
<number> option.

September 2016 Administering Avaya Collaboration Services 23


Comments on this document? infodev@avaya.com
Collaboration Services configuration

To work around this issue, you must select the entire phone number with your mouse cursor. This
selection triggers Collaboration Services to recognize the phone number and provide the Call
<number> option in Additional Actions.
Related links
Smart Tags or Actions configuration on page 23

Enabling Smart Tags in Outlook 2007


Before you begin
• Install Avaya Collaboration Services on your computer.
• Open Outlook.
Procedure
1. On the File menu, click New > Mail Message.
2. Click the Microsoft Office button .
3. Click Editor Options.
4. In the left pane, click Proofing.
5. Click AutoCorrect Options , and then click the Smart Tags tab.
6. Select Label text with smart tags.
7. In the Recognizers area, ensure that Collaboration Services (Avaya Collaboration
Services) is selected.
8. Click OK.
9. In the left pane, click Advanced.
10. In the Display email content section, select Show smart tags.
11. Click OK.
Related links
Smart Tags or Actions configuration on page 23

Enabling Smart Tags in Microsoft Word, Excel, or PowerPoint in


the Office 2007 suite
Before you begin
• Install Avaya Collaboration Services on your computer.
• Open a Microsoft Office application, such as Word, Excel, or PowerPoint.
Procedure
1. In Word, click the Microsoft Office button .

September 2016 Administering Avaya Collaboration Services 24


Comments on this document? infodev@avaya.com
Smart Tags or Actions configuration

2. Click Options.
3. In the left pane, click Add-Ins.
4. In the Manage field, click Smart Tags, and then click Go.
5. In the Auto Correct window, select Label text with smart tags.
6. In the Recognizers area, ensure that Collaboration Services (Avaya Collaboration
Services) is selected.
7. Click OK.
Related links
Smart Tags or Actions configuration on page 23

Enabling Actions in Outlook 2010 and later


Before you begin
• Install Avaya Collaboration Services on your computer.
• Open Outlook.
Procedure
1. On the Outlook ribbon, click File > Options.
2. In the Outlook Options window, click the Mail tab, and then click Editor Options.
3. In the Editor Options window, click AutoCorrect Options.
4. In the AutoCorrect window, click the Actions tab, and then select Enable additional actions
in the right-click menu.
5. In the Available actions area, ensure that Collaboration Services (Avaya Collaboration
Services) is selected.
6. Click OK.
Related links
Smart Tags or Actions configuration on page 23

Enabling Actions in Word, Excel, and PowerPoint 2010 and later


Before you begin
• Install Avaya Collaboration Services on your computer.
• Open a Microsoft Office application, such as Word, Excel, or PowerPoint.
Procedure
1. On the Word ribbon, click File > Options.
2. In the Word Options window, click the Proofing tab, and then click AutoCorrect Options.

September 2016 Administering Avaya Collaboration Services 25


Comments on this document? infodev@avaya.com
Collaboration Services configuration

3. In the AutoCorrect window, click the Actions tab, and then select Enable additional actions
in the right-click menu.
4. In the Available actions area, ensure that Collaboration Services (Avaya Collaboration
Services) is selected.
5. Click OK.
Related links
Smart Tags or Actions configuration on page 23

Activating Avaya Collaboration Services in the Microsoft Office


suite
About this task
Use this procedure to enable Avaya Collaboration Services in all Microsoft Office applications at a
time.
Before you begin
Open a Microsoft Office application, such as Word, Excel, or PowerPoint.
Procedure
1. In Word, click the text in the Security Warning message.
2. In the Information window, in the Security Warning area, click Enable Content >
Advanced Options.
3. In the Microsoft Office Security Options window, select Enable all code published by this
publisher.
4. Click OK.
Collaboration Services is now available in the Microsoft Office suite.

Enabling Avaya Collaboration Services in web browsers


About this task
Use this procedure to enable Collaboration Services in IE and Firefox. Collaboration Services is
automatically enabled when you install Collaboration Services on a computer running Google
Chrome.
By enabling the Collaboration Services Browser add-in, you can make calls from webpages in
Google Chrome, Firefox, and Internet Explorer. For more information about managing add-ins in
different browsers, see the following:
• For Internet Explorer: https://support.microsoft.com/kb/883256/EN-US?wa=wsignin1.0.
• For Firefox: http://kb.mozillazine.org/Uninstalling_extensions#Windows_Registry_extension.

September 2016 Administering Avaya Collaboration Services 26


Comments on this document? infodev@avaya.com
Enabling Avaya Collaboration Services in web browsers

• For Google Chrome: http://www.chromium.org/administrators/policy-list-3#Extensions.


Before you begin
Install the following:
• Collaboration Services
• One or more supported web browsers: Internet Explorer (IE), Mozilla Firefox, and Google
Chrome
Procedure
Do the following in the appropriate web browser:
• In IE, right-click the toolbar and select Avaya Collaboration Services.
• In Firefox, in the Add-ons Manager tab, select Avaya Collaboration Services.
Related links
Activating Avaya Collaboration Services in Internet Explorer on page 27

Activating Avaya Collaboration Services in Internet Explorer


About this task
You might need to update some settings in Internet Explorer for Collaboration Services to work. For
security reasons, some enterprises disable third-party extensions in IE, and this setting must be
enabled in IE to display the Collaboration Services add-in.
Procedure
1. Open Internet Explorer.
2. Click Tools > Internet Options.
3. Click the Advanced tab.
4. In the Browsing area:
a. Select Enable third-party browser extensions.
b. Ensure that the Enable Enhanced Protected Mode check box is cleared if you are
using Windows 8.
By disabling Enable Enhanced Protected Mode feature, the system correctly
highlights the phone numbers in IE with Collaboration Services.
5. Click Apply, and then click OK.
The next time you open IE, ensure that Collaboration Services is visible and functioning.

September 2016 Administering Avaya Collaboration Services 27


Comments on this document? infodev@avaya.com
Chapter 6: Collaboration Services
administration

Uninstalling Collaboration Services from the Windows


Control Panel
Procedure
1. On the Windows Start menu, click Settings > Control Panel > Uninstall a program.
2. In the Uninstall or change a program window, right-click Avaya Collaboration Services,
and then click Uninstall/Change.
3. Click Yes at the command prompt.
4. Check the files after uninstallation.
5. (Optional) Delete the files manually from C:\Program Files (x86)\Avaya
\Collaboration Services or C:\Program Files\Avaya\Collaboration
Services.

Uninstalling Collaboration Services through the Windows


command console
Before you begin
• Ensure that you have administration privileges on the Windows computer.
• Ensure that you have the same version of the
Avaya.CollaborationServices.Setup.exe or
Avaya.CollaborationServices.Installer.exe file that was used to install
Collaboration Services.
• Close the open web browsers and Office applications running on your computer.
Procedure
1. Open the Windows command console.
2. Navigate to the Avaya.CollaborationServices.Setup.exe or
Avaya.CollaborationServices.Installer.exe file.

September 2016 Administering Avaya Collaboration Services 28


Comments on this document? infodev@avaya.com
Upgrading Collaboration Services

3. Type Avaya.CollaborationServices.Setup.exe –remove or


Avaya.CollaborationServices.Installer.exe –remove.
4. (Optional) Type Avaya.CollaborationServices.Setup.exe –remove -silent or
Avaya.CollaborationServices.Installer.exe -remove -silent to perform a
silent uninstallation.
5. Press Enter.

Upgrading Collaboration Services


Procedure
1. Close any instance of an application that is running Collaboration Services.
2. Install the new version of Collaboration Services.
Related links
Upgrading Collaboration Services to support a new version of Microsoft Office on page 29
Uninstalling Collaboration Services from the Windows Control Panel on page 28

Upgrading Collaboration Services to support a new version of


Microsoft Office
About this task
Use this procedure to update Collaboration Services after upgrading to a new version of Microsoft
Office.
Procedure
1. Uninstall the earlier version of Microsoft Office.
2. Uninstall Collaboration Services.
3. Install and configure the new version of Microsoft Office.
4. Install the new version of Collaboration Services.
Related links
Upgrading Collaboration Services on page 29
Uninstalling Collaboration Services from the Windows Control Panel on page 28

September 2016 Administering Avaya Collaboration Services 29


Comments on this document? infodev@avaya.com
Collaboration Services administration

Setting the debug log levels for Collaboration Services


About this task
You can set the debug log level and gather the debug log information for Collaboration Services.
Procedure
1. To enable the diagnostic logging option, on the System tray, right-click Avaya Collaboration
Services, and then click Settings.
2. In the Settings window, click About, and then select Enable diagnostic logging.
3. Click Save.

Browser administration
The following sections describe the changes that you can make to the Collaboration Services
Browser Add-in anytime.

Disabling Collaboration Services in Google Chrome


About this task
You cannot disable the Collaboration Services add-in in Google Chrome by changing the settings on
the Chrome extension page. You must use a .bat file.
Before you begin
Ensure that you have administration privileges.
Procedure
1. Close all the open Google Chrome web browser sessions.
2. Open the Command window as an administrator.
3. Navigate to the Collaboration Services folder, and in the Command window:
a. Enter the file path.
b. Run the following command:
UninstallChromeExtension.bat

Collaboration Services is disabled in Google Chrome.

September 2016 Administering Avaya Collaboration Services 30


Comments on this document? infodev@avaya.com
Browser administration

Blocking websites to stop highlighting telephone numbers


About this task
You can block a website using a group policy. The Administrator has disabled the following site(s)
list in the Browser Add-in General tab displays blocked websites with a red icon. Collaboration
Services does not highlight telephone numbers on blocked websites.
Procedure
1. In the Windows registry, update the group policy as follows:
• For 64–bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AVAYA
\Collaboration\BlockedHost
• For 32–bit: HKEY_LOCAL_MACHINE\SOFTWARE\Avaya\Collaboration
\BlockedHost
2. Create a new value name with the REG_SZ type.
3. In Value name, type the site address.
4. In Value data, type Blocked.
Next steps
Restart Collaboration Services.

Unblocking websites using the group policy


About this task
Using the group policy, you can unblock websites. Collaboration Services highlights telephone
numbers on websites that are unblocked.
Procedure
1. In the Windows registry, update the group policy as follows:
• For 64–bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AVAYA
\Collaboration\BlockedHost
• For 32–bit: HKEY_LOCAL_MACHINE\SOFTWARE\Avaya\Collaboration
\BlockedHost
2. Remove the site address (value name) that you want to unblock.
Next steps
Restart Collaboration Services.

September 2016 Administering Avaya Collaboration Services 31


Comments on this document? infodev@avaya.com
Chapter 7: Troubleshooting Collaboration
Services

Assembly loading fails during an upgrade


Condition
When you upgrade from Release 6.2.2 to Release 6.3 or later, you might encounter a log4net
assembly loading failure. If this occurs, the upgrade fails.
Cause
The Release 6.2.2 assemblies are not cleaned.
Solution
1. Download the log4net file from http://archive.apache.org/dist/logging/log4net/binaries/
log4net-1.2.11-bin-newkey.zip.
2. Extract the archive.
3. Navigate to log4net.dll in \log4net-1.2.11\bin\net\2.0\release\.
4. Install this assembly to the Global Assembly Cache (GAC).
For more information about installing to the GAC, see http://msdn.microsoft.com/en-us/
library/dkkx7f79(v=vs.100).aspx.
You can see the successful installation when you run the installer for the new version of
Avaya Collaboration Services.

Avaya Collaboration Services installation fails


Condition
Avaya Collaboration Services installation fails if:
• You do not have the prerequisites installed on your computer.
• The version of your Microsoft Visual Studio 2010 Tools for Office Runtime x64 is 10.0.31007.
Cause
• Your computer is not connected to the internet to download or upgrade the prerequisites for
installing Avaya Collaboration Services.

September 2016 Administering Avaya Collaboration Services 32


Comments on this document? infodev@avaya.com
Avaya Collaboration Services reminder does not display all Outlook reminders

• The system fails to upgrade Microsoft Visual Studio 2010 Tools to the required version.
Solution
1. Connect to the internet.
2. Do one of the following:
• Uninstall Microsoft Visual Studio 2010 Tools for Office Runtime x64.
• Upgrade Microsoft Visual Studio 2010 Tools for Office Runtime x64 to the required
version.
3. Run Avaya Collaboration Services installer.

Avaya Collaboration Services reminder does not display


all Outlook reminders
Condition
In Microsoft Office Outlook 2010, the Avaya Collaboration Services Reminder window does not
display all reminders from the Outlook Reminder window.
Cause
The Microsoft Office Outlook interoperability call is unsuccessful and Avaya Collaboration Services
fails to get the meeting details from the Outlook reminder.
Solution
Workaround is unavailable.

Avaya Collaboration Services is unable to use Unified


Communication clients
Condition
Avaya Collaboration Services is unable to use Unified Communication clients. For example, if you
run a UC client as an administrator and Avaya Collaboration Services as a nonadministrator, you do
not get the following features from Avaya Collaboration Services:
• IM
• Voice call
• Video call
• Conference call
Cause
Avaya Collaboration Services internally communicates with the user interface of the UC clients. For
this communication, the applications must have the same level of security mechanism. When the

September 2016 Administering Avaya Collaboration Services 33


Comments on this document? infodev@avaya.com
Troubleshooting Collaboration Services

applications have different privileges, the operating system does not enable communication
between the applications.
Solution
Start both the UC client and Avaya Collaboration Services with the same privilege, either as an
administrator or a nonadministrator.

Avaya Collaboration Services does not work in Google


Chrome
Condition
When Google Chrome is running in a proxy environment, Collaboration Services does not work in
Google Chrome.

Cause
The bypass proxy option is disabled for local addresses.

Solution
1. In Google Chrome, click Settings.
2. On the Settings page, click Show advanced settings.
3. In the Network area, click Change proxy settings.
4. In the Internet Properties window, click LAN settings.
5. In the LAN Settings window, select Bypass proxy server for local addresses and click
OK.

Avaya Collaboration Services does not display Outlook


presence
Condition
Avaya Collaboration Services does not display Outlook presence when you change the network
connection.
Cause
When you start the computer, Avaya Collaboration Services retrieves the details of the network to
which you log in. If you connect to a different network, Avaya Collaboration Services does not get
any notification about the change in the network. Therefore, Avaya Collaboration Services cannot
display Outlook presence.

September 2016 Administering Avaya Collaboration Services 34


Comments on this document? infodev@avaya.com
Collaboration Services highlights all the E.164 numbers and locally formatted telephone numbers in the browser window

Solution
1. Restart Avaya Collaboration Services.
2. After establishing the connection to the new network, restart Outlook and Avaya Lync add-in.
Outlook displays the presence of contacts.

Collaboration Services highlights all the E.164 numbers


and locally formatted telephone numbers in the browser
window
Condition
The Collaboration Services plug-in for browsers highlights all numbers in the browser window that
are in the E.164 format or the country-specific format. All numbers are highlighted even if the
numbers are not telephone numbers.
Cause
Unknown
Solution
Workaround is unavailable.

Click-to-call and click-to-IM are unavailable in the Outlook


contact card
Condition
When the Microsoft Lync client is uninstalled after you install Collaboration Services, you might be
unable to:
• View the presence status of a contact.
• Access the click-to-call and click-to-IM capabilities from your Outlook contact card.
Cause
Microsoft Lync and Collaboration Services share a common Avaya UCA Type Library. The
UCOfficeIntegration Library might get unregistered if Lync is uninstalled.
Solution
Reregister the Avaya UCA Type Library to work without the Lync client.
1. Uninstall Collaboration Services and the Avaya UCA Type Library.
2. Reinstall Collaboration Services.

September 2016 Administering Avaya Collaboration Services 35


Comments on this document? infodev@avaya.com
Troubleshooting Collaboration Services

Conference bridge numbers are marked as normal


telephone numbers
Condition
When Google Chrome or Internet Explorer (IE) is used to edit a page or send a message or
document by email, Avaya Collaboration Services cannot distinguish between conference bridge
numbers and normal telephone numbers. Therefore, conference bridge numbers are marked as
normal telephone numbers. This issue only occurs when you are editing in the browser, not when
you are reading in the browser.
Cause
Unknown
Solution
Workaround is unavailable.

Invitation text is not removed from the meeting invitation


Condition
On a 32–bit Windows 7, in Outlook 2007, you might be unable to remove the conference details
from the meeting invitation using the Remove Conference Details button.
Cause
Unknown
Solution
Delete the invitation text from the meeting invitation manually.

Log file uninstallation error


Condition
When you uninstall Collaboration Services from Windows Control Panel, the system displays the
following error message:
Error opening installation log file. Verify that the specified location
exists and is writable.
Cause
This issue occurs when Windows Installer Logging is enabled, but the Windows Installer engine
cannot write the uninstallation log file correctly. For more information, see http://
support.microsoft.com/kb/2564571/en-us.

September 2016 Administering Avaya Collaboration Services 36


Comments on this document? infodev@avaya.com
Meeting template does not appear in the meeting invitation

Solution
Stop and restart the Explorer.exe process using Task Manager.

Meeting template does not appear in the meeting invitation


Condition
In Outlook 2013, outgoing meeting invitations do not contain conference details when you add a
meeting template using the Add Conference Details option. You are unable to:
• Access the regional bridge number to join the conference call.
• Join the conference call from your mobile device.
Cause
Known limitation with the Microsoft Office suite.
Solution
Repair the Microsoft Office suite in Windows Control Panel or do one of the following:
• Join the conference call by:
- Using the conference details in the Location field.
- Using the conference details in the Reminder window.
- Clicking Host Conference.
• Join the conference by dialing the bridge number manually if you are not using Avaya
Collaboration Services.
Note:
Ensure that the meeting organizer adds the regional access number to the invitation
manually.

Microsoft Internet Explorer changes the position of the


contact card in a remote computer
Condition
When you connect to a remote computer from the client computer, Internet Explorer in the remote
computer displays the browser contact card. If the screen resolutions of the client computer and the
remote computer are different, the position of the browser contact card in Internet Explorer might
change.
Cause
The client computer does not get the coordinates of the mouse pointer on the remote computer.

September 2016 Administering Avaya Collaboration Services 37


Comments on this document? infodev@avaya.com
Troubleshooting Collaboration Services

Solution
Workaround is unavailable.

Nationally formatted numbers are not highlighted when


Office 365 is running in Google Chrome
Condition
The default locale for Office 365 is the United States. If you override the locale to another country
when running Office 365 in Google Chrome, and then try to edit the Office 365 document, national
numbers for the new locale are not highlighted. Instead, the default U.S. numbers continue to be
highlighted.
Cause
This issue occurs because the internal URL for Office 365 is automatically redirected when a
document is edited in Google Chrome.
Solution
Workaround is unavailable for this issue in Google Chrome.
Google Chrome only highlights nationally formatted numbers for a new locale if you do not switch to
Edit mode. This issue does not occur when you edit an Office 365 document in Internet Explorer
(IE).

Numbers are not highlighted in the search results of web


browsers
Condition
When you search for an E.164 number in Internet Explorer, Mozilla Firefox, or Google Chrome,
Collaboration Services does not highlight some numbers in the search result.
Cause
Collaboration Services does not recognize numbers if HTML tags are embedded within the number.
Solution
Workaround is unavailable.

September 2016 Administering Avaya Collaboration Services 38


Comments on this document? infodev@avaya.com
Number recognition does not work in Internet Explorer

Number recognition does not work in Internet Explorer


Condition
When a webpage takes more than three seconds to load in Internet Explorer, Avaya Collaboration
Services does not mark the numbers on the webpage. For example, when you open Avaya contact
pages, http://www.avaya.com/usa/contacts, in Internet Explorer, Avaya Collaboration Services does
not mark the numbers on the webpage. But when you open this page in Google Chrome, Avaya
Collaboration Services marks the numbers on the webpage.
Cause
When the webpage takes more than three seconds to load, Avaya Collaboration Services stops
parsing and does not mark any number.
Solution
1. Increase the timeout period by changing the value of ParserTimeout in the registry at the
following locations:
• For a 64–bit Windows operating system: HKEY_LOCAL_MACHINE\SOFTWARE
\Wow6432Node\Avaya\Collaboration\<version installed on machine>
• For a 32–bit Windows operating system: HKEY_LOCAL_MACHINE\SOFTWARE\Avaya
\Collaboration\<version installed>
2. Type the version in the format: vX.X.X.
3. Set the ParserTimeout value to more than 3 seconds and less than 30 seconds.

Outlook does not display the Join Conference and Host


Conference menu options
Condition
You do not see the Join Conference or Host Conference button when you open an Outlook
meeting invitation.
Cause
The conference bridge number and web conference details are not correctly formatted in the
meeting invitation according to Collaboration Services standards.
Solution
1. Delete the meeting occurrence or series in your Outlook calendar.
2. Ask the meeting organizer to resend the meeting invitation with the conference details
correctly formatted.

September 2016 Administering Avaya Collaboration Services 39


Comments on this document? infodev@avaya.com
Troubleshooting Collaboration Services

Outlook freezes when using the click-to-call feature on an


email signature
Condition
When you click a telephone number on an Outlook signature to make a call with Avaya
Collaboration Services, Outlook freezes for approximately three minutes before the call starts.
Outlook does not freeze when you use click-to-call with a phone number in the body of the email.
Cause
The issue occurs when Instant Messaging Contacts is enabled in Outlook.
Solution
1. In Microsoft Outlook, on the File menu, click the Options tab.
2. In the Outlook Options window, click Mail > Editor Options.
3. In the Editor Options window, click AutoCorrect Options.
4. In the AutoCorrect window, click the Actions tab, and then clear Instant Messaging
Contacts.

Outlook and Avaya Collaboration Services contact cards


show different user capabilities
Condition
Different user capabilities are enabled in the Avaya Collaboration Services contact card and the
Outlook contact card. For example, video might be enabled in the Avaya Collaboration Services
contact card, but disabled in the Outlook contact card.
Cause
The Avaya Collaboration Services contact card uses the information in the UC client to determine
the capabilities for the user. The Outlook contact card uses a different algorithm.
Solution
Workaround is unavailable.

Outlook add-in fails to open .msg files


Condition
After you enable Collaboration Services in Outlook, you can only open copies of saved Outlook
email message (.msg) files once. If you immediately try to reopen the copied email message files,

September 2016 Administering Avaya Collaboration Services 40


Comments on this document? infodev@avaya.com
Other email clients do not support reporting a problem in localized languages

you might receive the following error: Cannot open file. The file may not exist, you
may not have permission to open it, or it may be open in another program.
This limitation does not prevent you from opening email messages directly in Outlook. You can open
email messages in Outlook as many times as you want.
Cause
This issue occurs due to a Microsoft API malfunction.
Solution
Do one of the following:
• Wait for three to five minutes before you try to reopen message files.
• Disable the Collaboration Services Reminder window by setting the HKEY_LOCAL_MACHINE
\SOFTWARE\Avaya\Collaboration\<version> DisableCCEReminderWindow registry
value to 1.
Note:
- You can set the registry value when installing Collaboration Services using the
DISABLECCEREMINDERWINDOW parameter.
- After setting the registry value, you can use the click-to-join conference functionality from
the Collaboration Services Appointment window, but not from the Reminder window.

Other email clients do not support reporting a problem in


localized languages
Condition
You cannot report a problem in localized languages when you use other email clients, except
Outlook. Other email clients such as Hotmail support only the English language. You can report a
problem by using the Report a problem button in the About tab of Avaya Collaboration Services.
Outlook opens an email with the text in the selected language.
Cause
Only the Outlook email client supports localized languages.
Solution
Workaround is unavailable.

September 2016 Administering Avaya Collaboration Services 41


Comments on this document? infodev@avaya.com
Troubleshooting Collaboration Services

Unable to use Outlook IM and Presence functionality from


Collaboration Services
Condition
You cannot use Outlook Presence and IM functionality from Collaboration Services, but only from
the Lync 2010 or 2013 client. This issue occurs when you modify Collaboration Services Presence
and IM setting for Outlook.

Cause
The DefaultIMApp value is incorrectly set.

Solution
1. Close Outlook.
2. Start the registry editor on your computer.
3. Navigate to HKEY_CURRENT_USER > Software > IM Providers.
4. Modify the DefaultIMApp value as appropriate.
• To disable the Collaboration Services Presence and IM functionality and set it to Lync
2010, set the value to Communicator.
• To disable the Collaboration Services Presence and IM functionality and set it to Lync
2013, set the value to Lync.
• To enable the Collaboration Services Presence and IM functionality, set the value to
CollaborationService.
5. Restart Outlook.

Unable to re-enable Avaya Collaboration Services in


Google Chrome
Condition
After removing the Collaboration Services add-in from Google Chrome, the add-in cannot be re-
enabled even after reinstalling Collaboration Services.
Important:
When Avaya one-X® Communicator Windows users upgrade to the latest version of Avaya
Collaboration Services, the users might be unable to see the Avaya Collaboration Services add-
in in Google Chrome.
Cause
Unknown

September 2016 Administering Avaya Collaboration Services 42


Comments on this document? infodev@avaya.com
Unable to close Microsoft Outlook when adding contacts from the global address book

Solution
Do one of the following:
• If you remove the Avaya Collaboration Services add-in from Google Chrome, you must uninstall
and then reinstall the Google Chrome browser.
• If you did not remove the Avaya Collaboration Services add-in from Google Chrome, you must
disable the add-in from Google Chrome instead of removing Avaya Collaboration Services.

Unable to close Microsoft Outlook when adding contacts


from the global address book
Condition
You can add contacts from the global address book to your Microsoft Outlook contacts. But when
you close Outlook after adding the contacts, the system does not close Microsoft Outlook.
Cause
Unknown
Solution
1. Disable the Avaya Collaboration Services Outlook add-on.
2. Close Microsoft Outlook.
3. Restart Microsoft Outlook.
4. Enable the Avaya Collaboration Services Outlook add-on.
Related links
Installing Avaya Collaboration Services on the desktop on page 20

Unable to start a web collaboration session in a Citrix


XenApp environment in Google Chrome
Condition
In a Citrix XenApp environment, the web collaboration link does not open in Google Chrome when
you start the web collaboration session using Collaboration Services from:
• The Avaya Communicator for Microsoft Lync client
• The Outlook Meeting Invitation window
• The Reminder window
The Google Chrome browser opens, but you are not automatically directed to the web collaboration
session as expected.

September 2016 Administering Avaya Collaboration Services 43


Comments on this document? infodev@avaya.com
Troubleshooting Collaboration Services

Cause
Unknwon
Solution
Before starting a web collaboration session from Outlook or Avaya Communicator for Microsoft
Lync, ensure that the Google Chrome browser is open on your computer.

September 2016 Administering Avaya Collaboration Services 44


Comments on this document? infodev@avaya.com
Glossary

Add-in A software component that adds a specific feature to an existing software


application.

Conference The process of conducting a meeting between two or more people through
the use of telecommunication circuits and equipment. For example, audio
conferencing or teleconferencing.

Virtual Desktop A desktop-oriented service that hosts user desktop environments on remote
Infrastructure (VDI) servers.

September 2016 Administering Avaya Collaboration Services 45


Comments on this document? infodev@avaya.com
Index
Special Characters G
.msg files ..............................................................................40 group policy ......................................................................... 31

A H
activating highlight
Microsoft Office suite .................................................... 26 telephone numbers .......................................................31
administration ...................................................................... 30
I
B
installation parameters .........................................................17
blocking installation requirements ......................................................14
websites installing
webpages .............................................................. 31 desktop ......................................................................... 20
browser ................................................................................ 30 multiple machines .........................................................21
installing and uninstalling
virtualized application environment .............................. 22
C interoperability requirements ............................................... 16
configuration
actions L
smart tags ..............................................................23
limitations
Actions and Smart Tags ............................................... 23
D
debug log levels M
setting ........................................................................... 30
documentation ....................................................................... 8 meeting ................................................................................ 37
document changes ................................................................ 7 meeting invitation .................................................................37
meeting template ................................................................. 37
E
N
enabling
Actions ..........................................................................25 new version ..........................................................................29
later ...............................................................................25
Office 2007 suite ...........................................................24
Outlook 2010 and later ................................................. 25
O
Smart Tags ................................................................... 24 options
web browsers ............................................................... 26 installation .....................................................................20
extracting Outlook add-in
exe ................................................................................19 fails ............................................................................... 40
MSI ............................................................................... 19 open ..............................................................................40
outlook freezes .................................................................... 40
F overview
Avaya Collaboration Services .......................................11
features
Avaya Collaboration Services .......................................11
file ........................................................................................ 19
R
remote server .......................................................................21
requirements
VDI ................................................................................14

September 2016 Administering Avaya Collaboration Services 46


Comments on this document? infodev@avaya.com
Index

S
setting
debug log levels ............................................................30
stop ...................................................................................... 31
support .............................................................................9, 29
support matrix
Google .......................................................................... 13
Office 365 ..................................................................... 13

T
terminology ............................................................................ 7
troubleshooting .................................................................... 40

U
unblocking
websites
webpages .............................................................. 31
uninstalling
Windows Control Panel ................................................ 28
Uninstalling
Collaboration Services ..................................................28
upgrading .............................................................................29

V
videos .................................................................................... 8

W
Windows command console ................................................ 28

September 2016 Administering Avaya Collaboration Services 47


Comments on this document? infodev@avaya.com

Das könnte Ihnen auch gefallen