GTE Omni Si Database Technical Practices Manual

							REGLINE#CONTENTS (10 COUNTERS PER LINE)
~~~L~RK030 TGOOTGOlTG02TG03TG04
TG05TG06TG07TG08TG09031 
TGlOTGllTG12
TG13TG14
TG15TG16TG17TG18TG19032 TG20
TG21TG22
TG23TG24
TG25TG26TG27TG28TG29033 TG30
TG31TG32TG33TG34
TG35TG36TG37
TG38TG39034 TG40
TG41TG42
TG43TG44
TG45TG46TG47
TG48TG49035 TG50
TG51TG52
TG53TG54
TG55TG56TG57
TG58TG59.~_036 TG60
TG61TG62-i-G63 __-_ ____ ____ ____ ____RLT. . .
EGTERK037 TGOOTGOlTG02
TG03TG04TG05
TG06TG07
TG08TG09038 
TGlOTGllTG12TG13TG14TGl5TG16TG17
TG18TG19039 
TG20.TG21
TG22TG23TG24TG25TG26TG27TG28TG29040 TG30
TG31TG32TG33TG34TG35TG36TG37
TG38TG39041 TG40
TG41
TG42TG43TG44TG45TG46TG47TG48
TG49042 TG50
TG51
TG52TG53TG54TG55TG56TG57TG58TG59043 TG60
TG61TG62TG63 ____ ____ ____ ____ ____---_
INC/OTGATB044 TGOOTGOlTG02TG03TG04
TG05TG06TG07TG08TG09045 
TGlOTGllTG12TG13TG14TG15TG16TG17TG18TG19046 TG20
TG21
TG22TG23TG24TG25TG26TG27TG28TG29047 TG30
TG31TG32TG33TG34TG35TG36TG37TG38TG39048 TG40
TG41
TG42TG43TG44
TG45TG46TG47
TG48TG49049 
TG50TG51TG52TG53TG54TG55TG56TG57TG58TG59050 TG60
TG61TG62TG63 ____ ____ ____ ____ ____RLT
8$@ TRK051 TGOOTGOlTG02
TG03TG04TG05TG06TG07
TG08TG09052 
TGlOTGllTGl2TG13TG14TG15TG16TG17
TG18TGl9053 TG20
TG21
TG22TG23TG24TG25TG26TG27
TG28TG29054 TG30
TG31TG32
TG33TG34
TG35TG36TG37
TG38TG39055 TG40
TG41
TG42TG43TG44
TG45TG46TG47
TG48TG49056 TG50
TG51
TG52TG53TG54TG55TG56TG57TG58TG59057 TG60
TG61TG62TG63 ____ ____ ____ ____ ____RLT
ZAGE058 BUS0BUS1 ---- ____
BUS4
BUS5BUS6BUS7 ----____(GET STARTED FILE)(EXPANSION FILE)
059 ----
_____________-___-__________-.______060 ----
____
_________--_____________-___.___061 ----
____________________._______--______
ZF062 BUS0BUS1(GET STARTED FILE) --------BUS4BUS5BUS6BUS7 ----____(EXPASION FILE)
063 ----
_____-____________._._______________064 ----
-___-_____..________
_____.__065 ----
_____________.-___________________._
Figure 2.5Traffic Register Layout (Continued)
5210
8187M-47 
						

							Table 2.2Traffic Data Commands Input and Output Formats
INPUT FORMATTD DT.- to display the date and time of
dayTD DT 
xx/yy/zz nn:nn - to change the
time-of-day clock.
TD BS. 
- to-begin a traffic study--TD ES.- to end a traffic study
where
xx = the month
YY= the day of the month
zz =the last two digits of the year
nn:nn =the time of day in hours and
minutes in 24-hour format
M-48
8187
OUTPUT FORMAT
xxIyy/zz nn : nn
DT 
xx/yy/zz nn : nn ? EXECUTED
BS site xx/yy/zz nn/nn aa bbb
cccc dddd/eeee/: Y. EXECUTEDES site 
xxlyylzz nn:nn aa bbb cccc
dddd/eeee/:? Y.EXECUTED
where
site =the data-base controlled ID
xxlyylzz= the month, day, and
year request is made
aa= the number of minutes be-
tween automatic traffic data
dumps
bbb =the number of seconds
between each traffic scan
cccc= the number of scans
between traffic data dumps
dddd/eeee = the first and last
addresses of the traffic registers
Y. is entered by the user.
5210 
						

							5210FTM 0184The following information is being supplied to clarify the operation
of the traffic data facilities on the 
OMNI SI in areas of:
l All trunks busy
l Overflow
l Usage
ATB (lines 41-47 in traffic layout) 
- Pegging occurs each time
the last available trunk (defined as the last trunk in the idle trunk
state) is changed from idle to any other trunk state. It is valid to
have ATB pegged for an incoming only trunk group, an outgoing
only trunk group,. or for a 2-way trunk group.
OVF (lines 48-54 in traffic layout) 
- Pegging occurs when the
system tries to use a trunk group which has all trunks busy. It is
valid for a 2-way trunk group or an outgoing only trunk group to
peg this count. It is invalid to have an incoming only trunk group
peg this counter. It is pegged when the system tries to use a
trunk in the trunk group which has all trunks busy.
Usage will be shown if:
1. The call was properly pegged for the number of calls, but this
was during a previous scan period, and the call stayed up
throughout successive scans. This would give usage with no
calls to the trunk group.
2. The trunk is implemented in data base and exists physically,
but is not connected to a CO trunk. This is primarily a problem
with Ground Start trunks going to the “incoming preseized”
trunk state. The usage scan sees the trunk as not idle, or
maintenance busy.
3. Trunks are in the “system out of service” state (trunk state 13).
This will show up as usage with no calls to that trunk group.
This applies to the following cases:
a. The trunk and trunk group exists in data base, but the
trunk(s) are marked as unequipped in 
T5551 when the
system comes up.
b. Whenever the PEC goes out of service, all the trunks in it will
will placed in a system out-of-service state.
c. If a 
Tl alarm occurs, all trunks in that Tl span will be placed
in a system out-of-service state.
NOTES:
1. Maintenance busy trunks are not counted in the usage
counts.
2. If the data base is set up correctly, it is possible to have
usage counters pegged up even though no calls have been
made.
8187M-49 
						

							TL-1 3Uzuu-I UUI
Display Command2.1.7 The display command (Line, Trunk, Call State) is used to
list the addresses and data of the tables listed below:
l T4170Line State Table. T4160
Line Call Store Link Table. T8941
Trunk State Table. T8944
Trunk Call Store Link Table. T1390
Call Store TableThis information is used in call tracing and is shown in section
6.0.The formats of the display commands are shown in Table 2.3.
M-5081875210 
						

							Table 2.3
Display Command Input and Output Formats
Iisplay Line State:
DISPLAY LINE DN STATEoutput
PAGEADDRESSDATA_--__-_ .2--_----_-_____- - _ - - -- - -
._..xxYYYY
zz
tvhererXX = page ID (DO, D2, D3, D4, D5,06, D7)
._YYYY = address of line state
ZZ = present state (see Table 2.4 for CEC Line State Codes)
display Line Call Store Link:Input
Input
DISPLAY LINE DN CSLINK
OutPut
PAGEADDRESSCS#PAGECS ADDR RANGE---m--v-m------m-__-------------__--_---_--____---_______xx
YYYYzzAABBBB-CCCC
Nhere:XX = page of line call store link
YYYY 
= first of two addresses of line call store link
ZZ = call store number in decimal
BBBB = start address of call store
CCCC = end address of call store
Output
PAGE------ADDRESSCS#-------------
---PAGE- - - - - - -CS ADDR RANGE---------------
xx
YYYYIDLE-NOT LINKED
Nhere:XX and YYYY are as above
idle-not linked means the line is not presently linked to a
cal I store.5210
8187M-51 
						

							Table 2.3 Display Command Input and Output Formats (Continued)Display Trunk State:
Input
DISPLAY TRUNK STATE
where:
 
.= system trunk number in decimal (O-63).
=-Output
PAGE
ADDRESSDATA
-------
-------------
---_-----xx 
-YYYY22where:
XX = page ID (DO, 
D2,03, D4, D5,06, D7)YYYY = address of trunk state
ZZ 
= present trunk state (see Table 2.5 for CEC Trunk State Codes)
Display Trunk Call Store Link:
Input
DISPLAY TRUNK CSLINKOutput
PAGE
ADDRESSCS#PAGECSADDR RANGE-- - - - -----------_-_----_--------------------_------------xx
YYYYzzAABBBB-CCCCwhere:XX = page of trunk call store link
YYYY = first o two addresses of trunk call store link
ZZ = call store number in decimal
AA = page of call store (DO, D2, D3, D4, 
05, D6, D7)BBBB = start address of call store
CCCC = end address of call store,
or
output
PAGE------ADDRESS---_________-CS#---PAGE-- - - - - -
CS ADDR RANGE____----_-_____xx
YYYYIDLE-NOT LINKEDwhere:
XX and YYYY are as above
idle-not linked means the line is not presently linked to a
call store.M-52
81875210 
						

							.bI”“-“” .““.
Table 2.3Display Format (Continued)
Display Call Store Address:
,lnput
DISPLAY CSADDRESSwhere:
 =call store number in decimal
output--..PAGECS ADDR RANGE..----------------_--------------
- xxBBBB-CCCCwhere:XX 
= page lD(D0, Dl, D2, D3, D4, D5, D6, D7)BBBB 
= start address of call store
CCCC 
= end address of call store
Table 2.4CEC Line State Codes
CODELINE STATE
ILine idle1 Line ringing
02Line busy
03Line digit collection
04Call-back in progress
05Call-back ringing
06Line locked out
07Line maintenance busy
08Staff for call-store assignment
09Line stall (idle)1 Line stall (off-hook)
I
061 Line off-hook recoveryIM-53
5210
8187
: 
						

							Table 2.5CEC Trunk State CodesM-54
CODETRUNK STATE
01Incoming pre-seized trunk
02Incoming mishandled trunk
03Incoming FX trunk wait for resources
04Incoming not answered (idle)
05incoming loop not answered (idle)
06Incoming busy (idle)
97.
08Incoming signaling A
Incoming signaling 8I
09) Incoming dialing (idle)1
OA08Incoming delay dial wait
Outgoing start dial wait
ocIOutgoing wink start wait
OD
OEOutgoing busy (idle)
Outgoing guard after release
OF
10Outgoing immediate dial
Outgoing glare check
Recorder Announcer message interval
12Incoming seizure stall
13System out of service (PEC out of service)
Outgoing wait for disconnect, PBX release first
15Retry, put in service
16Outgoing pre-seized
17Spare
18Outgoing dialing
19Outgoing busy (busy)
1AOutgoing not answered
18Outgoing wink start time
1cPanel Maintenance busy
1DNot busy
81875210 
						

							.-.----- .--.
Table 2.5CEC Trunk State Codes (Continued)
CODETRUNK STATE
1E
I1 Maintenance busy
1FSystem busy
20Incoming not answered (busy)
21_.1 Incoming loop not answered (busy)I
. . . .22Incoming busy (busy)
23incoming dialing
24 
.*
25Incoming dialing (busy)
Recorder Announcer start
26Recorder Announcer message cycle
27Call recovery trunk off-hook
28CAS Main ACD recorded announcement start
I
291 CAS Main ACD recorded message cycleI2ANailed connection
Maintenance Commands2.2 Maintenance commands are used to take suspected
defective lines, trunks, stations, or cards out of service. An
individual defective line, trunk, etc. can be taken out of service
without affecting the operation of the system. The defective unit
can be placed back in service after maintenance. The following
are the maintenance commands available in the system:
* Force commands
l Memory watch command
l Put commands
* Test commands
0 Trace commands
0 Unlock commands
Software IdentityThe Software Identity (SID) for a line or trunk must be determined
Methodbefore using the PUT or FORCE SID method of maintenance
command entry; however some commands such as FORCE
DN...OS. or FORCE TR 
CI...OS. do not require SID.
52108187M-55 
						

							Software IdentityFor initial installations, the SID number for lines or trunks can be
Calculationsfound in the Cable Pair Listing - Table in TL-130400-1001
Use the decimal listing under each line or trunk number.
1. To calculate the SID for lines use 
R C Table 221 and the
following calculation:
__SID =RC Table 221 primary identifier x 8 + circuit number; or
SID =Line card’s position number in the Line Card Address
Table T2541 x 8 + the circuit number; where:
VCIP, DVCIP, VPLC (types VPLO and 
VPLl), and VPLC2 (type
VP20 and VP21) cards are treated as voice cards
2: To calculate the SID for ports, use RC Table 22 and:
SID =RC Table 221 secondary identifier x 8 + circuit
number,where VCIP, DVCIP, VPLC (type VPLO and 
VPLl), and
VPLC2 (type VP20 and VP21) cards are treated as data cards
To calculate the SID for the CIP, use the following calculation:
SID =RC Table 221 primary identifier x 8 + circuit number
3. To calculate SID for trunks, use the following calculation:
SID =Trunk circuit’s position number in the Trunk Card
Address Table T2581
4. To calculate the SID for DTMF receivers:
SID =DTMF receiver’s position number in the DTMF
Receiver Address Table T2661.
5. To calculate the SID for conference cards:
SID =0 if conference card is in Conference Card 0 Address
Table T2741
SID = 1 if conference card is in Conference Card 1 Address
Table T2742.
NOTE: All SID calculations and entries must be in decimal.
Fault Code responses given by the system are in hexadecimal
and must be converted to decimal prior to the SID calculation or
entry.M-56
81875210