EXTRA FACILITY DESCRIPTION 1(12)

Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
EPK/MX IPAL 6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
EPK/MT (Pierre Gustafsson) 1998-04-17 B

CIL on HDU, Rural

Contents Page

1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Glossary and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 The file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Initiation of CIL on HDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.5 Retrieving CIL data from HDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.6 Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

3 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Created by: EBCINSV
 EXTRA FACILITY DESCRIPTION 2(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

1 General

1.1 Description

The CIL on HDU function provides storing of the Call Information Logging data on the Hard Disc
Unit (HDU). This is an alternative to the data output to external equipment, and will make the
SIU-board and the stationary terminal at the exchange unnessecary. The CIL data will be stored
1 kbyte at a time in a file on the HDU. The CIL data can then be transferred from the exchange to
a PC via xmodem and analysed. The maximum size of the CIL data files on the hard disc is set
via commands at the initiation of external dump.

1.2 Glossary and acronyms

CIL Call Information Logging

HDU Hard Disc Unit
 EXTRA FACILITY DESCRIPTION 3(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

2 Administration

2.1 General

The CIL on HDU facility stores Call logging data to the systems HDU. Three devices can be used
for storage. The data will be stored in files located in different directories, on which subfile
systems have been mounted. The subfile systems must be created prior to initiation of the facility
(at initiation of the exchange). The files can via commands be set to log calls of specific criteria,
e.g. minimum length of call. Maximum size of each file should be set at initiation.

To ensure that CIL data can be read from (by external application) and written to the HDU
simultaneously, one active file (for writing) and one passive (for reading) is used for each CIL-
device. These are located in different subdirectories under the CIL-x directory. As soon as the
active file is full, it is moved to the passive directory and becomes passive. If data is to be
retrieved before the file is full, the active CIL data file can be passivated by a command. The
passive file can then be transferred to a PC via xmodem.

The Call Logging on HDU facility is operated via commands from an I/O terminal. The command
groups used are CL (call logging) and ED (external dump).

The function mainly uses two units, FAM2 and EDH. The handler EDH must reside in LIM 1 and
the file administration program FAM2 must be an actice common function in the I/O-LIM.

It is possible to use dump to external equipment simultaneously with CIL on HDU.

 EXTRA FACILITY DESCRIPTION 4(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

2.2 The file system

In order to be able to store call information data on the HDU, the file system must be prepared for
this at initiation of the exchange. New directories for CIL should be created and new subfile
systems should be created and mounted. Subdirectory USR1/SES/ED is used for all call
information logging data.

SYSN

USR1 USR2 USR3

ACS SES

ED

CIL1 CIL2 CIL3

ACT PAS
subfile systems
(physical)
CIL active file

Figure: 2-1. Logical file structure

If the exchange is running with frequent traffic and retrieval of CIL data is not to be performed
more often than once a week, the files will require much discspace. Consequently, two subfile
systems are used for each of the CIL directories. One for the active file (ACT) and one for the
passive (PAS). The subfile systems are physical and can not be seen in the logical file structure.

In order to build up a new physical structure, the HDU has to be re-initiated, i.e. the device has to
be deleted first and then re-initiated with the new subfile systems included. To do this, we must
make sure that nothing is written to or read from the HDU by blocking its SCSI-port on the IPU
board. Also, the existing subfile systems have to be dismounted. The necessary command
sequence will be like this:

Block the SCSI port connected to HDU with BLEQI.

 EXTRA FACILITY DESCRIPTION 5(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

<BLEQI:EQU=1-0-XX-0;

EXECUTED

Dismount the existing subfile systems with FIMOE. (Prior to this, you can do a print out of all
subfile systems with command FISCP:IODEV=SYSDISK1;)

<FIMOE:SUBFS=SYSSUBFS11;

EXECUTED

<FIMOE:SUBFS=SYSSUBFS21;

EXECUTED

Delete HDU, i.e. end SCSI device with command IOSIE.

<IOSIE:NODE=SYSN,IODEV=SYSDISK1;

EXECUTED

Initiate HDU again, with the new subfile systems included.

<IOSII:NODE=SYSN,IODEV=SYSDISK1,SIPOS=3,SUBFS=SYSSUBFS11&SYSSUBFS21
&SYSSUBFSA1&SYSSUBFSP1&SYSSUBFSA2&SYSSUBFSP2&SYSSUBFSA3&
SYSSUBFSP3;
EXECUTED

The new subfile systems are created by FICRI command. We name them SYSSUBFSA1 to 3
and SYSSUBFSP1 to 3 for active files CIL1.ACT to CIL3.ACT and CIL1.PAS to CIL3.PAS
respectively. Also, the size of the subfile systems is set in command.

<FICRI:SUBFS=SYSSUBFSA1,SIZE=64;

SURE? (YES/NO)
YES;

EXECUTED

<FICRI:SUBFS=SYSSUBFSP1,SIZE=64;

SURE? (YES/NO)
YES;

EXECUTED

To enable construction of the logical file system (directories), the SCSI port connected to HDU
must be unblocked with BLEQE.
 EXTRA FACILITY DESCRIPTION 6(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

<BLEQE:EQU=1-0-XX-0;

EXECUTED

The logical paths should be constructed according to picture 2.1. The subdirectories under USR1
are created by command FIDII. Each CIL directory will in its turn have two subdirectories, one for
active file and one for passive file. The initiation must be done in two steps, i.e. directory CIL-x
must be created before its subdirectories (ACT and PAS).

<FIDII:PATH=/SYSN/USR1/SES/ED/CIL1;

EXECUTED

<FIDII:PATH=/SYSN/USR1/CIL1/ACT&/SYSN/USR1/SES/ED/CIL1/PAS;

EXECUTED

The subfile systems must be mounted in the file system, i.e. be affiliated to each one directory.
This is done with the File system mount initiate (FIMOI) command.

<FIMOI:SUBFS=SYSSUBFSA2,PATH=/SYSN/USR1/SES/ED/CIL2/ACT;

EXECUTED

2.3 Initiation of CIL on HDU

The prerequisites are that the file system is prepared for CIL storing, i.e. subfile systems must be
created at initiation of the exchange. The CIL on HDU option is initiated by setting a parameter in
the Initiate External Dump Equipment command (EDEQI). Also the affiliation between CIL files
and devices (directories on HDU) is set with ED commands. These are described in command
and parameter descriptions for External Dump.

Setting of storage file format, criteria for the calls that are to be logged and the initiation and
termination of Call Logging is done by using Call Logging commands and parameters described
in general Call Logging documents.

Example:

Two files are needed for call logging. One file for logging of all calls (for charging) and one file for
logging of international calls only. The files should be stored to each a CIL directory on the HDU.

Initiate (reserv) CIL directory 1 and directory 2 for external dump and a maximum file size of 58
Mbyte and 20 Mbyte respectively.
 EXTRA FACILITY DESCRIPTION 7(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

<EDEQI:DEV=CIL-1,SIZE=58;

EXECUTED

<EDEQI:DEV=CIL-2,SIZE=20;

EXECUTED

Initiate files LOGA and LOGB for (external) dump. The file name does not refer to the files that
will reside on the HDU, but the file for output of CIL data.

<EDFII:FILE=LOGA;

EXECUTED
<EDFII:FILE=LOGB;

EXECUTED

Link the files LOGA and LOGB to directories CIL-1 and CIL-2 on the hard disc respectively.

<EDDFI:DEV=CIL-1,FILE=LOGA;

EXECUTED

<EDDFI:DEV=CIL-2,FILE=LOGB;

EXECUTED

Verify external dump file settings by typing command EDFIP.

<EDFIP;

FILE ADMINISTRATION DATA

FILE STATE DEV DEVICE STATE SIZE PRIO

LOGA PAS CIL-1 STANDBY 58 -

LOGB PAS CIL-2 STANDBY 20 -

Affiliate files to call logging with CLOHI command. When call logging is done against the hard
disc (HDU), it is required to set parameter DMPSIZ=2 in this command. This states that CIL data
output is going to be in buffered form (i.e. one kilobyte at the time) as opposed to writing once for
each call occasion. Also, the output format is set by this command.
 EXTRA FACILITY DESCRIPTION 8(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

<CLOHI:FILE=LOGA,FORM=1,DMPSIZ=2;

EXECUTED

<CLOHI:FILE=LOGB,FORM=1,DMPSIZ=2;

EXECUTED

Initiate call logging output data for both files LOGA and LOGB. This command, CLODI also sets
criteria for calls that are to be logged. In this case LOGB file will only log calls beginning with 009.
Since LOGA is to log all calls, all CLODI parameters will be omitted in this case.

<CLODI:FILE=LOGA;

EXECUTED

<CLODI:FILE=LOGB,DIAL=009;

EXECUTED

You can also print / verify the call logging settings with command CLINP.

Initiate call logging traffic generation with command CLTGI.

<CLTGI;

EXECUTED

Now the CIL on HDU facility is activated and any calls will be logged and stored on the harddisc.

2.4 Alarms

As soon as an active CIL-file is full, it is copied into a passive CIL-file and alarm 352 is generated
in unit FAM2. This indicates that there is a new passive file to retrieve from the HDU. Also, if the
passive file is still not yet transferred from the exchange when the active one reaches 80% of its
predefined maximum size, alarm 352 is generated. This indicates that it is time to read the
passive file before it will be overwritten. The alarm contains information (addinfo) about in which
call logging directory on the harddisc the new passive file is to be found and which status it is
(New passive file created or active file 80% full). Consult Fault locating directions for alarm 352
for further information.
 EXTRA FACILITY DESCRIPTION 9(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

2.5 Retrieving CIL data from HDU

To avoid losing any CIL data, the file must be transferred from the exchange at regular intervals.
These intervals are depending on how much traffic is handled. The maximum file size and the
chosen call record format also affects the time between transfers.

A total of 517 842 records can be stored in a CIL directory if maximum file size is set to 58 Mbyte
and standard CIL data format is used. Each call record demands about 120 byte (if standard
format is used) and with an estimated 5000 calls per day the CIL data must be read once every
three months.

Passivation of CIL data

In order to enable all CIL data for transfer to PC, the active file can be passivated, i.e. a new
active file is created for new CIL data and the latest data is readable for the external equipment.
This is done by command EDFCI. To be sure no data is lost, the command will not be able to
execute if a passive file already exists. If a passive file exists it must first be retrieved and deleted
before running the command. The command then enables the latest data for reading and creates
a new active file for writing. Note: Since the command triggers a file copy procedure between two
subfile systems, it takes time to execute.

The syntax is (If the log-file under directory CIL-2 is to be deactivated):

<EDFCI:DEV=CIL-2;
ORDERED

SPONTANEOUS PRINTOUT
COPY SUCCESSFUL

To printout / verify the size of active and passive files, use command FIDAP

<FIDAP:PATH=/SYSN/USR1/SES/ED/CIL2/PAS,OPT=ALL;
FILE/DIRECTORY DATA

FILE FITYPE LINKS OWNER SIZE DATE

LOGB.PAS F 1 2 4582403 7APR98 16:59
END

File transfer and deletion

As soon as there is a new passive file to fetch (EDFCI has been run or alarm 352 generated), the
file transmission can be trigged from a remote PC-terminal. Any of the v24-ports on the I/O-card
can be used.
 EXTRA FACILITY DESCRIPTION 10(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

When retrieving a file from the exchange, the xmodem protocol is used. This must first be set by
In/out-commands. The transfer is then initiated by a file copy command (FICPI).

Xmodem protocol for a v.24 port (usually called SYSTERMINAL) is set by command IOIFC.

<IOIFC:IODEV=PORT2,PROC=XMODEM;

EXECUTED

Print I/O settings to verify. Use IOIFP command.

<IOIFP:IODEV=PORT2;
IO INTERFACE CHARACTERISTICS

IODEV IFACE BAUDR WORDL PARITY STPBIT PROC

PORT2 V.24 ALL 8 NONE 1 XMODEM

END

Transfer (copy) the LOGB.PAS file from the HDU via xmodem to remote PC using file command
FICPI. Be sure to use the correct absolute path. Consult manual for communication program
(FIOL / WinFIOL) for further advice on retrieving files from the exchange.

<FICPI:SPATH=/SYSN/USR1/SES/ED/CIL2/PAS/LOGB.PAS,IODEV=SYSTERMINAL2;
READY FOR TRANSMISSION

maintenance operator retrieves the file with PC terminal

EXECUTED

Note: Retrieving of the CIL data file (with FICPI) can not be done during dumping (even when the
terminal is no longer locked up).

The file must then be deleted from the CIL directory (to enable the use of command EDFCI). This
is done by command FIDIE.

<FIDIE:PATH=/SYSN/USR1/SES/ED/CIL2/PAS/LOGB.PAS;

SURE? (YES/NO)
<Y;

EXECUTED
 EXTRA FACILITY DESCRIPTION 11(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

2.6 Termination

To terminate the CIL on HDU facility completely means to close the output files and delete all
affiliations between HDU devices, files and criteria. It’s much like initiation, just reverse.

Example:

Terminate CIL on HDU.

End call logging traffic generation

<CLTGE;

EXECUTED

End call logging open header and call logging output data. Only the commands for file CIL1 is
shown.

<CLOHE:FILE=LOGA;

EXECUTED

<CLODE:FILE=LOGA;

EXECUTED

Delete the link between file LOGA and the device (call logging directory 1)

<EDDFE:DEV=CIL-1;

EXECUTED
 EXTRA FACILITY DESCRIPTION 12(12)
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.
6/1551-FAS 102 38 Uen
Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev File
1998-04-17 B

3 Hardware

No extra hardware is used for this facility. The internal Harddisc (HDU) is used to store the Call
Information Logging. In order to use three devices the hard disc must be of type HDU6 or later.
An external terminal can be connected to the exchange in order to read and analyse the data.

4 References

Operational Directions, External Dump 22/15431-FAS 102 38 Uen A

Command Description, External Dump 22/19082-FAS 102 38 Uen A
Parameter Description, External Dump 22/19084-FAS 102 38 Uen A
Operational Directions, Call Information Logging 24/15431-APD 101 02 Uen D3
Command Description, Call Information Logging 24/19082-APD 101 02 Uen D4
Parameter Description, Call Information Logging 24/19084-APD 101 02 Uen D4
Operational Directions, File Administration 1/15431-APD 101 02 Uen B3
Command Description, File Administration 1/19082-APD 101 02 Uen B4
Parameter Description, File Administration 1/19084-APD 101 02 Uen B
Fault locating directions, Alarm 352 9/15451-FAS 102 38 Uen A