
Route Plan Configuration Requirements 271
■ Manage Patterns — Dial string patterns are used by the VCX call
processor to route calls to the correct destination. See C
onfiguring
Patterns (DIRECTORY).
■ Manage End Points — An end point, identified by IP address, specifies
a device (for example, call processor or gateway) to which calls are
routed. See Managing End Points
.
■ Manage Routes — A route includes one or more end points. See
M
anaging Routes.
■ Manage Route Plans — You can use the Route Plan Wizard to create a
route plan or you can use Route Plans menu options to add, modify, or
delete route plans. See Managing Route Plans
.
■ Manage Source-Based Routing Parameters — You can control call
routing based on the source of a call (an indirect requestor IP address
or the members of a phone profile). Routing can be further controlled
according to date or time of day. See the following topics:
■ Managing Requestors
■ Managing Holidays
■ Managing Week Day Bands
■ Managing Day Time Bands
■ Managing Calendar Bands
■ Manage OutDial Patterns — An OutDial pattern is an optional
component of an end point and specifies how an outbound
destination number is modified. An OutDial pattern can be used to
strip off site-specific access codes. See M
anaging OutDial Patterns.
■ Manage Number Translation — You can control call routing by using a
translation string that matches a destination number and controls the
call according to configured source-based routing parameters (such as
date, time, or requestor IP address). See Configuring Number
Translation Patterns (DIRECTORY).
Route Plan
Configuration
Requirements
This section describes route plan configuration requirements in a VCX
system.
The route plans you need to define depend on your VCX system
configuration. As described in VCX Hardware Configurations
, a VCX
system can be installed on single site or across multiple sites.