Microsoft Lync Server 2010 : Enterprise Voice - Call Admission Control (part 2) - Network Region Links, Network Region Routes

3. Network Region Links

Network region links in Lync Server represent a bandwidth constraint between two network regions or central sites. Because network regions are generally geographically large, these links apply to a number of sites when communicating across regions. For example, a region link might be defined between North America and Europe for an organization. Region links must be created between two regions and might have a bandwidth policy profile associated. The bandwidth policy can be an existing policy or an administrator can create a new policy specifically for the region link.

To create a new network region link, use the following steps:

Alternatively, to use the Lync Server Management Shell to create a network region link, use the following:

New-CSNetworkRegionLink –Identity <Region Link Name> -NetworkRegionID1
<Region 1 ID> -NetworkRegionID2 <Region 2 ID> -BWPolicyProfileID <Bandwidth
policy profile ID>

4. Network Region Routes

A network region route object represents the network path between two regions. This might sound similar to a network region link. However, whereas a region link defines bandwidth on a direct link, a route defines the network path between regions.

In many cases such as a direct connection, there is a 1:1 ratio between region links and region routes, but this might differ when direct links between regions do not exist. For example, consider a scenario where North America and Europe have direct connectivity and Europe and Asia have direct connectivity each with network region links defined.

Those two region routes are straightforward, but a region route between North America and Asia needs to exist, and because calls traverse both region links, it must include each in the definition. In simple terms, a region route is a list of the region links traversed when communicating between two regions. When a call traverses multiple region links, the bandwidth policy of each link is applied.

To create a new network region route, use the following steps:

Alternatively, to use the Lync Server Management Shell to create a network region route, use the following:

New-CSNetworkRegionRoute –Identity <Region Route Name> -NetworkRegionID1
<Region 1 ID> -NetworkRegionID2 <Region 2 ID> -NetworkRegionLinkIDs <Comma
separated list of network region link IDs>

5. Network Intersite Policies

Network intersite policies are used to define a bandwidth policy between two sites in the same region that have a direct link. Similar to a region link, two sites are defined and a bandwidth policy profile is associated with the link. Intersite policies are generally created when two sites have constrained bandwidth to the central site in a region, but also have a direct link between each other without traversing the central site. Network intersite policies can be created only using the Lync Server Management Shell.

For each intersite policy required, use the following syntax:

New-CSNetworkInterSitePolicy –InterNetworkSitePolicyID <Inter-Site Policy
Name> -NetworkSiteID1 <Network Site 1 ID> -NetworkSiteID2 <Network Site 2
ID> -BWPolicyProfileID <Bandwidth Policy Profile ID>

6. Enable Call Admission Control

After configuring all the required objects and links, the final step in the process is to actually enable Call Admission Control.

To enable the feature, use the following steps:

Alternatively, to use the Lync Server Management Shell to create a network region route, use the following:

Set-CSNetworkConfiguration –EnableBandwidthPolicyCheck 1