Script

This example extends the simple example from Basic Routing Setup. If administrators want to configure the routes so that calls that are local to the context of the gateway are routed via that gateway, and other calls are routed through any of the gateways, the following configuration enables that scenario.

Table 1. User Policy

User policy	Phone usage
Default Calling Policy	Local 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
Universal Route	^\+?(\d*)$	GlobalPSTNHopoff	Red-GW1 Red-GW2 Dallas-GW1

• In this example, all users are assigned the Default Calling Policy.
  
  
• The policy has two phone usage attributes, Local and GlobalPSTNHopoff. For any number dialed by users who have this policy, a route that matches the Local phone usage attribute is sought before a match with a route that has the GlobalPSTNHopoff phone usage attribute is attempted.
  
  
• Redmond Local Route: This route will be used for calls made to a number that starts with +1 followed by either 425, 206, or 253, followed by seven digits, for users with a phone usage of Local.
  
  
• Dallas Local Route: This route will be used for calls made to a number that starts with +1 followed by either 972, 214, or 469, followed by seven digits, for users with a phone usage of Local.
  
  

Examples:

• Calls made to +1425555 0100 are routed using either Red-GW1 or Red-GW2 (Redmond Local Route).
  
  
• Calls made to +1214555 0100 are routed using Dallas-GW1 (Dallas Local Route).
  
  
• Calls made to +1203555 0100 are routed using either Red-GW1, Red-GW2, or Dallas-GW1 (Universal Route).
  
  
• If Dallas-GW1 is unavailable, calls made to +1214555 0100 are routed using the Universal Route (based on the GlobalPSTNHopoff phone usage).
  
  

See Also