Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
587 Data modules 
17
TEI
Used with 7500 and World Class BRI Data Modules. Appears only if the Fixed 
TEI field is 
y.
MIM Support
Used with 7500 Data Modules. Management Information Message Support. Used 
to support two types of capabilities: MIM endpoint initialization capability (SPID 
support), and other Maintenance/Management capability.
Country Protocol
Used with World Class BRI Data Modules. Enter the protocol that corresponds to 
your supported initialization and codesets. The Country Protocol must match any 
previously-administered endpoint on the same port. The following table lists the 
valid protocol entries.
Endpt Init
Used with 7500 and World Class BRI Data Modules. Endpoint initialization is a 
procedure, required for multipoint operation, by which User Service Order Profile 
(USOP) is associated with an endpoint on the ISDN-BRI. This association is 
made via the Service Profile Identifier (SPID), administered into the system and 
entered into the ISDN-BRI terminal. For a ISDN-BRI terminal to become 
operational in a multipoint configuration, both the administered SPID and the 
Valid entries Usage
0 - 63
Enter a 1- to 2-digit number.
Valid entries Usage
y/n
Enter a 1- to 2-digit number.
Country/Area Protocol
Australia 2
ETSI (Europe) etsi
Japan 3
Singapore 6
United States (Bellcore National ISDN) 1 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
588 Data modules 
17
SPID programmed into the ISDN-BRI terminal must be the same. This means that 
the SPID of the new or re-used terminals must be programmed to match the 
administered SPID value.
SPID
Used with 7500 and World Class BRI Data Modules. Appears only if the Endpt 
Init field is 
y. The Service Profile Identifier (SPID) is a variable parameter of up to 
10 digits. The SPID must be different for all terminals on the ISDN-BRI and from 
the Service SPID. The SPID should always be assigned. If the SPID is not 
assigned for the first ISDN-BRI on a port, any other ISDN-BRI assignment to that 
port is blocked.
MIM Mtce/Mgt
Used with 7500 Data Modules. 
Endpt ID
Used with World Class BRI Data Modules. Appears only if the Endpt Init field is 
y. This field provides for multipoint configuration conformance to the Bellcore 
Terminal Initialization procedures. In these procedures, a multipoint configuration 
requires that the last 2 digits of the Service Profile Identifier (SPID) be between 
00 and 63 and be binary unique for each endpoint. This field, combined with the 
SPID, gives the effective SPID administered into the terminal. Bellcore ISDN-1 
requires that the SPID programmed into the endpoint contain at least 9 digits. (For 
example, if the SPID field is 
1234, and the Endpt ID field is set to 01, then the 
SPID administered on the terminal is 000123401. The three leading zeros are 
necessary to create a 9-digit SPID.)
Valid entries Usage
y/n
Indicates the terminal’s endpoint initialization capability. 
Valid entries Usage
0 - 9999999999
Valid entries Usage
y/n
Entering y indicates the terminal supports MIM Maintenance 
and Management capabilities, other than endpoint 
initialization.
Valid entries Usage
00 - 62
Enter a 2-digit number. Each Endpt ID field must have a 
unique value for each endpoint on the same port. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
589 Date and Time 
17
Date and Time
Use this screen to set the system date and time, to select the daylight savings plan 
number, if any, and to show whether the current time is standard time or daylight 
savings. Settings on this screen affect your switch’s internal clock and timestamp. 
You should update the date and time for a leap year or a system restart after a 
power failure. The correct date and time assure that CDR records are correct. 
CDR does not work until the date and time have been entered. 
Field descriptions for page 1
Screen 68. Date and Time 
Day of the Week
Month
Day of the Month
Valid entries Usage
Sunday 
through SaturdayEnter the current day of the week. The system 
clock uses this as the current day.
Valid entries Usage
January
 through DecemberEnter the current month. The system clock uses 
this as the current month.
Valid entries Usage
1 
to 31Enter the current day of the month. The system 
clock uses this as the current date.
set time
                           DATE AND TIME
DATE
 Day of the Week: _______
Month: ________Day of the Month: __ Year: ____
TIME
Hour: __ Minute: __Second: __ Type: ________________Daylight Savings Rule: _ 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
590 Date and Time 
17
Year
Hour 
The system uses a 24-hour clock. For example, 14:00 is the same as 2:00 p.m.
Minute
Second
This display-only field shows the seconds and cannot be modified. It resets to zero 
when you save the information on this screen.
Ty p e
Daylight Savings Rule
This field displays which daylight savings rule is in use for your system. 
Valid entries Usage
1990
 to 2099Enter the current year. The system clock uses this as the current 
year.
Valid entries Usage
0
 to 23Enter the current hour to be used by the system clock. 
Valid entries Usage
0
 to 59Enter the current minute. The system clock uses this as the 
current minute.
Valid entries Usage
daylight-savings
Enter daylight-savings to indicate daylight savings time is 
in effect.
standardEnter standard to indicate standard time is in effect.
Valid entries Usage
0
 to 15Enter the appropriate rule number. The system clock uses this as 
the current daylight savings rule. These rules are defined on the 
Daylight Savings Rules screen. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
591 Daylight Savings Rules 
17
Related topics
To update the date and time for the change to or from daylight savings time, use 
the Daylight Saving Rule screen. Refer to ‘‘
Establishing daylight savings rules’’ 
on page 7 for instructions on how to set up daylight savings rules.
Daylight Savings Rules
Use this screen to enter up to 15 customized daylight savings rules. You can 
specify the day, month, date, time, and increment each daylight savings rule goes 
into effect and the day, month, date, and time it stops. Rule 0 makes no adjustment 
to the system clock for daylight savings and cannot be modified. Telephone 
displays are affected by these settings.
Field descriptions for page 1
Screen 69. Daylight Savings Rules 
Rule 
This display-only field indicates the daylight savings rule number.
change daylight-savings-rules Page 1 of 2
DAYLIGHT SAVINGS RULES
Rule Change Day Month___Date Time____Increment
0: No Daylight Savings
1: Start: first _________ on or after ________ __ at __:
__ ______Stop:  first _________ on or after ________ __ at __:__
2: Start: first _________ on or after ________ __ at __:__
Stop:  first _________ on or after ________ __ at __:__
3: Start: first _________ on or after ________ __ at __:__
Stop:  first _________ on or after ________ __ at __:__
4: Start: first _________ on or after ________ __ at __:__
Stop:  first _________ on or after ________ __ at __:__
5: Start: first _________ on or after ________ __ at __:__
Stop:  first _________ on or after ________ __ at __:__
6: Start: first _________ on or after ________ __ at __:__
Stop:  first _________ on or after ________ __ at __:__
7: Start: first _________ on or after ________ __ at __:__
Stop:  first _________ on or after ________ __ at __:__ 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
592 Daylight Savings Rules 
17
Change day (Start)
Month (Start)
Date (Start)
Time (Start)
The system uses a 24-hour clock. For example, 14:00 is the same as 2:00 p.m.
Increment (Start)
Change day (Stop)
Valid entries Usage
Sunday 
through 
SaturdayEnter the day of the week you want the clock to move ahead to 
begin daylight savings. If you leave this field blank, the clock 
will change on the exact date entered in the next two fields.
Valid entries Usage
January
 through 
December
Enter the month you want the clock to move ahead to 
begin daylight savings.
Valid entries Usage
0 
to 31Enter the day of the month you want the clock to move ahead to 
begin daylight savings.
Valid entries Usage
0 
to 23Enter the hour you want the clock to move ahead to begin 
daylight savings.
0 to 59Enter the minute you want the clock to move ahead to begin 
daylight savings.
Valid entries Usage
0 
to 23Enter the number of hours you want the clock to move ahead for 
daylight savings and to move back to return to standard time.
0 to 59Enter the number of minutes you want the clock to move ahead 
for daylight savings and to move back to return to standard time.
Valid entries Usage
Sunday 
through 
SaturdayEnter the day of the week you want the clock to move back to 
return to standard time. If you leave this field blank, the clock 
will change on the exact date entered in the next two fields. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
593 Dial Plan Record 
17
Month (Stop)
Date (Stop)
Time (Stop)
The system uses a 24-hour clock. For example, 14:00 is the same as 2:00 p.m.
Dial Plan Record
The Dial Plan is the system’s guide to translating the digits dialed by users. Both 
the Dial Plan Record and the Second Digit Table screens define your system’s dial 
plan.
Screen 70. Dial Plan Record Valid entries Usage
January
 through 
December
Enter the month you want the clock to move back to return to 
standard time.
Valid entries Usage
0 
to 31Enter the date you want the clock to move back to return to 
standard time.
Valid entries Usage
0 
to 23Enter the hour you want the clock to move back to return to 
standard time.
0 to 59Enter the minute you want the clock to move back to return to 
standard time.
change dialplan  Page 1 of 1
                                 DIAL PLAN RECORD 
Local Node Number: _
ETA Node Number: _
          Uniform Dialing Plan: _______ ETA Routing Pattern: _
UDP Extension Search Order: ____________________
FIRST DIGIT TABLE
  First                               Length
  Digit   -1-         -2-         -3-         -4-         -5-         -6-
    1: __________  __________  __________  __________  __________  __________
    2: __________  __________  __________  __________  __________  __________
    3: __________  __________  __________  __________  __________  __________
    4: __________  __________  __________  __________  __________  __________
    5: __________  __________  __________  __________  __________  __________
    6: __________  __________  __________  __________  __________  __________
    7: __________  __________  __________  __________  __________  __________
    8: __________  __________  __________  __________  __________  __________
    9: __________  __________  __________  __________  __________  __________
    0: __________  __________  __________  __________  __________  __________
    *: __________  __________  __________  __________  __________  __________
    #: __________  __________  __________  __________  __________  __________ 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
594 Dial Plan Record 
17
Local Node Number
Enter a number to identify a specific node in a switch network. This entry must 
match the DCS switch node number and the CDR node number if they are 
specified. 
ETA Node Number
Enter the number of the destination switch for Extended Trunk Access (ETA) 
calls. ETA calls are unrecognized numbers you can send to another switch for 
analysis and routing. Such numbers can be Facility Access Codes, Trunk Access 
Codes, or extensions that are not in the UDP table. 
Uniform Dialing Plan
The Uniform Dialing Plan field must be y on the System-Parameters 
Customer-Option screen before you can administer this field. 
The Uniform Dialing Plan is a separate screen that must be administered if 
4-digit 
or 
5-digit is entered in this field. The UDP provides a common 4- or 5-digit dial 
plan that can be shared among a group of switches. Additionally, UDP can be used 
alone to provide uniform 4- or 5-digit dialing between two or more private 
switching systems without ETN, DCS, or Main/Satellite/Tributary configurations.
NOTE:
Local extensions of fewer digits can still be administered, but cannot be 
reached from other switches.
!CAUTION:
Caution: If you change the entry in the Uniform Dialing Plan field, all UDP 
extension codes are lost.
Valid entries Usage
1
–63  Enter the number of a specific node in a network.
blank The field may be left blank if automatic restoration, DCS, and 
CDR are not used.
Valid entries Usage
1
 – 999  Enter the number of a destination switch.
Valid entries Usage
4-digit
   Use a 4-digit Dial Plan.
5-digitUse a 5-digit Dial Plan.
noneNo Uniform Dialing Plan is administered. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
595 Dial Plan Record 
17
See DEFINITY ECS Administration for Network Connectivity for more 
information on Uniform Dial Plans.
ETA Routing Pattern
Enter the number of the routing pattern to reach the destination switch.
UDP Extension Search Order
Appears only when Uniform Dialing Plan is 
4-digit or 5-digit. Specifies the first 
table to search to match a dialed extension.
First Digit Table 
This table defines the dialing plan for your system. The rows in the First Digit 
Table indicate what the system does when the row’s first digit is dialed. The 
columns indicate how long the dialed string will be for each type of call.
The First Digit Table may have any of the following codes:
naar (Automatic Alternate Routing shortcut dialing) — can be entered only 
if the Private Networking field and the AAR/ARS Shortcut Dialing field on 
the System-Parameters Customer-Options screen are both y. When an aar 
entry is used to route a call, the caller has access to all AAR features. Enter 
aar
 in any column but only for first digits 0 through 9 and *. You can enter 
aar only once in a given row, and only 
extension or attd can appear on a 
row with aar. 
Any extension entry that precedes 
aar on the row is considered during digit 
analysis. Any extension entry that follows 
aar on the row cannot be dialed 
directly.  Instead, an AAR number must be dialed, and digit conversion 
must be set up to convert the AAR number into an extension.
An attd entry can only appear in the first column and so attd can never 
follow 
aar. Attendant group extensions can be dialed directly, without an 
access code.
Valid entries Usage
1
 – 254  Enter the number of the ETA routing pattern
Valid entries Usage
local-extensions-first
Search the local Dial Plan first to match a dialed 
extension. 
udp-table-firstSearch the UDP tables for an off-switch (UDP) 
conversion. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Screen reference 
596 Dial Plan Record 
17
nars (Automatic Route Selection shortcut dialing)— can be entered only if 
the ARS field and the AAR/ARS Shortcut Dialing field on the 
System-Parameters Customer-Option screen are both y. When an ars entry 
is used to route a call, the caller has access to all ARS features. Enter ars in 
any column but only for first digits 0 through 9 and *. You can enter ars 
only once in a given row, and only 
extension or attd can appear on a row 
with ars. 
Any extension entry that precedes 
ars on the row is considered during digit 
analysis. Any extension entry that follows 
ars on the row cannot be dialed 
directly.  Instead, an ARS number must be dialed, and digit conversion 
must be set up to convert the ARS number into an extension.
An attd entry can only appear in the first column and so attd can never 
follow ars. Attendant group extensions can be dialed directly, without an 
access code.
nattd (Attendant) — Defines how users call an attendant. Attendant access 
numbers can start with any number from 0 to 9 and contain 1 or more 
digits. If a telephone’s COR restricts the user from originating calls, this 
user cannot access the attendant using this code.
(An attendant group number can also be defined as a two-digit number. The 
first digit is defined as 
misc on the First Digit Table, and the second digit 
(
0 through 9) is defined on the Second Digit Table screen.
ndac (Dial access codes) — Allows you to use trunk access codes (TAC) 
and feature access codes (FAC) in the same range. Dial access codes can 
start with any number from 0–9, * or # and can contain up to 4 digits. 
The system requires that a DAC have the longest length for a first digit in 
the First Digit Table.
You can use the DAC to activate or deactivate a switch feature or to seize a 
trunk from a trunk group, or both. In the first case, the DAC functions as a 
FAC, in the second as a TAC. 
For example, you can define the group 
300–399 for dial access codes, and allow both FAC and TAC in that range.
You can use 4-digit DACs for ordinary trunk access, but they do not work 
for attendant control of trunk groups, trunk-ID buttons, or DCS, and only 
the last 3 digits of the codes can be recorded in CDR records. A DAC must 
be the last item entered in a row when mixed station numbering is used.
nextension (primary extension)
 — Defines extension ranges that can be 
used on your system. Extension can have a first digit of 0 through 9 (* and 
# not allowed) and can be 1 to 5 digits in length. Extension cannot have the 
same first digit as the ARS or AAR feature access code (FAC).
For example, if extensions 400 through 499 are required, enter 
ext at the 
intersection of the -3- column and the First Digit 4 row.