Deployment Checklist for Call Admission Control

Topic Last Modified: 2012-10-08

To plan effectively for call admission control (CAC), you need to consider the following:

Prerequisites for deploying CAC.
Information required for CAC and configuration decisions that you must make in advance of deployment.

Deployment Prerequisites for Call Admission Control

Before you deploy call admission control, you must already have deployed your Lync Server 2013 internal servers, including either a Front End pool or a Standard Edition server.

Information Requirements for Call Admission Control

The following table summarizes the required information for deploying call admission control.

Information Requirements for Call Admission Control Deployment

Information	Summary of Information Required	Documentation
Lync Server capabilities required by your organization	Capabilities to be supported by your organization Capabilities to be enabled for individual users	Defining Your Organization's Requirements for Call Admission Control
Topologies and components to be deployed	CAC related components are automatically installed as part of Lync Server 2013	Defining Your Organization's Requirements for Call Admission Control
System requirements	Hardware requirements Software requirements Collocation requirements	Determining your system requirements
Infrastructure requirements	No specific infrastructure requirements are necessary for CAC	Infrastructure Requirements for Call Admission Control
Network interface requirements	Internal and external interface information Routing information (including information on the NextHop blog at http://go.microsoft.com/fwlink/p/?LinkId=203149, Microsoft Lync Server team’s customer response channel)	Deploying External User Access
Deployment strategy	Deployment sequence Workgroup or domain Security Monitoring and auditing Hardware considerations	Best Practices for Call Admission Control
Deployment process	Prerequisites Information requirements Process and procedures	Configure Call Admission Control