Home > GTE > Communications System > GTE Omni Si Database Technical Practices Manual

GTE Omni Si Database Technical Practices Manual

    Download as PDF Print this page Share this page

    Have a look at the manual GTE Omni Si Database Technical Practices Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 3 GTE manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 950
    							TL-130200-1001IREGISTER STORED DATA VALUEI
    I
    II
    II
    I
    I
    I
    ! RESPONSE CODEI
    i 00-Task 1I; PutPECII INS
    I
    II; :..-I
    )t
    . . .
    I
    II
    II
    II
    I6ICIDI
    IIEIHILI
    I1 
    PECNo.Ii OO=PECisUP I
    IIAddress of TCBI
    I
    II andRunning IIIII
    I
    I
    I
    I
    I
    I
    I
    I
    I
    I
    I
    I
    I
    I
    II
    II
    I
    II
    II
    II
    II
    I 01 -Task 2I; Put PEC 00sfIII 02-Task 4I
    II 
    AllowSBYCEC Ii to Check PECII LeadsI
    I
    II
    I 03-Task 5I
    i CheckSBYfI CEC-PECI
    I
    I
    5210
    II1 
    Ol=PECHas \i BadRAMI
    ( 02 = ControlfI LeadTestI
    ; FailurefI1 Address of Faulty 
    Bytej
    [ 01 =CPRST I
    I 
    02=Request I
    ; 03=10MS !IIIII
    I. .
    Ii 03=CommoniI Memoryisbad II Address of Faulty ByteiII
    II
    II
    I
    fIi 04=DiskUnit 1I
    IIIIIIt FailureftIIIII
    I
    III
    I
    II OS=StartII
    IIIII
    I
    ; Unit FailureII
    ,
    i 06=Channel iII
    II
    I
    I
    I MemoryIII
    II Failure onIIII
    II StartupIIIII
    I
    : PEC No.IIIAddress of TCBIII
    II!IIIIIII; PEC No.IIAddress of KBIIIIIIIII
    tIII
    IIII
    IIIIIIIIIII
    ; PEC No.1 OO=PECisUp IAddress of TCBIIII1 andRunning IIIII
    III( 01 =PEC HasII
    I
    IIBad RAM)1 Address of Faulty Byte;
    IIIL
    Figure 2.4Response Code/Quick Reference Guide
    ah37M-37 
    						
    							iI
    I
    tREGISTER STORED DATA VALUEI
    II1I
    II
    I
    I1 RESPONSE CODE
    II
    BICIIDIEIHILI
    II
    II1
    I II
    :I II 02 =Controli; 01 =CPRST ;I
    II I1 Lead TestII
    ! FailureII 02=Request IIII II; 03=10MS 1III IIII
    II III 03=Common III
    II II Address of Faulty Byte
    II;: II MemoryisBad IIf
    II
    I:I IiIIII III1I.--04= Disk
    I I
    II II Unit FailureiIII
    II IIII
    II II ,z=StartIIII
    I :iIIIUp FailureI
    II
    1I1. ;._II1
    II
    II II 06=Chanel III
    II I
    I iMemory Failure III
    II
    II
    II onStartupIII
    II IIII
    ! 04-Task 6: : PEC No.IIIAddress of TCBIIIi CheckSBYI i
    i OO=PECisUpII andRunning rI
    III CEC-PECI IIIII1 toINSI I
    I II Ol=PEC Has 1r Address of Faulty ByteI
    I
    II I; BadRAMII;
    IIII
    II IIII
    I
    I II 02 = Controlf Ol=CPRST II
    I
    I
    ILead TestI! 02=Request II
    II
    I
    I II FailureII I1III
    I
    f 03=lOMS ;
    IIiI II
    II I
    I 03 = CommonI MemoryisBad IIAddress of Faulty ByteII;
    I
    II I
    II II 04=DiskIIIIIIIII
    I
    I: IiUnit FailureIII
    I
    III
    II
    II Ii 05=StartIII
    II I; Up FailureIIIII IIII
    I
    I II 06 = ChanelII
    III
    I
    I
    I II Memory Failure III
    II III
    II II onstartupIII
    I
    I IIIII
    I OS-Task 7I OO=MakeIII1 I PEC No.II I
    ; OOS--INSIAddress of TCBII1 StartIII IIII
    I Communication I Ii 01 =MakeIII
    i Between CECI IIIIIII
    II I; 00%SBYIII
    II I
    II II TransitionIIIIII
    I 06-Task 15I III
    Address of TCBII1II
    Call RecoveryI II
    I IIII
    II I0
    IIIIr  07-Communica-i I ChannelIIIr tionschannel isI I No.II1  Back InsI IIII III IIII
    / 08-H/HC TapeI III III 
    WriteSuccessful ; ;III
    I 09-Power Re-I II: iII stored. NoSystem , II
    I
    I Shut-down
    I II
    I
    Figure 2.4Response Code/Quick Reference Guide (Continued)
    M-3881875210 
    						
    							I
    I
    fREGISTER STORED DATA VALUEI
    I
    t
    It
    i RESPONSE CODEtIIBICIDIEI
    t
    HILII1 
    lo- Task 29I Agent Recovery;; AgentI OO=Rec.OK IAddress of TCBi No.ofIII’’ I.D.I FF= REC. FailIIII; Attempt, ,( (Agt--00s) ;i RecoveryII I, Attempts III IIII
    : 1 I- CIP Port;;IPEC No.; 00 = CIP Port; Port No.I
    I
    I
    I StatusChange I I
    to 00sI
    III
    II II
    II
    I
    II I
    I 
    t-; Ol=CIPPort ;I
    I
    fI tI
    Ito 1sIII tI
    IIII. . . .
    II IIO2=CIPPort III
    I
    IIIII
    IIII I
    ItoMOOS ;I II
    IIII 12-CIPCard1 1 PEC No.III I-,. f OO=CIPCardI Card No.I) Status ChangeII Ito 00s ;II III
    III
    III
    II I
    I If 01 =CIPCard ;IIII
    IIto IS,II
    : 13-ESPI III11 PreviousCurrent ESP, OF = DataII
    I, , ESPState;IIII StateI Transm. to ESP1 begins at nextII
    II I; 02 = m-ServiceII
    II :Ii qtr. hourII
    IIIIt III I, ID=DataII
    II1
    I III Transm. begins iII I, in two qtr. hours II
    I
    I IIII
    I
    Ii 14-SBY-CEC Dynamic; ; Not ApplicableI
    ; Data UpdatedII III
    j 15-BLDUi ; PEC No.I
    II; BLDU No.; Error Type *I,II I,l 00 = Out of synchronization
    ,tII II,01 = In synchronizationIIII,tII II02 = Negative acknowledgeII IIIIIi03 = Invalid kev identitvIII II I,04= Invalid BLDU numberI
    Figure 2.4Response Code/Quick Reference Guide (Continued)
    Response Code.Following are the response code descriptions listed in
    Descriptionsnumerical order:
    Response Code 00
    This message is printed in response to an attempt to put the PEC
    in service. Before loading or putting a PEC in service, perform
    the following tests:
    (1)Test all of the random access memory of the PEC.
    (2)Test the control lead by clearing the response word in
    common memory and sending a Central Processor Reset
    signal (CPRST). Clear the CPRST signal. Check the
    response word in common memory to verify that the reset
    has occurred.
    (3)Test the request lead by using the same procedure as
    above.
    5210
    8187M-39 
    						
    							(4)Test the 10 ms interrupt line by using the same procedure
    as above.
    (5) Test the CEC-PEC common memory.
    Register Stored Value
    l Register B has the PEC number.
    l Register C has a value of 00 through 06 (see Register C
    value summary following Response Code 13). Value 00
    indicates that the PEC has been successfully placed in
    service and no further action is necessary.
    NOTE: Other possible values for register C are explained where
    applicable in the following response code?.
    Response Code 06
    Responds to a call recovery attempt and indicates that it was
    completed.
    RESPONSE CODE 08
    Responds to the successful completion of the station status disk
    write operation. It indicates that the station status dynamic data
    was backed up on the disk in its entirety; This response is
    posted after automatic write-on power failure or on maintenance
    request operations. To write station status data on disk, refer to
    maintenance request code 
    2E, Response 08 does not use the
    registers to convey information.
    Response Code 09
    Responds to the restored power after fault code 26 power failure
    has occurred and indicates that there is no system outage before
    power is restored. The station status memory may or may not be
    backed up, depending on the power failure status. If the station
    status write operation is in progress at the time of power
    restoration, the operation will continue until completed. However,
    if the operation has not begun, station status write operation will
    not occur. Response registers are not used to convey
    information.
    81875210 
    						
    							5210TL-130200-1001
    Response Code 10
    Responds to an Agent Instrument recovery task. See fault code
    28 description in the fault tables for conditions under which
    recovery will be attempted. If register C indicates that the
    recovery has failed, the Agent Instrument will be put out of
    service. If the recovery action is successful, the Agent
    Instrument will remain in its current state.
    Response Code 11
    Responds to placing an Integrated Featurephone CIP port in or
    out of service, or in a (MOOS) Maintenance Out-Of-Service
    busy state. When the port has failed for any reason, Fault Code_33 will be printed and the system will attempt a recovery (put
    back in service). See Fault Code 33 description for the
    conditions under which recovery will be attempted. If the
    recovery attempt fails, the port (Integrated Featurephone) will be
    put out of service.If the recovery attempt is successful, the port
    will remain in its current state. The port is placed in MOOS state
    when the Integrated Featurephone is in the process of
    downloading.
    Response Code 12
    Responds to placing an Integrated Featurephone CIP card in or
    out of service. See Fault Code 32 description for the conditions
    under which the CIP card will change its state.
    Response Code 13
    This message indicates that the ESP state has been changed to
    in service. This implies that MDR-ESP communications has
    been established and that remote FADS data is transmitted to the
    ESP as soon as the initial data collection period has ended.
    Register B indicates the previous ESP state. Register C contains
    the value 02 indication that the current ESP state is in service.
    Register D indicates when remote FADS data collected for 
    15minute periodic intervals begins to be transmitted to the ESP.
    The value OF in register D indicates that data transmission
    begins at the next quarter hour following the output of response
    13. If D = 10, data transmission begins on the following quarter
    hour. For example, response code 13 is received at 
    9:05; if D =
    OF, the data transmission begins at 
    9:15; if D = 10, data
    transmission will begin at 
    9:30.
    8187M-41 
    						
    							Response Code 14This message indicates that the standby 
    CEC’s dynamic data
    has been updated by the in-service CEC. This task is
    performed whenever a CEC goes from out of service to standbyand response 14 indicates completion of this task. To ensure
    dynamic data integrity between 
    CECs, recent change and CEC
    generic writes should not be performed until a response code 14
    has been printed after a CEC goes standby.
    Response Code 15
    This message indicates that the BLDU status has been changedfrom out of service to in service or from in service to out of
    service. Register B has the PEC number, register C has the
    BLDU number, and register D has the error types.
    81875210 
    						
    							TL-130200-1001Automatic Circuit2.1.4 The Automatic Circuit Assurance (ACA) log can be
    Assurance Logdisplayed on the system TTY or CRT terminal by entering the
    Request CommandsACA log commands. The ACA log is a record of the last 32
    reports that were generated. A printout of these reports is
    arranged in the same order that they occurred (earliest, first,
    most recent, last). The commands for executing an ACA log
    report are as follows:
    This command prints ACA reports stored in the ACA log.
    r-------------------------------------------------~IIIIIACA INS. or ACA INS DUMPI
    II
    L-----------------------------_----------~This command clears all reports in the ACA log.
    r-------------------------------------------------~IIII
    IACA INS CLEARI
    II
    L-------------------------------------------------~This command prints all ACA reports and then clears the log.
    52108187
    ACA INS DUMP CLEAR
    M-43 
    						
    							ACA Log DisplayThe ACA report is printed on the maintenance terminal in the
    following format:
    / SITE: AAAAMM/DDHH:MMI
    ISHORT
    IIITrunk GroupI
    ITrunk Number
    I
    IShort Calls..-
    IMinutes
    . . .tIor
    i SITE: AAAAMM/DDHH:MM
    ILONGIII
    ITrunk Group
    fTrunk Number
    ILong CallI
    IMinutesACA CALL REPORT
    xx
    xxx
    xx
    xxx
    ACA CALL REPORT
    xx
    xxx
    --
    xxx
    II whereI
    I SITE= Site identification
    ] MM/DD = Month/day
    ! HH:MM= Hour/minute
    I Short Calls= Number of short trunk seizures
    ! Long Calls =1 MinutesLong trunk seizure
    I= How long it took before the trigger threshold was reached
    1I=>I
    I
    II
    I
    I
    I
    I
    I
    I
    I
    I
    I
    I
    I
    I
    I=> 
    (
    I
    I
    I
    I
    I
    I
    I
    II
    II
    I
    I
    I
    II
    I
    I
    I
    I
    I
    I
    I
    I
    II
    I
    I
    I
    Traffic Data21.5 The traffic data polling commands are used to request an
    Polling Commandimmediate dump of the traffic data registers. Either the active or
    passive registers can be polled. The active registers are the
    registers used to store the results of the current traffic study
    period and the passive registers store the data of the previous
    traffic study period. Input format for the traffic polling commands
    is shown below. The traffic data will be transferred without
    header.
    To poll the active registers, enter:
    r-------------------------------------------------~II
    I[CNTL] As # [CNTL] B.
    IL-------------------------------------------------~“s” is defined as the ASCII representation of the hexadecimal
    site identity (site ID) defined in the data base (Table T6041).
    M-44
    61875210 
    						
    							I L-l 30200-l 001
    To poll the passive registers, enter:r-------------------------------------------------~III[CNTL] As ! [CNTL] 6.IL-------------------------_----____---------------------~NOTE: Depress and hold the CNTL control key while entering A
    and 
    B in the traffic data polling command. Do not depress the
    CNTL key when entering s, 
    #, or !.
    Time tif Day/Traffic2.16 The Traffic Data (TD) commands provide a means of. . .Study Commanddisplaying and setting the time-of-day clock in the system, and
    beginning and ending automatic traffic studies. The traffic data
    scan rate, the format of and timing between traffic data reports,
    . .and the site identification printed with each traffic data report are
    all controlled by the data base. The format of a traffic data report
    is shown in Figure 2.5.
    The data base determines how frequently the system will
    collect traffic information, and how often a traffic report will be
    printed out (refer to data base software Table T6041). Note that
    the automatic output indicator (Table T6041) must be set for the
    reports to be generated continuously. The reports will continue
    until terminated by the appropriate command. The traffic data
    command input and output formats are shown in Table 2.2.
    NOTE: The status command is used to display the current
    reading of the time-of-day clock.
    5210
    8187M-45 
    						
    							LINE#CONTENTS (10 COUNTERS PER LINE)REG
    TIME
    OUTS
    ATTENDTCONSOLE
    LOOP
    ATTEMPT
    LOOP
    USAGE000 ----
    TOLL
    RESTR;-E&T. x/C.INVALDID
    NO.RESTR
    0°’ lzDETINV
    AN#KE%s ---.
    002STILLBUSY;lg; ----!&.i%ELCALL
    PARK
    Oo3capELDLsLEVELLEVELTIME-------.1 WTG2 WTGOUT
    004 
    (2,ONSL.CON’& _-__ ____ ____ ____#2. . .005 CONSL. . . . .. . . . .. . . . .. . . .#1FNSL
    MISC.006 LINEATTEMPTSDTMF‘%E -.CONF CALLTONE 
    ---.STOREDETEC
    MISC.
    USAGE007 ----
    DTMFCONF CALLTONE ---.STOREDETEC
    008 ----DTMFCONF CALLTONE ----
    STOREDETEC
    RING
    ATTEMPTSRING
    USAGE
    RING
    OVERFLOW
    sLTAABRIOEY)
    ILsAEBONLY)
    LLsAEBONLY)
    MISCINC TRK
    CALLS
    009 PECO ____ ____ ---- ---- ----
    0’0 PECO ---- ___- _-__ ____ ____
    011PECO ___- ____ ____ ---_ ____
    012 KiiNCSCSN
    CSATOOR%ssNN%SN%ED013 INV
    PORTALR
    QUEDINV
    INVINVBAD
    NETW STATEPORTLINK014 ----
    -____________-----___015 
    AIODBLOCKED i&YDMCL ____
    HGC:!NWINT
    LEVEL 3016 TGOO
    017 
    TGlO018 
    TG20019 
    TG30020 
    TG40021 
    TG50022 TG60
    023 TGOO
    024 
    TGlO025 
    TG20026 TG30
    027 TG40
    028 TG50
    029 TG60
    TGOlTG02TG03
    TG04TG05
    TGllTG12
    TG13TG14TG15
    TG21TG22TG23TG24
    TG25
    TG31TG32TG33
    TG34TG35
    TG41TG42
    TG43TG44TG45
    TG51TG52TG53
    TG54TG55
    TG61TG62TG63. . . . . .. . . . . .
    TGOlTG02
    TG03TG04TG05
    TGllTG12TG13TG14TG15
    TG21TG22TG23TG24TG25
    TG31TG32TG33
    TG34TG35
    TG41TG42TG43TG44TG45
    TG51TG52TG53TG54TG55
    TG61TG62-,-G63 ____ ____CONF.
    RESTRCALL
    HOLD
    ____ACOF
    RESTR
    SILHOLD
    ----
    DIGITT/OUT
    ____
    ____INV
    AI-l-
    -_-_
    ____
    .,...
    DIGIT
    STORE
    DIGIT
    STORE
    DIGIT
    STORE
    INV
    TSINV
    STATEINV
    OFSTNOT
    QUED
    TSLOCK
    ____
    TG06
    TG16
    TG26
    TG36
    TG46
    TG56
    . . . . . .
    TG06
    TG16
    TG26
    TG36
    TG46
    TG56
    -__-TG07
    TG17
    TG27
    TG37
    TG47
    TG57
    TG07
    TG17
    TG27
    TG37
    TG47
    TG57----
    TGO6
    TG16
    TG26
    TG36
    TG48
    TG58
    TG08
    TGl8
    TG28
    TG36
    TG46
    TG56----
    TGO9
    TGl9
    TG29
    TG39
    TG49
    TG59
    . . . . . .
    TG09
    TGl9
    TG29
    TG39
    TG49
    TG59----
    M-46Figure 2.5Traffic Register Layout81875210 
    						
    All GTE manuals Comments (0)

    Related Manuals for GTE Omni Si Database Technical Practices Manual