Avaya Communicator for Windows Release 2.1.3
(Product version – 2.1.3.80)
GA Release Notes
Issue 1.3
18 January, 2016
© 2016 Avaya Inc. All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume
no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases.
Documentation disclaimer
Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications,
additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's gents, 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 the Customer or End User.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not
necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we
have no control over the availability of the linked pages.
Warranty
Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s
standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Website:
http://www.avaya.com/support
License
USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS
AVAILABLE ON THE AVAYA WEB SITE http://support.avaya.com/LicenseInfo/ ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE
TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. 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 standalone 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 Products, originally sold by Avaya and ultimately utilized by End User.
License type(s)
Named User License (NU). Customer 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 Product that permits one user to interface with the Product.
Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in
accordance with the terms and conditions of the applicable license agreements, such as "shrinkwrap" or "click wrap" license accompanying or applicable to the
Software ("Shrinkwrap License"). The text of the Shrinkwrap License will be available from Avaya upon End User’s request (see “Third-party Components" for
more information).
Copyright
Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use 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 identifying Third
Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site:
http://support.avaya.com/ThirdPartyLicense/
Preventing toll fraud
"Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee,
agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll
fraud occurs, it can result in substantial additional charges for your telecommunications services.
Avaya fraud intervention
If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention
Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site:
http://www.avaya.com/support
Trademarks
Avaya, the Avaya logo, and COMPAS are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All
other trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support Web site: http://www.avaya.com/support
2
Avaya 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
3
Contents
Contents
Document Overview ............................................................................................................................................................................ 5
What’s New .......................................................................................................................................................................................... 5
Inherited from previous release (Avaya Communicator for Windows 2.1.3) ...................................................................................... 5
Obtaining Avaya Communicator for Windows Release 2.1.3 Software ............................................................................................... 7
Installation Pre-requisites .................................................................................................................................................................... 8
Upgrading or Installing Avaya Communicator Release 2.1.3 ............................................................................................................... 8
Important Notes ................................................................................................................................................................................... 8
SRTP.................................................................................................................................................................................................. 8
SBC Support ...................................................................................................................................................................................... 9
Interoperability Support ...................................................................................................................................................................... 9
Client Work Station recommendation ............................................................................................................................................... 11
Security Considerations – Certificate Requirements ......................................................................................................................... 11
SIP Endpoint Provisioning .................................................................................................................................................................. 11
Avaya Communicator for Windows - Release 2.1.3 – Caveats/ Known issues .................................................................................. 12
Caveats ........................................................................................................................................................................................... 12
Known Issues and Limitations ........................................................................................................................................................ 13
Technical Support .............................................................................................................................................................................. 13
Abbreviations ..................................................................................................................................................................................... 14
4
Document Overview
This release letter is intended to inform all end users and system administrators of Avaya Communicator for Windows release
2.1.3 about its content, system requirements and any known caveats / known issue.
What’s New
Added support for Aura 7.0, Windows 10, and Office 2016
Avaya Communicator for Windows 2.1.3 resolves the following issues:
•
FW-5498 c crashed while it is shutting down and cannot not launch after that
•
FW-5538 Avaya Communicator for Windows crash when user logged-out and logged -in 2~3 time after SM Failover
•
FW-5611 MDA: AC Win client unrecoverable error reported when user logs in AC Win (no messaging server configured)
while already logged in AC iPad and 9641 SIP
•
FW-6499 MDA- Bridge line appearance on AC Windows greyed out if client which answers the call keep the call on hold
•
FW-7115 Unable to add contact when config server is configured unsecure mode - http (Volkswagen AG)
•
FW-7118 CFD: Unable to merge the calls - AVAYA GMBH
•
FW-7128 Danish language issues
•
FW-7130 Provide necessary support for Windows 10
•
FW-7137 On the Avaya Communicator for Windows in the collaboration window does not pop up when ACR is being
added to the call (AVAYA - APS)
•
FW-7162 (Office 2016) Join meeting icon is disabled when opening a meeting request
•
FW-7167 Propagation to Avaya Communicator for Windows SP3: CFD: 1XC not sending proper NOTIFY in 3PCC mode
(CLEVELAND CLINIC)
•
FW-7172 CFD: Duplicated call log entries when the call is answered on the hardphone (GUYER Y REGULES)
•
FW-7175 Propagation to Avaya Communicator for Windows 2.1.3 : update CURL lib to allow ME support TLS of version
1.1 and 1.2 for https connections
•
FW-7185 [Aura 7.0 Specific] Presence status doesn't display for searched enterprise contacts.
•
FW-7200 update CCE 6.6.3 build #7
•
FW-7201 AC Web client lose CTI control of S IP station after making the first call, if the SIP station is signed on by soft
client (Avaya Communicator for Windows administered as 9641SIP station type)
Inherited from previous release (Avaya Communicator for Windows 2.1.3)
Below features from previous releases are inherited in the new release:
5
o
Support for Avaya Multimedia Messaging 2.1
o
Collaboration Services Desktop Integration Support
–
Click to Dial Enhancement: TelURI, CallToURI handling
–
IM & Presence support
o
Instant Messages to contact from Search Results
o
Presence Enhancement
–
Manual & Automatic Away presence
–
Do not disturb
–
Presence from Enterprise Search Results
o
Show LDAP Display Name value in search results
o
Support for Avaya Aura Session Manager Failover-Simultaneous registration
o
Loading pictures from LDAP
o
USB Audio Device Controls:
o
–
Mute / Unmute, Answer / Hang-up
–
Jabra, Plantronics, Sennheiser and VXI supported with vendor provided software
Configuration
–
Service configuration
–
Dialing rules
–
Contact preference
o
Login/logout
o
Contact fan
o
o
–
Local Outlook contacts
–
Aura contacts
–
Aggregated Contact
–
Remove/Delete PPM Contacts
–
Index, scrolling
–
Live contact filtering
Make call/drag and drop
–
Make call (Audio or Video) from contact card: primary/select a number
–
Make call (Audio or Video) by dragging and dropping a contact onto the conversation 'setup' area
–
Receive call (Audio or Video)
–
Dial pad
–
Make call (Audio or Video) from History and IM card
Mid call control
–
Mute/Unmute
–
Pause/Unpause
–
Hold/Resume
–
DTMF
o
Escalate / De-escalate from a point to point audio call to a point to point video call
o
Multiple Call sessions
– Allows up to 3 concurrent call sessions
o
Local call history
o
Basic Call History Filtering based on Call types (Incoming, Outgoing, Missed, and All)
o
IM and Presence
o
LDAP Search
o
Conference (Audio + Video)
o
6
–
Adhoc Conference / Call Merging, Meet-me Conference
–
Moderator controls
–
Active talker
–
Escalate / De-escalate a conferencing session from voice to video
–
Mid call controls in audio/video conference
Collaboration
–
Document sharing, Screen sharing for the entire screen and a portion of the screen), Application sharing,
Whiteboard sharing
–
Share previous document
–
Delegate Moderator starting collaboration.
–
Escalate point to point audio/video call to a conference via Collaboration button
–
Escalate multiparty IM to audio ad-hoc conference call
o
Combined container for Collaboration and Video Conferencing
o
Message Waiting Indicator integration
o
Desktop Integration (Collaboration Services)
o
Enhancements to server certificate validation(Required)
–
Avaya Communicator validates the server identity certificate during the TLS connection establishment process.
If the application cannot establish a TLS connection because of an inability of the personal computer to
validate the certificate, the application displays an error message.
o
Web Collaboration - Launch Collaboration from the pop-up notification informing you that Collaboration has started.
o
Scopia 8.3 Integration
–
Scopia MCU Conferencing support [Support limited to direct dialing. No VIVR support]
–
Auto configuration via URL (User configuration settings provisioning)
–
A URL is populated in the user's registry file that points to the location of the user's settings file for
autoconfiguration. If there is no URL, the client will launch as normal without using the URL. If there is an error
in loading the parameters, the client launches as before with no user settings populated.
–
Selecting call from alternate numbers
o
Main window resize
o
Volume Control
o
Call Statistics
o
Keyboard shortcuts
o
Contact Fan Robustness
o
Dual Registration (H.323 and SIP)
o
Basic Multiple Device Access
o
New User Interface - Compact UI replaces immersive “spotlight” UI
o
Multi-stream Continuous Presence video with grid layout - Up to 4 streams
o
Secure Media (SRTP) for Video
o
Point-to-Point Audio and Video conference calls on SRTP
o
Consultative audio Call Transfer.
o
Contact Filtering by Source
o
Windows 8 & 8.1 Support (Desktop Mode with mouse/keyboard)
o
Multi-party Messaging
o
Language Selection in Settings
Obtaining Avaya Communicator for Windows Release 2.1.3 Software
Users can download the Avaya Communicator for Windows 2.1.3 installer from https://plds.avaya.com .
PLDS ID: TBD
File
Name:
“communicatorwin-2.1.3.80-dist.zip”
Follow below steps:
7
1.
After logging in to the PLDS site, click Downloads.
2.
To search for downloads; you must first select a company. Either type the company name in the field shown on the
web page or use the Find icon to search for and select the company.
3.
After selecting the company, click Apply Company.
4.
Enter the PLDS ID under “Download Pub ID” field and click on “Search downloads”.
5.
Click the download link to download the “Avaya Communicator for Windows 2.1.3” software.
Installation Pre-requisites

It is recommended that users update their operating systems with the latest updates before installing Avaya
Communicator for Windows.

It is recommended that users stay connected to the internet when installing Avaya Communicator for Windows 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 Avaya Communicator for Windows.

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, you must download and
install .NET 4 frameworks prior to Avaya Communicator for Windows installation on the system. This framework is
available at - http://www.microsoft.com/en-us/download/details.aspx?id=17718

It is recommended to upgrade the Java Runtime Engine & Flash player on the PC to the latest version.
Upgrading or Installing Avaya Communicator Release 2.1.3
Existing installations of Avaya Communicator for windows releases: 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2 can be directly upgraded to
Avaya Communicator 2.1.3 using the Avaya Communicator for windows installer (i.e.’ Avaya-Communicator-2.1.3.80.msi’).
New installations of Avaya Communicator for Windows 2.1.3 can be done on the operating systems listed ‘Interoperability
Support’ in this document.
For further information refer to the Avaya Communicator for Windows 2.1.3 guides available on Support site.
See below instructions for finding documents on the Avaya support site.
1.
Navigate to the Avaya Support web site at http://support.avaya.com/
2.
Click the Downloads & Documents tab, and select Documents.
3.
In the Product search box, enter the product name.
4.
Select the appropriate release number from the Choose Release drop-down menu.
If necessary, use the Content Type filter on the left to select the type of document you are looking for. For example, if you are
looking for user guides, you can select User Guides from the Content Type filter. Only documents in the selected category will
appear in the list of documents.
Note:
•
Users must install Collaboration Services package separately, as the Avaya Communicator for Windows installer does
not install Collaboration Services automatically.
•
Installations of Collaboration Services can be done using ‘CCE-6.6.3.7-installer.exe’ included in the Avaya communicator
for Windows zip file.
Important Notes
SRTP
Default settings on Avaya Communicator for Windows client 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 Avaya Aura Communication
Manager, Avaya Aura Session Border Controller, and Avaya Aura Conferencing and also on other clients and endpoints.
8
SBC Support
If you intend to log in to Avaya Communicator for Windows using Avaya Session Border Controller, configure the Avaya Session
Border Controller address or domain name for the Phone Server Address, Directory Server Address, and Presence Server
Address in the Avaya Communicator Settings. The same domain names can be used for these settings when Avaya
Communicator is inside or outside the enterprise network. Through Session Border Controllers, the DNS servers can resolve the
correct IP addresses from the same domain name in these two networks.
Interoperability Support
The following table shows the supported systems with Avaya Communicator for Windows 2.1.3
Product
Version
96x0 H.323 3.2
9600 Series IP Desk phones
96x0 SIP 2.6.13
96x1 H.323 6.4
96x1 SIP 6.4,6.5
Avaya Aura® Application Enablement Services
6.2, 6.3.8
Avaya Aura® Communication Manager
6.3, 6.3.2 (AA 6.2 FP3), 6.3.6 (AA 6.2 FP4), 6.3.8, 6.3 Security
Service Pack 6, 7.0
Avaya Aura® Communication Manager Messaging
6.3
Avaya Aura® Conferencing
6.0, 7.0, 7.2, 7.2.2, 8.0
Avaya Aura® Messaging
6.2, 6.3.1,6.3.2
Avaya Modular Messaging
5.2
Avaya Aura® Presence Services
6.2, 6.2.2(AA 6.2 FP3), 6.2.4(AA 6.2 FP4), 7.0
Avaya Aura® Session Manager
6.3, 6.3.4 (AA 6.2 FP3),
6.3.8 (AA 6.2 FP4),6,3.9, 7.0
Avaya Aura® Session Border Controller for Enterprise
6.2.100, 6.3
Avaya Aura® Solution for Midsize Enterprise
6.2,6.3.10
6.3.2 (AA 6.2 FP2),
Avaya Aura® System Manager
6.3.4 (AA 6.2 FP3),
6.3.8 (AA 6.2 FP4),6.3.10
7.0
Avaya Multimedia Messaging
2.0, 2.1
Meeting Exchange
6.2
Scopia Solution
8.3,8.3.1(FP)
Note:
•
Transferring 2 Point to Point audio calls requires Avaya Aura 6.2 FP2 or greater environment.
•
Point to Point video calling/conferencing requires Avaya Aura 6.2 FP2 or greater environment.
•
Secure Video with Point to Point or Conferencing calls requires Avaya Aura 6.2 FP3 or greater environment.
•
Secure AAC Video Conferencing requires AAC 7.2.2 or greater environment.
The following table shows the supported interoperable endpoints with Avaya Communicator for Windows 2.1.3.
Avaya Components
Supported Release
Avaya Client Applications
6.3 SP2
9
Avaya Communicator Android
2.0,2.1
Avaya Communicator for iPad
2.0
Avaya Communicator for iPhone
2.1
Avaya one-X® Communicator
6.2,6.2.5, 6.2.7, 6.2.10
Avaya one-X® Communicator for Mac OS
2.0.4
Avaya one-X® Mobile SIP for iOS
6.2.7
B100 Series Conference Phones - B179
2.3, 2.4
One-X Mobile UC with CES
6.2.4
The following table shows supported non-Avaya products with Avaya Communicator for Windows 2.1.3.
rd
3 Party Components
Software / Hardware
Supported Release / Model
LDAP
Microsoft Active Directory
Windows Server 2008 R2
Windows 2013
IBM Domino
8.5.3
Novell
8.8 SP8
Web Browser {Collaboration
Services Support}
Microsoft Internet Explorer
8.0, 9.0, 10,11
Google Chrome
24+
Microsoft windows
Windows 7 (x64, x86)
Professional, Enterprise, Ultimate Editions
Windows 8 (x64, x86)
Professional, Enterprise
Windows 8.1 (x64, x86)
Professional, Enterprise
Windows 10
Professional, Enterprise
Microsoft Lync
Lync
2010, 2013
Microsoft applications
Office
2007, 2010, 2013, 2016
{Collaboration Services
Outlook
2007, 2010, 2013
Other Applications
Office 365
Other Applications
Google Apps & enterprise Applications
Outlook
2007, 2010, 2013
HDX 7K Series
3.1.0-23277
RMX 2000
7.8
Scopia Solution
8.3
Support}
Other Applications
{Collaboration Services
Support}
Microsoft applications
{Local contacts for windows}
Polycom
Radvision
10
Client Work Station recommendation
Security Considerations – Certificate Requirements
As we evolve our portfolio of Unified Communications clients, Avaya is enhancing the security of its products including how
digital certificates are managed. Avaya Communicator for Windows introduces mandatory certificate validation for all TLS
connections.
Before you deploy Avaya Communicator for Windows you will need to determine whether the servers in your unified
communications infrastructure use certificates signed by a certificate authority that is trusted in the Windows operating system.
If your servers are using trusted certificates no further action is required
In order to establish TLS data connections Avaya Communicator for Windows requires a security certificate for each server that
it will be connecting to. In R2.1.3 the list of servers that should be considered (depending on your specific deployment
configuration) is:
•
Session Manager (SM)
•
Session Border Controller (SBC)
•
HTTP server used to host the settings file for service discovery
For more detail on specific provisioning and deployment considerations please consult the product documentation provided to
you by the Global Markets Introduction prime;
•
Administering Avaya Communicator for Windows
•
Using Avaya Communicator for Windows
•
Avaya Communicator for Windows Quick Reference Guide
SIP Endpoint Provisioning
Avaya Communicator for Windows Release 2.1.3 supports SIP endpoints only. The extension shall be provisioned as a SIP soft
client. For more information, see “Administering Avaya Communicator for Android, iPad, iPhone, and Windows”.
Admins should ensure:
On Avaya Aura System Manager:
11
•
SMGR Template is provided (for example, DEFAULT_9641SIP_CM_6_2)
•
IP Softphone is enabled
•
IP Video Softphone is enabled
•
CM-ES is in the originating and terminating application sequence
•
Set Type is set to SIP (for example, 9641SIP)
•
Bridge Call Alerting should be set to “Y”
•
8 call appearance required for scenarios related to Point-to-Point call merging
•
For the endpoint, conferencing profile should be configured on SMGR. This is required for using experience features
On Avaya Communication Manager:
•
For the Communication Manager signaling group associated with Avaya Session Manager, set Initial IP-IP Direct Media
to “Y”
•
Set the value of “Trunk group to SM” in field "Proxy Set Rte Pat"; available in Locations on CM
•
"SIP Endpoint Managed Transfer?" field in “system-parameters features” in CM should be set to "Y"
•
“Enforce SIPS URI for SRTP?” field on “change signaling-group” in CM should be set to “Y”
•
To support the secure calls, “Initial INVITE with SDP for secure calls?” field in “system-parameters features” and “Media
Encryption Over IP?” field in “system-parameters customer-options” should be set to "Y"
•
For the System Parameters, set “Override ip-codec-set for SIP direct-media connections” to “N”
On Avaya Aura Conferencing:
•
Video should be enabled for AAC conference user at AAC provisioning client
•
Deselect Encrypt RTCP parameter in Security -> SRTP settings of AAC. This is required to maintain SRTP on a conference
call. When this parameter is selected, the SRTP call becomes an RTP call when the moderator adds participants into the
conference.
Avaya Communicator for Windows - Release 2.1.3 – Caveats/ Known issues
Caveats
Avaya Communicator for Windows 2.1.3 release has following caveats
Key
Summary
Workaround / Notes
FW-7160
(Win 10) Timing issue with desktop sharing. It takes around 2-3 mins
to share entire screen.
None
SCAE-3665 /
FW-5437
Call logs for AAC Conference calls are not supported.
None
FW-2896
Presence feature does not work if Presence server address is set to
an FQDN instead of an IP address.
Set the Presence server IP address in
place of FQDN.
No fix planned, works as designed.
FW-2844
Avaya Communicator for Windows does not preserve the chat
conversation in the IM history.
None
UCAPPSSE-591
High bandwidth connections are required for use of video
functionality. On lower bandwidth networks, including slower VPN
connections; video users may experience disconnection of client, no
video or disabled functionality.
Workaround is to disable video via
settings -> video configuration tab or
connect via high speed connection to
your corporate network.
12
SCAE-5458
RV MCU 5110 – Avaya Communicator for Windows does not have
video after joining a SCOPIA meeting if SRTP is set to Enforce on CM
The SRTP capneg is not part of the Elite
5000 solution 8.3.Therefore, some
SRTP flows will not work by design with
Aura.
No fix planned, works as designed.
Known Issues and Limitations
Below are known issues on Avaya Communicator for Windows 2.1.3 with resolution or workaround as applicable
Key
Summary
Workaround
FW-4274
Presence status doesn't update/display for some of the newly
added contacts in contact lists
User to logout and log in again
FW-4484
For Domino LDAP, contact pictures from LDAP are not getting
displayed in Enterprise search and even after adding the contact
as PPM contacts
None
SCAE-4424
Avaya Communicator for Windows shows Grey Video Setting
Window after resuming from Sleep mode.
Close video settings window and open it
again.
SCAE-5513
Camera still acquired (Light ON) when video conference put on
hold to make an audio-only point-to-point call.
De-escalate video manually.
FW-5378
[MDA] After bridging and escalating to video call, video button of
Do not use video in bridging cases
Avaya Communicator for Windows was disabled (grey out)
FW-3849
If moderator is on a non-English Operating System, AAC
announcements do not play in that language.
None
FW-5646
Video of Avaya Communicator for Windows hosted conference
stopped to transmit after 15 minutes being in ad hoc video
conference
Disable VideoAuditTimer on AAC
configuration (VideoAuditTimer=0)
FW-5539
In split horizon environment, after switching from inside
corporate network to outside SBC network, loading PPM contacts
might take long time to load.
None
FW-5096
Avaya Communicator for Windows does not support failover to
BSM.
None
FW-7209
[Aura7.0] Video call is active on Avaya Communicator for
Windows, when other MDA (Avaya Communicator for iPad)
bridge in the call, Avaya Communicator for Windows drops out
and shows Bridge Appearance. Audio is also not available in call
once A2 bridged in.
None
Avaya Communicator for Windows crashed while it is shutting
down on Windows 10
None
PSTN participant got dropped from ad-hoc conference, when
moderator merged 2 P2P calls or escalated P2P call to Conference
via Collaboration
None
FW-7198
FW-7182
It will be fixed by CM-10261CM10261CM-10261
Intermittent issue
Related tickets: AAC-11015, ASM-53737
Technical Support
Support for Avaya Communicator for Windows Client is available through the normal Avaya escalation process. If you encounter
trouble with the clients:
1.
13
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.
Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation
available.
3.
If you continue to have a problem, submit a trouble ticket to Avaya.
When you request technical support, provide the following information:
•
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.
Abbreviations
1XM
: Avaya one-X® Mobile
1XC
: Avaya one-X® Communicator
CM
: Avaya Aura® Communication Manager
SM
: Avaya Aura® Session Manager
SMGR
: Avaya Aura® System Manager
AAC
: Avaya Aura® Conferencing
ACA
: Avaya Communicator for Android
AMM
: Avaya Multimedia Messaging
Avaya SBCE : Avaya Session Border Controller for Enterprise
TTP Certs
14
: Trusted Third Party Certificate