After adding all the relevant network information in the previous steps, it is now time to enable CAC.
Enabling CAC must be done for the sites in Topology Builder and globally in CSCP or PowerShell.
The following are the six steps to enable CAC in sites:
Invoke-CsManagementStoreReplication
).Proceed with the following steps to enable CAC globally:
There are a lot of site settings that we can manage through the Set-CsSite
command, but Enable call admission control is not one of them. This task has to be completed in Topology Builder.
The network configuration portion, however, can easily be performed through PowerShellin the following two steps:
Set-CsNetworkConfiguration -EnableBandwidthPolicyCheck 1
As an addition to enabling CAC, it might be a good idea to enable logging as well. This can be done with the following command:
Set-CsBandwidthPolicyServiceConfiguration -EnableLogging $true – LogCleanUpInterval 10.00:00:00 -MaxLogFileSizeMb 10 –MaxTokenLifetime 12:00:00
Consider how much data to keep, and adjust the parameters of this command as needed.
The previous command will enable logging and store data in the fileshare under the application server's PDP
directory, for example, \fileserver.mydomain.comShare1-ApplicationServer-1AppServerFilesPDP
. These files can be viewed in the Lync Resource Tool Kit Bandwidth Utilization Analyzer for further analysis.