Routing Outgoing Calls
Routing with Multiple Locations
Administrator’s Guide for Avaya Communication Manager
223
November 2003
Related topics
See
Multiple locations
on page 1616 of the Features/Technical Reference chapter for more information
on the Multiple Locations feature.
See
Setting the System Date and Time
on page 47 for more information about how to set your system
clock and specify the daylight savings rule for the location.
See
Establishing Daylight Savings Rules
on page 37 for more information about how to specify the dates
and times of daylight savings rules.
Routing with Multiple Locations
When you set up multiple locations, you can define call routing that covers all locations as well as call
routing specific to each individual location. Use your routing tables to define local routing for 911,
service operators, local operator access, and all local calls for each location. Leave long-distance and
international numbers that apply across all locations on the routing tables with
Location
field set to all.
Before you start
Be sure the
Multiple Locations
field on the
System-Parameters Customer-Options
screen is set to y. If
this field is set to n, contact your Avaya representative for more information.
AAR or ARS must be administered.
•
For AAR, verify that either the
Private Networking
field or the
Uniform Dialing Plan
field is y
on the System-Parameters Customer-Options screen.
•
For ARS, verify that the
ARS
field is y on the System-Parameters Customer-Options screen.
Each cabinet in a server or switch must be assigned a location number. See the Maintenance
documentation for your model for more information.
Instructions
For example, we will use ARS to set up local call routing for two Communication Manager server
locations. Our Chicago server is assigned to location 1, and our New York server is assigned to location
2.
Our example shows a simple local dialing plan. Each location already contains location-specific routing
tables. We’ll use route pattern 1 for local service calls and route pattern 2 for local HNPA calls in the
Chicago location.
Tip:
Create location-specific routing by assigning different route patterns for each location.