Microsoft Office Communicator 2007 R2 Phone Edition Release Notes

Welcome to the Microsoft Office Communicator 2007 R2 Phone Edition Release Notes. Refer to this file for information regarding known issues about the Office Communicator 2007 R2 Phone Edition client.

About This Document

Office Communicator 2007 R2 Phone Edition

Copyright

© 2009 Microsoft Corporation. All rights reserved.

About this Document

This document contains important information that you should know before you deploy and use Microsoft Office Communicator 2007 R2 Phone Edition. For detailed information about Office Communicator 2007 R2 Phone Edition, refer to the documentation included with your installation media.

Back to Top

Office Communicator 2007 R2 Phone Edition

A User in an Existing Audio Conference Cannot Start or Join a Video Call or Conference when Office Communicator 2007 R2 is Paired with Office Communicator 2007 R2 Phone Edition

Issue: When Office Communicator 2007 R2 is paired with Office Communicator 2007 R2 Phone Edition, if users are in an existing audio conference, they cannot start or join a video call or conference in one step.

Resolution: Users can start or join an audio call or conference, and then add video.

Office Communicator 2007 R2 Phone Edition Becomes the Default Audio Device When Attached to a Computer Using a USB Cable

Issue: When Office Communicator 2007 R2 Phone Edition is attached to your computer using the USB cable, it becomes the default audio device for your computer even when another audio device was configured for the computer before Communicator Phone Edition was attached. Although Communicator Phone Edition can still be used as your voice and audio device for Office Communicator and Microsoft Office Live Meeting 2007, you have to configure an audio device other than Communicator Phone Edition to play default audio, such as computer notifications and CD audio.

Resolution:

To configure an audio device other than Communicator Phone Edition for your computer, do the following:

  1. Click Start, and then click Control Panel.
  2. In Control Panel, double-click Sounds and Audio Devices.
  3. On the Audio tab, click the audio device that you want in the Default device list that is under Sound playback.
  4. On the Audio tab, click the audio device that you want in the Default device list that is under Sound recording.
  5. Click OK.

To set up audio and video for Office Communicator 2007 R2 and Communicator Phone Edition, please visit: http://office.microsoft.com/client/helppreview.aspx?AssetID=HA102900421033&ns=COMM2007R2&lcid=1033.

 

Additionally, you can install an update that prevents your computer from setting default audio to any USB audio device that is installed on your computer. This update must be installed before connecting Communicator Phone Edition to your computer using the USB cable. To install the update, please visit: http://support.microsoft.com/kb/935708/en-us.

Certificates Stored on an SSL-Enabled Server That Is Not Integrated with Active Directory Domain Services Must Have Private Root Certificates Manually Installed into AD DS

Issue: Office Communicator Phone Edition 2007 R2 searches for Active Directory objects of the category certificationAuthority. If the search returns any objects, it uses the attribute caCertificate. That attribute is assumed to hold the certificate and the device installs the certificate. If you store certificates on a standalone server that is not integrated with Active Directory Domain Services, but the server where the certificates are located is SSL-enabled, you must manually install the private root certificate into Active Directory Domain Services by using certutil.

Resolution:

To have the Root certification authority (CA) certificate placed in the caCertificate attribute, use the following command:
    certutil -f -dspublish <Root CA certificate in .cer file> RootCA

Note: You cannot manually install the Root CA certificate on the desktop phone. It must be passed using the network.

Office Communicator 2007 R2 Phone Edition Certificate Download Fails at Sign In Using UPN on Private Subnet

Issue: When signing in with a User Principal Name (UPN) on a private subnet using Communicator 2007 R2 Phone Edition, the certificate download may fail. For example, a user attempting to sign into a private subnet with a UPN such as username@<FQDN domain> will receive a certificate download error.

Resolution: Users should sign in using their network login credentials; for example, <FQDN domain>\username.

Office Communications Server 2007 R2 Application Log for the Software Update Service May Log an Event Error During Communicator Phone Edition Updates

Issue:

In some instances during device updating, the Office Communications Server 2007 R2 application log for the Software Update Service may log an event error. As a result, the audit log for device updates might not contain information about the update activity for a few minutes. However, device updates continue to work correctly and the audit logs continue to be generated.

 

Below is a sample event entry from the Office Communications Server 2007 R2 application log for the Software Update Service:

Error while writing audit log System.IO.IOException: The process cannot access the file '\\<your servername>\updates\Logs\Server\Audit\imageUpdates\RequestHandlerAuditLog_<your servername>.log' because it is being used by another process.

Resolution:

There is no workaround for this release.

When Using Communicator Phone Edition and Office Communicator 2007 R2 Integration Feature, Some Remote Access Products May Unlock Your Desk Phone

Issue:

When using the Communicator Phone Edition and Office Communicator 2007 R2 integration feature (USB cable connection), you can automatically unlock your desk phone from your computer. This feature occurs on your computer when Office Communicator 2007 R2 is running while the computer is locked. The computer detects the unlock computer request from the Windows operating system and allows the phone to be unlocked. For this feature to function, it is assumed that you are not using third-party remote access applications on your computer.

If you have installed third-party remote access applications on your computer, the remote access applications can be used to enable users to remotely access the local computer desktop while the computer is locked. In some cases, when a remote user connects to this third-party application, the application that is running locally sends an unlock request to the Windows operating system. As a result, Office Communicator 2007 R2 handles the remote sign-in as though it is a local user unlocking the computer desktop, and the Communicator Phone Edition and Office Communicator 2007 R2 integration feature unlocks the desk phone.

Resolution:

A third-party remote desktop application that is running on a computer that is using the Communicator Phone Edition and Office Communicator 2007 R2 integration feature (USB cable connection) is not supported.

To use third-party remote access desktop applications, you must disable the Communicator Phone Edition and Office Communicator 2007 R2 integration feature. To disable this feature, do the following:

  1. Disconnect the USB cable between your computer and the desk phone.
  2. In the Office Communicator title bar, click the Menu button.
  3. Point to Tools, click Set up Audio and Video, and then follow the instructions in Set Up Audio and Video, and disable Office Communicator Phone.

Potential Issue When Communicator Phone Edition Attempts to Discover and Install the Root CA Certificate During User Log-In

Issue:

An issue occurs when Communicator Phone Edition attempts to discover and install the Root CA Certificate during user logon for the following situation:

If the search for Active Directory objects of category certificationAuthority does not return any objects or there are empty caCertificate attributes, the device searches for Active Directory objects of category pKIEnrollmentService in the configuration naming context.

Such objects exist if Certificate AutoEnrollment has been enabled in Active Directory. If the search returns any objects, it uses the dNSHostName attribute returned to reference the CA and then uses the Web interface of the Microsoft Certificates Service to retrieve the Root CA certificate using the HTTP GET command http://<dNSHostname>/certsrv/certnew.p7b?ReqID=CACert&Renewal=-1&Enc=b64.

The Web Service call to dNSHostname functions only if the CA is a standalone CA. It does not function if it is an Enterprise CA, and the device displays the error message "Cannot validate server certificate" and user sign-in is not possible.

Resolution:

To resolve the above issue, do the following:

  1. Ensure that Active Directory is always available to the device.
  2. Install a standalone CA instead of the Enterprise CA.

To understand how Communicator Phone Edition uses certificates, see the Microsoft Office Communicator 2007 R2 Phone Edition User's Guide at http://go.microsoft.com/fwlink/?LinkId=140496).

Office Communicator 2007 R2 Phone Edition May Not Accept Update from the Update Server

Issue:

When Office Communicator 2007 R2 Phone Edition has build 522.xxx in the active region and the update server has the same build that is in the device's inactive region, an update does not occur. When a device has build 6907.xxx in the active region and the update server has a different version, the update occurs regardless of the version in the inactive region.

If Communicator Phone Edition has build 522.xxx in the active region, it sends an update request and receives a response from the update server, but Communicator Phone Edition does not download this update. The audit logs on the update server may be misleading in this case, because they show that Communicator Phone Edition made an update request and that update information was sent to Communicator Phone Edition, even though the update was not downloaded. Last Update Status on Communicator Phone Edition in this case appears as 200 OK.  

Resolution: Upload a different 522.xxx build to the update server and then have Communicator Phone Edition resend an update request. This time, the version in the active region, the version in the inactive region, and the version on the update server do not match, so Communicator Phone Edition will download the updates. Then roll back the update server to the original version of 522.xxx. Communicator Phone Edition will download the version 522.xxx update because that version is no longer in the inactive region.

Office Communications Server 2007 R2 Blocks Office Communicator Phone Edition 2007 Devices That Use a Version Before 1.0.522.34

Issue:

By default, Office Communications Server 2007 R2 blocks devices using Office Communicator 2007 Phone Edition with a version less than 1.0.522.*. If you attempt to sign in using the device, you receive the following error:

Cannot sign in to Communications Service.  Current version does not work with the available server.  Contact your system administrator.

Before you can sign in using the device, your administrator must first remove the Client Version Filter rule that is blocking the device.

Resolution:

 To remove the rule (for administrators):

  1. Open the Office Communications Server 2007 R2 snap-in.
  2. In the console tree, do one of the following:
  3. Under Client application version control, click the filter with an OCPhone user agent header that blocks for a software version less than 1.0.522.*, and then click Remove.

Office Communicator 2007 Phone Edition Devices Running a Build Before 1.0.522.98 Need a 2-Step Process to Update to the Latest Firmware

Issue:

If an Office Communicator 2007 Phone Edition device uses a build less than 1.0.522.98, you need to perform a 2-step process to update your phone to the latest Office Communicator 2007 R2 Phone Edition. 

Resolution:

(For administrators)

This procedure applies if you have provisioned Office Communicator 2007 R2 Phone Edition on the Update Server.

To update the Office Communicator Phone Edition version

  1. Sign on to Office Communicator Phone Edition.
  2. Update to the intermediate build using one of the following methods:
    a. Power cycle the device for an immediate update.
    b. Leave the device running for 24 hours after signing in and let the update install automatically.
  3. After updating the device to Office Communicator 2007 Phone Edition version 1.0.522.103, calibrate the device, and click Settings, and then click About to check the build version. The version should be 1.0.522.103.
  4. Repeat step 2.
    The device should now be updated to Office Communicator 2007 R2 Phone Edition with a version of 3.5.6907.0 or higher.

Some Versions of Office Communicator Phone Edition and Office Communicator Have Interoperability Issues

Issue:

Problem 1: If you are using a device running a version of Office Communicator Phone Edition that is less than 522.101 with a computer running Office Communicator 2007 R2, and you are signed in to Office Communicator 2007 R2, you cannot update your device to the latest version of Office Communicator Phone Edition because the device repeatedly signs out, preventing it from automatically updating.

Problem 2: If you are using a device running Office Communicator 2007 R2 Phone Edition and are running a version of Office Communicator 2007 that is less than 2.0.6362.129, Office Communicator 2007 signs out repeatedly.

Resolution:

Resolution to problem 1: To allow the automatic update to succeed, sign  out of Office Communicator 2007 R2 on the computer, sign in to the device with Office Communicator 2007 Phone Edition, wait for the device to update, and then sign back in to Office Communicator 2007 R2.

Resolution to problem 2: Upgrade Office Communicator 2007 either to a later version of Office Communicator 2007 (version 2.0.6362.129 or later) or to Office Communicator 2007 R2 (version 3.5.6709.0 or later) to be able to interoperate with Office Communicator 2007 R2 Phone Edition.

 

WMI Settings May Need to Be Changed To Update Office Communicator Phone Edition Devices (For Administrators)

Issue:

For administrators:

If the ExternalUpdatesDownloadURL and ExternalUpdatesStoreURL properties of the Windows Management Instrumentation (WMI) class MSFT_SIPUpdatesServerSetting are set to NULL, you need to use the following procedure to change the settings to update the device.

Resolution:

To update the WMI settings:

  1. Click Start, click Run, and then type wbemtest to open Window Management Instrumentation Tester.
  2. To enable all buttons on the wbemtest user interface, click Connect. In Namespace, type root\cimv2, and then click Enter.
  3. Click Query, and then type the following query, where $poolbackend$ is the back-end database for the pool:
    select * from MSFT_SIPUpdatesServerSetting where backend='$poolbackend$�
  4. Double-click the instance of the class.
  5. Double-click the ExternalUpdatesDownloadURL and ExternalUpdatesStoreURL properties and enter the following values:
    For ExternalUpdatesDownloadURL, type:
    https://**POOL_FQDN**/RequestHandlerExt/ucdevice.upx
    For ExternalUpdatesStoreURL, type:
    https://**POOL_FQDN**/DeviceUpdateFiles_Ext
  6. Click Save Property and then click Save Object.
  7. Verify that the WMI values are updated by querying the class as described in step 3. ExternalUpdatesDownloadURL and ExternalUpdatesStoreURL should be set to a non-NULL value.

Back to Top

Copyright

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.

Back to Top