Udostępnij za pośrednictwem

  • Artykuł

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.

 

Topic Last Modified: 2015-03-09

This example extends the example in Source-Based Routing. In this case, an administrator wants to define a failover route that can be used in case the Dallas-GW1 is brought down for maintenance, or is unavailable. The following tables illustrate the required configuration change.

Table 1. User Policy

User policy Phone usage

Default Calling Policy

Local

GlobalPSTNHopoff

Redmond Local Policy

RedmondLocal

Dallas Calling Policy

DallasUsers

GlobalPSTNHopoff

Table 2. 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 phone usage if a route for the DallasUsers phone usage is unavailable.