There are situations where the administrator wants to block calls from the enterprise to certain destinations due to toll-charges (for example, premium numbers such as operator assistance, and in the United States, 1900 and 1411 numbers).
Note that the current release of Office Communications Server does not allow for a configuration that can be used to explicitly block a destination. Calls are blocked implicitly if no matching pattern is found in the Routing table.
For example, if the administrator chooses to block calls to 1900 and 1411 numbers, he or she must define regular expressions that exclude 1900*. The following configuration shows an example of how this can be accomplished, and it does not preclude other ways of accomplishing the same effect.
Table 1. User Policy
User policy | Phone usage |
---|---|
Default Calling Policy |
Local International GlobalPSTNHopoff |
Table 2. Routes
Route name | Number pattern | Phone usage | Gateway |
---|---|---|---|
Redmond Local Route |
^\+1(425|206|253)(\d{7})$ |
Local |
Red-GW1 Red-GW2 |
Dallas Local Route |
^\+1(972|214|469)(\d{7})$ |
Local |
Dallas-GW1 |
NY Local Route |
^\+1(212|646|917)(\d{7})$ |
Local |
NY-GW1 |
Universal Route |
^\+?(?!(1900|1411))(\d*)$ |
GlobalPSTNHopoff |
Red-GW1 Red-GW2 Dallas-GW1 NY-GW1 |
Intl Route |
^\+([2-9])(\d*)$ |
International |
Red-GW1 |
The Universal Route is modified to route all numbers except 1900 or 1411 numbers with an optional leading +.
See Also
Concepts
Routing Configuration ExamplesBasic Routing Setup
Using the Correct Gateway for Local Calls
Limiting Certain Users to Local Numbers
Source-Based Routing
Configuring a Failover Route
Setting Up Basic Routing for Emergency Telephone Numbers
Setting Up an International Gateway
Configuring a New Gateway