Microsoft Office Communicator Mobile for Windows Mobile Release Notes

Welcome to the Microsoft Office Communicator Mobile for Windows Mobile Release Notes. Refer to this file for information regarding known issues about the Microsoft Office Communicator Mobile for Windows Mobile client.

About This Document

Communicator Mobile for Windows Mobile


© 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 Mobile for Windows Mobile. For detailed information about Microsoft Office Communicator Mobile for Windows Mobile, refer to the documentation included with your installation media.

Back to Top

Communicator Mobile for Windows Mobile

Communicator Mobile for Windows Mobile Is Not Displayed on the Home Screen by Default for Smartphones

Issue: By default, the Communicator for Windows Mobile home screen plug-in is not displayed on the Smartphone for Windows Mobile 6.x.

Resolution: Smartphone users must enable the home screen plug-in by selecting the Display on Home Screen option from the General tab under Options.

Sign In with Manual Configuration Fails if No Port Is Specified


For Communicator Mobile for Windows Mobile, signing in with Manual Configuration fails if the port number is not specified for the External name from the Server tab under Options.

Resolution: Provide the port number after the server name even if the server is configured for the default port in the format, for example, (for TLS). This will be automatically configured for default ports in a later release.

User Cannot Cancel Call via Work Call


After the Call via Work call has been set up, the user cannot cancel the call.

Resolution: There is no workaround for this release.

Communicator for Windows Mobile Disconnects When Connected to a Computer


Communicator Mobile for Windows Mobile disconnects when connected to a computer.

Resolution: To ensure that Communicator Mobile for Windows Mobile does not log off when your device is synchronized to your desktop, enable Allows data connections when connected to PC in Microsoft ActiveSync or Windows Mobile Device Center.

When Mobile Phone Forwarding Is Enabled, No Indication That Outgoing Single Number Reach Calls Are Forwarded

Issue: If you enable call forwarding on your mobile phone, there is no indication that when placing an outgoing single number reach (SNR) call, it will also be forwarded.

Resolution: Ensure that you have turned off mobile phone call forwarding (in your mobile phone settings), to ensure that outgoing SNR calls arrive on your phone.

After Upgrading Communicator Mobile, the Windows Start Menu Option "All Programs" Is Unavailable

Issue: After upgrading Communicator Mobile on some phones, the All Programs option in the Start menu is unavailable.

Resolution: On some phones, the All Programs option becomes unavailable after installing Communicator Mobile. When this occurs, you must restart the device.

Call via Work Option for Communicator Mobile Contacts That Are Also in the Contact List for Office Communicator Calls SIP URI Only


When you call a number in the Contact List for Communicator Mobile and that number is also in the Contact List for Office Communicator, the Call via Work option calls the SIP URI instead of the number selected.


When making Calls via Work to contacts that you have in Office Communicator, use Communicator Mobile to initiate the call.

When a Communicator Mobile Device Is Tethered to a Computer, Communicator Mobile Fails to Connect

Issue: When a Communicator Mobile device is tethered to the computer through ActiveSync and Communicator Mobile is set to automatic configuration, Communicator Mobile fails to connect.

Resolution: The latest version of ActiveSync does not forward DNS SRV requests. Therefore, automatic configuration does not connect for any non-standard server names. The workaround is to manually set up your SIP server in the setup for Communicator Mobile setup.

Back to Top


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