ATT DEFINITY Communications System Generic 1, Generic 3, System Management Instructions Manual

							CHAPTER 5. ADMINISTRATIVE TASK-VOICE TERMINAL
The 7302H01B and the 7303H01B are assigned using the 7303S Voice Terminal form.
The 7305H01B and 7305H02B are assigned using the 7305S Voice Terminal form.
Change Information on a Voice Terminal
The change command allows you to change translations on an existing voice terminal.
l To change information on a voice terminal, enter change station 3600. The system
displays the screen form that contains all the information currently assigned to extension
3600. Once the form appears on the screen, you can delete, add, or change any infor-
mation for that extension, except you cannot change the extension number. To change
the extension number, you must remove the voice terminal and add it back along with the
new extension number, or you can duplicate the voice terminal with a new extension
number. Once duplicated, the old voice terminal can be removed from the system. The
new (duplicated) voice terminal must be assigned a new port number until the old voice
terminal is removed. Press [ENTER] after you make your changes to transmit the
changed information into the system memory.
When the change command is entered, the system checks to determine if the extension number
is assigned. If the number is assigned, the screen displays the appropriate screen form. If the
extension number is not valid, the system responds with Invalid Extension.
The module is automatioally removed when the voice terminal is changed.
Remove Voice Terminal
The remove command is used to delete a voice terminal from the system memory.
The system allows you to remove things in an orderly fashion, which
assures that the system is
properly administered. Code calling items must be removed before the voice terminal can be
removed from translations.
The LWC super-retrievers list, secondary extension groups, and code calling items must be
removed before the voice terminal can be removed from translations.
A station user that is logged in as a CMS agent must be busied out before unplugging the station
to prevent faulty CMS reports.
The voice terminal must be busied out when the voice terminal is removed from the Automatic
Call Distribution (ACD) system.
Note: When a voice terminal that has a display is being removed from the system, the
display should be removed from the form for that voice terminal before the voice ter-
minal is removed from the system.
The 
list groups-of-extension (extension) [print] command provides a list of groups the exten-
sion number belongs to.
l To remove a voice terminal, enter remove station 3600. The system displays the Voice
Terminal form for extension 3600. Either press [ENTER] to remove the voice terminal
from the system, or press [CANCEL] to cancel the request. [CANCEL] should be pressed if
you entered the wrong extension number.
5-4 
						

							CHAPTER 5. ADMINISTRATIVE TASKS-VOICE TERMINAL
Display Information on a Voice Terminal
The display command allows you to look at a Voice Terminal form in the system. You cannot
change, add, or delete anything on the displayed form. If you see something that should be
changed, you must enter a change command such as change station 3600.
l To look at the features assigned to extension 3600, enter display stat ion 3600. The
Voice Terminal form for extension 3600 is displayed on the screen. No changes or addi-
tions can be done using this command. To obtain a printout of the data displayed on the
terminal, enter print or pr at the end of the display command.
Indentify Groups to Which a Voice Terminal Belongs
The System Manager can use the list command to obtain a list of all groups to which a voice ter-
minal belongs. The voice terminal must be removed from these groups before it can be removed
from the system.
The groups are searched and filed in the following order:
l Code Calling Lists
l Leave Word Calling System-Wide Retrievers List
l Secondary Extension Groups
l Data Extension Groups
The duplicate station command allows the user to add up to 16 voice terminals that have basi-
cally the same configuration as the voice terminal(s) being duplicated. Voice terminals are dupli-
cated by entering the command 
duplicate station  [start ] [board
] [count ] [1endpoint]. A brief description for each command variable is given
below.
l extension—is the extension number of the voice terminal to be duplicated.
l start extension—is an optional string that instructs the system to find unassigned exten-
sion numbers for the voice terminal(s) being added.
l board address—is an optional string that inducts the system to find unassigned ports in
the system for the voice terminal(s) being added.
lcount n—is the number of voice terminals to be added (1 to 16). This string also deter-
mines the number of lines that appear on the Duplication Station screen form. For exam-
ple, if a 2 is entered, two lines appear on the form, if 10 is entered, 10 lines will appear
on the form.
Once the command is entered, the Duplication Station screen form shown in Figure 5-1 or 5-2 is
displayed on the administration terminal. Also displayed are the screen forms for the voice termi-
nals being duplicated. Changes to the Voice Terminal screen form can be made, if desired.
The port number, extension number, and name will not be duplicated.
5-5 
						

							CHAPTER 5. ADMINISTRATIVE TASKS-VOICE TERMINAL
STATION
Security
Name
CodeExtPortRoom
JackCable
FIGURE 5-1. Duplication Station Form Without a Data Module
STATION
Security
Code
Data
Ext
Data
NameExtPortNameRoomJackCable
FIGURE 5-2. Duplication Station Form With a Data Module
5-6 
						

							CHAPTER 5. ADMINISTRATIVE TASKS-VOICE TERMINAL
The following steps give a brief example of how to duplicate two 7403D voice terminals.
1.
2.
3.
4.Enter 
duplication station 4000 [start extension 4001] [board] [count 2]
and press [RETURN]. The screen displays the Station Duplication form and the two dupli-
cated Voice Terminal screen forms.
Enter information on the appropriate the Station Duplication screen form.
Change information on the Voice Terminal screen form if required.
Press [ENTER].
 Forms are submitted and the system is placed in the list station mode. A
scan line for each voice terminal added is displayed on the screen prior to being submit-
ted to system translations. After the voice terminals have been listed, the screen
displays:
command successfully complted,
enter command:
5-7 
						

							CHAPTER 5. ADMINISTRATIVE TASKS-VOICE TERMINAL
How to Administer Voice Terminals Without Hardware
Administration Without Hardware (AWOH) provides the ability to administer station forms without
specifying a port location. Stations administered as such will not cause alarm or errors to be
generated when the station is translated but not yet installed. These station types are referred to
as “phantom” stations. The AWOH feature supports the following applications:
l Ability to administer station forms without specifying a port location
l Ability to provide call coverage (induding AUDIX coverage), by use of phantom exten-
sions, for users who do not have stations physically boated on the switch
l Ability to use phantom extensions for Automatic Call Distribution (ACD) Dialed Number
Identification Service (DNIS). This application allows a phantom extension to be admin-
istered on the switch for each call type that needs to be identified to ACD agents. The
phantom extension is either use “Call Forwarded’ (via an attendant console) to an ACD
split, or its coverage path is defined to include the ACD split. The Name field that is
administered for the phantom extension will identify to the ACD agent which service the
caller is attempting to reach, allowing the agent to properly address the caller.
l Ability to store station templates that can later be used with the duplicate station com-
mand when implementing many station forms of the same type in the system.
The primary use of the Administration Without Hardware feature is to streamline system initializa-
tion, major additions, and rearrangements/changes by allowing voice terminal translations to be
entered before the actual ports are assigned. Port assignments can be done at a later time, as
required.
The use of this feature is limited to analog, Digital Communications (DCP) (7400D series of termi-
nals), and hybrid terminal types.
Administration Without Hardware is administered on a per voice terminal basis by the System
Manager. Normal station administration is required, with the exception of entering an 
X in the
Port field to indicate that there is no hardware associated with the station.
Note: This feature is not supported on ISDN-BRI stations or ISDN-BRI data modules.
Appropriate instructions are provided in each of the voice terminal administration instructions
located in the Implementation manual for your system.
5-8 
						

							CHAPTER 5. ADMINISTRATIVE TASK-VOICE TERMINAL
How to Administer Data Modules and Voice Terminal Adjuncts
Data Module Administration
The following types of data modules can be used by the system:
l Recorded Announcement Data Module
l Data Line Data Module (DLDM)
l Digital Terminal Data Module (DTDM)
l Modular Processor Data Module (MPDM)
l Modular Trunk Data Module (MTDM)
l 7400A and 7400B Data Modules
l 7500B Data Module (BRI)
The screen forms used to assign modules are listed below:
l Recorded Announcemont Data Module — has a built-in data module when used in con-
junction with the Netcon data module which allows the system to transfer the recorded
announcements file from the TN750 Annoucementcircuit pack to the system tape and
from the system tape back to the Announcement
circuit pack. This module is assigned
using the Recorded Announcement
Data Module screen form.
l Data Line Data Module — is a data module used to connect EIA-232-C devices to the
system. The DLDM provides direct connection for up to eight ports. This module is
assigned using the DLDM screen form.
l Modular Processor Data Module — is a multipurpose data module configured to provide
the digital switch interface to support various data interface requirements. One screen
form must be completed for each MPDM installed. Enter 
pdm in the Type field.
l Modular Trunk Data Module — is a multipurpose data module configured to provide digi-
tal switch interface to support trunk data requirements. One screen form must be com-
pleted for each MTDM installed. Enter 
tdm in the Type field.
The DTDM screen form must be administered if “y” is entered in the Data Module field for voice
terminals that have a Data Module field. The extension number of a DTDM cannot be changed.
The DTDM must be removed and then added back with a new extension number.
The 7400A and 7400B Data Modules are desktop modules that offer full duplex asynchronous
communications for DCP voice terminals and asynchronous devices such as SMDR and PMS.
The 7400A and 7400B data modules can also be used on the trunk side which provides connec-
tivity to asynchronoushost computers. These modules are assigned using the Data Module form
assigned to the voice terminal that can have this type of module.
5-9 
						

							CHAPTER 5. ADMINISTRATIVE TASKS-VOICE TERMINAL
For the 7500B Data Module, multipoint administration is allowed for terminals with Service Profile
Identification (SPID) initialization capabilities. if the 
duplicate data-module command is used to
add a 7500B and the user wishes to add an SPID value which is different from the extension, the
SPID field must be modified after the Data Extension field is entered or modified.
The following commands can be used:
l
l
l
l
l
l
l
add data-module xxxx (ext. number or “next”)
If next is entered instead of an extension number, the system will automatically select
the next lowest available extension number. This command should not be used when
prefixed extensions have been assigned on the Dial Plan.
change data-module xxxx (ext. number)
displaydata-module xxxx (ext. number) [print]
duplicate data-module xxxx (extension number ofdata-module to be duplicated)
list data-module (starting ext. number) xxxx (count)
remove data-module or station xxxx (ext. number)
status data-module xxxx (extension number)
Hardware Requirements
A Digital Line circuit pack must be installed to avoid alarms before a PDM and Trunk Data
Module (TDM) can be administered. A TN726 Data Line circuit pack is needed for data line-type
data modules. A TN750 circuit pack is needed for the Recorded Annoucement
data module.
5-10 
						

							CHAPTER 6. HARDWARE RECONFIGURATION
CHAPTER 6. HARDWARE RECONFIGURATION
Overview
Before voice terminals, trunks, and data modules can be added to the system, specific types of
circuit pack must already be installed in the cabinet. The System Manager must determine if the
required circuit pack exists in the system, and if a port on the circuit pack is vacant. If a vacant
port is not available, a circuit pack must be installed before the corresponding voice terminal or
trunk can be added.
The System Manager can use the Circuit Pack screen form to assign the circuit packs before
voice terminals, trunks, and data modules can be added to the system.
The system provides a set of commands that is used to display system and circuit pack (board)
configuration. These commands allow the System Manager to list the current system hardware
configuration. From this listing, the System Manager can determine if additional hardware (circuit
packs) is required.
When adding a new circuit pack, the carrier loading procedures in the Implementation manual
must be followed. All items must be entered for the Port Assignment Record.
The following commands are used to list system and circuit pack (board) configurations:
l list configuration all
l list configuration board (3-character board number)
l list configuration station
l list configuration trunk
l list configuration control
l list configuration software-vintage [long]
l list configuration port-network (1-3)
l list configuration carrier 2 character cabinet [1-3], carrier [A-E]
Whenever features are assigned to buttons on voice terminals, the associated button must be
labeled.
6-1 
						

							CHAPTER 6. HARDWARE RECONFIGURATION
Circuit Pack Administration
Circuit pack administration is a capability that allows theSystem Manager to assign circuit packs
to carrier slots before the circuit packs are actually installed in the slots. The circuit packs are
assigned on the Circuit Pack screen form. The form has five pages, one for each of the port car-
riers. Page 1 is for Carrier A, page 2 is for Carrier B, etc.
Before any voice terminals, attendant consoles, trunks, pooled modems, etc., can be assigned to
the system, the correct type of circuit pack must be installed in the appropriate slot or a circuit
pack must be assigned to the slot using the circuit pack administration form. The circuit packs
are assigned to slots using the circuit pack (TN circuit pack number) code.
Once the circuit packs have been assigned to a slot in the carrier, the System Manager can add
the appropriate voice terminals, trunks, etc., to the system.
The System Manager can assign a circuit pack to the system by entering the command change
circuit-pack and inputting the circuit pack code beside the available slot number. Once the circuit
pack code has been assigned, the System Manager can then enter the appropriate port number
on the screen form for the voice terminal, trunks, pooled modem, etc.
If administering without hardware (see “How to Administer Voice Terminals Without Hardware” in
Chapter 5 of this document), enter an X in the Port file on analog, digital, and hybrid voice ter-
minals to indicate that there is no hardwareassociated with the port assignment. This permits
pre-administration of voice terminals that will be implemented at a later time. These voice termi-
nals are referred to as “phantom stations.”
Port assignments can be made at a later time.
The following commands can be used to administer circuit packs. Pressing [HELP]
 provides a list
of circuit pack codes that can be entered on the form.
l display circuit-packs [print]
l change circuit-pack
6-2 
						

							CHAPTER 7. SYSTEM BACKUP FOR DEFINITY G1 AND G3i
CHAPTER 7. SYSTEM BACKUP FOR DEFINITY G1 AND G3i
DEFINlTY G1 and G3i systems use a tape-only backup system with or without a duplication
option. In case of a power failure of ten minutes or more, the system translations can be
restored using the data on the system or backup tape.
Save Translation
To ensure that the tape drive cassette tape contains the most recent copy of the translation data,
the system can automatically save the translation data onto the cassette tape every 24 hours.
Note: Automatic daily backup of the system translation data is controlled by an entry in the
system parameters that is defaulted to “y” (yes), which means the system will
automatically save the translation data every 24 hours.
If many translation data changes are made, it is recommended that the System Manager save
the translation data using the save translation command. This will save the new changes on the
cassette tape without having to wait for the next automatic daily translation backup. If extensive
changes, additions, or deletions are made, translations should be saved more frequently, alter-
nating the two tapes. Then, in case of a power outage, only the data entered since the last
“save” will be lost. See the “Tape Backup” sections of this chapter.
WARNING: It is recommended that “save translations” should be performed after
business hours so dial tone delays will not be encountered.
WARNING:
“save translations” should not be performed if any tape alarm conditions
occur or if this system is having problems.
Save and Restore Recorded Announcements
The recorded announcements in the system can be saved on the system cassette tape by enter-
ing the command 
save announcements spe-active/spe-standby. These commands should
only be used after business hours or when the system is operating during a low usage period.
The system takes about 45 minutes to one hour to transfer the recorded announcements from
the announcement board to the system tape. During this time period, the administration terminal
cannot be used to administer the system until the transfer is complete; however, all other
administration terminals, if provided, are allowed to perform administration procedures.
The recorded announcementsin the system can be restored back into the system memory from
the system tape by entering the command 
restore announcement. The system performs an
audit to make sure that the announcements on the announcementboard match the announce-
ments administered in the switch. If the restore announcements fails in a duplicated system
because of a tape or tape drive failure, the system will alarm the tape drive that didn’t restore and
switch to the standby Switch Processing Element (SPE) provided the standby is operational. The
restore announcements must then be re-entered on the new active SPE to restore the announce-
ments.
7-1