[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-02

Verify that your infrastructure meets the following security, user configuration, and scenario-specific hardware prerequisites.

Administrative Permissions and Certificate Infrastructure

Ensure that your environment is configured with the following administrative user groups and certificate infrastructure for use during the Enterprise Voice deployment process.

  • Administrators deploying Enterprise Voice should be members of the RTCUniversalServerAdmins group.

  • Administrators performing the configuration tasks must have adequate permissions:

    • CsVoiceAdministrator: This administrator role can perform voice configuration tasks, manage voice applications, and assign voice policies to end users.

    • CsUserAdministrator: This administrator role can manage user properties, such as enabling Enterprise Voice for a user. This administrator role can also assign per-user policies, with the exception of the archiving policy; move users; and manage common area phones and analog devices.

    • CsAdministrator: This administrator role can perform all of the tasks of CsVoiceAdministrator and CsUserAdministrator.

    Delegation allows more administrators to participate in your Office Communications Server deployment without opening up unnecessary access to resources. For more information about administrative permissions, see the Planning for Microsoft Communications Server 2010 documentation.
  • MKI (Managed Key Infrastructure) is deployed and configured, using either a Microsoft or a third-party certification authority (CA) infrastructure.

    For more information about certificate requirements in Communications Server 2010, see “Certificate Infrastructure Requirements” in the Planning documentation.

User Configuration

If you collocated the Mediation Server with each Front End pool or Standard Edition Server during Front End deployment, user settings necessary for Enterprise Voice were configured automatically during installation of the files for those server roles.

If you are newly deploying the Enterprise Voice workload at this time, before you begin the deployment process, designate a primary phone number for each user who you plan to enable for Enterprise Voice. As the administrator, you are responsible for ensuring that this number is unique. Before implementation, all primary phone numbers must be normalized (correctly formatted) and copied to each user’s Line URI property using Communications Server Control Panel.

For examples of primary phone numbers required for Enterprise Voice deployment, see the “Sample Normalization Rules” section of “Dial Plans and Normalization Rules” in the Planning for Microsoft Communications Server 2010 documentation.

Scenario-Specific Hardware Requirements

Ensure the following hardware is running in your environment only if your Enterprise Voice deployment needs are as described here.

  • If connectivity to the public switched telephone network (PSTN) or Private Branch Exchange (PBX) is through a Time Division Multiplexing (TDM) connection, one or more IP-PSTN gateways are available before you publish your topology during the Enterprise Voice deployment process. If the connection is through a Session Initiation Protocol (SIP) trunk to a Session Border Controller (SBC) at an Internet Telephony Service Provider (ITSP), an IP-PSTN gateway is not required.

  • If you deploy connectivity to the PSTN for a branch site, but the WAN link to the central site is not resilient, a Survivable Branch Appliance is required.

Next Steps: Install Files or Configure PSTN Connectivity

After verifying software and environmental prerequisites for Enterprise Voice, you can use the following content to either a) install the files for Mediation Server, only if you are deploying a standalone Mediation Server or pool, or b) begin configuring settings to route calls for Enterprise Voice users: