IP Phone User Manual

Route Plan Configuration Requirements 277
For instructions on adding an end point, see Adding End Points.
4 Create three routes.
a Route1 includes the end points created for R1a and R1b.
b Route2 includes the end points created for R2a and R2b.
c Route3 includes the end points created for R3a and R3b
For instructions on adding routes, see Adding Routes
.
5 Create a pattern for each region.
A pattern is a dial string prefix that indicates which regional call processor
should receive a call. You associate a pattern with a route when you
create a route plan.
You can consider a prefix as a site ID. A prefix is created as a dial rule and
added to the dial plan in effect for users at a region. For example, if the
site ID on region 1 is 61, the site ID on region 2 is 62, and the site ID on
region 3 is 63 you would create these patterns: 61*, 62*, and 63*.
For instructions on adding a pattern, see Adding Patterns
. For
information on dial rules and plans, seeConfiguring Dial Rules
and
C
onfiguring Dial Plans.
6 Configure a route plan to associate a pattern and a route.
In this example, you would create a route plan that associates Route1
with the dialing pattern 61*, a route plan that associates Route2 with
the dialing pattern 62*, and a route plan that associates Route3 with the
dialing pattern 63*.
For instructions, see Adding a Route Plan
.
You do not need to perform these steps on a secondary server (in this
example, R1b). Data replication between the primary and secondary
servers ensures that the routing information gets propagated to both
servers in the redundant pair.
At this point, you have two options regarding the route configuration on
the other regional servers:
■ You could perform steps 2 through 6 on the primary servers hosting
R2a and R3a. This would configure all the servers as equals. In this
case, each region includes redundant routes to every other region with
the end points defined as type Call Processor.
■ Allow only R1a to have all of the routing information for the other
regional servers, as configured in steps 2 through 6. In this case, on