GTE Omni Si Database Technical Practices Issue 1 Manual

							-TL-130500-1001
SYSTEM SOFTWARE34.0 System software is classified as either generic software
(operating system) or data base software (site dependent). All
major call-processing functions are performed by the system
generic software, which receives direction from the operating
parameters incorporated into the system data base software.
The software is loaded into the system through a disk drive.
First, a floppy disk containing the generic program is put in the
disk drive and loaded onto hard disk. Next the data base disk is
loaded onto the hard disk. The system memory can then be
loaded from the contents of the hard disk. Details of disk loading
are contained in TL-130300-1001. For information on updating
disks to accommodate changes, see TL-130400-1001.
Generic Software34.1 All major call-processing functions are performed by the
and Subprogramssystem generic software, which receives direction from the
operating parameters incorporated into the system data base
software.
Generic software residing in the system CPU memory is primarily
divided into the following subprograms:
l Executive
0 Inter-process Communications
l Call Control
l Attendant Console/Agent Instrument Control
l Digit Analysis
l Administration/Maintenance
0 Line Control
l Station Features
l Trunk Control
l System Features
l CAS Branch
l Message Detail Recording
0 Hotel/Health Care
o Featurephone Directive-Command Handling
l Featurephone Response-Event Handling
Executive34.1.1 The executive subprogram maintains real-time control of
Subprogramthe system environment and is responsible for performing the
following operations:
l Job scheduling
l Monitoring and controlling system operations
l Allocating common system resources
The operating subprogram provides routines within the
supervisory program that accomplish process-report and real-
time services for the application programs. The executive
subprogram is divided into the foreground scheduler and the
background scheduler.
SVR 52108187s-31 3 
						

							s-31 40500-l 001
l The foreground scheduler consists of a dispatcher that
periodically schedules the following routines:
- Peripheral processor foreground scheduler activation
- System real-time clock update
- Outpulsing DTMF and MF tone
- Sending CAS audible tone identification
l The background scheduler consists of a dispatcher that
schedules routines that perform the following:
- Check for lOO-ms, 500-ms, l-second, and l-minute
scheduled jobs.
- Process events including line- and trunk-status changes,
such as on-hook and off-hook conditions and digit
presentation, Attendant Console actions, and system
maintenance test results.
- Process information obtained by the Foreground Scheduler.
Inter-Process34.1.2 The inter-process communication subprogram performs
the following operations:
Communication
Subprograml Passes the action directive to the proper processing
application program.
l Reports the events from each peripheral device and passes
them to the proper processing application program.
Call Control34.1.3 The call control subprogram processes the events
Subprogramreported by the digit-outpulsing and trunk-scan routines, the
console-handler and digit-analysis subprograms, and
allocates the following system resources when required:
l Call stores maintain the current status of all calls in progress in
allocated blocks of memory. A call store is allocated at the
time a line or trunk seizure is processed and retains this
information throughout the call duration.
0 Register-senders (digit stores)
- Register-sender (digit store) memory blocks are
dynamically allocated upon processing of a line seizure and
are linked to the associated call store during digit
accumulation and outpulsing.
- The register-sender (digit store) memory contains the
control words required to accumulate, store, and 
outpulse a
maximum of 16 digits.
8187SVR 5210 
						

							.-,...-TL-130500-1001
Attendant34.1.4 The Attendant Console/Agent Instrument control
Console Controlsubprogram performs the following operations as required by the
Subprogrambackground scheduler:
l Analyzes the status of the Attendant Console and Agent
Instrument pushbuttons as reported by the peripheral
processors’ status-handler routine.
l Causes the appropriate lamps on the Attendant Console and
Agent Instrument to light.
l Reports the status of the Attendant Console and Agent
Instrument pushbuttons to the call processing subprogram for
further disposition.
For example, depressing one of the LOOP pushbuttons and the
START/STOP pushbutton on the Attendant Console causes the
remote console handler subprogram to light the LOOP, POS
RLSE, and START/STOP 
pushbuttons/LEDs and to report the
event to the call processing subprogram. The call processing
subprogram then allocates a call store, a register-sender, and a
DTMF receiver to that loop.
Digit Analysis34.1.5 The digit analysis subprogram is activated when
Subprogramthe system receives a digit and performs the following
operations:
l Analyzes each received digit.
l Checks system features against the codes dialed.
e Checks to ensure that a connection can be made to a
terminator.
o Reports the type of equipment to which the call has been
terminated.
On station-to-trunk calls, the digit analysis subprogram
monitors the outpulsed digits and performs the appropriate 
digit-absorption and code-screening functions.
SVR 5210
8187s-31 5 
						

							TL-130500-1001Administration34.1.6 The administration subprogram performs the following:
Subprogram
e Memory-reload routine
- Reloads information into the system’s generic and data base
memories when the system is initialized or on a return from
a power failure.
- The routine is resident in the ROM on the system CPU card
and, when activated, reloads all of the software data base.
- The memory reload function in the peripheral processor is
controlled by the on-line central processor.
e Disk routine
When activated, outputs the data base from system CPU
memory onto the hard disk in data base files.
0 Traffic-data-verification routine. When activated, performs
the following functions:
- Collects event and usage data.
- Automatically outputs the collected data if desired.
- Provides an interface for remote data-collection systems.
0 Inputioutput routine. When activated, performs the following
functions:
- Provides an interface for the digital system test set.
- Provides an interface for the TTY.
- Provides local/remote memory read/write capability.
Maintenance34.1.7 The maintenance subprogram consists of the following
Subprogramroutines:
e The fault-detecting test routines are run continuously to detect
the following faults:
- Memory faults
- Network faults
- Interprocessor communication faults (central processor-to-peripheral processor and central processor-to-central
processor)
@ The fault-analysis and fault-report routines analyze detected
faults and perform the following functions:
- Rerun the fault-detecting test or a different test.
-Report the fault to the Attendant Console where it is indicated
by an alarm display and hard copy via maintenance TTY.
- Store fault data in an error log and initiate a reconfiguration.
S-31 68187SVR 5210 
						

							.TL-130500-1001
Line Control
Subprogram
Station Features
Subprogram
Trunk Control
SubprogramSystem Features
Subprogram
Centralized
Attendant Service
Branch SubprogramSVR 5210l The system-reconfiguration-and-call-recovery routine
performs the following functions:
a. Reloads the peripheral processor after a peripheral
processor fault.
b. Saves all established two-way and three-way calls.
l Installation initialization, cold start for the data system
(equipped).34.1.8 The line control subprogram monitors the lines for 
on-hook, off-hook, and flash conditions, and reports any activity to
the call control subprogram.The line control subprogram
assigns the digit stores and DTMF receivers to lines when
needed.34.1.9 The station features subprogram controls and executes
the station features with the digit analysis and call control
subprograms.
34.1.10 The trunk control subprogram processes incoming and
outgoing trunk seizure, incoming and outgoing trunk signaling,
and trunk release information with the call control subprogram.
The trunk control subprogram also allocates digit stores and
DTMF receivers to trunks when needed.
34.1.11 The system features subprogram performs the system
features under the control of the digit analysis subprogram, and
reports to the call control subprogram. The following features
are executed by this subprogram:
0 Intercept
0 Class-of-service checks
l 
AIOD (Automatic Identification of Outward Dialing)
0 Station hunting
0 ACD (Automatic Call Distribution)
34.1.12 The CAS branch subprogram monitors seizure,
signaling, and release of the 
PRLTs (PCM Release Line Trunk)
with the call control subprogram. The CAS branch subprogram
also allocates digit stores and DTMF receivers for the 
PRLTs.The CAS branch subprogram also performs the following CAS
related features:
0 CAS attendant camp-on and recall
o CAS attendant recall on no-answer
0 CAS attendant silent hold
o PRLT night answer control and direct and group access
8187s-31 
						

							Message Detail34.1.13 MDR (Message Detail Recording) provides the means
Recordingfor recording cat1 information pertaining to incoming and outgoing
Subprogramtrunk calls. As the trunk calls proceed through the system, MDR
obtains various pieces of information about the calls. MDR
analyzes this information and stores the results in a call record
block. The call record block can then be sent to one of several
terminal devices. Call record blocks can be output via one port
of the FB-20992-A NSDC (Narrow Serial Device Control) card.
Hotel/Health Care34.1.14 The Hotel/Health Care subprogram handles the
Subprogramfollowing device and feature operations:
8 Wake-up (timed reminder) processing
Q Message waiting (message center) processing
@ Room-to-room blocking processing
0 Room restriction processing
B Maid service processing
d H/HC feature activation/cancellation via telephone
@ H/HC feature activation/cancellation via Attendant Console
* KEDU (Key Entry Display Unit) processing
8 H/HC printer processing
Integrated34.1 .I 5 This Integrated Featurephone subprogram handles all
FeaturephoneIntegrated Featurephone related functions. The CPU responds to
Directive Commandthe program, performing the necessary processing and
Handlingtranslations associated with all Integrated Featurephones
Subprogramconnected to the system, controlling the CIP (Control Interface
Processor) data ports, and sending the appropriate commands to
the Integrated Featurephone. The following related Integrated
Featurephone activities are perforrned in this subprogram: The MDR output may be in ASCII or GTE-modified EBCDIC.
The information may be delivered in real time (i.e., each call
reported as it is finished), or the call records may be saved for a
period of time (elected in the data base) and delivered in a batch.
The MDR output may be delivered to a TTY, a minicomputer, a
recording/mass storage unit, or a modem (which will connect to
a remote device).
0 Message metering processing
0 DND (Do Not Disturb) processing
e CLR (Combined Line and Recording) trunk operation
@ H/HC dynamic data back-up and reload
@ New call command queuing
B) Status command distribution (idle, ringing, busy, hold, etc.)
Q Reset command distribution (line or DSS appearances)
(P Directory number verification (line and intercom)
o Status keeping (line, hold, privacy, and waiting call count)
8187SVR 5210 TL-130500-1001 
						

							Integrated
Featurephone
Response-Event
Handling
Subprogram
System Data Base
Data Base
Memory Listings
SW 5210TL-130500-1001
34.1 
.16 This Integrated Featurephone subprogram processes
responses received from the connected Integrated
Featurephones. Cross-correlation between Integrated
Featurephones, their associated line complements, and the
system line-directory numbers is performed, and the event is
sent to the CPU. This handling subprogram also initiates control
of associated Integrated Featurephone functions, such as
commands returned or sent to other appearances, as well as the
updating of privacy, status and new call queue tables.
Thetypical response handling performed by this subprogram are the
following types of Integrated Featurephone-initiated activities:
o Accept/reject
l Account code
l Answer
l Call hold
0 Call retrieve
l Forward
l Off-hook/on-hook
0 Privacy
34.2 The system data base contains all the customer-unique
information (such as the amounts and types of lines, trunks,
station features, and hardware items) that are a part of the
system. The data base is arranged in system memory as a
series of tables. The tables are designated with the letter T and
identified by a four-digit number 
(T-XxXx).A hard copy printout of all the T tables (data base) is supplied
with each system. The hard copy provides the system memory
address of each table and is a printed record of the data
contained for that system. Information in the tables can be
changed as needed when features are added or deleted or when
the system hardware is modified (telephones added, etc.).
Changes to the system data base must be routinely noted in the
listing so that references to the data base are accurate. 
TL-130400-l 001, describes how information is initially prepared for
the tables. TL-130200-1001 describes how the contents of the
tables are altered (Recent Change) after they have been written
into system memory.
34.2.1 System configuration and features are set up when data
base programming is performed. Data base programming
sheets (Record Codes) contain information that must first be
organized into various groupings and then loaded onto a floppy
disk. These groups of data are identified as tables, which are
designated with a T and identified by a 4-digit number. These
groupings are then loaded into specific addresses in system
memory.
8187 
						

							TL-130500-1001--For example, refer to the Line Data (LD) Record Code
Assignment Data Sheet (Figure 34.1) and note that above the file
and card position entry header (columns 18, 19, and 20) are
the table references T2541, 
T2551, T2561, and T2571.
--___TTTT
TTTTTTT TTTTTTTTTTTTTT66665222267 6222256 J57, 4444 , 4
I 1234 I  3; 555510 141 5555 ,‘I43303Ill 0 I30456785 14, 4567 Ill0II335318, 5 I85, 1111 I 1 ;111102 Ill ,111 I 11,II /II7809‘01 6 I12I II
F
SN RC;LC0 E0 EO,I,G 01 N0R aC D INP IMD E IEIE 5; SI  NT;T N; RE I1II
IIN0, 01 uIIII  MIIII EIII’ NIIII’ T
III
II,I
III
III1IIIIIIII
I
II1
,
III
IIIII
IIII I I, I I, I I I I I I I I T I ‘1 II I I I I I I I II I I  I  I II I1111111111111111,111121212l21212~2,2,212l3,3~3l3l3,3,3i3l313l4,4,47~8~9~0~,~2131415161Jl~l9101,12131415161J1~19101,121314151617I~l9lOl,l)I I I I I I I I I I f I I I1 I I I I I’ I  I I I  I I  11 1 I
TTTT7 TTT
55655 556
440 0 I1  3 ’3I 33, 31 II1,II , I ; I6’ 67I 9;  9 ’
I1III1114;IIIIII ,I
CF IIDlALI  SPEED
I DCID 01 D D I,M GlRlW NI0E ICALLICALLI I0’1 El I  E DID R’MIA 01N* IPICKITT II
‘V NIV 5’ V 5 E IRP;T;R ’
U; R;I
;E D,E T; E T N );A ;D I
IIRI,R I, R I  T,WIII, TTIT N, T N I  ,OIC IILE I P G IE GI G I I  I15 IILp ’ I  R‘/ III
NH ;CP;X R’ R f N;IT PI p , D ,;A ’
Go I KIN IUII ’  I,u’ jIII v IIT;IE I PI
IIIII/fH IIII
IIIII!II
III1I
IIIIIIII
I
II
IIIIIIII
IIIIII
IIII
II
I
I‘E IIIIIIIIIiI II
IIII’ II1  I
--T-T-T----T-T---
;:;
i-L;---T---414,4144 I4 145 I 5i-r;2;,T,3141516718190 1  12 134 1  56 1  78 190111213~415 67 18I I II IIII I 1  I  II
NOTES:
* 1 = USED IN DETERMINING SOFTWARE ID WHICH IS PLACED IN T6441. TJ054.75330.* 2 = USED IN FILLING TABLE TJ055.* 3 = USED IN DETERMINING FEATUREPHONE DATA LlNK NUMBER.
MAXIMUM NUMBER OF RECORDS = 256.
Figure 34.1Line Data Record Code Assignment Data Sheet
S-3208187Now refer to the hard copy of the customer Memory Tables
listing. The Table of Contents (Table 34.1) in the listing identifies
these tables as the Line Card Address Tables for PEC 0 and also
shows that they are contained on Data Page 0.
SVR 5210 
						

							TL-130500-1001
Next, look up the table in the actual listing (Table 34.2), for
example T2541 (PEC 0). Note that each table in the listing
consists of two parts, a page with the descriptive details of the
table (header), followed by the page (or pages) of the actual
address structure and the data contained in each address
(resulting from the data base programming).
The descriptive information indicates that “This table provides the
hardware position of each equipped line card, determines the
order of line scanning, and establishes the SOFTWARE ID for
every line in Peripheral Equipment Complex 
0.” Each bit position
representation in each word or byte is also described, which
makes it possible to interpret or read the ones and zeros of the
digital data. For instance, bits 3 and 2 are used to specify in
which file a line card is installed, where file A is represented by
00 and file B is represented by 01.
The listing also shows that the line software ID numbers begin
with 0, 8, 16, etc., through 248. A note in the descriptive
information describes how to determine a line software ID. First,
find that line’s card position and file in the table; then, take that
location’s partial software ID (under entry number) and add that
line’s circuit number to it to calculate its software ID. Thus, with
8 circuits on each line card, these 32 entries provide the system
with the software ID (O-255) for 256 lines.
For any line software ID, the memory contents (in binary) can be
found and interpreted using the descriptive information sheet.
The hexadecimal address, which is used in the microprocessor
program to find the location in memory of this information, is also
provided. In normal operation a request for a “read” from the
maintenance TTY would reference this address. The hex entry
equivalent of the binary contents is also provided since the
maintenance TTY outputs the memory contents in hexadecimal.
For convenience purposes, each page of the listing also 
prov.,‘c>sa conversion table. When a change to the binary contents is to
be made, the hexadecimal equivalent can be determined for
each entry using the maintenance TTY.
Table T2581 is used for the TC (Trunk Circuit) Record Code,
where the file, card position, and circuit columns refer to trunks
located in PECO. When referring to the descriptive information
sheet for this table and comparing it to the line data, it becomes
apparent that the memory contents layout is the same, except
that now bits 1 and 0 indicate the actual trunk circuit on the card.
SW 52108187S-321 
						

							TL-130500-1001
The use of T tables by the system CPU now becomes more
apparent. As described earlier, the line and trunk circuits are
scanned by the MPB85 cards in the same file; therefore, the card
position and file must be known in order to perform the scan
routines for lines and trunks. The CPU processes all calls using
software IDS. When a request for service is detected during a
scan, the system receives sensing data, which is then compared
with data in the T tables as a means of searching for a match.
When a match occurs, the software ID is established. If the
request for service was a station, the CPU can take the software
ID, go to T5381 (LD (Line Data) Table) to determine the 
N-displayable and displayable COS (Class-of-Service) group that
this software ID (station) is in. T5381 provides the index number
(O-15) for T6091 (N-displayable COS, Record Code NC) and
the index number (O-9) for T6101 (Displayable COS, Record
Code DC) where the CPU can find all the specific COS
assignable features permitted/denied for the line requesting
services.
To summarize, the Data Base Programming/Assignment Data
Sheets information is used to generate on ODDB (Office
Dependent Data Base) floppy disk and listing (either a specific
customer’s data base or the FGBS standard data base). The
system’s generic program and the ODDB are loaded into the
system, which places all this data in specific memory addresses
where groupings of data are designated as T tables. See Tables
34.3 and 34.4.
Table 34.1
Office-Dependent Data Base Listing Table of Contents
. . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...TABLE OF CONTENTS.
.
..
. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
; CECDATA
PAGE 0.
.
. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .TABLE
NUMBER
. 
;;541- - _
T2581
T2621
T2661
T2701
T2741
T2742
T3111
T3151
T3201
T3202
T3203START
TABLE NAMEADDRESS
---------_--__-_________________________---------_ _ _PEC-0 LINE CARD ADDRESS TABLE
- -1-&iPEC-0 TRUNK CARD ADDRESS TABLE
1031PEC-0 CONSOLE CARD ADDRESS TABLE
1073PEC-0 DTMF RECEIVER CARD ADDRESS TABLE
1075PEC-0 
AIOD CARD ADDRESS TABLE107DPEC-0 CONFERENCE CARD 1 ADDRESS TABLE
107EPEC-0 CONFERENCE CARD 2 ADDRESS TABLE
107FPEC-0 RLT CARD ADDRESS TABLE
1080PEC-0 RLT TRUNK TYPE TALE
1090PEC-0 KEDU ADDRESS TABLE
1 OAOPEC-0 PRINTER ADDRESS TABLE
1 OA2PEC-0 PRINTER BAUD RATE AND PARITY TABLE
1 OA4
S-3228187SVR 5210