This section provides guidance on routing configurations for some common scenarios. This is by no means prescriptive guidance, but is 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.
|The following examples demonstrate how routes are configured in Office Communications Server. For these routes to work, numbers routed to each gateway must be localized on the gateway, using the gateway’s administrative interface.|
The following figure captures the gateway deployment and site topology that is used to illustrate the scenarios in this section.
The following are the characteristics in the sample deployment:
- There are three sites (Redmond, Dallas, and New York).
- The Redmond site has two gateways (Red-GW1, Red-GW2).
- The Dallas site has one gateway (Dallas-GW1).
The example scenarios in this section assume that the normalization rules and location profiles have been configured, and the post-translated number is what is used for the routing decision.
|The examples in this section assume that gateways have been deployed and configured. For details about gateway deployment, see Enterprise Voice Server-Side Components.|
In This Section
Correct Gateway for Local Calls
Users to Local Numbers
Setting Up Basic
Routing for Emergency Telephone Numbers
Setting Up an
to Certain Destination Numbers