Avaya Communication Manager Administrator's Manual page 264

Routing Outgoing Calls
Figure 112: Locations screen
change locations
Loc. Name
No
1 Main
xxx _______________ _ __:__
xxx _______________ _ __:__
xxx _______________ _ __:__
xxx _______________ _ __:__
2. Type y in the ARS Prefix 1 required for 10-digit NANP calls field.
Our dial plan requires users to dial a 1 before all 10-digit (long distance) NANP calls.
3. Type Chicago in the Name field in the Number 1 row.
Use this field to identify the location.
4. Type +00:00 in the TimeZone Offset field in the Number 1 row.
In our example, the system time and the Chicago location time are the same.
5. Type 1 in the Daylight Savings Rule field in the Number 1 row.
In our example, daylight savings rule 1 applies to U.S. daylight savings time.
Tip:
Use the display daylight-savings-rules command to see what rules
Tip:
have been administered on Communication Manager.
6. Type 312 in the Number Plan Area Code field in the Number 1 row.
In our example, 312 is the local area code for Chicago, location 1.
7. Type New York in the Name field in the Number 2 row.
8. Type -01:00 in the TimeZone Offset field in the Number 2 row.
In our example, subtract one hour from the system clock in Chicago to provide the correct
time for the location in New York.
9. Type 1 in the Daylight Savings Rule field in the Number 2 row.
In our example, daylight savings rule 1 applies to U.S. daylight savings time, and both
locations use the same rule.
10. Type 212 in the NANP field in the Number 2 row.
In our example, 212 is the local area code for New York, location 2.
11. Press Enter to save your changes.
264 Administrator Guide for Avaya Communication Manager
LOCATIONS
ARS Prefix 1 Required For 10-Digit NANP Calls? y
Timezone Daylight- Number ARS Attd Loc.
Offset Savings
Rule
+ 00:00 0
__
__
__
__
Plan FAC FAC Parms. fix
Area
Code
___ ____ ____ __
___ ____ ____ __
___ ____ ____ __
___ ____ ____ __
Page 1 of 1
Pre- Foreign
Domain
Route
Pattern
____ _______
____ _______
____ _______
____ _______