Subject: Date:June 26, 2012

1. Avaya one-X® Communicator 6.1 Service Pack5 (SP5)

Avaya is introducing significant enhancements to its Avaya one-X® Communicator 6.1 Service
Pack 5(SP5) release. Included as an entitlement with Avaya Aura™ Enterprise Edition, this soft
client application enhances user productivity and reduces costs by unifying Avaya’s desktop
communications capabilities.

2. What’s new with Avaya one-X® Communicator 6.1 Service Pack 5(SP5)
Avaya one-X® Communicator is Avaya's next-generation soft phone supporting both H.323 and SIP
audio and video, and providing access to all communications’ media in a single interface. The new
6.1 Service Pack 5(SP5) release of Avaya one-X® Communicator introduces significant user
interface and usability enhancements.

Note:

The major enhancements in this Release of R6.1 SP5 Product Version 6.1.5.07-SP5-
37495:
 Citrix Support for Windows 2008 R2 with Citrix XenApps 5/6
 Support add-in features (C2D Firefox 3.x, C2D IE 8.x, Wipe to Dial and Outlook Integration
2007/2010) with Citrix XenApps 5/6 on Windows Server 2003 and 2008
 Support E911 Emergency Number for SIP (SM6.2)
 Support silent mode installation via the setup.exe
 Click to Dial Support for Firefox 4, 5, 6+, 9.0 and 10.0
 Source icon for Avaya one-X® Client Enablement Services integration (CES) contacts
 Support for 14xx, 16xx and 94xx phone types
 Support for 96x1 phone types
 Support Avaya Aura Conferencing (AAC) 7.0 audio
 Support Avaya Aura Conferencing (AAC) 7.0 video (SIP mode, H.264 AVC only)

Notes:

 Outlook integration feature is supported with Microsoft Outlook 2007 SP1 & SP2 and 2010.
 Outlook 2007 users with Microsoft Office version less than 12.0.6520.5000 will have to
request and install Hotfix KB976477 prior/post installation of Avaya one-X® Communicator.
User can request this Hotfix at http://support.microsoft.com/kb/976477/.
 Outlook 2007 users with Microsoft Office version equal to or higher than 12.0.6520.5000
and Outlook 2010 do not need to install the above Hotfix. Users can directly proceed with
Avaya one-X® Communicator installation.
[(Microsoft Office version of Outlook 2007 is indicated in Help->About Microsoft Office
Outlook. The first line of the about dialog shows the Outlook 2007 version followed by
Microsoft version.)]

1
  Docking is no longer supported in the new visual design.
 An incoming call notification no longer fades away.
 It is mandatory to configure an Extension and Password under Telephony settings for Avaya
one-X® Client Enablement Services integration (1XCES) along with Avaya one-X Client
Enablement Services integration (1XCES) URL, username and password under Login
settings.
 In failover geo-redundancy environment, only “This Computer” mode supported.
 Bridge Conference Controls in Deskphone mode configured for SIP users do not work as
expected.                                                                                                                                   
Workaround: Using the keypad star codes the moderator can,
Turn Lecture Mode On/Off
Hold/resume Conference
Lock/Unlock Conference
The moderator will not be able to Hold/resume, Mute/Unmute or drop participants
 Avaya one-X® Communicator does not support ad-hoc IM 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.
 When User is registered to Avaya one-X Communicator in other phone mode, the
application may unexpectedly close/exit during or when adding participants into conference..
 AST features are supported in “This Computer” mode for SIP & H.323.

3. System Test Environment

System Name Version Information

Session Manager R6.2

SMGR version – 6.2.0 – SP1 build –
6.2.0.0.15669-6.2.12.104
Software update revision – 6.2.13.1.1870.
ASM version – 6.2.1.0.621007

R6.1
S MGR version - 6.1.0 (Build -
6.1.0.0.7345-6.1.5.702)
Software Update Revision - 6.1.11.1.1860

Communication Manager R016x.02.0.823.0Patch 02.0.823.0-19786

R016x.00.1.510.1 Patch 00.1.510.1-19528

Presence Services 06.01.02.00.0903

H.323 Desk phone 46xx/96xx Avaya one-X® desk phone 2.0 and 3.1

SIP Desk phone 96xx SIP 2.6.4, 2.6.5.124, 2.6.6.0, 2.6.7.0

Desktop - Windows Operating System Windows-XP 32-bit and 64-bit

Professional, Windows 7 32-bit and 64-bit
Enterprise, Windows Vista 32-bit Ultimate.

2
 Windows Vista 64-bit Enterprise
RMX2000 7.0.3.8.3942001

Avaya one-X Client Enablement Services 6.1.2.0.19

(CES)

4. Avaya one-X® Communicator 6.1 Service Pack 5(SP5) System Requirements

Minimum PC Hardware Requirements:

 Pentium 1.2 GHz single-core processor (or higher).

 Minimum Pentium 4 2.0 GHz or dual-core processor (or equivalent) required for video
support.
 1 GB RAM (higher for Vista and Windows 7 as recommended by Microsoft).
 100 MB Dedicated Video RAM.
 At least 3 gigabytes (GB) of available space on the hard disk, if Microsoft .NET Framework
4.0 is not already installed, else 1GB will suffice.
 Keyboard and a mouse (or some other compatible pointing device).
 Video adapter and monitor with 1024 x 768 or higher resolution.
 Network Interface Card (NIC).
 USB Headset for “This Computer” mode.

Recommended USB Cameras – NOTE: Where possible, please follow Microsoft Windows
Operating System Recommended Hardware requirements based on Operating System version
information.

HD Cameras Driver Version

Creative Live! Cam Socialize HD 1.2.1.0
Microsoft Lifecam Cinema 3.20.240.0
Logitech® Webcam C905 13.0.1788.0
Non HD Cameras
Logitech® Webcam Pro 5000 12.0.1278.0
Logitech® Quick Cam Messenger 12.0.1278.0
Creative Live! Cam Notebook Pro 1.2.6.627
Logitech® Webcam Pro 9000 13.0.1783.0

Minimum PC Hardware requirements for High Definition video:

 Intel Dual Core or Core 2 Duo or Core i3 and higher.
 At least 100MB dedicated video memory (if shared from main, main needs to be
compensated additionally by 100MB).
 At least 2GB RAM.
 HD camera (note up to 720p is supported in 6.0).

5. Avaya one-X® Communicator R6.1 Service Pack 5 (SP5) Supported Codec’s

3
  isac
 G.722-64k
 G.729 A
 G.729AB
 G.711A
 G.711MU

Note: If the Communication Manager is configured for G.729 codec set then the Avaya one-X®
Communicator H.323 users must need to add the following four lines in the config.xml file.
<parameter>
<name>EnableG729</name>
<value>1</value>
</parameter>

The config.xml file can be found in the following location:

For Windows XP: “C:\Documents and Settings\<USER_NAME>\Application Data\Avaya\Avaya
one-X Communicator”

For Windows 7 and Vista: “C:\Users\<USER_NAME>\AppData\Roaming\Avaya\Avaya one-X

Communicator”.

Avaya one-X® Communicator 6.1 Service Pack 5 (SP5) Installer Information

      1. During installation, the option to select Avaya one-X® Client Enablement Services, Video
Integration, Microsoft Outlook Integration, Browser Integration for IE and Firefox features no
longer exists. These features are installed by default and require server related administration
support and configuration in the Avaya one-X® Communicator Settings tab.
       2. It is recommended to use the Setup.exe file for Avaya one-X® Communicator R6.1
Service Pack 5 (SP5) installation.
Notes:
Default installed protocol is SIP but with UI option to switch between signaling protocols.
Switching between protocols requires a restart of Avaya one-X® Communicator. To use
H.323 protocol, follow these instructions:
1)Go to Settings UI and select H.323 protocol. Save this setting and then restart Avaya
one-X® Communicator.

Avaya one-X® Communicator “onexc_6.1.5.07.zip” software zip is packaged with the

following files:

 R6_1_SP5_GA_Release_Letter (this document)

 LICENSE.rtf
 ONEXC_Resolved_SP5_Tickets_2012June.xls
 Setup.exe (Avaya one-X® Communicator installer for non- Citrix mode)
 Setup_Citrix.exe (Avaya one-X® Communicator installer for Citrix mode)
 vcredist_x86.exe
 dotNetFx40_Full_x86_x64.exe

4
  onexc_setup_6.1.5.07_37495.msi
 vstor40_x86.exe (for Outlook 2007 or 2010 integration running on 32-bit system)
 vstor40_x64.exe (for Outlook 2007 or 2010 integration running on 64-bit system)
 onexcuiadmin.exe (for Administrators)

Important Notes:

1. On 64 bit O/S’s, VC redistributable of 32 bit version is required because Avaya one-X®

Communicator is a 32 bit application. Therefore even after installing 64 bit version of VC
++ 2005 redistributable, installer will prompt to install 32 bit version of VC++ 2005
redistributable.
2. There is a command line provision to enable installation logging during installation using
Setup.exe.
Instructions:
1. Run the command prompt as administrator.
2. Change directory to the path where the installation package is extracted.
3. Run the Setup.exe using command line as follows. Setup.exe /log or Setup.exe
--log
4. Complete the installation process as directed by the Setup wizard.
5. This will create two text files namely SetupLog.txt and MSILog.txt in the current
directory.

6. Installation/Upgrade guide lines for MSI installation.

Note that msi installation should only be used if previous R 6.1 SP3 version is installed using the
Setup.exe application.
Installing Avaya one-X® Communicator by double-clicking the .msi application defaults the
signaling protocol to SIP. A user upgrading from H323 protocol might want to use the command
line switch SIGNALPROTOCOL to retain it. Instructions below:
 Run the command prompt as administrator.
 Change directory to the Setup.exe/.msi file path.
 Install the Setup.exe/.msi using command line e.g.,

Silent Installation for .msi:

Instructions to install H.323 protocol and all supported features:
msiexec /i onexc_setup_6.1.5.07_37495.msi /qn SIGNALPROTOCOL=”1”
ENABLECLICKTODIALIE=”1” ENABLECLICKTODIALFF=”1” ENABLEOUTLOOKADDIN=”1”

instructions to install SIP protocol and all supported features:

msiexec /i onexc_setup_6.1.5.07_37495.msi /qn SIGNALPROTOCOL=”0”
ENABLECLICKTODIALIE=”1” ENABLECLICKTODIALFF=”1” ENABLEOUTLOOKADDIN=”1”

Silent Installation for Setup.exe:

5
 Prerequisites:
“.msi” and “.exe” needs to be added in “Inclusion list for low risk file types” and enabled.

Windows-7:
 From run -> gpedit.msc and open “Local Group Policy Editor”

Windows-XP:
 From run -> gpedit.msc and open “Group Policy”

 Go to User Configuration -> Administrative Templates -> Windows Components ->

Attachment Manager -> Inclusion list for low risk file types
 Select option “Enable” and enter .msi;.exe;
 Click “Apply” and “Ok”

Install without options:

Execute the command
setup.exe /q

(This will install one-X Communicator without setup UI and automatic launch of Communicator
post-install.)

Install with options

Note: Any MSI option can be passed in /v:"<options>".
setup.exe /q /v:"LAUNCHAPPONEXIT="1" SIGNALPROTOCOL="1"”

Instructions to install H.323 protocol and all supported features:

Setup.exe /q /v:"LAUNCHAPPONEXIT="1" SIGNALPROTOCOL="1"
ENABLECLICKTODIALIE="1" ENABLECLICKTODIALFF="1" ENABLEOUTLOOKADDIN="1""

Instructions to install SIP protocol and all supported features:

Setup.exe /q /v:"LAUNCHAPPONEXIT="1" SIGNALPROTOCOL="0"
ENABLECLICKTODIALIE="1" ENABLECLICKTODIALFF="1" ENABLEOUTLOOKADDIN="1""

(This will install one-X Communicator without setup UI, no post-install launch of communicator)

Where:

Parameter Name Default Allowed Notes

value Values

ENABLECLICKTODIALIE 1 0 or 1 Set to ‘1’ to enable click-to-dial for

Internet Explorer or ‘0’ otherwise.

ENABLECLICKTODIALFF 1 0 or 1 Set to ‘1’ to enable click-to-dial for

Mozilla Firefox or ‘0’ otherwise.

ENABLEOUTLOOKADDI 1 0 or 1 Set to ‘1’ to enable outlook

N integration for Avaya one-X

6
 Communicator or ‘0’ otherwise.

SIGNALPROTOCOL 0 0 or 1 Set ‘1’ for H323 protocol and ‘0’ for

SIP protocol.

NOROOTCERTIFICATES 0 0 or 1 Set to ‘1’ to not install the root

certificates.

DSCPFORVIDEO 0 0 or 63 Sets value of DSCP for video.

If you don’t specify any of the above-mentioned command-line parameters, their default value
will be used. Again, it is strictly advised to use Setup.exe for installation.

7. Known System Interactions after installing or using Avaya one-X® Communicator 6.1
Service Pack 5 (SP5)
 Avaya one-X® Communicator Release 6.1 Service Pack 5(SP5) requires the most up-to-
date video driver version for your system. If your video driver is not current, you may
experience system blue screen freezes, or system lockups caused by interactions between
outdated video drivers and recent installed operating system patches.
 Launching Avaya one-X® Communicator on a Windows XP Professional SP3 system may
enable the WPFFontCache service that could take upto 50% of the CPU. To prevent this,
disable the WPFFontCache service.
 Terminal Services and RDP (Remote Desktop) are not 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.
 At times, Uninstall may not be successful on Windows 7 64 bit machine for standard user

8. Known Issues in Avaya one-X® Communicator 6.1 Service Pack 5(SP5)

It is not possible to list all the known issues here. The list below is been categorized and
identifies the most critical and major issues and/or issues that users are most likely to see.
Installation/Upgrade and Login/Registration:
 ( SIP Shared Control/Deskphone)When Avaya one-X® Communicator is configured for
Multiple Session Managers(SM) IP's and, if the order of the IP is changed, Avaya one-X®
Communicator does not login in Deskphone mode.
 Avaya one-X® Communicator H.323 registered in Deskphone mode displays incorrect
Phone Type in "About Avaya one-X Communicator".
 Application may unexpectedly close/exit after restart on changing settings 
 MS Visual C++ Runtime error observed (R6025- pure virtual function call) on a particular
Win-XP system.
 There is no warning message on Avaya one-X Communicator (1XC) UI after logging the
same extension in hard phone in the middle of the call.
 If user extension is already logged on a Hardphone and tries to login into Avaya one-X®
Communicator Deskphone mode or tries to login on to Hardphone while application logged

7
 in Deskphone mode, he might not be able to login. He needs to exit the application and login
again.
 At times, User might not be able to login into client
Work around: Instead of login - go to settings -access a few pages and click OK. Now login
 Avaya one-X® Communicator installation may not be successful in Citrix deployments when the CA
root certificate is already installed in more than one certificate store on the server. This issue has
been observed with Citrix 4.7 on Windows 2003 SP2.
Work around: install through command line, with parameter norootcertificates the installer
will not install the root certificates. This installs the application successfully
From the command line, execute the following command

Setup_Citrix.exe /norootcertificates

 Normal and Silent installation failed if a non-admin user tries to install or upgrade with "Run
as Administrator"
Work around:

On Windows-7, a non-admin user wants to install or uninstall with "Run as Administrator" then
he/she need to configure the windows as mentioned below:

“Detect application installations and prompt for elevation” needs to disabled in the “Local
Security Policy”

========================================================================
=============Login Windows-7 as a Administrator user.

Go to Start->Run, type “Local Security Policy”, Press Enter

In the opened window choose “Local Policies->Security Options->User Account Control: Detect
application installations and prompt for elevation” and set the option disabled.

“User Account Control Settings” option needs to be enabled.

====================================================

Login Win-7 as a Administrator user.

Go to Start->Run, type “UAC”, press Enter

In the opened window don’t keep the UAC as “Never notify”.

Keep it as default i.e. “Always notify me (and do not dim my desktop) when:” ………

Restart the system and login as a non-admin user. (If machine is not restarted the changes
will be not reflecting)

Then try installation and un-installation with “Run as Administrator”, then it will prompt the user
for Admin authentication.

8
Telephony Conference:
 When User is registered to Avaya one-X® Communicator in other phone mode, the
application may unexpectedly close/exit during or when adding participants into conference.

 User logged in Deskphone mode is not able to resume a Held Conference call from Avaya
one-X® Communicator.
Workaround: Resume the held conference call from Hard-phone.
 The Drop button does not appear on Avaya one-X® Communicator UI, when client is
registered in Deskphone mode for H.323 protocol (Phone Type 9640)
Workaround: Drop the participant from the Hard-phone.
 “Unable to add participant” message window pops up for 2/3/4/5/6 party conference
initiated from Avaya one-X® Communicator SIP.
 (SIP) "Conference Error" is seen when trying to conference two SIP endpoints.
 Conference Originator cannot drop last party from conference, if, a participant adds another
party to conference.

Presence& IM:
 Presence in contacts search result shows up after 7 seconds.
 At times, Presence of SIP contacts tagged as Favorite does not show up on Avaya one-X®
Communicator H.323.
Workaround: Exit Avaya one-X® Communicator and login back, presence for SIP contacts
gets updated correctly.
 SIP & H.323: Upon Logout, Presence shows "Available"
 Avaya one-X Client Enablement Services (CES) SIP user's Presence status is not
displaying in the Search Result/ My Contacts/ Favorites/ VIP contact list.
 SIP: Notification of “leave from the IM conference” is not displaying, if a SIP user leaves
from the multiparty IM conference
 SIP: Offline message is displaying at SIP User-A, if another SIP User-X leaves from the
multiparty IM conference and then User-X make a call.
 SIP: Self user name is displaying in the IM window if another SIP user leaves from the
multiparty IM conference.
 Thin presence line displayed in call log instead of Presence jelly bean
 Cannot start IM at times after changing the sip server and presence server settings
 On Windows -7 & Vista 64 bit machine, at times, Presence note is not saved.
Workaround: Restart the PC.
 Presence icon (jelly bean) may not be available on Avaya one-X® Communicator UI when
logged in without Client Enablement Services integration (must configure AND enable/check
Public Directory name look up in Settings/Preferences)
 When user logs off from Avaya one-X® Communicator and logs in, presence is viewed as
offline, presence gets updated to available after 25 seconds or if user performs an activity
like going off-hook.
 Avaya one-X Client Enablement Services (CES) SIP user's Presence status is not
displaying in the Search Result/ My Contacts/ Favorites/ VIP contact list under H.323 Avaya
one-X Client Enablement Services (CES)
 (14xx,16xx,94xx H.323)"currently offline" message is displayed on the IM window, when IM
from 1XC H.323 is initiated to 9641 .

9
 Multiparty IM (SIP with or without Avaya one-X Client Enablement Services (CES) ): If
host ,SIP, user leaves IM , logs off and logs in, then the far-end/participant users gets Host
presence update in their IM window.

Voice Message:
 SIP/H.323 with Avaya one-X Client Enablement Services (CES): new Voice Messages may
not reflect immediately or while the client is active
Workaround: Restart the application
 SIP/H.323 with Avaya one-X Client Enablement Services (CES): Voice Messages deleted
are visible while the client is active, the messages are not updated.
Workaround: Restart the application
 Message Waiting Indicator doesn't glow for Avaya one-X® Communicator in Deskphone
mode (Shared Control)

Contact Management:
 "Unable to add contact" message pops up, for contacts configured with pager details.
 (SIP)"Unable to add contact" message window pops up, when user adds his own self
contact as Favorite.
 SIP with or without Avaya one-X Client Enablement Services (CES): Email filed is blank
when any H.323/SIP user is added into My Contacts or Favorites list from the "PPM" search
 SIP with or without Avaya one-X Client Enablement Services (CES): Email filed is blank
when any H.323/SIP user is searched from "PPM" name look-up.
 SIP with Avaya one-X Client Enablement Services (CES): Double work number is displaying
(IM filed copies into one Work number).
 Domino LDAP Contacts with Umlaut characters cannot be added as Favorite.
 Contacts deleted from Avaya one-X® Communicator or from hard-phone don't get synced,
the user has to log-off & login back for the changes to reflect
 When user is adding a contact as VIP from Call Logs/Search, contact view is changed from
current view to VIP.
 (SIP Deskphone) Contacts deleted from Avaya one-X® Communicator or from hard-phone
don't get synced, the user has to log-off & login back for the changes to reflect
 Cannot add contact to Favorite from Show Details.
 Contact details screen is stretched corresponding to length of Presence note set by that
contact.
 If contacts are deleted from Favorites /VIP (those are added from Call log), then after delete,
they are still listed under “All” filter list.

Audio & Video:

 Video doesn't negotiate if Avaya one-X® Communicator H.323 with desk phone as 9640
phone type calls to Avaya one-X® Communicator SIP Video endpoint.
 Video license notification shown incorrectly after enabling video
 Application may unexpectedly close/exit while trying to launch video window before it was
launched by itself after login
 No error is displayed to user if video cannot be negotiated with far end
 Cannot reacquire camera in One X C after it is released by other application

10
 Detach - reattaching camera on active video call doesn’t resume video after un-muting
requires 2 Hold - Resume operations
 Video call from Flare converged client gets converted into audio call after it is answered at
one-XC client.
 User-A's video mute icon is not displaying when make or receive a call from a video enabled
User-B ("show your video image automatically on login with video capabilities" is unchecked
for User-A).
 Different behavior with Logitech and Microsoft cameras.
 Incoming call ringing alert isn’t available if secondary ringing device is disconnected on
incoming call.
 Audio device muted or the volume is 0..." message is observed at times during idle login
state or on an active call state (with proper audio path).
 If audio driver is not configured, then Audio Error Message window pops up when user logs
into Avaya one-X® Communicator H.323 is Deskphone mode.
 Video statistics on-line help for transmit and receive bit rate incorrect.
 No video, if check box “Send video image automatically” is unchecked on both the user
ends.

Outlook Integration:
 (Outlook contacts are more than 1000+) Contact matching Window pops up after 20-25
seconds for incoming call.
 High CPU and memory utilization while indexing outlook contacts.
 Outlook Re-indexing is very slow or unsuccessful at times, when outlook has more than
1900 contacts configured/saved.

Call handling:

 No DTMF between SIP to H.323 (DTMF feedback sound is available locally but not at
remote end).
 Status of call is not updated on Avaya one-X® Communicator (1XC), when user logs into
Avaya one-X® Communicator (1XC) Deskphone while an active call is in progress between
Hardphone and far-end.
 Avaya one-X® Communicator (IXC) in Deskphone mode: The incoming call on Avaya one-
X® Communicator (1XC) UI and the toast window shows up after a delay of 10seconds
 If audio driver is not configured, then Audio Error Message window pops up when user logs
into Avaya one-X® Communicator H.323 is Deskphone mode.
 No voice path and call can't be held for existing call if call is transferred to extension number
which is not registered or invalid number
 Citrix Integration: Click-2-Dial for Internet Explorer does not work (Windows Server 2008)
unless Internet Explore Enhanced Security Configuration is disabled
 On a active video call , If Avaya one-X® Communicator (1XC) SIP "A" endpoint muted video
and Avaya one-X® Communicator (1XC) "B" try to mute video , Video call gets dropped ,
there is audio only call between the endpoint
 [Avaya one-X® Communicator (1XC), Client Enablement Services (CES) SIP
extension]Two call appearance for a “brdg-appr” call seen on Aura 6.1

Call Log:

11
  Answering a call on secondary station creates inconsistent Call log entry
 (14xx/16xx/94xx DCP)Call log is not updated with name, after conference call is ended.
 CM IP address is saved in SIP call log when initiator SIP drops out from Conference call.

UI:
 Phone type for 96x1 is displayed as 96xx in Avaya one-X® Communicator (1XC) help
About window
 Field Types are not present Under Field button, even though all fields are selected in
"Show in this Order"
 User cannot select a number as Also ring in the Call handling tab, immediately after
adding the number under the phone numbers tab. The user has to close the general
settings tab and reopen it to perform this operation.
 Unusual UI may appear for Avaya one-X® Communicator (1XC) when Avaya one-X®
Communicator (1XC) is added as Meet-Me conference participant. Conference call runs
for long duration and ended.
 "Invalid Number" message window pops up intermittently (30% reproducible)
 The codec set used is G.729A and user views the Audio Statistics in Avaya one-X®
Communicator (1XC) it displays only shows G.729.The "A" is not displayed
 On Windows 7, the statistics does not update microphone and speaker level changes.

 On clicking search button in Basic Search with empty search field, the "Appstart" (Arrow
+ hourglass/ Arrow +circular refresh) cursor remains on the screen endlessly.

Inter-op
 [Avaya one-X® Communicator (1XC) with Client Enablement Services (CES)]Favorites
tagged from Avaya one-X® Communicator (1XC) does not always sync up with the one-
X Mobile (1XM) Client when the user has logged into both the clients. The vice versa
works properly.
 User cannot set or change presence note on the Avaya one-X® Communicator (1XC)
client (with Client Enablement Services (CES) integration) if there is already an existing
note on the one-X Mobile (1XM) client for the same user.
 User cannot change the presence Availability in the Avaya one-X® Communicator (1XC)
(integrated with Client Enablement Services (CES)) if the value is not set to Auto-
Manage for the same user on one-X Mobile (1XM).
 (Avaya one-X® Communicator (1XC) integrated with Client Enablement Services (CES))
Display name of the user vanishes after sometime when the user is logged in the SIP
mode on a Windows 7 Professional Machine.
 “Block/Allow All Calls and Allow VIP calls" feature when set form the one-X Mobile
(1XM) client is not updated on the Avaya one-X® Communicator (1XC) client of the
same user.
 Sun One Directory: not able to delete port number (389) while changing the settings
from Active directory to sun one Directory.

AAC:
 If video window is manually closed and Avaya one-X® Communicator "A" dial AAC
conference as moderator and another Avaya one-X® Communicator (1XC) "B" join as
participant, Black Video window appears at remote endpoint (Avaya one-X® Communicator
[1XC] SIP "B")

12
 Video- Avaya one-X® Communicator (1XC) Mute video feature indicates video freeze at
remote end instead of "Far end has muted video"
 video- Avaya one-X® Communicator (1XC) stop or end a call doesn't drop video at remote
end during conference
 AAC 7.0 conference Video call is not negotiated if one-X® Communicator (1XC) SIP
endpoint selects video call with bit rate as 384 kbps or less in AAC conference , Audio only
call between AAC conference participants
 Though audio quality is good, high Jitter value, perceived delay and poor audio quality seen
in audio statistics.

Network:
 User checks the "UDP/TCP port range preferences" in Network Settings and edits the port
range other than default value, logs into Avaya one-X® Communicator, the Port range is
unchecked.
 Avaya one-X® Communicator (1XC) is not able to make call & not in sync with Desk Phone
after local network recovers
 Client gets stuck in logging state when network loss is encountered due to computer sleep
mode
Network Recovery:
 (SIP in “This Computer”)After the network recovery, user is not able to acquire the server
services, due to which PS & Call session are not through.
Workaround: Exit Avaya one-X® Communicator and login in again.
 (H.323 in “This Computer”) After network recovery, the warning message "Connection to IM
service was lost. Attempting to recover" stays on UI. User has to manually close this
warning message.
 Cannot initiate call from Avaya one-X® Communicator after network recovery - call session
id error.
Workaround: Log-off Avaya one-X® Communicator & Login again.
 Avaya one-X® Communicator SIP Logged in with Client Enablement Services
integration, after network recovery, Avaya one-X® Communicator logs in and the user
name is not displayed.
Work around: User exits Avaya one-X® Communicator & re-logs in then name is displayed
correctly
 Avaya one-X® Communicator H.323 logged in with Client Enablement Services
integration, after network recovery, Avaya one-X® Communicator is logged into
Standalone and "Instant Messaging Service Connection Lost" stays on UI.
Work around: User has to restart the client.
 (SIP Deskphone with Avaya one-X Client Enablement Services (CES)) Contacts are not
displayed after the network recovery in Avaya one-X® Communicator (1XC) SIP
deskphone.
Workaround: Click on either Show Call Logs and again click on Show Contacts.
 (SIP Desk-phone with Avaya one-X Client Enablement Services (CES)) Active call is not
displayed after the network recovery in Avaya one-X® Communicator (1XC) SIP deskphone.
Workaround: Drop the call from Hard-phone, Exit Avaya one-X® Communicator (1XC) and
login back

13
 (SIP Deskphone with Avaya one-X Client Enablement Services (CES)) Presence does not
get updated after the network recovery in Avaya one-X® Communicator (1XC) SIP
deskphone.
Workaround: Exit Avaya one-X® Communicator (1XC) and login back.
 Avaya one-X® Communicator (1XC) is not able to make call & not in sync with Desk Phone
after local network recovers.
Workaround: Exit Avaya one-X® Communicator & Login again.
 (Deskphone mode)When Hardphone recovers from network outage, sync between Avaya
one-X® Communicator (1XC) and Hardphone is lost.
Workaround: Exit Avaya one-X® Communicator (1XC) and login back once phone recovers
from network outage.
 (H.323) When Avaya one-X® Communicator (1XC) logged in “This Computer”, is on a active
call, after network recovery, the application logs off and Login error message window pops
up. User has to login back. The two audio may not be available.
Work around: Hold/Resume the call from Avaya one-X® Communicator (1XC), two-way
audio re-established.

Failover-Failback:
 (SIP)When Primary Session Manager (SM) fails & Avaya one-X® Communicator registers to
secondary SM, it takes more than 30 seconds for the Presence to get functional.
Workaround: Exit Avaya one-X® Communicator & Login again.
 (SIP)When Primary Session Manager (SM) fails & Avaya one-X® Communicator registers to
secondary Session Manager (SM), Conference is not successful.
Workaround: Exit Avaya one-X® Communicator & Login again.
 When Primary SM goes down, Avaya one-X® Communicator (1XC) logs off, user tries to
login with secondary SM, application might unexpectedly close/exit.
Workaround: Re-Login into the application.
 (H323 Deskphone)When Main CM goes down, Avaya one-X® Communicator (1XC) logs off
& login in not successful.
Workaround: Exit Avaya one-X® Communicator & Login again.
 (SIP Deskphone)When Primary SM goes down, Avaya one-X® Communicator (1XC) logs
off, user tries to login with secondary SM, application might unexpectedly close/exit.
Workaround: Re-Login again into the application.

 Registration fails if Avaya one-X® Communicator (1XC) to LSP for H.323 and BSM for SIP if
only primary is being configured on Avaya one-X® Communicator (1XC) and CM/SM
pushes ESS/LSP and SM2-BSM IP to Avaya one-X® Communicator (1XC).
 Conference icon of H.323 user/extension is not proper during primary SM down.
 While on a active call of Avaya one-X® Communicator (1XC) integration with SIP Avaya
one-X Client Enablement Services (CES), if primary SM goes down then presence icon
changes from Orange (Busy) to Green (Available).
 While on a active call, Primary SM goes down, user drops the call from Avaya one-X®
Communicator (1XC), call is not dropped at the farend
 While on a active call of SIP with or without Avaya one-X Client Enablement Services (CES),
if primary SM goes down, then Hold and Resume takes more than 15/20seconds to update

14
 User name of SIP Avaya one-X Client Enablement Services (CES) disappears during
primary SM down

15