Configuring a Failover Route
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.
Extending the previous example, if an administrator wants to define a failover route that may be used in case the Dallas-GW1 is brought down for maintenance, or is unavailable, the following example illustrates the required configuration change.
Table SEQ Table \* ARABIC 95 User Policy
User Policy | Phone Usage |
---|---|
Default Calling Policy |
Local GlobalPSTNHopoff |
Redmond Local Policy |
RedmondLocal |
Dallas Calling Policy |
DallasUsers GlobalPSTNHopoff |
Table SEQ Table \* ARABIC 96 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 |
In the previous example, a phone usage of GlobalPSTNHopoff is added after the DallasUsers phone usage in the Dallas Calling Policy.
This enables calls with the Dallas Calling policy to use routes that are configured for the GlobalPSTNHopoff if a route for DallasUsers phone usage is unavailable.