Professional Documents
Culture Documents
2 FP6
(Product version 6.2.6.03-FP6)
GA Release Notes
Issue 1.0
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 generally makes available
to users of its products. 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 Web sites 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 its Hardware and Software (Product(s)). Refer to your sales
agreement to establish the terms of the limited warranty. In addition, Avayas 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 Web site: http://support.avaya.com. Please
note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States
and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya.
License
2
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 End User a license within the scope of the license types described below. 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
End User. 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. Software
means the computer programs in object code, originally licensed by Avaya and ultimately utilized by
End User, whether as stand-alone Products or pre-installed on Hardware. Hardware means the standard
hardware originally sold by Avaya and ultimately utilized by End User.
License type(s)
Named User License (NU). End User may: (i) install and use the Software on a single Designated
Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a
Server so long as only authorized Named Users access and use the Software. Named User, means a user
or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole
discretion, a Named User may be, without limitation, designated by name, corporate function (e.g.,
webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate
function, or a directory entry in the administrative database utilized by the Software that permits one user
to interface with the Software.
Shrinkwrap License (SR). Customer 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). (see Third-party Components for
more information).
Copyright
Except where expressly stated otherwise, no use should be made of materials on this site, the
Documentation, Software, or Hardware provided by Avaya. All content on this site, the documentation
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.
Third-party components
Certain software programs or portions thereof included in the Product may contain software distributed
under third party agreements (Third Party Components), which may contain terms that expand or limit
rights to use certain portions of the Product (Third Party Terms). Information regarding distributed
Linux OS source code (for those Products that have distributed the Linux OS source code), and
3
Identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to
them is available on the Avaya Support Web site: http://support.avaya.com/Copyright.
The open source license text file, OpenSourceLicense.txt, is available in the Licenses folder on the
Avaya one-X Client Enablement Services server: /Licenses/OpenSourceLicense.txt.
"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.
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 Web site:
http://www.avaya.com/support
Trademarks
Avaya, the Avaya logo, Avaya one-X Communicator, Communication Manager, Modular Messaging,
and Conferencing are either registered trademarks or trademarks of Avaya Inc. in the United States of
America and/or other jurisdictions. All non-Avaya trademarks are the property of their respective owners,
and Linux is a registered trademark of Linus Torvalds.
Downloading documents
For the most current versions of documentation, see the Avaya Support Web site:
http://www.avaya.com/support
Avaya provides a telephone number for you to use to report problems or to ask questions about your
product. The support telephone number is 1-800-242-2121 in the United States. For additional support
telephone numbers, see the Avaya Support Web site:
http://www.avaya.com/support
4
Contents
About Avaya one-X Communicator ............................................................................................................ 6
Getting Started.............................................................................................................................................. 6
Downloading the Avaya one-X Communicator Release 6.2 FP6 GA ......................................................... 11
Avaya one-X Communicator client installation requirements.................................................................. 12
Upgrading or Installing Avaya one-X Communicator 6.2 FP6 client ........................................................... 13
Important Notes.......................................................................................................................................... 14
Interoperability ........................................................................................................................................... 16
Caveats and Known issues with Avaya one-X Communicator 6.2 FP6 Release .......................................... 19
Caveats ........................................................................................................................................................ 19
Known Issues............................................................................................................................................... 20
Technical Support ....................................................................................................................................... 21
Appendix A: Acronyms ................................................................................................................................ 23
5
About Avaya one-X Communicator
Avaya one-X Communicator is a rich Unified Communications client that provides enterprise users with
simple, intuitive access to their everyday communications tools. Users can better manage
communications tasks, making them more productive, responsive, and accessible regardless of where
they are working on any given day.
Getting Started
Review these notes prior to installing the one-X Communicator 6.2 FP6 software.
This release has many new features as listed below in addition to defect fixes over the previous release:
As an Avaya one-X Communicator user you now have the ability to set customized ring tones
with the option of including a notification ringtone (single beep) for the following:
Personalized ringing for Incoming Calls
Bridged Call Appearance
Team button
Call Pickup
6
Support 'from-forking' - receiving and presenting messages sent from the same user on
alternate devices
With the latest implementation, if a user logs in with an Avaya Multimedia Messaging (AMM)
client such as Avaya Communicator for Windows as well as Avaya one-X Communicator and
begins a conversation with another user, Messages sent from the user's AMM client will be
visible on Avaya one-X Communicator. If the AMM client leaves the conversation, Avaya one-
X Communicator will display a 'you have left the conversation' message and disable the
controls. This behavior is consistent with AMM. If the user needs to resume the conversation
with the far-end, open a new IM window.
As an Avaya one-X Communicator user you now have the ability to send DTMF tones in the
following new ways:
Paste a number in the main number field and send as DTMF tones
Select a contact number entry and send as DTMF tones
Avaya one-X Communicator now accepts entering DTMF tones through the PC
keyboard even if the Avaya one-X Communicator Dial Pad is hidden. This feature is
supported in This Computer & Shared Control Mode for both H323 & SIP version of
Avaya one-X Communicator.
As an Avaya one-X Communicator User, you are able to transfer files securely through the IM
Chat Window.
As an Avaya One-X Communicator solution administrator, you will be able to manage the
Periodic Polling Interval using the one-X Communicator Admin Tool. The Polling Interval shall
contain a single positive integer, in the range from 5-120. The units represented are minutes.
The Client reduces unnecessary ad hoc queries to the presence server. This feature is disabled
by default & administrator need to refer to the user document about guidelines that need to be
followed when enabling this feature.This will be done through the following algorithm:
Avaya Collaboration Services Presence Queries for existing favorites will be retrieved
from the current buddy list No Adhoc Presence Query to be sent.
If the Presence Query is for a non-favorite, then the presentity should be queried from
the periodic polling list. (The data may already exist locally).
7
Returning Federated Presence of Buddies
Avaya one-X Communicator and Microsoft Outlook users are now able to see the Presence of
and send IM to Federated Favorites in any email if contact is in the to, from or cc fields. You
can make a call or send an IM to federated buddy.
As an Avaya one-X Communicator user you now have the ability to change the audio path
modes (This Computer/Desk Phone/Other Phone) from the Avaya one-X Communicator Login
screen, instead of having to go through settings screen. The behavior on the Login Screen
mimics the behavior presented through the Settings->Out Going Calls Tab.
Avaya one-X Communicator users can now uses a click to fax and click to sms feature using an
sms/fax gateway address administered through Avaya one-X Communicator Centralized Admin
tool. (An SMS/Fax gateway needs to be available and properly configured)
If a contact card (in Search Results, My Contacts, Favorites) has an administered SMS/FAX
number, then the Email Icon will show a drop down (similar to the Phone Icon with multiple
Numbers) through which the user is able to click on the desired number and launch the Email
Client & compose a message to the appropriate SMS/FAX recipient.
Additionally, you will be able to launch and send a FAX message, if a FAX Number has been
administered in PPM or CES, in the following scenarios:
CES name lookup (contacts search)
CES contacts (FAV, VIP)
PPM private contacts
Mark and Delete multiple entries (Contacts/Call Log entries) at the Same Time Using Right
Click Menu in List
Avaya one-X Communicator users are able to mark and delete multiple entries in Call Log or
Contacts using the left click menu. The user is now given a "Delete Selected" option on the left-
click menu in the list when more than one item in the list is selected. This is provided for both
call log and contact lists.
SIP Presence enhancement for users (Contacts, Buddy Management) not in your enterprise
8
With this enhancement Avaya one-X Communicator will display appropriate Presence Status of
Contacts added from a PPM or an LDAP Lookup. A user could also manually add a contact with a
valid IM Address. Contact Lookup could be an Aura user or a Federated User with a valid IM
Address configured in LDAP or PPM.
With this feature enhancement Avaya one-X Communicator users will now be able add a
contact containing # as part of any telephone number. This is possible as the first part of the
number or at any other location.
Single Call Log Entries for one call if it was answered over EC500
If an Avaya one-X Communicator user answered an incoming call on the Mobile Device
(EC500), the call log shows a single entry for the "Answered Call".
Call initiated over AD Search shows the Name on the Call appearance and Call Log
This feature enhancement addresses name resolution for outgoing calls initiated from LDAP
search. Resolution shall be performed in the following preference order i.e. Local Contacts-(My
Contacts (PPM-SIP, Local-H323)), Outlook, LDAP, and Network. This feature has no interaction
with CES Name Look-ups, or CES Call Logs.
Avaya one-X Communicator users will now be able to see Presence status on Search results on
name-lookups that Avaya one-X Communicator supports, in particular LDAP and CES with some
architectural changes in signaling which are intended to reduce load on the Avaya Presence
Server and enabled increased server capacity.
Avaya one-X Communicator SIP will now be able to discover the Presence Server address
through PS Communication Profile administered in User profile page of System Manager
without configuring it in manually. With to this Implementation, Avaya one-X Communicator
will get seamless presence updates through PS restarts and failures.
9
Notification for New Instant Messages
With the latest implementation Avaya one-X Communicator users will see a pop up toast when
the IM window is not in focus. The IM notification allows the user to either ignore or look into
IM details. It will automatically disappear if the user does not click on it after few seconds or if
the user clicks on the X button to dismiss toast. If Do Not Disturb is set, the Notification pop up
is not shown.
Interaction between SIP/H.323 Offline Call Journaling and preserving Name Resolution
With this enhancement Avaya one-X Communicator provides name resolution for Offline
contacts.
Avaya one-X Communicator in SIP mode, on downloading call logs from SM/PPM will replace
all attributes with the exception of the Name Attribute that is in the local call record.
Avaya one-X Communicator H323 mode, when operating with the Offline call journaling
feature enabled, performs Name Resolution based on Local Contacts and MS Outlook contacts
for all calls generated by Avaya one-X Communicator and missed call records received from
CM.
Avaya one-X Communicator users in a call pickup group now get a visual notification for an
incoming call to any member of the pick-up group similar to one that is displayed on an
incoming call. This pop up contains the Name/Number of caller and person who was called
initially. The user is able to take the call by simply clicking on the Accept button.
Ad-Hoc presence requests must not be sent by default for non-buddy contacts in Outlook
Due to solution limitations with presence server and Avaya one-X Communicator, Avaya one-
X Communicator does not by default send ad-hoc presence requests for non-buddies
appearing in Outlook email. This is configured through the Centralized Admin Tool through
Admin Parameter Enable Outlook Presence for Non-Favorite Contacts with three options Not
set, False & True
If it set to
Not set -> Avaya one-X Communicator will drop all the requests from CCE for non-buddy
contacts and returns Unknown presence back to CCE.
False -> Avaya one-X Communicator will drop all the requests from CCE for non-buddy contacts
and returns Unknown presence back to CCE.
10
True -> Avaya one-X Communicator will process all the requests from CCE for non-buddy
contacts and sends Ad hoc subscription to PS.
The one-X Communicator install suite contains following packages and allows users to choose
application(s) they want to install on their machines -
11
Avaya one-X Communicator client installation requirements
Hardware requirements Users must have the following minimum hardware configuration to be able
to install and run one-X Communicator application properly -
12
Installation pre-requisites
It is recommended that users update their operating systems with the latest updates before
installing one-X Communicator.
It is recommended that users stay connected to the internet when installing one-X
Communicator client, so that required software / pre-requisites can be downloaded and
installed without interrupting the installation, if these are not available on the machines prior to
installing one-X Communicator.
If you are using proxy server to access internet and use automatic proxy detection or automatic
configuration script, installer would not be able to access the internet to download the pre-
requisites. In this case, it is recommended that you download and install .NET 4 framework prior
to one-X Communicator installation. This framework is available at -
http://www.microsoft.com/en-us/download/details.aspx?id=17718
Close applications like Microsoft Internet Explorer, Google Chrome, Microsoft Outlook or Lotus
Notes before installing or upgrading to the one-X Communicator 6.2 FP6 client.
Existing installations of one-X Communicator on release 6.1 SP8 , 6.1 SP9 , 6.2 GA, 6.2 SP1 ,6.2 SP2, 6.2
FP3, 6.2 FP4 or 6.2 SP5 can be directly upgraded to Avaya one-X Communicator 6.2 FP6 release using
the one-X Communicator 6.2 FP6 install suite.
New installations of one-X Communicator 6.2 FP6 can be done on the operating systems listed in
interoperability section in this document.
For further information please refer to the Avaya one-X Communicator 6.2 FP6 guides available on
Support site.
13
Important Notes
Video SRTP configuration on one-X Communicator client: By default, Avaya one-X Communicator 6.2
release onwards has Video SRTP enabled on Best Effort basis, so no need to update any configuration to
support this feature. Video would be SRTP enabled only when TLS is selected for login over SIP This
Computer mode.
ENFORCE_SIPS_URI = 1
SDPCAPNEG = 1
MEDIAENCRYPTION = 1,2,9
It is recommended to keep SRTP settings on Best Effort on the Aura components as well like
Communication Manager, Session Border Controller, Avaya Aura Conferencing and also on other clients
and endpoints.
Video SRTP is supported only in SIP This Computer mode in environment having Avaya Aura 6.2 FP3 or
later / AAC 7.2 FP2 or later. With Avaya Aura 6.2 FP2, video would be supported on RTP only.
Table below shows audio and video support over SRTP or RTP for different user types and login modes -
14
SIP Shared Control:
Make sure, the parameter SET ENABLE_PPM_SOURCED_SIPPROXYSRVR is always set to 1 in
46xxsettings file for all 96x1 SIP phones to allow successful login.
Also, make sure to have the server IPs (primary and secondary) listed in same order on both Avaya one-
X Communicator and 96x1 SIP desk phone for successful login and working of Avaya one-X
Communicator in SC mode.
If you are using proxy server to access internet and use automatic proxy detection or automatic
configuration script, installer would not be able to access the internet to download the pre-requisites. In
this case, it is recommended that you download and install .NET 4 framework prior to one-X
Communicator installation. This framework is available at - http://www.microsoft.com/en-
us/download/details.aspx?id=17718
For further information please refer to the Avaya one-X Communicator 6.2 guides available on Support
site.
Avaya one-X Communicator Login / PPM download with Avaya Aura Session Manager 6.2 FP4:
With SM 6.2 FP4 new installations, the "demo" certificates will no longer be installed by default. This
does not affect SM upgrades, as all existing certificates are preserved through the upgrade process.
All new installs will by default use SIP and HTTP certificates signed by System Manager. Careful planning
should be done to ensure all far end devices are similarly equipped with System Manger signed
certificates. Otherwise, existing TLS connections will no longer function.
For connecting Avaya one-X Communicator 6.2 FP6 with Session Manager 6.2 FP4 new install, please
ensure that either SMGR MGMT certificate is installed and trusted by Avaya one-X Communicator
users (client) machine or the demo certificate is installed on SM.
Using the SM command line, initTM is available to install the "demo" certificates in either of the
following ways:
# initTM d
OR
# initTM demo
15
Note: to assist in viewing certificate status, new information has been added to the status available on
System Manager under: Home / Elements / Session Manager / System Status / Security Module Status.
Interoperability
Following is the list of systems supported by Avaya one-X Communicator release 6.2 FP6:
Avaya Aura Communication 5.2.1, 6.2, 6.3 (AA 6.2 FP2), 6.3.2 (AA 6.2 FP3), 6.3.6 (AA 6.2
Manager FP4) ,6.3.8
Avaya Aura Session Manager 6.3, 6.3.2 (AA 6.2 FP2), 6.3.4 (AA 6.2 FP3), 6.3.8 (AA 6.2 FP4),
6.3.9
Avaya Aura System Manager 6.3, 6.3.2 (AA 6.2 FP2), 6.3.4 (AA 6.2 FP3), 6.3.8 (AA 6.2 FP4),
6.3.9, 6.3.10
Avaya Aura Conferencing 7.0, 7.2, 7.2.2 (7.2 FP2), 8.0 , 8.0.3
Avaya Aura Presence Services 6.2 (AA 6.2 FP2), 6.2.2 (AA 6.2 FP3), 6.2.4 (AA 6.2 FP4)
16
Avaya one-X Mobile SIP iOS 6.2.3(FP)
Avaya IP Desk phones H.323 Phones 96xx, 96x1 (6.3, 6.3.1 , 6.4, 6.5, 6.6)
Operating Systems (32 / 64 bits) Microsoft Windows 7 Enterprise, Ultimate and Professional
17
Microsoft Office 2007, 2010, 2013
365
Google Chrome 41
Mozilla Firefox 37
Cameras HD Cameras
Creative Live! Cam Socialize HD Web Cam
LifeCam Webcam Cinema
Logitech Webcam C905
Non-HD Cameras-
Creative Live! Cam Notebook Pro Webcam
Logitech QuickCam Messenger, Webcam Pro 5000,
Webcam Pro 9000
1. Avaya Collaboration Services 6.5.3.2 when installed with Avaya one-X Communicator 6.2 FP6 will
support interoperability with following 3rd party components
365
18
Browsers Microsoft Internet Explorer (IE) 8, 9, 10, 11
Google Chrome 41
Mozilla Firefox 37
2. Avaya one-X Communicator does not directly interop with Avaya Multimedia Messaging (AMM)
2.0/2.1. It supports AMM when used as an Avaya Aura Presence Services instant messaging client.
This support is available only when AMM is deployed with Avaya Aura Presence Services 6.2.4 (AA
6.2 FP4).
Caveats and Known issues with Avaya one-X Communicator 6.2 FP6 Release
Caveats
Avaya one-X Communicator 6.2 FP6 GA Build has following caveats
ONEXC-10292 AutoDial Feature button is not supported with Avaya one-X None.
Communicator-SIP
NA Terminal Services and RDP (Remote Desktop) are not None
supported. When using Avaya one-X Communicator over an
RDP (Remote Desktop) connection, audio and video devices
may not be available, listed with correct names or not
working properly, depending on specific machine
configuration
NA Avaya one-X Communicator does not support ad-hoc IM None
conference (Group chat/Multi-User chat) session with
multiple OCS (Office Communications Server) users. Only
point-to-point IM chat can be successful between Avaya one-
X Communicator and OCS (Office Communications Server)
users.
ONEXC-8967 / Avaya one-X Communicator doesnt Support re-start video Re-initiate the call if you want to
ONEXC-8276 on an active call once video is stopped by the user. establish the video again on the
call.
ONEXC-10034 Team Button functionality is currently not supported in SIP None.
/ ONEXC-4515 Other Phone mode.
19
Known Issues
List of other open issues on Avaya one-X Communicator 6.2 FP6 and since 6.2 GA release;
ONEXC-5270 Avaya one-X Communicator SIP Shared Control It is recommended to have the server IPs
mode Login issues if Avaya one-X Communicator (primary and secondary) listed in same
and desk phone server IPs not listed in same order. order on both Avaya one-X
Communicator and desk phone.
Dialing Rules
ONEXC-11649 Outside Line Access Code is not added, when number None
starts with the same digit as the prefix
Call Handling
Call Logs
ONEXC-11785 Two call log entries observed for 1XC H323 RW mode None
user when an incoming alerting call is answered
immediately after login if Offline call Journaling is
enabled.
ONEXC-11717 Call Log does not suppress dialed PIN Codes for None
private calls if you use the "Enter name or number"
Field in Avaya one-X Communicator to dial out
Presence and IM
ONEXC-11781 Failed to initiate IM message from PPM search result. Search from LDAP & Send IM.
ONEXC-8081 When entering Sleep or Hibernation, Presence does Logoff or manually change the Presence
not update to Offline. to Offline before entering Sleep or
Hibernation.
Contacts
ADCE-2771 CCE browser contact card is not returned for parent None
20
/ADCE-2769 AD domain/ AD contact
CES Integration
ONEXC-8326 Bridge Conferencing (with MX) window of Avaya one- See call duration value on the call
X Communicator might show incorrect call duration appearance display on main Avaya one-
at times. X Communicator UI for actual duration.
ONEXC-8710 Avaya one-X Communicator SIP mode - Presence Presence will be reset in an hour for that
status not updated after failover, if user was on active user automatically.
call during SM failover.
Technical Support
Support for Avaya One-X Communicator Client is available through the normal Avaya escalation
process. If you encounter trouble with the clients:
1. Retry the action. Follow the instructions in written or online documentation carefully.
2. Check the documentation that came with your hardware for maintenance or hardware-related
problems.
3. Note the sequence of events that led to the problem and the exact messages displayed. Have
the Avaya documentation available.
Configuration settings.
Usage scenario, including all steps required to reproduce the issue.
Screenshots.
Copies of all logs related to the issue.
All other information that you gathered when you attempted to resolve the issue.
21
22
Appendix A: Acronyms
MM Modular Messaging
MX Meeting Exchange
MGMT Management
23