Share via

  • Article

Communicator Mobile for Windows Mobile

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

Office Communicator Mobile provides instant messaging (IM), enhanced presence, and telephony for users in your organization who are connecting from a smartphone or Windows Professional mobile device. Mobile devices enable users to extend the reach of Office Communications Server 2007 R2. This topic describes planning considerations for Office Communicator Mobile that include identifying prerequisites and technical requirements, Office Communications Server components required, and deployment guidance.

Mobile Device Prerequisites

A Windows Mobile-powered device must meet the following requirements to support Office Communicator Mobile:

  • Runs either Windows Mobile 6.0 or Windows Mobile 6.1.

  • Has 12 MB of available disk space.

  • Has a voice and data plan from your carrier.

In addition, the computer you use to install Office Communicator Mobile must meet the following requirements:

Required Server Components

The following list describes the Office Communications Server components that are required to implement Office Communicator Mobile:

  • Office Communications Server 2007 R2. Office Communicator Mobile requires a deployment of Office Communications Server 2007 R2. Previous versions of Office Communications Server must be upgraded to Office Communications Server 2007 R2 to support Office Communicator Mobile.

  • PSTN Gateway. A PSTN gateway is used to perform protocol conversions between the public switched telephone network (PSTN) and Office Communications Server 2007 R2.

  • Reverse Proxy. A reverse proxy is typically used in front of Web servers and presents a single interface to clients. It is also used to balance the load on a Web server farm.

  • Mediation Server. A Mediation Server provides signaling and media translation between Office Communications Server 2007 R2 Enterprise Voice infrastructure and the PSTN or a PBX. The Mediation Server is hosted inside the corporate firewall and is typically placed between the Office Communications Server environment and the Media Gateway.

  • Voice Mail Configuration. The Office Communicator Mobile user account must be configured with an Exchange mailbox and be enabled for Enterprise Voice.

  • Outside Voice Control. Outside Voice Control is a unified communications application that is automatically installed on each Office Communications Server 2007 R2 Front End Server in an Enterprise pool and on every Standard Edition server.

  • Exchange Client Access Server. The Client Access server role supports the Microsoft Outlook Web Access and Microsoft Exchange ActiveSync client applications and the Post Office Protocol version 3 (POP3) and Internet Message Access Protocol version 4rev1 (IMAP4) protocols. The Client Access server role accepts connections to your Exchange 2007 server from a variety of different clients, including mobile devices. The Client Access server role is required in every Exchange Server 2007 organization.

  • Exchange Unified Messaging deployment. Microsoft Exchange Server Unified Messaging (UM) integrates with Office Communications Server 2007 R2 to offer voice mail functionality.

  • Address Book Server deployment. The Address Book Server is an integral component of the Office Communications Server 2007 R2 Front End Server and is installed along with other server components. One of the Address Book Server’s primary tasks is to update search results for Communicator Mobile for Windows Mobile clients by writing global address list information from the RTC database to the Office Communications Server Address Book database (RTCAb).

  • Address Book Web Query Service configured. The Address Book Web Query Service provides global address list information from the Office Communications Server Address Book database to Communicator Mobile for Windows Mobile clients.

Technical Requirements

Before you deploy Office Communicator Mobile, it is important that you understand the deployment requirements on both the server and the mobile device.

Server Requirements

  • Office Communicator Mobile uses the same Enhanced Presence Model used by Office Communicator and Office Communications Server 2007 R2. For details about the server requirements, see Communicator.

  • Before you can begin using Outside Voice Control, you must install and activate the Outside Voice Control application. For details about the Outside Voice Control application, see Outside Voice Control.

  • Before adding contacts from Active Directory Domain Services to your mobile device, in WMI, msft_sipaddressbooksetting class, set WebServiceEnabled equal to true. For details about how to do this, see ”Using WMI to Configure Address Book Server Settings” in the Microsoft Office Communications Server 2007 documentation at https://go.microsoft.com/fwlink/?LinkID=136340

Client Requirements

  • Install certificates.

    The CA certificate chain for the Office Communications Server 2007 R2 deployment must be downloaded and installed to the certificate store of the mobile device. The root certificates for many popular CAs are included on the mobile device.

  • Confirm that installation is not to a storage card.

    Office Communicator Mobile does not support installation to a storage card. The installation files can be installed from a storage card, but the disk that holds the installation files must not be a storage card.

  • Upgrade Windows Mobile 5.0 clients to Windows Mobile 6.0 or 6.1.

    Previous versions of the Windows Mobile operating system must be upgraded to version 6.0 or 6.1 prior to installing Office Communicator Mobile.

Deployment Process

The Office Communicator Mobile deployment process is very similar to the Office Communicator deployment process. After a deployment of Office Communications Server 2007 R2 has been completed, Office Communicator Mobile is configured and no additional server configuration is needed. Installation of Office Communicator Mobile can be initiated on the mobile device.

Table 1. Office Communicator Mobile Deployment Process

Phase Steps Permissions Documentation

Pre-Setup tasks

  1. Verify Office Communications Server 2007 R2 deployment.

  2. Determine whether your organization provides a CA.

  3. Install prerequisites.

Administrator

Communicator Mobile for Windows Mobile Installation Prerequisites in Deploying Communiator Mobile for Windows Mobile in the Client Planning and Deployment documentation

Installing Self-Signed Certificates in Deploying Communiator Mobile for Windows Mobile

Install Office Communicator Mobile on phone.

  • Install over the air (OTA)

  • Install using Windows Mobile Device Center.

  • Install from a storage card.

  • Install using ActiveSync 4.5.

Administrator

Installing Communicator Mobile for Windows Mobile over the air (OTA)

Installing Communicator Mobile for Windows Mobile Using ActiveSync 4.5

Installing Communicator Mobile for Windows Mobile using Windows Mobile Device Center

Installing Communicator Mobile for Windows Mobile from a Storage Card
topics in Deploying Communicator Mobile for Windows Mobile

Configure the client.

  1. Configure account settings.

  2. Configure general settings.

  3. Configure server information.

Administrator

Configuring the Client in Deploying Communiator Mobile for Windows Mobile

Test

  1. Test IM and presence.

  2. Test Outside Voice dialing.

  3. Add a contact from AD.

Administrator

Outside Voice Control Architecture in the Technical Overview in the Getting Started documentation

The Microsoft Office Communicator 2007 R2 Getting Started Guide available at https://go.microsoft.com/fwlink/?LinkID=140488