This article has been archived. It is offered "as is" and will no longer be updated.
This article describes the Communicator Mobile 2007 R2 issues that are fixed in the Communicator Mobile 2007 R2 update that is dated July 2010.
Issues that this hotfix package fixes
Provides home screen support for new home screens in Windows Mobile 6.5+ phones.
Provides integration within the phone dialer for Windows Mobile 6.5+ phones.
Enables Communicator Mobile 2007 R2 to recognize when the phone is roaming and by default prevents Communicator Mobile 2007 R2 from signing in to roaming networks.
Provides additional support for joining conference calls from a Windows Mobile appointment. To do this, press Menu, and then press Join Conference.
Lets users log on by using a user name in the firstname.lastname@example.org format, in addition to the domain\user format.
Enables the functionality by which callbacks are now automatically accepted when the user uses the Call via Work option.
Resolves the problem in which the Microsoft Installer (.msi) installation fails on a Windows XP Service Pack 3 (SP3)-based computer. In this situation, users should install Communicator Mobile 2007 R2 by using a (.cab) installation.
Fixes the problem in which AT&T FUZE devices that are set for a High-Speed Downlink Packet Access (HSDPA) connection cannot handle voice and data at the same time. In this situation, calls that use the Call via Work option fail unless the device is reverted to 3rd Generation (3G) by disabling HSDPA.
End User License Agreement (EULA) update to allow OEMs pre-install Communicator Mobile 2007 R2 in addition to Standalone Web downloads.
Note This fix is available in all of the localized versions of Communicator Mobile 2007 R2 that are released.
Release Date: July 2010
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
There are no prerequisites for installing this hotfix.
You do not have to restart the computer after you apply this hotfix.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issue that listed in this article.
The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Build Number: 6906.29.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates