Topic Last Modified: 2012-09-21
The following example shows how an administrator can define a failover route for use if the Dallas-GW1 is down for maintenance or is otherwise 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 | Trunk | Gateway |
---|---|---|---|---|
Redmond Local Route |
^\+1(425|206|253)(\d{7})$ |
Local RedmondLocal |
Trunk1 Trunk2 |
Red-GW1 Red-GW2 |
Dallas Local Route |
^\+1(972|214|469)(\d{7})$ |
Local |
Trunk3 |
Dallas-GW1 |
Universal Route |
^\+?(\d*)$ |
GlobalPSTNHopoff |
Trunk1 Trunk2 Trunk3 |
Red-GW1 Red-GW2 Dallas-GW1 |
Dallas Users Route |
^\+?(\d*)$ |
DallasUsers |
Trunk3 |
Dallas-GW1 |
In Table 1, 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.