280 CHAPTER 10: CONFIGURING ROUTING AND TRANSLATION SERVICES
ID for region 1 is 61 and the site ID for region 2 is 62, you would create
two patterns: 61* and 62*. You also need to create a pattern that
identifies calls to the PSTN, for example, 81*.
For instructions on adding a pattern, see Adding Patterns. For
information on dial rules and plans, see Configuring Dial Rules and
Configuring Dial Plans.
6Configure a route plan to associate a pattern and a route.
In this example, you would create three route plans.
One plan associates Route1 with the pattern 61*.
The second plan associates Route1 with the pattern 62*.
The third plan associates Route2 with the pattern 81*.
For instructions, see Adding a Route Plan.
7Configure an OutDial pattern and assign it to an end point associated
with a route.
The OutDial pattern is used to strip off site-specific access codes, which
facilitates call routing.
For instructions, see Managing OutDial Patterns.
Next, create a route on the host regional office to all branch offices
located within its region, as described in the next section.
Configuring a Route from a Regional Office to a Branch Office
In a multi-site system that includes branch offices, a region must include a
route to each of its branches. This enables the regional office to route
calls to branch users. Do not configure routes directly to any branch
offices in a different region. Each region is responsible for routing calls to
its branch offices. This minimizes the number of routes that need to be
configured and maintained.
This example describes how to create routes on a region that point to its
branch offices. The example uses the same simple multi-site system
described in Configuring Routes on a Branch Office:
■R1a identifies the primary call processor in region 1.
■R1b identifies the secondary call processor in region 1.
■R2a identifies the primary call processor in region 2.
■R2b identifies the secondary call processor in region 2.