Microsoft Office Communicator 2007 R2 Release Notes

Last updated January, 200 9

Welcome to the Microsoft® Office Communicator 2007 R2 Release Notes. Refer to this article for information regarding known issues about the Office Communicator 2007 R2 release.

Release Notes

This document contains important information that you should know before you deploy and use the Office Communicator 2007 R2 client.

Office Communicator Office Communicator 2007 R2 Users Dialing In To Conference Auto Attendent Using The Published Phone Number Do Not See User Friendly URI

Issue:     Office Communicator 2007 R2 users who are dialing in to the Conference Auto Attendent 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.

Find Previous Conversations Will Not Work if Office Communicator 2007 R2 and Outlook Are Not Running in the Same Language

Issue:     Find Previous Conversations from Office Communicator 2007 R2 will result in an error if Communicator and 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.

Office Integration For Office Communicator 2007 R2 Users Does Not Work After Installing Office Communications Server 2007 R2 Attendant

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.

Office Communicator Uses Policy Value to Determine Connection Security Mode

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.

Hebrew Characters Cannot be Typed or Pasted Into the Dial Pad

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.

Co-Existing Office Communicator 2007 and Office Communicator 2007 R2 Endpoints May Show Different Counts of Unread Voicemails

Issue:     If you have co-existing Office Communicator 2007 and Office Communicator 2007 R2 endpoints, you may see different counts of unread voicemails.

Resolution:     There are no workarounds for this issue. Please upgrade your co-existing endpoints to Office Communicator 2007 R2.

Office Communicator 2007 and Office Communicator 2007 R2 Coexistence Has Limitations

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.

Search May Not Work on Certain Fields in 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 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:

  • Vista: userprofile%\AppData\Local\Microsoft\Communicator

  • Windows XP: %userprofile%\Local Settings\Application Data\Microsoft\Communicator\<user_sip_address>

Office Communicator 2007 R2 Is Not Compatible with Office Communications Server 2007

Issue:     Office Communicator 2007 R2 users who are logged on to an Office Communications Server 2007 computer observe 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.

Changes to System Default Sound Device While Office Communicator 2007 R2 Is Running Require Communicator to Be Restarted

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 and then restarts it.

Resolution:     Close Communicator, and then restart it.

Audio or Video Device Detection Fails on Windows Vista if the User Plugs the Device into a Different USB Port

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 may not recognize it because Windows gives it a different name. This issue is limited to Windows Vista.

Resolution:     The user can re-attach the device to the port to which it was originally attached.

Custom Sound File Fails to Play in Communicator

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 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.

Office Communicator 2007 R2 Cannot Make VoIP Calls to External Users After Connecting Through a Virtual Private Network (VPN)

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.

Audio/Video Interoperability Between Office Communicator 2005 and Office Communicator 2007 R2 Is Not Supported

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.

Office Communicator Fails to Cancel Installation

Issue:     If a user attempts to cancel installation of Office Communicator 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.

The MUI Pack Is Not Functional if Installed in a Different Folder Than Office Communicator

Issue:     The Multilingual User Interface (MUI) Pack is not functional when it is installed in a different folder than Office Communicator.

Resolution:     Always ensure that the MUI Pack and Office Communicator are installed in the same folder.

Back to Top

Applies To: Communicator 2007 R2



Was this information helpful?

Yes No

How can we improve it?

255 characters remaining

To protect your privacy, please do not include contact information in your feedback. Review our privacy policy.

Thank you for your feedback!

Support resources

Change language