Security and Configuration Prerequisites for Enterprise Voice
Topic Last Modified: 2012-01-25
Verify that your infrastructure meets the following security, user configuration, and scenario-specific hardware prerequisites.
Administrative Rights 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 rights:
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 Microsoft Lync Server 2010 deployment without opening up unnecessary access to resources. For details about administrative rights, see the Planning for Microsoft Lync Server 2010 documentation.
Managed key infrastructure (MKI) is deployed and configured, using either a Microsoft or a third-party certification authority (CA) infrastructure.
For details about certificate requirements in Lync Server 2010, see Certificate Infrastructure Requirements in the Planning documentation.
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 Lync 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 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 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), a 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:
Install the Mediation Server, as described in Install the Files for Mediation Server, but only if you want to deploy a stand-alone Mediation Server or pool because Mediation Servers are installed as part of the Front End pool or Standard Edition server deployment process when collocated.
Or, begin configuring settings to route calls for Enterprise Voice users, as described in Configuring Trunks and Translation Rules.