Security and configuration prerequisites for Enterprise Voice in Lync Server 2013
Topic Last Modified: 2012-10-18
Verify that your infrastructure meets the following security, user configuration, and scenario-specific hardware prerequisites.
Administrative Rights and Certificate Infrastructure
Be sure 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.
Note
Delegation enables more administrators to participate in your Lync Server deployment without opening up unnecessary access to resources.
Managed key infrastructure (MKI) is deployed and configured, by using either a Microsoft or a third-party certification authority (CA) infrastructure.
Note
For details about certificate requirements in Lync Server, see Certificate infrastructure requirements for Lync Server 2013 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 Lync Server Control Panel.
Note
For examples of primary phone numbers required for Enterprise Voice deployment, see the Dial plans and normalization rules in Lync Server 2013 section of Dial plans and normalization rules in Lync Server 2013 in the Planning documentation.
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 in Lync Server 2013, 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 in Lync Server 2013.