------------------------------
[Hit (ESC) to return to CFE!]
------------------------------

                           CFE S12 Single Line Observation Help
                           ------------------------------------ 
    			   For: CFE V5.5        

Improvements in this slo version 
 1.    PRA can have a  SLO by GDN.
 2.    PRA can have a SLO session by NA.
===========================================================================
WARNINGS - EACH S12 SWITCH CAN ONLY HAVE A MAXIMUM OF 215 CALLS ON SLO!
There is a system limit of 215 simultaneous calls which can be under observation or sampled.  
This is a limit of the SACEADM.  The system printer also becomes a bottleneck if too many calls 
are under observation/sampling it is MANADATORY to minimise the number of observations.

BRA Always remove observaton as soon as the required data is captured.  If too many 
customers on a single module (ie. >5) are on SLO. Processor restarts may occur!

PRA Only apply SLO to a single PRA interface and then for a short period of time
CFE will limit the use of the GDN to a single PRA, if a GDN has more than one DIP then CFE will 
allow the single selection of a PRA from within the Trunk Hunt Group for observation!
===========================================================================
HELP FOR VIEWING D Ch PROTOCOL IN S12
-----------------------------------------------------
 A.     S12 Exchanges can undertake layer 3 protocol analysis if the customer
        has the relevant observation categories added to their number data profile.
        Once this is done local viewing is undertaken within OCFE by routing
        a copy of all RRN 121 (SLO) Reports to the logical exchange terminal
        that you the user are attached to.  Four important points to be noted.

 1.     A REPORT IS ONLY ISSUED (some time) AFTER THE CALL IS COMPLETED.
 2.     DURING SHORT TERM MONITORING YOU WILL SEE ALL CALL TRAFFIC FOR ALL
        CUSTOMERS UNDER OBSERVATION ON THAT SWITCH!
 3.     REPORT IS ONLY FOR SELECTED NUMBERS (MNs)
 4.     ONLY EIGHT MONITOR CELLS (8DNs) can be under observation per ASM (magazine)
        EG. 1xBRA with 8xMNs - To monitor all traffic requires 8 sessions.

 B.     OCFE supplies the terminal functions you need, these notes are to
        explain the use of each key.

 "1".  Intiate Observation on a Service.
       (1)    Requests input as to monitoring direction
       (2)    Checks customer data category to see if already ON
       (3)    Warns & Aborts if already ON
       (4)    Modifies customer data as required.
       (5)    Prompts on MN observation.
       (6)    Updates Activation History.

 "2".  Remove Observation from a Service.
       (1)    Modifies customer data as required.
       (2)    Updates Activation History.

 "3".  Remove old SLO sessions.
       (1)    Prompts for DN or GDN.
       (2)    Removes OBSERV category from select DN or GDN.
       (3)    Updates Activation History.
       
---------------------------------------------------------------------------------
Multiple sessions can be established (eg. one for each MN) with the reports
being sent to the local sorter.  To view reports and log the reports locally,
 ...read on...
---------------------------------------------------------------------------------
 "4".  Capture & View {LNCD} SLO Reports.
       (1)    Modifies Report Routing to your local terminal.
       (2)    Closes EXCH command log file.
       (3)    Opens a SLO.log file in H:\ozterm\log\...

 "5".  Stop Capture & View of {LNCD} SLO Reports.
       (1)    Closes the SLO.log file in H:\ozterm\log\...
       (2)    Re-Opens the EXCH command log file.
       (3)    Removes Report Routing from your local terminal.

 "6".  Check Activation History.
       (1)    A text file in your H:\OZTERM\LOG subdir that keeps a record of
              all capture sessions.  It is updated whenever a customer session
              is opened or closed.

 "V".  View SLO.LOG File
       (1)    Allows examination of the raw SLO reports contained in a
              text file in your H:\OZTERM\LOG subdir.
       (2)    Best viewed with SLO.LOG closed (Session closed off).

 "E".  Examine Protocol Trace
       (1)    Allows examination of the processed SLO data in a K1195 look
              alike format. Contained in a text file called SLOT.TXT in your
              H:\OZTERM\LOG subdir.
       (2)    If required, store the SLOT.TXT under another filename as it will
              be overwritten when next you next start a observation.
 "D"   Directory Number change existing or create a number.

------------------------------------------------------------
 HOW DOES ONE CONVERT A SLO REPORT TO A K1195 PROTOCOL TRACE?

 For an observation that has been captured on the local terminal,

       (1)    Close the local session via the "4" key.
       (2)    Go to DSTAT and first ensure that it is configured correctly
              for S12-SLO [via F2].  The settings required are;

              A.     Protocol - ETSI
              b.     Time - Hr Min Sec
              c.     Later 2 Trace Option - No L2
              d.     Analyser - S12
              e.     Output - Trace
              f.     Input File Name - H:\ozterm\log\slo.log
              g.     Output File Name - SLO

       (3)    In DSTAT press F3 to process!  When complete ...

       (4)    Alt Tab to Ozterm and press "E" to examine the protocol trace.

       (7)    If necessary, re-check the raw reports which contain the
              associated call handling data via the "V" key.

       (8)    Rename & Save SLO files where required for future reference.

 For long term observation or where full statistical information is required,

       (1)    Recover your call traffic reports via FTP from the sorter.
              (This process will be distributed by SE Brisbane when made
              available by S12 NBT)

-----------------------------------------------
LIMITATIONS OF SINGLE LINE OBSERVATION TRACING?


       (1)    Practical limit of 8 customers per ISM or ASM less degradation
              of call tracing occurs.  ie You can establish more than 8 sessions,
              the first 8 will work but no RRN121s will come out for those established
              past the 8th. A RRN 7469 will be offered per call indicating that the
              observation was unsuccessful. 
              Contact the TMG to audit and correct. 

       (2)    Effectiveness in LHG monitoring and PRA still to be defined.

       (3)    Message Octet Limit
              Due to limtations / fault within S12 platform, all messages are
              limited to 64 octets.  While this is OK for the majority of
              D ch traffic, SETUP messages particularly those containing UU1
              IE's may be truncated.  DSTAT & READQ931 will read up to the
              switch limit.  This issue is being SE'd by S12 NBT.

       (4)    If service has MNs, a seperate session for each MN is required else
              only traffic to the nominated individual number will be caught.

                                                 Ron Durkin (09/01/97)
