Sunteți pe pagina 1din 13

BETA DRAFT - CISCO CONFIDENTIAL

Release Notes for


Cisco UC Integration™ for Microsoft Office Communicator
Beta Release – 7.1(1221.5892)

Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (64387)
Fax: 408 526-4100

Customer Order Number:


Text Part Number:

Corporat e Headquart ers


Cisco Systems, Inc.
170 West Tasm an Drive
Beta DRAFT - CISCO CONFIDENTIAL

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT
TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS
MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY
PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET
FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED
HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED
WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by
the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX
operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF
THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED
SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR
ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL,
CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR
LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF
CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network
logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step,
Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ
Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the
Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath,
Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.;
Changing the Way We Work, Live, Play, and Learn, Discover All That’s Possible, and Empowering the
Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA,
CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS
logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel,
EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-
Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are
registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other
countries.
All other trademarks mentioned in this document or Web site are the property of their respective
owners. The use of the word partner does not imply a partnership relationship between Cisco and
any other company. (0106R)

Cisco Unified CommunicationsManager EFT Software: 7.0(03.99731.9)


Copyright © 2005, Cisco Systems, Inc.
All rights reserved.
Beta DRAFT - CISCO CONFIDENTIAL 3 Overview 3

Table of Contents

1 Overview ..................................... 4
2 Instructions on Installing and
Upgrading Cisco UC Integration ™
For Microsoft Office
Communicator ............................... 4
2.1 Software Requirements ................... 4
2.2 ............................................................ 4
2.3 Cisco Unified Communications
Manager Support .................................... 5
2.4 File Posted for Download ................ 5
2.5 Desktop OS Requirements .............. 6
2.6 Supported Hardware ........................ 6
2.7 Tested PC Audio Devices ................ 7

3 Caveats / Known Issues ............ 8


4 Resolved Defects ..................... 12

3
4 Beta DRAFT - CISCO CONFIDENTIAL

1 Overview
This is the Release Notes for use with the Beta version 7.1(1194.5190) release of the Cisco UC Integration ™ For
Microsoft Office Communicator.
These Release Notes should be used in conjunction with the “Integration Guide.” posted in the Forum.

All EFT Documentation and required software can be found at the below link, you need your CCO ID to download the
documentation and software.
We're pleased to announce that the Cisco UC Integration™ for Microsoft office Communicator will support both OCS
2007 R1 and R2 when it releases. The target release date is still July 15th. The latest build posted here also supports
both OCS 2007 R1 and R2.

https://upload.cisco.com/cgi-bin/swc/fileexg/main.cgi?CONTYPES=IPCBU-forum
Forum : CUCIMOC BETA

2 Instructions on Installing and Upgrading Cisco UC


Integration ™ For Microsoft Office Communicator
It is very important that you read and follow below instructions in order to successfully install and configure your Cisco
UC Integration ™ For Microsoft Office Communicator. For complete installation instructions please refer to the Admin
guide and Training materials posted to the Forum.

2.1 Software Requirements


 Cisco Unified Communications Manager (CUCM).
o CUCM LDAP Directory Sync and LDAP User authentication. (Recommended)
o CUCM User-ID/Pwd should be same as AD User-Id/Pwd. (Required)
 Microsoft Office Communications Server 2007 R1
 Microsoft Office Communicator 2007 (minimum build number 2.0.6362.111)
 Microsoft Windows Operating System (XP SP2/SP3 (32-bit) or Vista SP1 (Ultimate, Enterprise or Business 32-
bit & 64-bit))
5 Beta DRAFT - CISCO CONFIDENTIAL 5

2.3 Cisco Unified Communications Manager Support


 Cisco Unified Communications Manager 6.1(3)
 Cisco Unified Communications Manager 6.1(4)
 Cisco Unified Communications Manager 7.0(2a)SU1 or later
 Cisco Unified Communications Manager 7.1(2) later

Please note the following requirements / caveats for using CUCM 6.1(3) . . .

CUCM 6.1(3):
- COP file will be required for CUCM to register the client services framework as a device type.
- 3 DLU's are always required no matter whether CUCIMOC is used as a primary phone, or in 'adjunct mode'
(adjunct mode means used in addition to an existing IP phone connected to CUCM).

CUCM 6.1(4):
- No COP file will be required, as the device type is included already.
- When using CUCIMOC as a primary phone, 3 DLU's will be required. When using in 'adjunct mode', only 1
DLU will be required.
The DLU requirement is less likely to be an issue for customers that are using our Cisco Unified Workspace
Licensing as plenty of DLU's are available.
If starting with 6.1(3) and then moving to 6.1(4) at a later date, then the DLU's will be freed up on upgrading.

2.4 File Posted for Download

File Name Description


Client Installers
Cisco_UC_ IntegrationTM_for_Microsoft_Office_Communicator.exe Includes .NET 3.5 SP1 installer stub - can be run
by user on desktop for standalone install.
Cisco_UC_ IntegrationTM_for_Microsoft_Office_Communicator.msi Expects .NET 3.5 SP1 to be pre-installed -
silently installs via push mechanisms
Configuration Files
Sample_CUCIMOC _CUCSF_AdminData.bat A sample .BAT file that creates the necessary
registry settings on user desktop. Need to be
run on each user machine. File needs to be
customized for customer environment with
correct IP addresses.
CUCIMOC_CUCSF_AdminData.adm An ADM File used to edit and deploy registry
settings for end user desktops. (Automated
way to deploy registry settings part of
SampleCSFClientDeviceSettings.bat)
COP Files for CUCM
ciscocm.galway.alpha.csf.cop.sgn The COP file used to create the new CSF Device
Type in CUCM. COP file needs to be installed on
servers and server needs to be rebooted after
5
6 Beta DRAFT - CISCO CONFIDENTIAL
COP file install.

cmterm-cupc-dialrule-wizard-0.1.cop.sgn This COP file needs to be installed on the TFTP


Server and TFTP Service needs to be restarted
after the COP file install. The Dial Rules is used
to create and deploy Application & Directory
Lookup Rules. This process needs to be
repeated anytime a change is made to
Application or Directory lookup rules.
Documentation
Integration_Guide_for_Configuring_Cisco_UC_Integration_for_Micros Integration Guide
oft_Office_Communicator_Release_7_1.pdf

User_Guide_for_Cisco_Unified_Communications_Integration_for_Mi User Guide and Quick Start Guide


crosoft_Office_Communicator_Release_7_1.pdf

Client Installation Recommendations


 For desktop installation, the EXE installer must be used. Reasons:
o EXE installs pre-requisites
o EXE overcomes UAC on Vista
o EXE internationalizes the installation and displays the installer dialogs in the systems culture
o EXE creates the installer logs

 MSI is for mass deployment with centralized tools.

2.5 Desktop OS Requirements

2.6 Supported Hardware


Desktop
7 Beta DRAFT - CISCO CONFIDENTIAL 7

Laptop

2.7 Tested PC Audio Devices


Polycom Speaker phone USB
ClearoneChat 50 USB
Platronics 510 Blue Tooth
Jabra 8110 USB
Jabra 8120 USB
Jabra 9120
Jabra 405 flex (planned, but out of stock, so no testing got done)
Jabra AdvantagePlus
Plantronics CS50
Plantronics CS60
Plantronics DA60
Plantronics DSP400
Plantronics DA 55
Clarysis i750
Futiro USB

7
8 Beta DRAFT - CISCO CONFIDENTIAL
3 Caveats / Known Issues
User Facing Features (Login, Place call, Transfer, Conference etc) Related Caveats
 In some scenarios security suites using “Host-Based Intrusion detection Pervention (HIPS)” can kill the Cisco
UC Integration ™ For Microsoft Office Communicator process, believing it to be a threat, showing no obvious
reason for the crash in Cisco UC Integration ™ For Microsoft Office Communicator logs.
o Workaround: Disabling HIPS will prevent this from occuring and customer can add Cisco UC
Integration ™ For Microsoft Office Communicator to exception process list if HIPS is confirmed to be
blocking.
 For certain users the Cisco UC Integration ™ For Microsoft Office Communicator options in pop-up don’t show
a clear checkbox.
o Workaround: Hoover over the mouse you can see that there is option to check call forward or save to
communications history etc.
 Cisco UC Integration ™ For Microsoft Office Communicator cannot dynamically grow and shrink the size of the
tab as users drag the MOC tab. This can lead to white space around the tab/conversation pane.
o Workaround: None
 Cisco UC Integration ™ For Microsoft Office Communicator registration fails when moving from one CUCM
cluster to another cluster. If Cisco UC Integration ™ For Microsoft Office Communicator was part of Secure or
Mixed mode cluster and you need to register to another cluster then the CTL file needs to be deleted. Location
of the CTLFile.tlv below.
o XP: C:\Documents and Settings\<username>\Application Data\Cisco\Unified Communications\Client
Services Framework\Security\sec\CTLFile.tlv
o Vista: C:\Users\<username>\AppData\Roaming\Unified Communications\Client Services
Framework\Security\sec\CTLFile.tlv
 Cisco UC Integration ™ For Microsoft Office Communicator causes high CPU with old video drivers.
o Condition: High CPU caused due to old drivers for NVIDIA Quadro FX 570M video card.
o Workaround: Upgrade NVIDIA drivers to version 6.14.11.7715 or above to fix this issue.
 Cisco UC Integration ™ For Microsoft Office Communicator DTMF doesn’t function properly in Cisco UC
Integration ™ For Microsoft Office Communicator Softphone mode and MP6.0
o Condition: Cisco UC Integration ™ For Microsoft Office Communicator registered to CUCM7.X cluster
in softphone mode and MP6.0 is on CUCM6.X cluster, ICT between MP7.0 and MP6.0 cluster.
o Workaround: Use Cisco UC Integration ™ For Microsoft Office Communicator is deskphone mode.
 When on a active call using Cisco UC Integration ™ For Microsoft Office Communicator and if a user tries to
bring-up the list of devices from “Tools -> Select Device for Conversation Pane” user receives error as “There
was an error performing the operation, there are already pending changes being made. Please try again later”.
o Workaround: Access the options under Tool -> Select Device for Conversation Pane when not on a
call.
 Users receive “No Phone number is associated with this contact” error when they try to place a call by
drag/drop for certain users.
o Condition: Users SIP URI and email address are different.
o Workaround: Either set the SIP URI and email address to be the same or use right-click on contact use
“Place a call” option. This is fixed in FCS build.
 Accessibility – Full Support for accessibility will be in the FCS Drop.
 CUCM 6.1(3) Conferencing.
o Softphone Conferencing – User will only see ‘Conference’ as a participant in the roster.
 Cisco UC Integration ™ For Microsoft Office Communicator user-id login is case sensitive.
9 Beta DRAFT - CISCO CONFIDENTIAL 9

o The CUCM User Page login is not case sensitive but Cisco UC Integration ™ For Microsoft Office
Communicator login uses CCMCIP service to get the list devices and this process is case sensitive.
o Solution: Match the user-id case with the case in CUCM.
o Fix: This defect has been fixed in later releases of CUCM.
 Partial support for Multi-line configurations
o If a phone is configured for multiple lines only a single line can be controlled by Cisco UC Integration ™
For Microsoft Office Communicator
o The controlled line is the first line in the list of line returned by the CTI service of CUCM.
 NOTE: To change the controlled line in non-partitioned scenarios (ie line that have different
DNs) see workaround in Addendum II
 NOTE: For partitioned scenarios (ie the DN is the same on both lines) no workaround is
available. Support for this will be added in future releases of Cisco UC Integration ™ For
Microsoft Office Communicator.

OCS R2 and “On the Phone” Custom presence status

Below steps are required to enable “On the Phone” custom presence status for OCS R2 clients.
o Host/Post Cisco-presence-states-config.xml file on an https location, this file can be posted on OCS
Server itself or at any https server location. This file contains the custom presence status “On the
Phone” defined.
o The cisco-presence-states-config.xml file to put on the server can be found, on a PC with CUCIMOC
installed, in the “Cisco Systems\CUCIMOC\config\presence” subdirectory of the “All Users” profile
which is typically located:
o On Windows Vista at “C:\ProgramData\Cisco Systems\CUCIMOC\config\presence”
o On Windows XP at “C:\Documents and Settings\All Users\Cisco
Systems\CUCIMOC\config\presence”
o The user desktops needs to be updated with the server location of the Cisco-presence-states-
config.xml file either via Group Policy or can be updated locally by running the batch file to update
the registry.
o Updating xml file server location using group policy - For more information on configuring Microsoft
Office Communicator Policies please refer to the “Microsoft Office Communications Server 2007 R2
Client Group Policy Documentation” which can be found at:
o http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=5D6F4B90-6980-430B-9F97-
FFADBC07B7A9&displaylang=en
o Updating xml file server location using BAT file – Please download the following BAT file
On_the_Phone_Status_Config_Sample.bat file and update the https:// server location to match your
configuration, please use FQDN for the server name. The contents of the bat file can be added to your
existing bat file used to update other registry entires.
o In our sample bat file we are using https://OCS.cisco.com/cisco-presence-states-config.xml
for server location, please update the URL to match your configuration.
o Run updated batch file on users’ desktop, along with other Registry entries that are required for
CUCIMOC to be operational.

9
10 Beta DRAFT - CISCO CONFIDENTIAL
Microsoft Office Communicator Related Caveats
 Not able to exit MOC from system tray – “Communicator cannot exit now because it is currently being used by
another process”.
o This should no longer be reproducible, if it happens please report via Forum.
 MOC CPU spikes to 50% and becomes unresponsive when resumed from sleep on Vista machines.
o Solution: Please install the following patch for MOC from MS Website.
o Communicator 2007 hotfix rollup package: December 19, 2008
 MOC allows minimize of Cisco UC Integration ™ For Microsoft Office Communicator tab using the drop-down
arrow on the separation bar between MOC and Cisco UC Integration ™ For Microsoft Office Communicator
tab but can’t maximize.
o Workaround: Users need to manually re-size instead of using the up-arrow to restore the original
settings.
 MOC allows resizing of Cisco UC Integration ™ For Microsoft Office Communicator tab below MOC and Cisco
UC Integration ™ For Microsoft Office Communicator tab completely disappears and no option to
restore/bring-up Cisco UC Integration ™ For Microsoft Office Communicator tab.
o Workaround: Exit out of MOC and re-login to MOC
 AD user phone numbers are not displayed to MOC end users.
o This is a known issue with OCS. Please take a look at the below links for additional information. In
addition to the below links please refer to the information in the training material on OCS Address
book synchronization.
o http://support.microsoft.com/kb/939530
o http://support.microsoft.com/kb/299875/
o http://support.microsoft.com/kb/953113
o http://www.windowsecurity.com/articles/Client-Certificate-Authentication-IIS6.html
 Custom state “On the Phone” does not show as a presence option.
o Solution: Ensure the following registry entry exists & the file it refers to exists.
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator]
“CustomStateURL”=“file:/C:\\Documents and Settings\\All Users\\Cisco Systems/CUCIMOC
/config/presence/cisco-presence-states-config.xml”
o Check the value (if it is set) for EnableSIPHighSecurityMode in the registry.
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator]
“EnableSIPHighSecurityMode”=dword:00000001
o If it is set - change the value to 2. Restart MOC.
 Users will see multiple instances of presentationhost.exe running after hibernate/resume, this does not have
any adverse effects and will be cleared after the next PC restart.
 In rare circumstances Click to Call menus dont appear in Word and Excel 2003
o Solution: In both Word and Excel remove mscoree.dll from the disable list in Help menu->About
window->disable items
 In rare circumstances the CUCIMOC Tab appears blank
o Solution: Download and run the following Microsoft Hotfix:
o http://www.microsoft.com/downloads/details.aspx?FamilyID=adb47247-4e27-4490-a153-
39d8334172d9&displaylang=en

Installation Related Caveats


 Presentation Host crash after installation of Cisco UC Integration for Microsoft Office Communicator as result
Cisco UC Integration for Microsoft Office Communicator doesn’t load within MOC.
11 Beta DRAFT - CISCO CONFIDENTIAL 11

o Solution: Please run the tool posted on MS Website to fix any permission related problems and
relaunch MOC.
o http://www.microsoft.com/downloads/details.aspx?FamilyID=adb47247-4e27-4490-a153-
39d8334172d9&displaylang=en
 “Platform Requirements Not Met” Message in the Cisco UC Integration ™ For Microsoft Office Communicator
Tab area.
o Issue: The required Microsoft .Net 3.5 Service Pack 1 is not installed or is incorrectly installed.
o Steps to Resolve:
Reinstall/repair .Net 3.5 Service Pack 1 using the Cisco UC Integration ™ For Microsoft Office
Communicator installer with the .Exe extension (not .msi)
or
re-install/repair .Net 3.5 Service Pack 1 using the following
http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-
fdaa79a8ac3d/dotnetfx35.exe
 Localization Support.
o For localized presence, Cisco UC Integration ™ For Microsoft Office Communicator depends on MOC
reading a file (cisco-presence-states-config.xml) containing the “localized “On the Phone” string.
o If this file contains certain Locale ID’s MOC will not read the file and custom “On the Phone” presence
will not be available to Cisco UC Integration ™ For Microsoft Office Communicator users
o Currently we are aware of issues with the following Locale variants,
o Spanish – 3082
o Chinese – 2052
o In addition to the above file we will be supplying, in the install folder, two additional files called:
o cisco-presence-states-config-3082.xml
o cisco-presence-states-config-2052.xml
 If using McAfee anti-virus software McAfee 8.0 Patch 16 or McAfee 8.5 patch 5 are the minimum supported
sue to a memory issue with Presentationhost.exe
 In rare circumstances during installation the installer can show high CPU usage while the License Dialog is
displayed. This can slow the scroll down through the License Agreement.
o Solution: Upgrade to Windows Installer 4.5

Features / Deployments Not Supported

 Running Cisco UC Integration ™ For Microsoft Office Communicator on a Virtual Machine within MAC (Apple
Notebook)
 C2Call for MS PPT 2007 is not supported.
 Same Directory Numbers in different Partitions on a IP Phone.
o Cisco UC Integration ™ For Microsoft Office Communicator can’t be configured to control/monitor a
specific Directory Number if a user has same Directory Numbers on more than 1 line on a IP Phone.
 Multi-line is not supported.
o Cisco UC Integration ™ For Microsoft Office Communicator can monitor/control only 1 line on an IP
Phone. Cisco UC Integration ™ For Microsoft Office Communicator can’t control/monitor more than 1
line on a IP Phone.

11
12 Beta DRAFT - CISCO CONFIDENTIAL
4 Resolved Defects

Defect Description
CSCsx07451 Some call states are not shown in conference window
CSCsx12983 Usability: Stronger visual indication of the active call in the Stack
CSCsx14667 Contacts Search should search for user login name & alternative number
CSCsx28738 Call Fwd to alternative device in conference call not updating
CSCsx33200 MOC tab gets wiped when contact is dragged over
CSCsx51425 Hover symbol for contact not consistent on session window
CSCsx56128 Installer should place Call with Edit shortcut in 2 addl locations
CSCsy08826 DTMF does not work to MP in deskphone
CSCsy10856 CUCIMOC:CUCIMOC User Authentication is Case sensitive
CSCsy17354 CUCIMOC process will not start after silent install using Altiris Deploy
CSCsy31722 Mute & Volume control not available for the conference initiator.
CSCsy78065 UI buttons sluggish to open. sometimes takes two clicks.
CSCsy94633 CUCIMOC process causes high CPU when answering inbound call
CSCsz03224 Communication History Timestamp does not show AM or PM
CSCsz03261 Unable to tab from MOC into CUCIMOC Tab
CSCsz04620 CUCIMOC shows participant that has already left conference in DP mode
CSCsz18203 Drop Target Waves do not disappear
CSCsz22541 CUCIMOC dialing different number than specified on conference with
CSCsz22693 CUCIMOC Crash on Resume from Standby
CSCsz22763 CSF does not notify clients when call preservation is active in SP mode
CSCsz23881 Loging into CUCIMOC password field should have focus.
CSCsz24023 User Cannot Signout immeaditely after login.
CSCsz25386 "Error occurred in application you were using" after upgrade
CSCsz31763 Conversation window doesn't show 1-1 call when two particpants remain
CSCsz36297 Right click menu "add to conference" does not work
CSCsz40724 Multiple clicks on call button opens "instruction" window multiple times
CSCsz48824 Right-click on a recent comm. entry shows name instead of "Place a call"
CSCsz49046 Only monitor non-selected devices when selecting a device
CSCsz51888 Call option in outlook persona menu needs to be disabled
CSCsz53167 Installing CUCIMOC does not give you the choice of where to install.
CSCsz53660 DTMF does not function properly with MeetingPlace 6.0
13 Beta DRAFT - CISCO CONFIDENTIAL 13

CSCsz55062 CUCIMOC Crash on Startup


CSCsz55070 Incorrect tab display on "Stop Communications Pane"
CSCsz55090 Unable to switch controlled deskphone device
CSCsz55095 CUCIMOC tab does not expand to MOC horizontal width
CSCsz55623 Comm History Conference records right click menus not working correct.
CSCsz56539 CUCIMOC doesn't work in deskphone mode if speakerphone is disabled
CSCsz56769 With no audio devices,PRTs pop up and CUCIMOC tab never finishes loading
CSCsz58387 In DP mode,disabled volume/mute buttons look v.similar to enabled
CSCsz58475 Conversation History window remains in top corner before maximising
CSCsz59018 Audio interface not updated if disconnected during a call
CSCsz62473 CUCIMOC not passing audio to the USB headset
CSCsz62791 CUCIMOC and CSF Logs at different location and no csf logs in PRT
CSCsz63554 Can't remove failed-joined participant from Conference roaster
CSCsz63796 Increase performance of LDAP Phone Number searches
CSCsz65223 MOC not updated from "Idle" to "On the Phone" when handset of DP lifted
CSCsz66656 Click on dtmf pad gives cursor, but does not collect digits
CSCsz67291 Can't hear incoming audio after USB headset is unplugged
CSCsz67651 Status bar doesn't show CF turned on when restart MOC
CSCsz70099 "Application Deployment Canceled" in tab
CSCsz72601 Cannot drag and drop certain users into drop target. No numbers in CSF
CSCsz76558 Right-Click,Place A Call for an Outlook contact doesn't close MOC window
CSCsz82942 Remove "Do not prompt again" when deleting Comms History Event
CSCsz94802 Call Park in conference not working properly
CSCsz95227 Conversation window not opening after answering toast
CSCsz95277 Signed certificates not known by the java keystore, results in no login
CSCta04377 DND not set in MOC after shared line device enters DND
CSCta04386 DND not cleared in MOC after shared line device exits DND
CSCta05974 Improve query to better match display names and first/last name combos
CSCta05981 Intermittent search failure for users on 2nd and subsequent search DNs
CSCsz07590 Caller Name incorrect when number not in LDAP
CSCta15444 Dispatcher thread suspended in CUCIMOC caused by options window loading in parallel
to call history window
CSCta14742 L10N: On the Phone Presence for Spanish & Chinese
CSCta13211 CUCIMOC exits as a result of no registry key
CSCta11255 Internet Explorer Localisation - Call with Edit doesn't work

13

S-ar putea să vă placă și