[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-13

Every subnet in your network must be associated with a specific network site. This is because subnet information is used to determine the network site on which an endpoint is located while a new session is being attempted. When the location of each party in a session is known, advanced Enterprise Voice features can apply that information to determine how to handle the call setup or routing.

Important:
All configured public IP addresses of the Audio/Video Edge servers in your deployment must be added to your network configuration settings. These IP addresses are added as subnets with a mask of 32. The associated network site should correspond to the appropriate configured network site. For example, the public IP address corresponding to the A/V Edge server in central site Chicago would have NetworkSiteID Chicago. For more information about public IP addresses, see “Determining Firewall and 50k Port Range Requirements.

For more information about working with network subnets, see the Communications Server Management Shell documentation for the following cmdlets:

Tip:
If you are working with a large number of subnets, we recommend using a comma separated values (CSV) file to associate the subnets to sites. The CSV file must have the following four columns: IPAddress, mask, description, NetworkSiteID.

To associate a subnet with a network site using Management Shell

  1. Open Communications Server Management Shell.

  2. Run the New-CsNetworkSubnet cmdlet to associate a subnet with a network site:

    Copy Code 
    New-CsNetworkSubnet -SubnetID <String> -MaskBits <Int32> -NetworkSiteID <String>

    For example:

    Copy Code 
    New-CsNetworkSubnet -SubnetID 172.11.12.13 - MaskBits 20 -NetworkSiteID Chicago

    In this example, you created an association between the subnet 172.11.12.13 and the network site “Chicago”.

  3. Repeat step 2 for all subnets in your topology.

To associate subnets with network sites by importing a CSV file

  1. Create a CSV file that includes all of the subnets you want to add. For example, create a file named subnet.csv with the following content:

    IPAddress, mask, description, NetworkSiteID

    172.11.12.0, 24, "NA:Subnet in Portland", Portland

    172.11.13.0, 24, "NA:Subnet in Reno", Reno

    172.11.14.0, 25, "EMEA:Subnet in Warsaw", Warsaw

    172.11.15.0, 31, "EMEA:Subnet in Paris", Paris

  2. Open Communications Server Management Shell.

  3. Run the following cmdlet to import subnet.csv, and then store its contents in the Communications Server 2010 management store:

    Copy Code 
    import-csv subnet.csv | foreach {New-CSNCSSubnet  _.IPAddress -MaskBits $_.mask -Description $_.description -NetworkSiteID $_.NetworkSiteID}

To associate a subnet with a network site using Control Panel

  1. Open Communications Server Control Panel.

  2. In the left navigation bar, click Network Configuration.

  3. Click the Subnet navigation button.

  4. Click New.

  5. On the New Subnet page, click IP address, and then type the IP address of the subnet you want to associate with a network site that will employ media bypass.

  6. Click Mask, and then type the bitmask to apply to the subnet.

  7. Click Network site ID, and then type the site ID of the site to which you are adding this subnet.

    Note:
    You can retrieve site IDs for your deployment by running the Get-CsNetworkSite cmdlet. For more information, see the RTCCmdlets.chm or inline help for Communications Server Management Shell.

  8. Optionally, click Description, and then type additional information to describe this subnet.

  9. Click Commit.

Repeat these steps to add other subnets to a network site.