Source-Based Routing
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.
There are certain situations where the administrator would like to limit the gateway that is used for calls from users from a particular location. The following configuration illustrates how this may be accomplished for a situation where an administrator would like to limit calls from Dallas users to always exit out of the Dallas gateway.
Table SEQ Table \* ARABIC 93 User Policy
| User Policy | Phone Usage |
|---|---|
Default Calling Policy |
Local GlobalPSTNHopoff |
Redmond Local Policy |
RedmondLocal |
Dallas Calling Policy |
DallasUsers |
Table SEQ Table \* ARABIC 94 Routes
| Route Name | Number Pattern | Phone Usage | Gateway |
|---|---|---|---|
Redmond Local Route |
^\+1(425|206|253)(\d{7})$ |
Local RedmondLocal |
Red-GW1 Red-GW2 |
Dallas Local Route |
^\+1(972|214|469)(\d{7})$ |
Local |
Dallas-GW1 |
Universal Route |
^\+?(\d*)$ |
GlobalPSTNHopoff |
Red-GW1 Red-GW2 Dallas-GW1 |
Dallas Users Route |
^\+?(\d*)$ |
DallasUsers |
Dallas-GW1 |
Administrator creates a policy called Dallas Calling Policy and assigns a phone usage of DallasUsers to it.
All users in Dallas are assigned the Dallas Calling Policy.
For a call originated by a user with this policy, since the only route that contains this policy is the Dallas Users Route, Dallas-GW1 is always selected as the egress gateway for all calls.
The previous configuration example does not preclude users from other locations (for example, with Default Calling Policy) from using the gateway located in Dallas.