[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-01

A network inter-region route defines the route between a pair of network regions. Each pair of network regions in your call admission control deployment requires a network inter-region route. This enables every network region within the deployment to access every other region.

While region links set bandwidth limitations on the connections between regions, an inter-region route determines which linked path the connection will traverse from one region to another.

For more information about working with network inter-region routes, see the Communications Server Management Shell documentation for the following cmdlets:

In the example topology, network inter-region routes must be defined for each of the three region pairs: North America/EMEA, EMEA/APAC, and North America/APAC.

To create network inter-region routes

  1. Open Communications Server Management Shell.

  2. Run the New-CsNetworkInterRegionRoute cmdlet to define the required routes. For example, run:

    Copy Code
    New-CsNetworkInterRegionRoute -Identity NorthAmerica_EMEA_Route -NetworkRegionID1 NorthAmerica -NetworkRegionID2 EMEA -NetworkRegionLinkIDs "NA_EMEA”
    Copy Code
    New-CsNetworkInterRegionRoute -Identity NorthAmerica_APAC_Route -NetworkRegionID1 NorthAmerica -NetworkRegionID2 APAC -NetworkRegionLinkIDs "NA_EMEA, EMEA_APAC"
    Copy Code
    New-CsNetworkInterRegionRoute -Identity EMEA_APAC_Route -NetworkRegionID1 EMEA -NetworkRegionID2 APAC -NetworkRegionLinkIDs "EMEA_APAC"
    The North America/APAC network inter-region route requires two network region links because there is no direct network region link connecting them.