Routing Configuration Examples
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
This section will provide guidance on routing configuration on some common scenarios, this is by no means a prescriptive guidance, but is just meant to illustrate the flexibility offered by the routing framework.
As mentioned earlier, the routing logic uses the phone usage attribute assigned to the caller as well as the dialed number in order to determine the optimal route, the following scenarios include configuration settings for phone usages for the user and routing table configuration to accomplish the desired routing behavior.
Important
The following examples demonstrate how routes are configured in Communications Server. For these routes to work, numbers routed to each gateway must be localized on the gateway, using the gateways administrative interface.
The following figure captures the gateway deployment and site topology that will be used to illustrate the scenarios in this section:
Figure 35 Gateway deployment and site topology
.gif "d3eae4ab-3a48-48e9-8f98-2a7f1b2df1c0")
The following are the characteristics in the sample deployment:
3 sites (Redmond, Dallas, New York)
Redmond site has 2 gateways (Red-GW1, Red-GW2)
Dallas site has 1 gateway (Dallas-GW1)
The example scenarios in this section assume that the normalization rule and location profiles have been configured, and the post-translated number is what is used for the routing decision.
Note
The examples in this section assume that gateways have been deployed and configured. For the details of gateway deployment, see the Microsoft Office Communications Server 2007 Enterprise Voice Planning and Deployment Guide.