ATT System 25 Administration Manual

							Here is an example of the T (target select) command with PDC (Main Menu item 2).
You see:
PDC = 9876 Action = 1 Data = 201
>
You enter T 8765 [ Return ] and see:
> PDC = 8765
Action =
Action Groups
Some action numbers are parts of groups. These groups are sets of closely related system
parameters that need to be changed as a group. For example, when you assign a voice
terminal, you must also assign a PDC. (See the example at the end of this section.) If you
change the data value for an action item and the system prompts you with another action
item, you are administering an action group.
The number of actions may vary from group to group, but no group contains more than five
actions. All action values within a particular group are consecutive. The system continues to
prompt you for the next action item through the last action in that group.
After modifying a parameter that is part of an action group, you must complete the
modifications to the group by entering data values for the remaining action numbers. This
protects System 25 from acting on partially complete data.
NOTE: If you change to an action number outside of the group you are currently in, all the
data values entered for that group remain as they were before you began modifying the
group. In other words, if you leave a group (by selecting an action outside the group) before
entering the last data value for that group, all changes for that group are abandoned.
Here is an example of administering an action group.
You see:
Port = 10408 Action = 1 Data = 0
You enter D 201 [ Return ] and see:
> Data = 201
Port = 10408 Action = 1 Data = 201
>
Port = 10408 Action = 2 Data = 0
> Data =
NOTE: The fourth line of this display demonstrates how the system automatically
brings up the next member of the group.
How to Use the System 2-7 
						

							You enter 6789 [ Return ] and see:
> Data = 6789
Port = 10408 Action = 2 Data = 6789
>
NOTE: There are no more members in this action group, so the system does not
prompt for more data values.
Display Support IDs
The Display Support feature lets you enter an ID (or name) for each PDC, DDC, FPDC, DGC
access code, and trunk, creating a database for use during system administration. For
systems with a Switched Loop Attendant Console (SLAC), it is essential that you enter this
information. For systems with a Direct Trunk Attendant Console (DTAC), entering this
information is optional.
In a SLAC system, the Display Support database provides call information to Attendants on
the SLAC display. Display IDs also provide a convenient way to search for information
during administration. DTAC System Administrators as well may find it helpful to use the
Display Support search functions (see Action numbers 40 through 43 in Chapter 14).
Keep the following parameters in mind when entering Display IDs:
n    The maximum number of Display IDs the system can store is 272.
n    Display IDs can contain 11 characters or less, and must be enclosed in double quotes.
Acceptable characters include any printable ASCII character (including spaces), except the
double quote.
NOTE: Only the first 9 characters are shown on voice terminal displays.
n    To remove a Display ID, you enter two double quotes, with no space in between.
n    When entering a Display ID name, it is recommended that you use the format
“last name,first name”.
Procedures for entering specific Display IDs are included in the applicable administration
procedure chapter.
Lists, Searches, and Port Removal
Lists
Several Main Menu command areas involve administering a group or list. These areas are
DGC, FPDC, Toll Calls Allowed List, and ARS. There are also Night Service Trunk lists
under the Port and PDC Main Menu items.
Each of these areas includes a “display” action that shows the members of the list. When
you select this action, the system displays the first member of the list. To see the next
member in the list, type C or c to continue.
2-8 How to Use the System 
						

							For example, if you select Main Menu item 5 (FPDC) and want to display active FPDCs,
You see:
> Action =
You enter 1 [ Return ] and see:
> Action = 1
c to continue list, anything else to abort
>
FPDC: Action = 1 Data = 6666
>
You enter C and see:
FPDC: Action = 1 Data = 7777
>
You enter C and see:
FPDC: Action = 1 Data = 8888
>
You enter C and see:
FPDC: Action = 1 Data = 9999
>
You enter C and see:
P16: END OF LIST
FPDC: Action = 1 Data = 0
>
NOTE: You may also “abort” the list by typing a, d, or m.
Searches
The Search menu item is similar to the lists described above. However, most types of
searches require at least two steps:
nAction = 1 Data =[data value] to identify the type of search you want.
nAction = 2 Data =[data value] to narrow the range of the search.
nA few search areas require a third step, Action = 3 Data = [data value] to further
narrow the range of search—for example, to just translated or untranslated ports.
When you enter the type of search and the required qualifiers, you begin the actual search by
typing C or c, “commence search”.
How to Use the System 2-9 
						

							Removing Ports
When (under Port or PDC on the Main Menu) you try to remove a port from the system,
there are several kinds of associations you may want to investigate before you remove that
port from the system. These associations (for example, the appearance of a trunk on several
station buttons or an external alert associated with a station) are called blocks. System 25
generates warning messages about these blocks so you do not perform an administration
function that goes beyond your intent. For each type of association, you will see a
warning message. To go on with the action, you respond to the system message
C for continue, any other key for abort. When there are no more associations with a station port
you want to remove, you will see this warning message,
W18: NO MORE BLOCKS.
The system displays this message to prevent you from accidentally removing a port from the
system.
The next section describes system responses, such as warning messages, in more detail.
2-10 How to Use the System 
						

							System Responses
During an administration session, there are occasions when you may enter inappropriate
information at a prompt. While System 25 does not catch all input errors, it does catch many
of them. System 25 has three means of responding to incorrect input.
n    Error messages
n    Print messages
n    Warnings
Error Messages
Error messages appear in the following general form:
Error nnnn[Where nnnn is a number]
aaaaa aaaa[Where aaaaa aaaa is a message]
A second level of help is also available. If you need more information about an error
message, you can type a question mark, “?”, at the next prompt. You will see a second
message in this general form:
Error nnnn[Where nnnn is a number]
bbbbb bbbb[Where bbbbb bbbb is an expanded message]
Consider a specific example. You can only change a station PDC to a number that does not
already exist in the dial plan. For example, say that you attempt to change PDC 1654 to PDC
1653, which is being used elsewhere.
To change a station PDC:
1At the Main Menu prompt, enter 2 to access the PDC
menu.
2At 
PDC = , enter the PDC you want to change, 1654.
3At 
Action = , enter 2 to tell the system you want to enter
a new PDC.
4Type d and at 
Data = , enter the new dial code, 1653.
If you see:
Error 7012
inappropriate request
Data =
that station may already exist.
(Continued)
How to Use the System 2-11 
						

							5To request additional help on this error message, type ?
The second level error message is followed by a new
prompt.
Error 7012
PDC already exists
Data =
The system continues to prompt for correct data.
Print Messages
This kind of message is straightforward—it conveys information. A print message does not
describe an error condition.
A print message appears at the end of certain search lists. For example, if you enter the
Search option (item 8 from the Main Menu) and search the table of most recent system
errors, you see the following message when you reach the end of that list:
P16: END OF LIST
Warning Messages
A warning message gives you the opportunity to reconsider the administration activity you
are about to perform. One of the more vivid possibilities for serious repercussions would be
your command to cold start the system.
A cold start removes all the current translations in the system, installs default translations,
and cancels all calls in progress on the system. The cold start command, which can be issued
from Main Menu item 9 (Save/Restore), produces serious system disruption. (This command
should be used only by qualified Systems Technicians.)
If you issue an administration command to force a system cold start, you see the following
warning message:
W23: YOU ARE ABOUT TO FORCE A COLD START
C for continue, any other key for abori
>
At this point, you can still change your mind and back out of the cold start action by entering
any character except “C”.
2-12 How to Use the System 
						

							Initializing the System
This section outlines the procedure for administering initial system translations (initializing the
system).
To initialize the system, you must know the desired configuration. The System 25
implementation forms contain all the information necessary to initialize the system; they also
form the basis for system Administration Records. These forms should be properly organized
in the Administration Records Binder.
As the system is initialized, it is essential that you write all port assignments on the forms as
the ports are translated. Failure to do this will make future changes and additions very
difficult.
The steps outlined in the “Initialization Sequence” section should be followed in the
sequence indicated to set up the system. Difficulties may arise if this sequence is not
followed.
Default Translations
Two types of cold starts are possible with System 25. They differ in the extent of their
default assignments. A “full default” cold start is usually reserved for an extreme system
disruption, that might result from a damaged system translation tape or from replacing a
memory board.
The other type of cold start is a “limited default” cold start. It assigns only system defaults
(from Menu 4) to the system, leaving port assignments (Menu 1) blank. This type of cold
start may be particularly useful during system initialization, if the dial plan you want to
administer is greatly different from the one System 25 assigns in a full-default cold start. The
next two sections describe these cold starts in more detail. For specific cold start procedures,
see Action=20 under “Administering Tape Save/Restore Operations”.
Full-Default Cold Start
With a full-default cold start, System 25 assigns default dial codes and trunk numbers (see
Table 3-1). As you attempt to assign dial codes to stations and trunks following the steps
outlined in Chapter 4, you may encounter error messages indicating that the numbers/codes
you are trying to assign are already assigned. It may be that the default numbering plan
conflicts with the one you are implementing. If this happens, change the conflicting default
code by first removing the existing dial code, then replacing it with another.
Initializing the System 3-1 
						

							TABLE 3-1 Default Dial Code Assignments
Port
Trunk Numbers (not part of dial plan)
Station Dial Codes:
Multiline voice terminals
Single-Line voice terminals
Data terminals
System Dial Codes:
Trunk Access Codes:
Loop start
Ground start
Tie trunks
Attendant Call Park
Night Service
Modem Request Code
(Pooled Modem)
ARSDefault Code
0001 - 0104
200 - 238
300 - 355
400 - 599
600 - 704
100
101
102
800 - 807
810
820
9
Limited Default Cold Start
If you have many conflicting default codes, you may want to perform a limited default cold
start. This type of cold start does not assign a numbering plan to the system, except for the
800-series numbers and the ARS code listed in Table 3-1. Since the system does not assign
defaults for stations and trunks, it is easier for you to assign numerous new dial codes, since
default-assigned dial codes do not have to be removed before you can add the new codes.
A limited default cold start does assign most of the system defaults from Menu 4, except the
modem request code and Central Office (CO) trunk pool access code. You need to reassign
those codes after a limited default cold start. (See Action=60 and Action=71 in
“Administering System-Wide Options”.)
Unassigned Trunk Ports
It is also important to untranslate (or remove) any unassigned trunk ports on System 25. To
untranslated, follow the procedure for removing a trunk. This tells the system that no facility
is assigned to that port. Since outgoing trunk selection of pooled facilities is made in reverse
order of trunk assignment (last assigned is first selected), default assigned trunks that are not
actually connected to incoming facilities will result in the selection of unconnected port
circuits for outgoing calls. System users will receive a reorder tone when trying to access
such ports. The Circuit Pack (CP) will display a red alarm Light Emitting Diode (LED) and
the attendant console will display a green alarm LED. Then you will have to untranslate the
port.
3-2 Initializing the System 
						

							Initialization Sequence
Begin with a Cold Start
When you administer the initial translations, it is important that you begin from a known
condition. You can establish a known condition by forcing a cold start (Menu 9, Action=20,
Data=1 or 2). As explained in the previous section, a full default cold start (which takes
about 3 minutes) causes the system to check all slots for valid CP types and assign default
translations to all ports (except auxiliary trunk ports). A limited default cold start, which
takes about 30 seconds, causes the system to assign system-menu defaults but no port-
specific translations.
During a full default cold start, the SAT lists all CPs in the system. When the cold start is
complete, every CP (except the Memory and Auxiliary Trunk) should show a green LED; in
addition, the yellow LED on the Service Circuit should be flashing or steady and the CPU
green LED should be flashing. No red LEDs should be on.
When a limited default cold start is complete, the yellow LED on the Service Circuit should
be flashing or steady, the CPU green LED should be flashing, and the green Tone Detector
LED should be steady. No red LEDs should be on.
If you cannot bring your system to the state you want, refer to the System 25 Installation and
Maintenance Manual before proceeding.
To Initialize the System
The implementation forms provide the information you need to complete the administration
procedures in the following chapters and enter initial translations. When you initialize the
system, you should accept default values for all options and parameters not listed on the
implementation forms. These defaults have been chosen to provide good service for most
customers.
Table 3-2 lists the order of administration procedures and implementation forms you need to
initialize the system.
Initializing the System 3-3 
						

							TABLE 3-2 Initialization Sequence
From the information provided on this form,Enter these translations:
1
System Options FormEnter system toll restriction options,
pooled modem options, and other system
options following the procedures in
“Administering System-Wide Options”.
2Toll Calls Allowed Lists FormEnter these lists following the procedures
in “Administering System-Wide Options”
3Floating Personal Dial CodeEnter all FPDCs following the procedure in
List“Administering System-Wide Options”
4System Speed Dialing ListEnter System Speed Dialing numbers
following the procedure in “Administering
System-Wide Options”
5Virtual Facility ListEnter virtual facility codes following the
procedure in “Administering System-Wide
Options”.
6System Barrier Codes FormEnter remote access options following the
procedures in “Administering System-
Wide Options”.
7Trunk FormsAssign all trunk ports and assign each
trunk’s Class of Service following the
procedures in “Administering Trunks”.
Be sure to record port assignments on the
trunk forms.
8Auxiliary Equipment OptionsAssign and set up any special feature
Formsports following the procedures in
“Administering Auxiliary Equipment”.
Again, be sure to record port assignments.
Continued on next page
3-4 Initializing the System