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.

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.
  
  

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

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.

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

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.