This topic describes the components, prerequisites, technical requirements, and overall deployment process for providing enterprise cellular telephony, also known as "outside voice," to the 2007 R2 version of Microsoft Office Communicator Mobile clients in your organization. This topic focuses primarily on the deployment process and requirements for the Outside Voice Control application, without which outside voice would not be possible.

Outside Voice Components

To provide support for outside voice to your organization"s mobile clients, you must deploy the Outside Voice Control application, Enterprise Voice, and Communicator Mobile.

Note:
Because outside voice provides Enterprise Voice functionality to mobile clients, this topic assumes that you have already considered the planning required to deploy Enterprise Voice functionality to other unified communications clients and the planning required to deploy mobile clients and, therefore, does not reiterate those requirements.

Outside Voice Control

The primary component for enabling outside voice for mobile clients is the Outside Voice Control application. 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. The installation and activation process for all unified communications applications, including Outside Voice Control, is integrated into the Office Communications Server server or pool installation and configuration processes. Before you deploy an Office Communications Server Enterprise pool or Standard Edition server, ensure that your IT infrastructure, network, and systems meet the infrastructure requirements. For details, see Enterprise Pools and Standard Edition Serversin the Planning and Architecture documentation.

Communicator Mobile

The clients that can use the functionality provided by Outside Vocie Control are:

  • The 2007 R2 version of Communicator Mobile for Windows.

  • Communicator Mobile for Java.

We strongly recommend that you deploy the Outside Voice Control application before you deploy Communicator Mobile. Communicator Mobile deployment requires that Office Communications Server be deployed internally. Furthermore, clients cannot use the features of Outside Voice Control until the deployment process for both the application and the deployment process for Communicator Mobile have completed.

For details about planning your deployment of Communicator Mobile, including deployment of the Communicator Web Access server, Edge Server, and media gateway, see Communicator Mobile for Windows Mobileand Communicator Mobile for Java.

Note:
Outside Voice Control cannot interoperate with Office Communications Server 2007 Mediation Server, and it requires that you deploy only Office Communications Server 2007 R2 Mediation Servers in the forest.

Deployment Prerequisites

Note:
The Office Communications Server pool creation, pool configuration, and server installation processes are mentioned in this topic to provide context, but the planning and deployment information for those processes are described in detail in other sections of this documentation set. Similarly, the Enterprise Voice and Communicator Mobile deployment processes are mentioned in this topic to provide context, but the planning and deployment information for Enterprise Voice and Communicator Mobile are described in detail in other sections of this documentation set.

Before you can begin using Outside Voice Control, you must install and activate the application by doing one of the following:

  • If you are deploying Outside Voice Control in an Enterprise pool, create a pool, configure the pool, and then add a server to the pool. For details, see the Create the Pool, Configure Pool and Applications, and Add Servers to the Pooltopics in Deploying Office Communications Server 2007 R2 Enterprise Edition in the Deployment documentation.

  • If you are deploying Outside Voice Control on a Standard Edition Server, install a server. For details, see Install Standard Edition Serverin Deploying Office Communications Server 2007 R2 Standard Edition in the Deployment documentation.

Any or all unified communications applications can be activated during the pool configuration or server installation process. If you do not activate Outside Voice Control during your initial deployment of Office Communications Server 2007 R2, you can activate the application later either by doing one of the following:

  • In an Enterprise pool, rerun the Add Servers to the Pool task. For details, see Add Servers to the Poolin the Deploying Office Communications Server 2007 R2 Enterprise Edition documentation.

  • On a Standard Edition server, rerun the Configure Standard Edition Server task. For details, see Configure Standard Edition Serverin the Deploying Office Communications Server 2007 R2 Standard Edition documentation.

  • From the Office Communications Server 2007 R2 snap-in, run the Application Activation Wizard. For details, see Activate an Applicationin Deploying Unified Communications Applications in the Deployment documentation.

Port Requirements

Unified communications application deployment is integrated with the Office Communications Server 2007 R2 deployment process. As a result, the requirements to deploy the application server and to install the applications are the same as those for configuring a pool and adding a Front End Server or installing a Standard Edition server in Office Communications Server 2007 R2. However, the applications do use different default SIP listening ports. If you use a load balancer, ensure that the load balancer is configured with the ports used by any applications that will run in the pool.

The following is the default port allocation for all unified communications applications, but you only need to configure listening ports for the applications you activate.

Table 1. Application Listening Ports

Application Port

Conferencing Attendant

5072

Conferencing Announcement Service

5073

Response Group Service

5071

Outside Voice Control

5074

Note:
All instances of the same application in a pool use the same SIP listening port.

For details about the permissions required to configure a pool, see Configure Pool and Applicationsin the Deploying Office Communications Server 2007 R2 Enterprise Edition documentation.

For details about the permissions required to install and activate a Front End Server, see Add Servers to the Poolin the Deploying Office Communications Server 2007 R2 Enterprise Edition documentation. For details about the permissions required to install and activate a Standard Edition server, see Install Standard Edition Serverin the Deploying Office Communications Server 2007 R2 Standard Edition documentation.

For details about server hardware and software requirements, client hardware and software requirements, infrastructure requirements, and load balancer requirements required to deploy an Office Communications Server Front End Server, see Office Communications Server Infrastructure Requirementsin the Supported Topologies and Infrastructure Requirements documentation.

Deployment Process

The deployment process for Outside Voice Control is similar to other unified communications applications and is described in the following table.

Table 2. Outside Voice Control Application Deployment Process

Phase Steps Permissions Documentation

Install and activate Office Communications Server 2007 R2.

All unified communications applications and the application server are installed by default.

  • In an Enterprise Edition deployment, activate the Outside Voice Control application during the pool configuration process.

  • In a Standard Edition deployment, activate the Outside Voice Control application during the server installation process.

Administrators group

RTCUniversalServerAdmins group

Domain Admins group

  • For an Enterprise pool, the Configure Pool and Applicationsand Add Servers to the Pooltopics in the Deploying Office Communications Server 2007 R2 Enterprise Edition documentation

  • For a Standard Edition server, Install Standard Edition Serverin the Deploying Office Communications Server 2007 R2 Standard Edition documentation

Start the application.

Using the Office Communications Server 2007 R2 snap-in, start the application.

RTCUniversalServerAdmins group

Start an Applicationin the Deploying Unified Communications Applications documentation

Important:
If you are migrating from an earlier deployment of Office Communications Server, all Mediation Servers must be migrated to Office Communications Server 2007 R2 for Outside Voice Control to function properly.

Post-Deployment

To use Outside Voice Control, you must also deploy Enterprise Voice and either the 2007 R2 version of Communicator Mobile for Windows or Communicator Mobile for Java or both. For details, see the following topics:

See Also

Other Resources

Outside Voice Control Architecture
Application Server Architecture