Toshiba Perception E Ex Digital Pbx Installation And Maintenance Manual

							CHAPTER 3 
DATA INPUT/OUTPUT PROCEDURES 
1. General 
1.01 
Prior to actual system programming, cus- 
tomer data is recorded on special System Record 
Sheets which correspond with the prompts outlined 
in the data block tables contained in this manual 
(see Appendix 1). Afterthese sheets arecompleted 
and after the PERCEPTION, or PERCEPTlONe, 
system is connected to the data terminal (see 
Chapter 2), data can be entered into the system via 
the Data Input Utility Programs. Once the informa- 
tion is input, it can be printed out via Data Output 
Procedures and tested via special Maintenance 
Procedures. The Utility Programs used to program 
and maintain customer data are summarized as 
follows: 
1) Data Input Procedures-used when entering 
or making changes to Customer Data. 
2) Data Output Procedures-used for obtaining 
printouts of the contents of the Customer Data 
memory. 
3) Maintenance Procedures-used when test- 
ing the system. The System FD contains only 
the 
DSYS, DTRF, and TPER maintenance 
programs, while the maintenance FD con- 
tains all other maintenance programs. 
1.02 Within this manual, tables dealing with Data 
input and Data Output Procedures are presented 
collectively under each chapter category of data 
(e.g., System Data, Station Data, etc.). This pro- 
vides a convenient reference to all information that 
deals with a specific type of data. Maintenance 
Procedures, consisting of the Data Dump and 
various test procedures, are grouped into their own 
chapter at the end of this manual. For convenient 
reference, each Utility Program’s location within 
this manual is listed in Table 3-l. 
1.03 Each Utility Program has a4-letter mnemonic 
name that is used to identify it and to call it up from 
the disk on which it is contained. Each program’s 
PROGRAMMING PROCEDURES 
SECTION 200-255-303 
JANUARY 1993 
mnemonic name is included in the listing in Table 3- 
1. Before a Utility Program can be called up, an 
Authorization Procedure must be performed. 
2. Data Input 
2.01 
Before PERCEPTION,~,, system data can 
be input, option selections must be made and then 
listed on the System Record Sheets (see Appendix 
1). The System Record will then serve as a pro- 
gramming guide and installation record. 
2.02 The System Record contains a form for each 
Data Input Utility Program. Each form is identified 
by the Utility Program name and by the program’s 
corresponding mnemonic that is requested by the 
system (for example: System Data Block = 
DSYS 
Program). 
2.03 Data input via a Utility Program is accom- 
plished by responding to the program’s prompts. 
These prompts are listed in their proper order in the 
System Record Sheets. Space is provided to rec- 
ord a response to each prompt. 
2.04 Refer to each Utility Program’s specific in- 
structions for an explanation of the possible re- 
sponses to each prompt. Record each selected 
response on the program’s corresponding System 
Record Sheet. 
2.05 To input new customer data or to change an 
established database, perform the Authorization 
Procedure and then enter the mnemonic name of 
the desired Data Input Utility Program (see Chapter 
4). Refer to the completed System Record Sheets 
and input the required information. 
3. Data Output 
3.01 
To print. out data that is contained in the 
various data blocks of the customer database, 
perform the Authorization Procedure and then en- 
ter the mnemonic name of the desired Data Output 
Utility Program. Within this manual, Data Output 
programs are grouped next to their related Data 
Input Program. For detailed instructions on how to 
print out data, refer to each specific program and 
program table. 
3-I  
						

							t-cays- 
PROGRAMMINGPROCEDURES 
SECTION 200-255-303 
--: 
7-w I( 
JANUARY1993 ., 
~~ .,@23 -I&L -7. 
c. 
TABLE3-1 
UTILITYPROGRAMREFERENCEGUIDE 
DATAINPUTANDOUTPUTPROCEDURES 
TABLE 1 NAME I MNEM.I PAGE 
11-2 1 Print DDIU DB I PDIU 11-6 
11-3 
I Modem Poolina DB I DMDMI 1 l-8 
I Print Modem Poolina DB I PMDMI 11-9 
.:.12-l p Least Cost Routing DB DLC 1 12-1 
12i;2 - &east Cost Routine DB 1 IDLCl 1 12-3 
I26 - &east Cost Routing DB 2 1 DLC2 12-8 
- 12-7 1 Print Least Cost Routing DB 1 PLCR I 12-l 3 
Lodging/Health Care 
Features DB 
I I DHMF 13-2 
13-2 Print Lodging/Health Care 
Features DB PHMF 13-3 
13-3 Message Registration DB DMRD 13-5 
13-4 Print Message Registration DB PMRD 13-7 
14-1 I Speed Dial List DB 1 DSDL 1 14-2 
14-2 I Print Speed Dial List DB 1 PSDL 14-3 
15-1 1 Traffic Measurement DB 1 DTRF 1 15-2 
16-l I Alphanumeric Message DB IDMSG I 16-1 
16-2 
I rnt Alphanumeric Message PMSC 1 6-2 
I I 
I I I 
3%1 @I ACD/MIS DB I DACM I 17-4. 
17-2 I Print ACD/MIS DB 1 PACM 1 17-7 
l&l@ 1 Verifiable Account Codes DB I DVAC I 18-2 
18-2 
I Print Verifiable Account 
Codes DB I I  PVAC 18-4 
IURES 
HNEM.  MAINTENANCEPROCE 
TABLE I NAME 
19-l Backup Memory Check 
Entry Proc. 
19-2 I Data Dump Program 
Ill 
I 
I 
Electronic and Digital 
19-3 - 4 Telephone/Attendant Console 
Test Proc. 
19-5 Peripheral Equipment 
Diagnostic Proc. PAGE 
DMYC 19-1 
DDMP 19-2 
lTRM 
19-4 
TPER 19-11 
NOTE: 
Error codes associated with each data block are listed after each data block table. 
3-2  
						

							PRQGRAMMING PROCEDURES 
SECTION 200-255-304 
FEBRUARY 1992 
CHAPTER 4 
AUTHORIZATION PROCEDURES/UTILITY 
PROGRAM USE 
1. Authorization Procedure 
1 .Ol Before any Utility Program can be called up, 
PERCEPTlONe and PERCEPTlONe, systems 
require an authorization code to be entered. This 
prevents unauthorized tampering with the Cus- 
tomer Database. 
1.02 There are four levels of authorization (each of 
which has a unique 4-digit code that is assigned in 
the system memory). Each authorization level al- 
lows certain input, output, and maintenance proce- 
dures to be performed. When shipped from the 
factory, all levels are assigned 0000. Codes are 
changed with the Authorization Code Change pro- 
cedure (DCHG). 
2. Authorization Level Allowances-Data input 
Procedures 
2.01 The data input activities that are allowed to 
each of the four authorization levels are as follows: 
Level 1: Can do all activities of Levels 2 and 3. 
Can change the 4-digit codes of Levels 1, 2, 3, 
and 4. 
Level 2: Can do all Level 1 activities except change 
or read out codes for Level 1. 
Can change Level 2,3, and 4 codes. 
Level 3: Normally assigned for end user use. 
Can change: 
System Data Block 2 
Class of Service Data Block 
Station Data Block 
Attendant Data Block 
DSS Console Data Block 
Station Message Detail Recording Data Block 
Speed Dial List Data 
Digital Data Interface Unit Data Block 
Modem Pooling Data Block 
Alphanumeric Message Data Block 
Level 4: Normally assigned for ACD Supervisor 
use. 
Can change ACD/MIS Data Block. NOTE: 
No otherauthorization level can access ACD/ 
MIS Data Block. 
3. Authorization Level Allowances-Data Out- 
put Procedures 
3.01 The entrance of the different authorization 
codes permits specific customer data to be$nted. 
The data output activities that are allowed to three 
of the four authorization levels are as follows: 
Levels 1, 2, or 3: Print System Data Block 
Print System Data Block 2 
Print Class Service Data Block 
Print Station Data Block 
Print DSS Console Data Block 
Print SMDR Data Block 
Print Digital Data Interface Data Block 
Print Modem Pooling Data Block 
Print Speed Dial List Data Block 
Print Call Pickup Groups 
Print Hunting Arrangements 
Print Alphanumeric Message Data Block 
Levels 2 or 3 only: Print System Data Block 
Print Access Code Data Block 
Print Message Center Data Block 
Print Trunk Group Data Block 
Print Trunk Data Block 
Print Toll Restriction Data Block 
Print Least Cost Routing Data Block 
Print Lodging/Health Care Features Data Block 
Print Message Registration Data Block 
Pri?t Paging Group Data 
4. Authorization Level Allowances-Mainte- 
nance Procedures 
4.01 The maintenance activities that are allowed 
to three of the four authorization levels are as 
follows: 
Levels 1, 2, or 3: Data Dump Program 
Electronic and Digital Telephone/Attendant 
Console Test 
Levels 1 or 2 only: Backup Memory Check Entry 
Procedure 
Peripheral Equipment Test 
4-1  
						

							PROGRAMMINGPROCEDURES 
SECTION 200-255-304 
FEBRUARY1992 
5. Execution of Authorization Procedure 
5.01 To perform the Authorization Procedure: 
1) 
2) 
3) Plug in and power up the data terminal. 
The system will respond with a copyright and 
then greater than sign (>). 
Press the carriage return [9 key. 
l The system will respond by printing COD 
and will print several characters in the 
spaces to be occupied by your next entry 
(this is done to mask the authorization 
code). 
This masking measure is not effective when  IMPORTANT! 
a CRT is used. Be careful not to leave the 
authorization code displayed on the screen. 
4) Enter the 4-digit authorization code (0000 
default value), followed by a 
q . 
l The system will print: 
ERROR if an invalid code is entered 
(return to Step 2). 
OK if a valid code is entered (proceed to 
request Utility Program). 
6. Utility Program Use 
6.01 After performing the Authorization Procedure 
and receiving an OK response, enter the mne- 
monic of the required Utility Program. 
6.02 After the Utility Program name is entered, the 
program will be loaded from the disk. When the 
loading is complete, the system will prompt REQ for 
Request. 
6.03 Entering data via a Utility Program is a matter 
of responding to the prompts given by the system 
via the data terminal. The prompts and the required 
responses are mnemonics that are usually abbre- 
viations of the actual English word required. 
6.04 If an improper response is made to a prompt, 
the system will respond with an error message. The 
error message will be a “?,, when the error is obvious, but in most cases it will be an alphanu- . . 
mericcode. The alphanumeric code consists of five . . . 
letters (identifying the program) and two numbers 
(identifying the error). Error code lists are provided 
in this manual to explain each error code. 
6.05 Boxes are used to indicate keys on the pro- 
gramming terminal. The m (control) key must 
be held down while simultaneously pressing either 
key. Press the carriage return key 
appears. The following keys are 
available when using Utility Programs (press the 
5 - pycegr each.code): 
I nore lrne entered-the same prompt 
will be repeated. 
mEBackspace will allow you to overwrite the 
W-May be entered at anytime-the system will  previous character(s). 
stoo execution and return to the REQ oromot. 
F-Exits the program-ends the u.se of bne 
utility. The system will respond with SAVE. A ‘Y” 
entry will cause the system to copy all present 
data onto the disk. If more changes are to be 
made, enter “N.” 
NOTE: 
The above key indications are for Texas ln- 
struments Silent 700 series terminals. Other *. 
6.06 When data already exists for a given prompt 
and a change is not required, entering a 
q will 
advance the system to the next prompt without 
changing existing data. 
6.07 Tables 5-1 through 19-5 show the format of 
each Utility Program. Programs are grouped into 
general categorical areas (e.g., System Data, Fea- 
ture Data, etc.). Each Data Output program is 
grouped with its related Data Input program(s). If 
applicable, each data table is followed by a list 
explaining the error codes which pertain to that 
program. Using the appropriate tables as guides, 
enter data that has been previously recorded in the 
System Record Sheets. 
4-2  
						

							CHAPTER 5 
SYSTEM DATA 
1. Authorization Code Change (Table 5-1) 
1 .Ol The DCHG Program changes the authoriza- 
tion codes which are used in the Authorization 
Procedure. 2. 
1.02 To use the DCHG Program: 
Complete the Authorization Procedure (Level 1 
or 2). Enter: 
Enter: DCHGm (in response to the OK prompt). 
The next prompt will be: LiXXXX (Level 1 au- 
thorization code). (XXXX = present code.) 
New L2 code (4 digits) 
q . j 
L3XXXX (Level 3 authorization 
code). 
Enter: 
(XXXX = present code.) (XXXX = present code.) 
New L3 code (4 digits) 
q , 
L4XXXX (Level 4 authorization 
code). 
NOTES: Enter: New L4 code (4 digits) 
q , 
I. If a Level 2 authorization code was given En ten m m (to exit the program). 
PROGRAMMING PROCEDURES 
SECTION 200-255-305 
JANUARY 1993 
above, L 1 willnotbe output. Go to the next 
prompt (L2). 
If a Level 3 authorization code was en- 
tered above, an error message will be 
given, Level 3 cannot change the authori- 
zation codes. 
Enter: New L 1 code (4 digits) a. 
L2XXXX (Level 2 authorization 
code). 
TABLE 5-l 
Procedure - Authorization Code Change 
Authorization Procedure must be completed. If an OK response is received, proceed as follows: 
NOTES: 
1. 
2. a. An error message will be received if Level3 or Level4 was given in the Authorization Procedure. 
6. If Level2 was given in the Authorization Procedure, L 1 will be omitted and the response to CHG 
will be: L2 = XXXX. 
c. XXXX = Present code of the designated level 1 - 4. 
The possible responses are: 
YYYY = 
(9 This new access code will replace the existing XXXX. 
= Carriage Return - the code will not be changed and the system will issue the next 
prompt. 
= 
Ignore line entered. 
= Backspace. 
- Stop printing and return to REQ. 
= Exit program. 
3. Enter: Y or N. 
5-I  
						

							PROGRAMMINGPROCEDURES 
SECTION 200-255-305 
JANUARY1993 
2. System Data Block (Table 5-2) 
2.01 The System Data Block (DSYS Program) 
contains miscellaneous data entries that apply to 
the system as a whole rather than to any individual 
station or trunk. Data is entered as follows: 
REQ (Request)-Indicates that the program has 
loaded. Since data is always present, only the 
CHG response is possible. 
EXP (Expansion Cabinet)-Indicates whether or 
not an expansion cabinet is installed. 
Enter: Y: if an expansion cabinet is installed. 
N: if only the basic cabinet is installed. 
NOTES: 
1. Y must be entered to enable the system to 
provide up to 20 simultaneous confer- 
ences in a cabinet using a second NPRU 
PCB. 
2. If N is entered, then only ten simultaneous 
conferences will be supported. 
NOD (Number of Drives)--Indicates whether one 
or two disk drives are being used. (Two drives 
are used only with D.02 or later software ver- 
sions.) 
Enter: 1: 
;$s& ..q: 
M%LwzG if only a single drive (FDDO) is used. 
if two drives (FDDO and FDDl) are 
used. (The system will not access 
maintenance programs in FDDl if 1 is 
entered, unless the Maintenance FD 
is used in place of the System FD.) 
TOR (Time of Daily Routine)-Specifies the time 
of day that the daily routine task (System Dump) 
will run (listed after the next prompt). 
Enter: 24-hour clock time. 
(For example: 1315 = 1:15 pm.) 
DRT (Daily Routine Task)-Specifies whether or 
not a System Data Dump is to be performed at 
the time specified in response to TOR. 
Enter: DDMP (Data Dump) or NONE. 
TEN (Tenant Service)-Specifies whether or not 
tenant service is to be used. If “Y” is entered, 
incoming trunk calls, dial calls, intercepts, etc. 
will be routed to the proper attendant console 
(Att. #O for Tenant #0, and Att. #l for Tenant #l). 
Tenant designation for each telephone and trunk 
is selected in response to the TEN prompt in the 
5-2 following Data Blocks: Electronic/Digital Tele- 
phone (DEKT Program), Standard Telephone 
(DSTT Program), and Trunk Group (DTGP Pro- 
gram). If “N” is entered, then the attendant 
consoles will operate in the load sharing mode. 
Enter: Y or N. 
NOTE: 
In tenant service, when the Attendant console 
transfers a call to a station, if the call RNAs and 
recalls back to the Attendant, it will recall to the 
original Attendant that transferred the call. In 
some cases this may mean the call will recall 
to the Attendant that the station is not as- 
signed to. 
ICPl (Intercept #l)--If the attendant takes control 
of a trunk group by using the trunk group access 
control feature, then stations that place calls to 
that trunk group will be routed to Intercept #Il. 
This entry defines ICPl as being either overflow 
tone (OFL) or the attendant (ATT). 
Enter: ATT or OFL. 
ICP2 (Intercept #2)-An incoming call from a DID, 
TIE, or CCSA trunk to a non-existing DN will be 
routed to Intercept #2 when the system is in day 
service and to overflow tone when night service 
is active. This entry defines ICP2 as being either 
overflow tone (OFL), the attendant (An), a 
standard station, or an answering device con- 
nected to a trunk or a standard station pdrt 
(TNNX, LNNX). 
Enter: AlT, OFL, TNNX, or LNNX. 
ICP3 (Intercept #3)-A call that is’violating trunk 
access restrictions will be routed to Intercept #3 
when the system is in day service and to overflow 
tone when night service is active. This entry 
defines ICP3 as being either ovetflow tone or the 
attendant. 
Enter: AIT or OFL. 
LCR (Least Cost Routing)-A 7 response en- 
ables Least Cost Routing in the system. Refer to 
the Least Cost Routing Data Block DLCI and 
DLC2 Programs. 
Enter: Y or N. 
APG (All Page Access Code)-Defines the All 
Page access code. The use of this code will 
simultaneously access Internal Group 0 Paging  
						

							PROGRAMMING PROCEDURES 
SECTION 200-255-305 
JANUARY 1993 
AAT (Not Used): 
Enter: m. 
APX (Not Used): 
Enter: (9. 
LNl (Listed Directory Number #l)-Defines the 
LDN #l , which is used with the DID feature when 
routing a call to the attendant console (maxi- 
mum: 4 digits). 
Enter: 1, 2, 3, or 4 digits or NONE. 
LN2 (Listed Directory Number #2-Defines the 
LDN #2, which is used with the DID feature when 
routing a call to the attendant console (maxi- 
mum: 4 digits). 
Enter: 1, 2, 3, or 4 digits or NONE. 
NT1 (LDN #1 Night Number)-Defines the desti- 
nation to which LDN #l calls will be routed when 
the system is in night service (DN or Universal 
Night Answer). 
Enter: 1,2, 3, or 4 digits or UNA. 
NT2 (LDN #2 Night Number)- The response to 
this prompt defines the destination to which LDN 
#2 calls will be routed when the system is in night 
service (DN or UNA). 
Enter: 1, 2, 3, or 4 digits or UNA. 
BLFl (Busy Lamp Field #l)-Defines one of the 
hundreds groups that is to be displayed by the 
console BLF. 
Enter: 1 digit (1 - 9). 
BLF2 (Busy Lamp Field #P)-Defines one of the 
hundreds groups that is to be displayed by the 
console BLF. 
Enter: 1 digit (1 - 9). 
OFLl (Overflow DN-Attendant Console #IO)- 
Defines the destination for calls that are rerouted 
from attendant console #0 during an overflow 
condition. 
Enter: 1, 2, 3, or 4 digits or NONE (UNA). 
NOTE: 
This data may also be changed via the atten- 
dant console. 
OFL2 (Overflow DN-Attendant Console #l)- 
Defines the destination for calls that are rerouted 
from attendant console #l during an overflow 
condition. 
Enter: 1, 2, 3, or 4 digits, or NONE (UNA). 
NOTES: 
1. The overfiow destination can also be 
changed at the attendant console. 
2. OF1 2 applies to tenant 1 and wiiinotprint 
out when the system is not in tenant ser- 
vice. -. 
MMP (Meet-me Page Access Code)-Defines 
the access code that is used by the attendant or 
attendant-position electronic/digital telephone to 
“park” a call for the Meet-me Page feature (maxi- 
mum: 3 digits; the system default is 10). 
Enter: 1,2, or 3 digits. 
REM (Remote Access DN)-Defines the DN that 
is used to assign a trunk for “Remote Access to 
Services” operation (maximum: 4 digits). The 
DN must be the same as an assigned station DN. 
Refer to the note at the NIT prompt in the DTRK 
Program . 
Enter: 1,2, 3, or 4 digits, or NONE. 
RAC (Remote Access to Services Change 
Code)-Defines the access code that must be 
entered before the system’s remote access code 
can be changed. The remote access code can 
be changed from either an attendant console or 
an attendant-position electronic telephone after 
entering the change code. The remote access 
code is used by outside callers who want to 
access the system’s remote access feature. 
Enter: 1, 2, or 3 digits. 
ACC* (*Access Code)-Defines the digit that is to 
be used by a rotary dial telephone in place of the 
a button. 
Enter: 1 digit or NONE. 
NOTE: 
AAC * must not conflict with either the DN or 
other access codes-it is not checked by 
software. 
5-3  
						

							PROGRAMMING PROCEDURES 
SECTION 200-255-305 
JANUARY 1993 
ACC# (# Access Code)-Defines the digit that is that are released due to the DPT timer will hear 
to be used by a rotary dial telephone in place of overflow tone. This timeout is used with the line 
the 1 button. lockout feature. 
Enter: 1 digit or NONE. Enter: Time in seconds. 
NOTE: 
AAC# must not conflict with either the DN or 
other access codes-it is not checked by the 
software. NOTES: 
1. The Dial Pause Timeout also controls the 
release of an idle attendant console m 
button. 
COT (Camp-on or Call Waiting Timeout)-De- 
fines the Camp-on and Call Waiting feature 
timeout period. 
Enter: Time in seconds. 
For example: 30. 2. Outbound calls can send DTMF tones 
until the DPTtimerexpires. Once the timer 
expires, it changes to the transfer mode. 
RNA (Ring No Answer Timeout)-Defines the 
Ring No Answer timeout period for attendant- 
handled calls, 
Enter: Time in seconds. 
NOTE: PBT (Pushbutton Timeout)-Defines the maxi- 
mum pause that is allowed between digits that 
are dialed on a trunk from a DTMF telephone. 
The transmit voice path from a DTMF telephone 
to a trunk is broken during dialing. The PBT timer 
determines how quickly the path is restored 
and therefore, should be set as short as 
possible. 
Enter: Time in seconds. 
See Note following TEN prompt on page 5-2. 
AOF (Attendant Overflow Timeout)-Defines the 
timeout period for the attendant overflow facility. 
Enter: Time in seconds, 
CFD (Call Forward No Answer Timeout)-De- 
fines the Call Forward No Answer timeout 
period. 
Enter: Time in seconds. LLO (Line Lockout Time)-Defines the length of 
time that overflow tone is applied to a station 
after having been released due to the DPT timer. 
After this timeout occurs,’ the station will hear 
silence. When Emergency Ringdown is used, a 
transfer to the Emergency Ringdown destination 
will not occur until the LLO timeout period has 
elapsed. 
Enter: Time in seconds. 
NOTE: 
The CFD timeout period must be less than 
RNA time or else RNA time will be in effect. ACB (Automatic Callback Reserve Time)-De- 
fines the length of time that the called station or 
trunk in an AC6 call is reserved for the caller. 
Enter: Time in seconds. 
HLD (2500 Hold/Electronic/Digital Telephone 
Park Timeout)-Defines the timeout period for 
the recall of a held call to a single line telephone 
or of a parked call to an electronic/digital 
telephone. 
Enter: Time in seconds or NONE. 
DPT (Dial Pause Timeout)-Defines the maxi- 
mum pause that is allowed before the first digit is 
dialed or between other digits that are dialed 
from an electronic/digital telephone. Stations DLY (Delay Ring Timer)-Defines the time period 
between the ringing of Direct-in Line day an- 
swering stations programmed to ring immedi- 
ately, and stations set for delayed ringing. For 
example, if stations 200 and 201 are set for 
immediate ringing, and station 202 is set for 
delayed ringing, then when a call rings in, the 
delayed ring-time period must elapse before 
station 202 will ring. 
Enter: Time in seconds (0 - 99). 
5-4  
						

							PROGRAMMINGPROCEDURES 
SECTION 200-255-305 
FEBRUARY1992 
account code that has not been entered before 
or during the call. 
Enter: Time in seconds (0 M 255). 
HFS (Handsfree Answerback Station)-A ‘Y” 
response allows calls from any station to voice- 
announce to an electronic/digital telephone that 
is equipped with Handsfree Answerback. 
Enter: Y or N. 
HFA (Handsfree AnswerbackAttendant)-A Y” 
response allows calls from the attendant to voice- 
announce to an electronic/digital telephone that 
is equipped with Handsfree Answerback. 
Enter: Y or N. 
MDR (SMDR Equipped)-A”Y” response enables 
SMDR and activates the MDR alarm on the 
console. 
Enter: Y or N. 
UNAO (Universal Night Answer Zone 0)-A re- 
sponse of 0 assigns UNA Zone 0 to Tenant 0. A 
response of 1 assigns UNA Zone 0 to Tenant 1. 
(This prompt will only appear if TEN was an- 
swered Y.) 
Enter: TEN0 or TENl. 
UNAI (Universal Night Answer Zone 1)-A re- 
sponse of 0 assigns UNA Zone 1 to Tenant 0. A 
response of 1 assigns UNA Zone 1 to Tenant 1. 
(This prompt will only appear if TEN was an- 
swered Y.) 
Enter: TEN0 or TENl. 
5-5  
						

							PROGRAMMING PROCEDURES 
SECTION 200-255-305 
FEBRUARY 1992 
TABLE 5-2 
Procedure - System Data Block 
Authorization Procedure must be completed. If an OK response is received, proceed as follows: 
Meet-me Page Access Code 
Remote Access DN 
Remote Access to Services Change Code 
“*‘I Access Code 
‘W Access Code 
Camp-on (or CWT) Timeout 
Ring No Answer Timeout REM 
RAC 
ACC* 
ACC# 
COT 
RNA 1 - 4 digits or NONE (NONE) 
1 - 3 digits (#*2) 
1 digit or NONE (NONE) 
1 digit or NONE (NONE) 
0 - 255 seconds (50) 
0 - 255 seconds (31) 5&6 
5&6 
Default values are noted in parentheses (). (continued) 
5-6