© 2009 Microsoft Corporation. All rights reserved.
Issue: If a user changes the System Default sound device through the Windows Control Panel while Office Communicator 2007 R2 is running, the changes will not take effect until the user closes Communicator 2007 R2 and then restarts it.
Resolution: Close Communicator 2007 R2, and then restart it.
Issue: If a user selects a device as the preferred audio or video device for conversations using Office Communicator 2007 R2, and then detaches the device and plugs it into a different USB port, Communicator 2007 R2 may not recognize it because Windows gives it a different name. This issue is limited to Windows Vista.
Resolution: The user can reattach the device to the port to which it was originally attached.
Issue: After a user selects a custom sound to be played by Office Communicator 2007 R2, Communicator does not play the sound. The most common .wav files have a WAVEFORMTEX format. However, there is a WAVEFORMATEXTENSIBLE format that supports higher quality sound and more channels. Communicator 2007 R2 does not support the WAVEFORMATEXTENSIBLE format. Files with the WAVEFORMTEX and WAVEFORMATEXTENSIBLE format have the same extension (.wav), so the user cannot distinguish them by looking at the filename.
Resolution: There is currently no resolution. Users must select .wav files that do not use the WAVFORMATEXTENSIBLE format.
Issue: If a user has both internal and external SIP servers configured and signs in to Office Communicator 2007 R2 from home without using a virtual private network (VPN) and then connects through a VPN, Communicator automatically signs out and signs back in. In this state, the user cannot make VoIP calls because the Media Relay fully qualified domain name (FQDN) cannot be resolved.
Resolution: Sign out manually and sign back in, re-entering the credentials.
Issue: Audio/video interoperability between Office Communicator 2005 and Office Communicator 2007 R2 is not supported.
Resolution:
No workaround is available. Users in the enterprise need to upgrade to Office Communicator 2007 or newer to have audio/video interoperability with Office Communicator 2007 R2.
Issue: Because of a recent change in the policy that allows users to search contacts in their organization by various fields (GAL policy), Office Communicator 2007 R2 may have contact search issues.
Resolution:
Remove the policy key SearchPrefixFlags in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator) and delete the GAL database. The GAL database is in the following folders:
Windows Vista: userprofile%\AppData\Local\Microsoft\Communicator
Windows XP: %userprofile%\Local Settings\Application Data\Microsoft\Communicator\<user_sip_address>\
Issue: If you have co-existing Office Communicator 2007 and Office Communicator 2007 R2 endpoints, you may see different counts of unread voice mails.
Resolution: There are no workarounds for this issue. Please upgrade your co-existing endpoints to Office Communicator 2007 R2.
Issue: Office integration for Office Communicator 2007 R2 users does not work after users install Office Communications Server 2007 R2 Attendant.
Resolution: There is no workaround for this issue. Users must uninstall Office Communications Server 2007 R2 Attendant to restore Office integration.
Issue: If Office Communicator clients are required to connect by using the High Security mode, the Group Policy EnableSIPHighSecurityMode should be set prior to connecting with the server. If you do not set this policy, part of the sign-in process will not use High Security mode.
Resolution:
No workaround is available for this release.
Issue:
In Office Communicator 2007 R2, Hebrew characters cannot be typed or pasted into the dial pad text box.
Resolution:
No workarounds are available for this release.
Issue:
Find Previous Conversations from Office Communicator 2007 R2 result in an error if Communicator and Microsoft Office Outlook are not running in the same language (for example, Communicator in English and Outlook in German).
Resolution:
Run Office Communicator 2007 R2 and Outlook in the same language.
Issue: Office Communicator 2007 R2 users who are dialing in to the Conference Auto Attendant using the published phone number see a GUID for the URI (instead of a friendly URI) in the Conversation window.
Resolution: No workaround is available for this release.
Issue: When a user sets up Call Forwarding rules (Boss Admin or Team Call) from Office Communicator 2007 R2 and tries to log on by using Office Communicator 2007, Office Communicator 2007 stops responding.
Resolution:
Upgrade to Office Communicator 2007 R2 on all devices.
Issue: Office Communicator 2007 R2 users who are logged on to an Office Communications Server 2007 computer see incorrect behavior during incoming calls. For example, clicking "answer call" on the incoming call system alert does not result in an audio conversation, the user gets disabled call control regions, and the call is disconnected after some time.
Resolution: Do not use Office Communicator 2007 R2 with Office Communications Server 2007.
Issue: If a user tries to cancel installation of Office Communicator 2007 R2 after the message "Writing to system registry values" appears, the installation appears to be canceled and the message "Microsoft Office Communicator Setup was not successfully completed" appears. However, the installation is not canceled.
Resolution: No workarounds are available for this release.
Issue: The Multilingual User Interface (MUI) Pack is not functional when it is installed in a different folder than Office Communicator 2007 R2.
Resolution: Always ensure that the MUI Pack and Office Communicator 2007 R2 are installed in the same folder.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Internet Explorer, MSN, Outlook, SQL Server , Windows, Windows Live, and Windows Vista are trademarks of the Microsoft group of companies.
All other trademarks are property of their respective owners.