CIL Spec Issue 5

1QHA 50491 AAW
Issue 5
REALITIS DX
CALL INFORMATION LOGGING (CIL)
SUPPLEMENT
CONFIDENTIAL
This is an unpublished work the copyright in which vests in Siemens plc. All rights reserved.
The information contained herein is confidential and the property of Siemens plc and is supplied without liability for errors or omissions. No part
may be reproduced,
Siemens disclosed or used except as authorised by contract or other written permission. The copyright and the foregoing restriction
Communications
on reproduction and use extend to all media in which the information may be embodied.
Technology Drive
Beeston
Nottingham NG9 1LA
A division of Siemens plc, Registered No: 727817, England.
ENGLAND Registered Office: Siemens House, Oldbury, Bracknell, Berkshire RG12 8FZ, England
Telephone: Nottingham (0115) 943 0300

This page is intentionally blank.
Page ii Issue 5 Copyright subsists, for restrictions refer to the title page 1QHA 50491 AAW
ISSUE STATE
The whole of this supplement is at the issue state shown in the table below.
DATE SIG. ISSUE CHANGE

14.03.00 AM 1 5027865
05.06.00 FAC 2 5028671
01.12.00 AM 3 5028964
03.06.03 FAC 4 5030550
03.10.03 FAC 5 5030624
CHECKED: TITLE:
FC Realitis DX Call Information Logging (CIL) Supplement
1QHA 50491 AAW Copyright subsists, for restrictions refer to the title page Issue 5 Page iii
Page iv Issue 5 Copyright subsists, for restrictions refer to the title page 1QHA 50491 AAW
CONTENTS
Page
Title page.......................................................................................................................... i
Issue state....................................................................................................................... iii
Contents.......................................................................................................................... v
Glossary.......................................................................................................................... ix
1 ABOUT THIS SUPPLEMENT.......................................................................1-1
1.1 SCOPE......................................................................................................... 1-1
1.2 CONDITIONS OF USE.................................................................................1-2
1.3 UPDATE POLICY.........................................................................................1-2
1.4 EXCLUSION OF LIABILITY..........................................................................1-2
2 GENERAL INFORMATION..........................................................................2-1
2.1 OVERVIEW OF CIL......................................................................................2-1
2.2 SOFTWARE REVISION INFORMATION......................................................2-2

2.2.1 CIL details for Realitis 8 Application pack 3 (8.0.031)..................................2-2
2.2.4 CIL details for Realitis 8................................................................................2-3
2.2.5 CIL details for Realitis 7.1.............................................................................2-3
2.3 HARDWARE.................................................................................................2-8
2.3.1 CIL access over Ethernet.............................................................................2-8
2.3.2 CIL access over the V.24 port....................................................................2-10
3 FULL CIL RECORDS...................................................................................3-1
3.1 INTRODUCTION...........................................................................................3-1
3.1.1 Basic Records...............................................................................................3-3
3.1.2 Continuation Records...................................................................................3-6
3.1.3 Conference Records.....................................................................................3-7
3.1.4 Exception Record.........................................................................................3-8
3.1.5 Order of Record output.................................................................................3-9
3.2 BASIC RECORD FORMAT.........................................................................3-10
3.2.1 Description of the fields in a “Basic Record”...............................................3-12
3.3 CONTINUATION RECORD FORMAT........................................................3-23
3.3.1 Description of fields in a “Continuation Record”..........................................3-25
1QHA 50491 AAW Copyright subsists, for restrictions refer to the title page Issue 5 Page v
3.4 CONFERENCE RECORD FORMAT..........................................................3-28
3.4.1 Description of the fields in a “Conference Record”.....................................3-30
3.5 EXCEPTION RECORD FORMATS............................................................3-31
3.5.1 Description of the fields in “Exception Records”.........................................3-32
3.5.2 Exception Record (codes 1 to 5)................................................................3-33
3.5.3 Exception Record for ISDN (code 6)...........................................................3-35
3.5.4 Exception Record for Packet Switching (code 7)........................................3-37
3.5.5 Exception Record for Packet Switching (code 8)........................................3-38
3.5.6 Exception Record for CIL inactivity (code 10).............................................3-39
3.5.7 Exception Record for System Restart (code 11).........................................3-40
3.5.8 Exception Record for Faulty Trunk Reporting (code 15).............................3-41
3.5.9 Exception Record for R2 CLI (code 16)......................................................3-42
3.5.10 Exception Record for iSPS Packet Switching (code 17).............................3-43
3.5.13 Exception Record for DPNSS Remote Party Details (code 20)..................3-46
3.5.14 Exception Record for CIL Account Code (Code 21)...................................3-48
3.5.15 Exception Record for Virtual Directory Numbers (Code 22).......................3-50
3.5.16 Exception Record for Malicious Call Trace (code 23).................................3-52
3.5.17 Exception Record for Malicious Call Trace (code 24).................................3-54
3.5.18 Exception Record for Diversion to PSTN (code 25)....................................3-56
3.5.19 Exception Record for Extension Lock/Unlock (code 26).............................3-57
3.5.20 Exception Record for Home-working activation (code 27)..........................3-58
3.5.21 Exception Record for Home-working de-activation (code 28).....................3-59
3.5.22 Exception Record for Home-working Long Call (code 29)..........................3-60
3.5.23 Exception Record for Hot-desking activation (code 30) and
de-activation (code 31)...............................................................................3-61
3.5.24 Exception record for Home-working call details (code 32)..........................3-62
3.5.25 Exception Record for Hot-desking call details (code 33)............................3-63
3.5.26 Exception record for Calling Line Identity (CLI) details (code 34)...............3-64
3.5.27 Exception Record for Invalid Pin Keyed (code 102)...................................3-65
3.6 EXAMPLE CALLS TO ILLUSTRATE THE OUTPUT OF CIL RECORDS...3-66
3.6.1 PSTN call to an Operator............................................................................3-66
3.6.2 Extension call to the PSTN.........................................................................3-67
3.6.3 Extension to extension call.........................................................................3-68
3.6.4 Extension call to the PSTN, including Conference.....................................3-69
3.6.5 Operator call to the PSTN, extends to Extension and releases..................3-71
3.6.6 Operator call to the PSTN, extends to Extension (waits for answer)..........3-72
3.6.7 Extension call to the Operator....................................................................3-73
3.6.8 Extension call to the Operator (Both and Release buttons pressed)..........3-74
4 TEXTUAL CIL...............................................................................................4-1
4.1 INTRODUCTION...........................................................................................4-1
4.2 TEXTUAL CIL OUTPUT...............................................................................4-2

4.2.1 Textual CIL example.....................................................................................4-3
Page vi Issue 5 Copyright subsists, for restrictions refer to the title page 1QHA 50491 AAW
Figures Page
Figure 2.1 CIL port connection for CILE..................................................................2-10
Figure 2.2 CIL port connection for Textual CIL.......................................................2-10
Tables Page
Table 2.1 V.24 port pin connections.......................................................................2-11
Table 3.1 Basic Record format for software revisions 2.1, 2.2 and 2.3..................3-10
Table 3.2 Basic Record format for software revisions 2.4 onwards.......................3-11
Table 3.3 Basic Record feature numbers and names............................................3-14
Table 3.4 Basic Record call duration examples.....................................................3-17
Table 3.5 Continuation Record format for software revisions pre-6.1, or
Revision 6.1 onwards with SPCAC set to 0 and SPACO set to 1..........3-23
Table 3.6 Continuation Record format for software revisions 6.1 onwards
SPCAC set to 1......................................................................................3-24
Table 3.7 Conference record format for software revisions 2.1, 2.2, 2.3...............3-28
Table 3.8 Conference record format for software revisions 2.4 onwards...............3-29
Table 3.9 Exception Record codes........................................................................3-31
Table 3.10 Exception Record format for exception codes 1 to 5.............................3-33
Table 3.11 Exception Record format for exception code 6......................................3-35
Table 3.14 Exception Record format for exception code 10....................................3-39
Table 3.31 Exception Record format for exception codes 30 and 31......................3-61
Table 3.35 Exception Record format for exception code 102..................................3-65
1QHA 50491 AAW Copyright subsists, for restrictions refer to the title page Issue 5 Page vii
Page viii Issue 5 Copyright subsists, for restrictions refer to the title page 1QHA 50491 AAW
GLOSSARY
ACD Automatic Call Distribution.
ACI Advanced Connectivity Interface. A descriptive name used when

describing the UPI card.
APNSS DPNSS where signalling is carried on a discrete signalling circuit to

control physically distant traffic circuits.
ASCII American Standard Code for Information Interchange. ASCII is the

most common format for text files in computers and on the Internet. In
an ASCII file, each alphabetic, numeric, or special character is
represented by a 7-bit binary number (a string of seven 0s or 1s). 128
possible characters are defined. ASCII was developed by the
American National Standards Institute (ANSI).
Baud Rate A measure of the rate of transmission usually in units of bits per
second. Start, data and stop bits are all included.
CIL Call Information Logging.
CILE Call Information Logging Equipment.
CLI Calling Line Identity.
CPU Central Processing Unit.
DDI Direct Dialling In. Implicitly, DDI trunks are incoming from the PSTN.
DLI Digital Link Interface.
DPNSS Digital Private Network Signalling System.
DX Digital eXchange. A generic term use to describe the Realitis and

iSDX systems.
EXCH Exchange (e.g. PSTN) trunk.
Gateway PBX A PBX which connects a DPNSS trunk to a non-DPNSS trunk (e.g. a
DPNSS to DASS gateway).
HCIL MMI command to halt CIL output.
I/O Input/Output.
IP Internet Protocol. A network protocol used to send messages requiring

an address or the host name of the addressee.
IPBX Inter PABX trunk.
ISDN Integrated Services Digital Network.
iSDT Integrated Services Digital Terminal.
1QHA 50491 AAW Copyright subsists, for restrictions refer to the title page Issue 5 Page ix
iSDX Integrated Services Digital Exchange.
iSPS Integrated Services Packet Switching.
LAN Local Area Network. A data communications network within a limited

physical area.
MCT Malicious Call Trace.
MF4 A dual tone multi-frequency, voice band signalling system for sending
and receiving digits.
MMI Man Machine Interface. The interface at the DX for configuration and
maintenance of the system.
Mobile TAC Mobile Trunk Access Class of service.
NU Number Unobtainable.
NUC Nailed Up Call.
OLI Originating Line Identity.
PABX Private Automatic Branch Exchange.
PBX Private Branch Exchange.
PIN Private Identity Number.
PSD Packet Switched Device.
PSTN Public Switched Telephone Network.
PTO Public Telephone Operator.
R2 CCITT Line and Register Signalling System.
RAD Recorded Announcement Device.
RCIL MMI command to resume CIL output.
Realitis DX An EMC approved digital exchange.
Realitis DX150 A single cabinet EMC approved digital exchange, formerly known as
the Realitis Micro.
Realitis DX150E A single cabinet EMC approved digital exchange supporting up to 6

DLIs.
Realitis DX150R A one- or two- unit system designed to be mounted in a 19-inch

electronic equipment rack or be free-standing on a desktop,
supporting Realitis 7.1 software release. The system is an EMC
approved digital exchange supporting 144 extensions and up to 6
DLIs.
Page x Issue 5 Copyright subsists, for restrictions refer to the title page 1QHA 50491 AAW
Realitis DXR The name of a one-, two-, three- or four-unit PABX designed to be
mounted in a standard 19-inch computer rack or free-standing (table-
mounted), supporting Realitis 8.0 software release and onwards. The
Realitis DXR is manufactured by Siemens Communications.
Realitis DXR* The name of a one- or two-unit PABX designed to be mounted in a

standard 19-inch computer rack or free-standing (table-mounted),
supporting Realitis 8.0 software release and onwards. The Realitis
DXR* is manufactured by Siemens Communications.
RS-232C RS-232C is a standard that describes the physical interface and

protocol for relatively low-speed serial data communication between
computers and related devices. It was defined the Electronic
Industries Association (EIA), originally for teletype devices.
TAC Trunk Access Class.
TBCD Telephonic Binary Coded Decimal. In all TBCD fields, digit 0 is

represented as 10 decimal. A null TBCD digit represents nothing. All
TBCD fields are terminated by nulls if less than full.
TCP Transmission Control Protocol. The transport protocol used to

transport messages over a network.
TLI Terminating Line Identity.
UPI Universal Peripheral Interface card. The UPI functions as an MMI

input/output processor for the CPU. The diagnostic, application files,
the system operating and MIB agent software are supplied pre-loaded
onto the flash memory. The UPI provides the following facilities: up to
four delta channels, four V.24 interfaces, SCSI interface, Ethernet
interface, mass storage up to 8Mbyte, arbitration logic.
V.24 Part of the series of ITU interface specifications.
VDN A Virtual Directory Number, one which has no physical channel

address on the system.
VDU Visual Display Unit.
WAN Wide Area Network. This is a network that covers an area larger than
a city or a metropolitan area.
1QHA 50491 AAW Copyright subsists, for restrictions refer to the title page Issue 5 Page xi
Page xii Issue 5 Copyright subsists, for restrictions refer to the title page 1QHA 50491 AAW
1 About this supplement
SECTION 1
ABOUT THIS SUPPLEMENT
1.1 SCOPE
This supplement describes the Call Information Logging (CIL) interface and the CIL output
for Realitis DX and iSDX systems. The information provided in this supplement can be
used to assist in the design of Call Logging Information Equipment (CILE) that may be
connected to the following range of systems running software revisions from 3.6.201 up to
and including Realitis Rev 8:
 Realitis DX (Digital Exchange);

 Realitis DXR/DXR* (Realitis Rev 8 onwards only);
 Realitis DX150R (Realitis Rev 7.1 only)
 Realitis DX150/DX150E;
 iSDX-series (iSDX-L, iSDX-T, iSDX-S or iSDX-Micro).
This supplement is not intended as a stand-alone document and must be used in

conjunction with the appropriate publications (where referenced) when activating CIL on
DX systems.
The word system or DX is used throughout this supplement to refer to the Realitis DX,
Realitis DXR/DXR*, Realitis DX150R, Realitis DX150(E) or iSDX-series of switches unless
it is necessary to distinguish between them. Where a reference is made to a particular
revision of software, the following applies:
 5.2 and earlier - for iSDX-series only.

 6.0 - for Realitis DX only.
 6.1 and 6.2 - for Realitis DX, Realitis DX150E, Realitis DX150 and iSDX-series (not
including the iSDX-MN).
 6.3 - for Realitis DX, Realitis DX150R, Realitis DX150E, Realitis DX150 and iSDX-
series (not including the iSDX-MN).
 7.1 - for Realitis DX, Realitis DX150R, Realitis DX150E, Realitis DX150, iSDX-L/T,
iSDX-S and iSDX-Micro.
 8.0 and onwards - for Realitis DX, Realitis DXR/DXR*, Realitis DX150E,
iSDX-L/T, and iSDX-S.
1QHA 50491 AAW Copyright subsists, for restrictions refer to the title page Issue 5 Page 1
Section 1 : About This Supplement Realitis DX Call Information Logging (CIL) Supplement
This supplement is divided into four Sections:
 Section 1 : About this supplement - provides a description of the contents of this

supplement and its use.
 Section 2 : General Information - provides an overview of CIL (Call Information
Logging), information on the changes or additions to the CIL output on software
revisions 6.0 onwards and a description of the hardware interface (Ethernet and V.24)
on DX systems.
 Section 3 : Full CIL Records - provides detailed information on the structure and
contents of the various types of Full CIL records output by DX systems.
 Section 4 : Textual CIL Records - provides detailed information on the structure and
contents of the Textual CIL output by DX systems.
1.2 CONDITIONS OF USE
This Supplement may only be used by the party it is sent to by Siemens (“the Recipient”)
and a subcontractor of the Recipient to whom the Recipient has subcontracted the use
which is authorised hereunder and provided that any such subcontractor accepts all of the
terms and conditions within this Supplement.
This Supplement may only be used for the purpose identified in 1.1 above.
Siemens shall have no obligations to make any changes to or update the Supplement or
to answer any queries or provide any support in respect of it.
This Supplement may not be disclosed by the Recipient to any third party save as
expressly authorised hereunder.
This Supplement is an unpublished document and is disclosed on a confidential basis.
1.3 UPDATE POLICY
The information in this supplement may be updated by an up-issue of the whole

supplement. This may be produced to correct one or more errors, to incorporate
information due to changes in equipment design, or a combination of both. Errors of an
editorial nature usually do not warrant an up-issue on their own, and are corrected when it
becomes necessary to incorporate technical changes.
The issue state page at the front of the supplement gives the current issue state for the
whole of this supplement.
1.4 EXCLUSION OF LIABILITY
This Supplement is provided free of charge and As Is and Siemens shall not be
responsible for any errors or omissions within or for it, any losses, costs or damages
indirect or direct, or any loss of profit or consequential loss arising from and or in
connection with its use and whether arising from negligence or otherwise, save in respect
of personal injury due to its negligence.
Page 2 Issue 5 Copyright subsists, for restrictions refer to the title page 1QHA 50491 AAW
2 General Information
SECTION 2
GENERAL INFORMATION
2.1 OVERVIEW OF CIL
CIL (Call Information Logging) is a feature that provides records of all incoming and
outgoing PSTN and inter-PBX calls, and all calls made between extensions.
The DX system transmits call information data (when available) to a Call Information
Logging Equipment (CILE). The logger can be connected to one of the V.24 ports or to the
Ethernet port on the System card or UPI card. It can be a dedicated processor with high
capacity hard-disks or an application program that is run on a PC. This latter gives the
flexibility of running other applications on the same equipment, such as an information
service or a directory package for console operators.
Note: Ethernet port address information is contained in this publication. If the

information on how to set-up and activate this feature is required, a request must
be made via Product Management at Beeston.
The CIL output reports all incoming and outgoing PSTN, IPBX calls and all calls between
extensions. Invalid and incomplete dialling sequences are ignored. Additional information
includes:
 Time at the end of the call;

 Julian date;
 Duration of the call;
 Meter pulses (if provided);
 Trunk access code;
 Trunk routeing digits;
 Call account code (if applicable).
Notes:
1. Trunks that have been reported as faulty are also indicated.
2. Additional records specific to Siemens Communications may also be output with the
CIL data. To avoid any malfunctions the attached CILE must be programmed to
ignore record types that are not specified in this Supplement.
Section 2 : General Information Realitis DX Call Information Logging (CIL) Supplement
There are two types of CIL:
 Full or unrestricted CIL - The CIL data is output in binary format. The CILE is a
computer (with appropriate software) that stores and analyses the data to produce
traffic records, statistical graphs and charts, etc.
 Textual or restricted CIL - The CIL data is in ASCII format, and contains a restricted
number of call records (see Section 4 Textual CIL records). The CIL equipment is a
dumb line-printer or screen-monitoring terminal.
The type of CIL used is configurable by the system parameter SPCIT (0 = Full (normal)
CIL, 1 = Textual CIL). The configuration can be changed at the maintenance terminal.
Refer to the Realitis Electronic Publications, Command Manuals and Service Manuals for
further information on system MMI commands and settings.
2.2 SOFTWARE REVISION INFORMATION
The following is a summary of CIL improvements that were introduced for the most recent
Realitis DX software revisions. Refer to Section 1 of this supplement for information about
system types and the software revisions they support. Refer to the Realitis Electronic
Publications, Command Manuals and Service Manuals for further information on system
features, MMI commands and settings.
2.2.1 CIL details for Realitis 8 Application pack 3 (8.0.031)
This application pack for Realitis 8 software release introduced the following.
Basic Record indicating feature code 61 - this code is used to indicate that a Join-in
Conference has been activated. When an activation is successful, a "Basic Record" with
the appropriate feature code is output to the CIL port
Exception Record code 34 - is output to the CIL port to indicate the Calling Line Identity
(CLI) that is sent when the User-selectable CLI feature is used (refer to subsection 3.5.26).
This application pack for Realitis 8 software release introduced the following.
Basic Record indicating feature codes 57, 58, 59 and 60 - these codes are used by the
Hot-desking/Home-working features to indicate when a session has been activated or
deactivated. When an activation or deactivation is successful, a "Basic Record" with the
appropriate feature code is output to the CIL port.
 57 - Home-working session activated.

 58 - Home-working session deactivated.
 59 - Hot-desking session activated.
 60 - Hot-desking session deactivated.
Exception Record codes 32 and 33 - are output to the CIL port to indicate call details for
either Home-working or Hot-desking feature (refer to subsections 3.5.24 and 3.5.25).
Realitis DX Call Information Logging (CIL) Supplement Section 2 : General Information
This software release contained no additions or improvements for CIL and supports all
previous software release updates on DX systems.
2.2.4 CIL details for Realitis 8
2.2.5 CIL details for Realitis 7.1
The following features introduced for 7.1 have an effect on CIL output.
Hot-desking and Home-working
The following features were introduced to enable users to access their PABX extension
Directory Number (DN) and facilities using a hot-desking environment within the office
(Hot-desking) or at home (Home-working).
Users who wish to hot-desk or home-work, are allocated a personal number (a Virtual
Directory Number - VDN) which can be dynamically mapped to a physical telephone
(PABX or PSTN). The physical phone can be: the user’s office telephone (if they have
one), a designated hot-desk telephone (one with EHD COS) or a home telephone
(remote).
Note: Hot-desking telephones can be on the same node (local) as the office telephone
or on a different node (remote) within the private network.
When a personal number is mapped to a hot-desk or home-working telephone, a hot-

desking or home-working session is said to be activated. Calls made by a Hot-desking
user or home-worker, are output as normal calls (Basic records, etc.) and are identified by
the personal number (VDN). Calls made to a personal number are output as normal calls
to the personal number (VDN). Additional CIL records are produced to cover the use of a
trunk to and from the Home-working telephone.
A session may be deactivated automatically, because of a period of inactivity or the time-

of-day. MMI command attributes are used to specify whether a particular user is exempt
from inactivity and/or time-of-day controls. Hot-desk users can use a feature to extend the
period of a hot-desking session by an amount specified by a system parameter.
Hot-desking - this feature allows users to make and receive voice calls from selected
telephones (known as hot-desk telephones) retaining the same telephony attributes such
as DN, COS, TAC, name text (if configured) and group membership assigned to them
using Virtual Directory Number (VDN) configurations on the local PABX. To other users on
the internal (private) or external (PSTN) networks, the hot-desk user appears as though
they are always using the same telephone.
Home-working - this feature allows users to make and receive voice calls to/from the
private network from a telephone on the public network. To callers who are using the
company's network (internal or external), the home-worker appears as though they are
using an office telephone on the private network. The home telephone is treated by the
PABX as a POT (Plain Ordinary Telephone).
To make calls from their home telephone into the private network, the home-worker must
first call a DDI number on the PABX. This number is translated into a feature code that is
used to activate a home-working session (if not already activated) and log on to the PABX.
Once the user has logged in, they can make calls and access the features available to the
users of an analogue telephone (POT). The PABX records all failures to log in with a
reason. Using a MMI command (LFPU), the list and clear information detailing the failures
can be retrieved.
Feature security considerations - system administrators can monitor the Home-working

feature for breaches in security or inappropriate use, by collecting and analysing the CIL
“Basic Record” (feature number 55 - forced or 56 - user invoked output when a password
has been changed successfully) and the “Exception Record” (code 29 is output for long
calls indicated the connection (trunk) used and the dialled digits) for each call.
Exception Record codes 27 and 28 - are output to the CIL port to indicate either
activation or de-activation of the home-working feature (refer to subsections 3.5.20 and
3.5.21). The home-working session can be activated and deactivated by: the home-
worker, by a privileged extension or by an operator with PVG COS. The DX MMI can also
be used to deactivate a home-working session. Users may specify a time-delay before a
home-working session is activated. A “returned to desk” feature can be used by a home-
worker at their office telephone (if they have one) to deactivate the session.
Exception Record code 29 - is output to the CIL port indicating long call durations for
home-working connections. The record output is controlled by the system parameters
TMLC1 and TMCLR (refer to subsection 3.5.22).
Calls to/from the internal (private) or external (public) networks to the hot-desking/home-
working telephone and vice versa will be output (on a per call basis) as normal CIL records
("Basic", "Continuation", "Conference" and "Exception") and use the personal number
(VDN) to identify the user. Additional CIL records are also output to indicate the
connection (trunk) used when making calls to/from the home-worker’s telephone.
Exception Record codes 30 and 31 - are output to the CIL port to indicate either
activation or de-activation of the hot-desking feature (refer to subsection 3.5.23). Hot-
desking sessions can be activated and deactivated by: the hot-desk user, by a privileged
extension or by an operator with PVG COS. The DX MMI can also be used to
activate/deactivate a hot-desking session. A “returned to desk” feature can be used by a
hot-desk user at their office telephone (if they have one) to deactivate the session.
Basic Record indicating feature codes 55 and 56 - these codes are used by the Hot-
desking/Home-working features to indicate when a user password has been changed.
When a password has been changed successfully, a "Basic Record" with the feature code
"55" or "56" is output to the CIL port.
 55 - forced password change.

 56 - user invoked password change.
If a session is activated or deactivated by the hot-desk/home-worker user, a password

may be required. MMI command attributes are used to specify whether a particular user is
exempt from password control. The expiry period for passwords is controlled by a system
parameter (TMPPE) and a user is forced to change their password on activation of the
hot-desking or home-working feature. Passwords can also be changed by the user dialling
the correct feature code.
Additional records for conference calls - are output to the CIL port at the point in a call
when additional parties are added to the call. The extra records (e.g. Basic and
Conference) are in addition to the records that are normally output at the end of each
phase of a call. Refer to subsection 3.1.3 for further information.
The following features introduced for 6.2 have an effect on CIL output:
 Extension Lock/Unlock - also known as Alternate COS/TAC.

 Divert to anywhere - in particular, diversion to the PSTN.
The effects on the CIL output are as follows. For full details, refer to Section 3 on
individual record types.
 Feature codes are added to the “Basic Record” for the Extension Lock/Unlock feature.
Locking an extension sets its COS and TAC to a system-defined “Alternative COS and
TAC”. Unlocking the extension restores its normal COS and TAC.
 The “Exception Record 25”, records the diverting extension when a call is diverted to
the PSTN in order that call charges can be allocated appropriately.
 The “Exception Record 26” records details of Extension Locking and Unlocking.
Realitis 6.1 software was introduced to allow the Realitis DX and iSDX systems to be run
on a common software platform. This enabled the iSDX to benefit from the Ethernet
interface capability already supplied as standard on the Realitis DX running software
revision 6.0. Changes that affect the CIL output generated by telephony or data calls
made at software release 6.1 are included in this supplement.
Notes:
1. The iSDX-Micro was renamed the Realitis Micro, so that all sales of products in
European markets now bear the Realitis name.
2. With effect from Release 6.1.202, the Realitis Micro was renamed Realitis DX150 to
reflect the software modification to allow up to 144 extensions.
3. The Realitis DX150E replaced the Realitis DX150 in 1999 and has a hardware
modification to allow up to 6 Digital Link Interfaces (DLIs).
Existing iSDX systems in European markets are supported for upgrades of software only.
iSDX systems can be sold outside Europe where the EMC regulations do not apply. The
name iSDX-Micro is reserved for the extended port, non-EMC version of a Micro.
Realitis and optiset E telephones were introduced with Revision 6.1 with no specific effects
upon CIL output.
New or changed features that affect CIL output are:
 Handling of routing digit strings longer than 18 digits.

 Account codes.
 Virtual numbers.
 Malicious call trace.
 Pull Diversion.
For CIL equipment to maintain full compatibility with the Realitis 6.1 and subsequent
software releases, then the following general points will have to be incorporated into the
CILE. Full details are included in Section 3 for individual record types.
Continuation Record
This is used for outgoing calls and has a optional format controlled by the setting of a
system parameter (SPCAC). This parameter is normally set to 0 (default) in order to
continue with the pre 6.1 format. The format (set to 1) allows a longer outgoing dialling
sequence of digits to be recorded (26 digits instead of 18) and moves the Account Code
data to a separate “Exception Record” (code 21) in order to allow this expansion to occur.
Exception Record 21
This is used for all account codes and is always associated with the previous “Basic
Record” for the same extension number. More than one account code could be dialled
from an extension. For each account code an exception record is created. At Release 6.1,
account codes can be recorded for any type of call, internal, incoming or outgoing
external. The “Exception Record” enables call account codes of up to 20 digits to be used
(pre 6.1 the limit was 8 digits).
Note: Account codes can be recorded in the pre 6.1 format for continuity, but only when
the parameter SPCAC is set to 0 and the parameter SPACO is set to 1.
Virtual Directory Number
Virtual Directory Numbers (VDNs) enable users with no fixed location to have normal
telephone directory numbers without associated dedicated physical addresses. A virtual
number must be either diverted to an extension, operator, voice messaging or paging
system, or allocated to a Line key on a keysystem telephone. Virtual numbers use the
same class-of-service and feature arrangements as other directory numbers.
When used in a Keysystem group a VDN can be used as the calling number or the
called/connected number in a telephone call.
For example:
Extension 2000 is a real number attached to a physical keysystem telephone and is

allocated to Line key 1. Extension 2549 is a VDN in use on Line key 2 and is shared with
another physical keysystem telephone bearing the real number 2200.
Therefore, if the Line key for 2549 is pressed, 2549 becomes the calling number in a CIL
Basic Record (this does not tell which telephone is in use). The same situation occurs if
the VDN 2549 is called. It could be answered at either the 2000 or the 2200 telephone.
This release of software (6.1) allows for VDN calls by adding an “Exception Record”
(code 22) to the full CIL record of the call. This record would show 2549 as the VDN and
2000 as the real number in a call in which 2549 is shown as one of the parties in the Basic
or Conference record. This extra information allows calls to be tracked to physical
extensions.
Malicious Call Trace (MCT)
This feature can be invoked in one of five ways.
 Entry of a feature code from an extension.

 Entry of a feature code from an extension on behalf of another extension.
 Pressing of MCT function button on an operator console.
 Using MMI.
 Automatically for incoming trunks calling particular extensions.
When used, it causes two “Exception Records” to be given immediately (“Exception

Record” code 23 and 24).
 Exception Record code 23 - is used to indicate the extension number of the party who
requested the trace and also the extension number of the calling/called party.
Extensions located nearby can invoke an MCT request (avoiding interrupting the
connected malicious call) in this case the two numbers are different.
 Exception Record code 24 - (immediately follows a code 23 record) is used to indicate
the information of the calling malicious party, being either an extension number (local
call) or node number or a trunk number plus CLI digits, if known. The CLI will always be
available on a DPNSS or QSIG call and may be available on an ISDN, DASS2 or R2
call. The call for which MCT is requested will still be recorded as a normal call in CIL.
Users can invoke MCT before the end of a call. In this case, the complete CIL “Basic
Record” of the call is the next “Basic Record” for that called party to be received in the CIL
data stream. Alternatively, the user can invoke MCT after the call has ended. In this case,
there is a reduced level of information, as the DX does not retain call information after the
end of a call. The “Exception Record” code 23 is produced for the requesting extension,
but the “Exception Record” code 24 has no information on the Malicious caller. The CIL
analysis must relate this MCT request to the latest previous “Basic Record” containing the
extension number of the requesting party.
Pull diversion
The feature codes (49, 50, 51) have been added to “Basic Record”. All incoming calls are
diverted to a specified extension. This diversion is set from the specified extension and
can be password controlled. Password control must be enabled by MMI (if used).
Note: This feature may also be known as “Follow Me” or “Call Follow Me”.
Continuation Record (Flags F3 and F4)
These two flags (F3 and F4) in the “Continuation Record” are no longer in use. Previously,
the flags used to contain the Save and Repeat Dialled Number information.
2.3 HARDWARE
DX systems transmit call information data to the Call Information Logging Equipment
(CILE). The logger can be connected to one of the V.24 ports or to the Ethernet port on
the System card or Universal Peripheral Interface (UPI) card.
It is important that CILE equipment that is connected to the V.24 ports or the Ethernet port
must be approved by the relevant approvals authority and must meet the appropriate
safety standards for that equipment.
Siemens Communications will not accept any liability for the connected equipment.
WARNING
PROTECTION AGAINST ELECTRIC SHOCK OR

DAMAGE TO EQUIPMENT
The interconnection ports are classified as SELV (safety extra-low voltage)

interconnection ports as defined in European standard EN60950.
As such these ports must only be connected to SELV ports on other equipment.
2.3.1 CIL access over Ethernet
In addition to CIL access over V.24 ports, in all Realitis DX and iSDX systems with
Software Revision 6.0 onwards, the System card or UPI card (Advanced Connectivity
Interface (ACI)) allows remote access to the CIL stream over the Ethernet.
Note: Ethernet port address information is contained in this publication. If the

information on how to set-up and activate this feature is required, a request must
be made via Product Management at Beeston.
The CIL TCP server on the System/UPI cards allows a maximum of three concurrent
connections from remote client equipment (e.g. CILE). When the three connections are in
use, subsequent connection requests are rejected.
Connecting to the CIL server
To gain connection to the CIL server on the System/UPI cards, it is necessary for the
remote CILE to open a TCP/IP connection to the IP address of the active side DX. The
connection request must contain the logical port number of the particular service required.
The DX System/UPI card TCP/IP address is specified by the variable "IPACT" in the
permanent database, the local maintenance engineer would normally program this
address.
The Logical port number for the CIL Server is defined below:
Port Number (decimal) Service Information
17257 CIL Server This is ‘Ci’ in ASCII
Once a connection is established, the DX will begin sending packets to the connected
client, containing CIL records in the format described below.
CIL Ethernet stream format
CIL records are defined as having a fixed length of 22 octets. The CIL Ethernet server
transfers CIL information as a stream of 22 octet records formatted according to the four
standard CIL record types. The start of each record is uniquely identified by the CIL record
header and contains the bytes EEFF hex (TBCD).
CIL records are given in real time on the stream. It should be noted that a particular
Ethernet packet may contain any number of complete CIL records.
Maintaining CIL client connections
In addition to the CIL record data, the CIL server in the DX periodically ‘polls’ the status of
all connected clients using a special Heartbeat Message (HM).
A heartbeat message consists of 4 bytes, as follows:

Byte 0 1 2 3
Heartbeat message 0 0 FF FF
On receiving a heartbeat message, the connected client is required to respond with a

heartbeat message of its own (i.e. echo the message back to the DX). Heartbeat
messages are transmitted to each connected client every 2 seconds. If a connected client
fails to respond for more than 30 seconds, the DX server considers the client to have
disconnected, and closes the associated TCP/IP connection.
If the client process fails to receive a number of heartbeat messages from the DX, it may
assume that the DX connection has been lost, and attempt to re-connect to the associated
server (i.e. this may happen in the course of a DX restart).
Heartbeat messages are embedded within the CIL stream every 2 seconds, regardless of
other information being transmitted from the DX. A CIL client process is required to
separate the incoming stream into CIL records and heartbeat message accordingly.
The effect of switch-overs and restarts
If a DX switch-over or restart occurs, all connected sockets are destroyed. A client process
may detect this condition by the loss of heartbeat messages from the switch for a period of
time. If this occurs, the client is responsible for re-establishing communication by
requesting a new connection to the associated server.
2.3.2 CIL access over the V.24 port
The V.24 ports from the System or UPI cards are presented via three V.24 port wall boxes
(Realitis DX, Realitis DXR/DXR*, Realitis DX150R, iSDX-L/T and iSDX-S), mounted
directly on the side of the system (Realitis DX150E, Realitis DX150, iSDX-Micro) or on the
patch panel (Realitis DX, Realitis DXR/DXR* and Realitis DX150R) for the connection of
peripheral devices (e.g. CIL equipment). The ports use the standard V.24 pin connections.
The following diagram shows how CIL equipment can be connected to the CIL Port on a
DX.
Figure 2.1 CIL port connection for CILE
From software revision 3.6.201 onwards, Textual CIL output can be configured as an
alternative to the full CIL output otherwise given.
When Textual CIL is configured, a printer or VDU can be connected to the CIL port to
display the textual CIL records.
Figure 2.2 CIL port connection for Textual CIL
For further details of Textual CIL output, refer to Section 4.
Electrical characteristics of the CIL port
When CIL equipment (a printer or a VDU) is connected to the CIL port, the DX is the DCE
and the CIL equipment (printer or VDU) is the DTE. The DTE must be configured for
asynchronous (e.g. Character Mode) operation.
Use the V.24 to CIL cable assembly (1HAU 50477 AAA - 25 way D-type) between the
equipment connected to the CIL V.24 port and the System/UPI card. If the adapter cable
is not used, return to Siemens Communications.
The CIL port is a 25 way D-type connector and the pin assignments comply with ISO
2110. Table 2 .1 V.24 port pin connections shows the interchange circuits supported by
this port, together with associated pin numbers.
Table 2.1 V.24 port pin connections
Pin Function
Number
1 Protective Earth.
2 Transmit Data (TXD). See Note.
3 Receive Data (RXD).
4 Request to Send (RTS).
5 Clear to Send (CTS). ON confirms that the logger is ready to
receive next character from the DX. OFF state is maintained until
logger is ready.
6 Data Set Ready (DSR).
7 Signal Ground (DSG). Provides reference potential for signals on
the interchange circuits.
8 Data Channel Received Line Signal Detector (RLSD).
20 Data Terminal Ready (DTR).
Note: Characters (data) MUST NOT be passed from the logger into the DX as this can
cause the DX to crash.
When a DCE (DX) is connected to a DTE (CILE) the pins normally have a straight through
connection. The following pins must be connected together depending on the system and
software revision to ensure the connection remains active, thus preventing loss of data.
For all platforms with a V.24 CIL port on a System card (software revision 7.1 onwards):
The provision for full hardware handshaking is supported in compliance with the
V.24/RS232 standard. If enabled in software, then pin 20 must have a signal present
when external equipment is connected and pin 4 must have a signal present when
external equipment is ready to receive data.
For systems with a V.24 CIL port on a UPI card (software revision 6.0 onwards):
 Realitis DX series and iSDX systems - Pins 4, 6 and 20 are connected together, and
must have a signal present.
 iSDX-Micro - Pins 4 and 20 are connected together, and must have a signal
present, and
Pins 6, 8 and 20 are connected together, and must have a signal
present.
For systems with software revision 5.2 and earlier:
 iSDX-L/T - Pins 6 and 8 are connected together, and

Pins 4 and 20 are connected together.
 iSDX-S/MN - Pins 5, 6 and 8 are connected together, and
Pins 4 and 20 are connected together.
 iSDX-Micro - Pins 4 and 20 are connected together.
The interface for CIL uses unbalanced, double - current working, the basic principles of
which are as follows. There is one wire per interchange circuit, but two signal states can
be applied:
 Mark (1), which is a negative voltage (-v) with respect to signal ground (Pin 7).
 Space (0), which is a positive voltage (+v) with respect to signal ground (Pin 7).
Voltage levels for signals originated by the CIL port are:
Mark = between -9 volts and -12.0 volts with respect to signal ground.
Space = between +9 volts and +12.0 volts with respect to signal ground.
Voltage levels for signals received by the CIL port are:
Mark = between 0 volts and -12 volts with respect to signal ground.
Space = between +3 volts and +12 volts with respect to signal ground.
Notes:
1. iSDX systems running 5.2 only. If the Alarm/CIL interface card is disconnected
from the backplane at any time, a resume CIL (RCIL) MMI command must be
issued in order to restart the CIL. It is also advisable to issue a halt CIL (HCIL)
command before disconnecting the card. Also, the Clear to Send is normally set
“HIGH” as the DX has not been programmed to receive information from DTE
attachments.
2. In cases where attachments return data to the CIL port causing the system to fail,
Siemens Communications cannot be held responsible.
Data transmission parameters
The data transmission parameters are fixed as follows, for full CIL on the CIL port. The
lowest order data bit is transmitted first.
Number of Start bits 1
Number of Data bits 8
Number of Parity bits 0
Number of Stop bits 2
-----
Total 11
The transmission rate used by the DX can be varied, depending upon the number of lines
and the capabilities of the CIL equipment being connected to the CIL port.
The recommended minimum rates are as follows:

Number of Lines Minimum Transmission Rate
Up to 1400 lines 1200 baud.
1400 to 2800 lines 2400 baud.
Above 2800 lines 9600 baud.
On systems incorporating ACD working the recommended Baud rate is 9600.
In terms of characters per second, and of CIL records per second, the transmission rates
are as follows:
Baud Characters per CIL records per CIL records per
sec for full CIL sec for Full CIL sec for Textual CIL
1200 109 4 <1
2400 218 9 <1
4800 436 19 1
9600 873 39 3
Transmission speeds for Textual CIL are dependent upon the maximum speed attainable
by the peripheral device.
3 Full CIL records
SECTION 3
FULL CIL RECORDS
3.1 INTRODUCTION
In Full CIL, records are encoded in a binary format. The following is an example of two CIL
records and they are shown in hexadecimal format:
EEFF 0153 0040 403E 00D0 1E38 0155 02A1 0003 0000 CFFD
EEFF 8A10 0001 78A4 6530 0000 0000 0000 0000 0000 D0E4
The CIL output reports all incoming and outgoing PSTN and IPBX calls. It also reports all
the internal calls made between any telephone, operator console or data device. Flags are
extensively used in call records to show feature usage and also the nature and progress of
a call (e.g. through third party transfers).
Individual calls may produce more than one record for a variety of reasons, such as call
transfer and changes in the members of a conference call.
For this reason, more than one record type has been specified. The four types are:
 Basic Records.
 Continuation Records.
 Conference Records.
 Exception Records.
When more than one record is created for an event, typically the end of a call or at the end
of each phase of the call, the different types of record are output in the above order, as
appropriate. If there is more than one “Exception Record”, the sequence in which they are
output is not defined.
Records are created for all calls made through the system. For CIL purposes, new call
records are not only created when a genuinely new call is made, but also:
 If an enquiry call is made by an extension.

 If a transfer is invoked.
 If an operator dials an extension or an outgoing number with a calling party on hold.
 If the number of parties involved in a conference call changes.
Calls of any duration are recorded, in order that a complete data record of the volume and
nature of traffic through the telephone system may be maintained. Only invalid and
incomplete dialling sequences are not recorded.
Section 3 : Full CIL Records Realitis DX Call Information Logging (CIL) Supplement
No parity bit is provided and so an 8-bit call record checksum byte, two's complement
additive, is used to detect:
 All odd numbers or errors in one bit position.

 All even numbers of errors in one bit position which are not self compensating.
All binary call data will be transmitted as call records of 22 bytes. These records consist of
2 header bytes, and 18 data bytes, 1 record sequence byte, 1 record checksum byte.
0 1 2 to 19 20 21
Header Data bytes RS RC
Where:
Header - is a fixed pattern to identify the start of a record (EEFF - hexadecimal).
Data bytes - contains the event information for a call. Each record type is identified by the
“A” field (refer to the relevant subsection for further details on the record formats).
 “Basic Record” (0), see subsection 3.2.

 “Continuation Record” (1), see subsection 3.3.
 “Conference Record” (2), see subsection 3.4.
 “Exception Record” (3), see subsection 3.5.
RS - The Record Sequence byte is provided to give evidence to the CILE of a CIL Record
loss caused by overflow of the DX buffer. A missing Record Sequence Number (RSN),
indicates a record that the CILE has not received. The RS field contains a binary value in
the range 0 to 255. A RSN is added to every CIL record before transmission and is
incremented by one from the previous value (modulo 256). Once the 255 th record has
been output the counter re-sets to zero.
Note: The RSN indicates the order in which the CIL records were output, not the order
they were created.
RC - The Record Checksum byte is an 8 bit cumulative checksum and is calculated from
all the characters transmitted between the header characters and the RSN. Overflow at
any stage of the calculation is ignored and the two's complement of the resulting
checksum is transmitted.
Record synchronisation can be maintained at the CILE by looking for the 2 byte header
and then counting off the remaining 20 bytes of the call record before looking for the next
header bytes.
Realitis DX Call Information Logging (CIL) Supplement Section 3 : Full CIL Records
3.1.1 Basic Records
Basic Records are either formatted as in Table 3 .2 (before software revision 2.4) or as in
Table 3 .3 (after software revision 2.4).
In summary, “Basic Records” are created to record the following events, and their
progress:
(i) An incoming operator-answered trunk call is answered at:

an operator console;
a dedicated night answer extension;
a night bell for answer.
(ii) An incoming PSTN DDI trunk seizes and dials a valid destination number and is:
a DX extension;
an outgoing IPBX trunk;
an outgoing PSTN trunk;
an operator console.
(iii) An IPBX seizes an incoming call and dials a valid destination number and is:
a DX extension;
an outgoing IPBX trunk;
an outgoing PSTN trunk;
an operator console.
(iv) An incoming dedicated trunk makes a call to its dedicated extension number.
(v) An extension dials a valid destination number which is:

another extension or a pilot number;
an outgoing PSTN, IPBX trunk or operator console.
(vi) An extension dials a valid DX feature code. These include:

Do Not Disturb;
Cancel Do Not Disturb;
Set Extension Abbreviated Dialling Number;
Camp-on;
Cancel Camp-on;
Set Call Diversion;
Cancel and Reset Call Diversion;
Faultsman's Ring-Back;
Cancel all extension restrictions;
Invoke inward extension call restriction;
Invoke outward extension call restriction;
Invoke both inward and outward extension call restriction;
Bar extension access to a single trunk;
Re-allow extension access to a single main trunk group;
Re-allow extension access to all main trunk group;
Set System Time;
Set System Date;
Ring Back When Next Used;
Keyed Cleaned by Staff (default when no password);
Keyed Fixed Ringback;
Keyed Cancel Fixed Ringback;
Keyed Global Cancel Fixed Ringbacks;
Keyed Delayed Ringback;

Keyed Cancel Delayed Ringback;
Keyed Global Cancel Delayed Ringbacks;
Fixed Ringback;
Delayed Ringback;
Re-ring;
Display Telephone Call Successful;
Display Telephone Call Failed;
Operator Key Action;
Keyed Clean by Guest;
Change Password for Pull Diversion;
Set Pull Diversion;
Cancel Pull Diversion;
Lock Extension;
Unlock Extension;
Home-working or hot-desking forced password change;
Home-working or hot-desking user invoked password change;
Home-working session activated;
Home-working session deactivated;
Hot-desking session activated;
Hot-desking session deactivated;
Join-In Conference.
Other DX extension features are recorded by the use of flags in the call records of the
relevant calls.
(vii) An extension picks up a call ringing at another extension.
(viii) An extension causes a call transfer by going on-hook.
(ix) An extension picks up a call ringing the night bell.
(x) An extension causes a call transfer by dialling the call park (transfer on hold)
feature.
(xi) A call times out on ringing and is forwarded to another extension or to an

operator.
(xii) A call times out in the Held condition and is forwarded to an operator owing to the
engaged state of the Holding extension.
(xiii) The number of parties in a call increases or decreases as a result of adding a

party to a conference or a party clearing down.
(xiv) An extension answers an automatic call-back call, (Call Back when Free or Next
Used).
(xv) An operator dials a valid destination number, whether or not a calling party is
held.
(xvi) An operator causes a call transfer by use of the RELEASE button.
(xvii) An operator causes a call transfer by camping a call onto a busy extension.
(xviii) An operator causes a call transfer by using the JOIN button.
(xix) An extension picks up a call held at another extension.
(xx) An operator dials one of the following extension control features validly:
Cancel All Call Restriction;
Invoke Inward Call Restriction;
Invoke Outward Call Restriction;
Invoke Inward and Outward Restrictions;
Bar Extension Access to Single Trunk TAC Group;
Re-allow Extension Access to Single Trunk TAC Group;
Re-allow Extension Access to All Trunk TAC Groups.
(xxi) An operator dials one of the following services validly:

Set/Cancel Do Not Disturb;
Set/Cancel Call Forwarding;
Set System Time;
Set System Date.
(xxii) An extension dials a valid hunt group number.
3.1.2 Continuation Records
If the call being recorded is a transit call, or an outgoing PSTN or IPBX call, a
“Continuation Record” (see Table 3 .6 or Table 3 .7) is required. The record contains the
dialled digit string which can be up to 18 digits long (SPCAC set to 0) or 26 digits long
(SPCAC set to 1) depending on the system parameter. The following are also contained in
this record:
 Meter Pulses.
 Account Code (depends upon SPCAC being set to 0).
 Trunk Access Code.
 Further flags relating to outgoing calls.
By using an extra record for this purpose, the DX is able to limit the contents of the “Basic
Record” to information required for all the three basic types of call - incoming, internal, and
outgoing - thus limiting the amount of data to be transmitted.
A “Continuation Record” always immediately succeeds the “Basic Record” with which it is
associated.
3.1.3 Conference Records
A “Conference Record” is used to augment a “Basic Record” to give an indication of all the
parties in a conference call (up to a maximum of six). This figure does not include the local
operator or the channel for tones. Table 3 .8 shows the record format as it was pre-Rev
2.4 software revision, while Table 3 .9 shows the record format from software revision 2.4
onwards.
Software revisions prior to - 7.1: “Conference” and “Basic” records are output to the
CILE at the end of each phase of the call. For example:
1. Adding a third party to an existing two party call, causes the “Basic Record” related
to the two party call to be output to the CILE. On termination of the conference,
additional “Basic” and “Conference” records are output.
2. If a party clears down from a conference and there are still more than two parties in
the call, the existing “Basic Record” and “Conference Record” are output to the
CILE. On termination of the conference, additional “Basic” and “Conference” records
are output.
3. If the clear-down results in only two parties being left in the call (so ending the
conference and clearing the conference bridge), then the “Basic” and “Conference”
records associated with the conference call are output to the CILE. When the two-
party call is terminated an additional “Basic Record” is output.
4. If a trunk is involved in a conference a “Continuation Record” is output at the end of

the call and the trunk party is identified in the associated “Basic Record”. For further
information refer to subsection 3.1.2.
Software revisions 7.1 onwards: extra “Conference” and “Basic” records are output to
the CILE when a party is added to a conference at the beginning of each phase. This
follows the transfer termination CIL records for both the; originating party and added party;
the originating party and the previously held call.
Also, “Conference” and “Basic” records are output to the CILE at the end of each phase of
the call. For example:
1. If a party clears down from a conference and there are still more than two parties in
the call, the existing “Basic Record” and “Conference Record” are output to the
CILE. On termination of the conference, additional “Basic” and “Conference” records
are output.
2. If the clear-down results in only two parties being left in the call (so ending the
conference and clearing the conference bridge), then the “Basic” and “Conference”
records associated with the conference call are output to the CILE. On termination of
the two party call, an additional “Basic Record” is output.
3. If a trunk is involved in a conference a “Continuation Record” is output at the end of

the call and the trunk party is identified in the associated “Basic Record”. For further
information refer to subsection 3.1.2.
3.1.4 Exception Record
“Exception Records” are used to indicate any other details that are not related to a specific
call and extra details of calls not included in other record types (i.e. DASS, ISDN and
Packet switched calls). Exception records are produced to give the following information:
 System time or date change.

 CIL halted or resumed by MMI request.
 DASS or ISDN call information, including OLI/TLI and Call charge data.
 Packet switch call information.
 CIL inactivity notification.
 System restart.
 Faulty trunk reported.
 R2 CLI (Calling Line Identity).
 DPNSS Remote Party Details.
 Call Account code.
 Virtual Directory Number related to real Directory number.
 Malicious Call Trace.
 Diverting party on Diversion to PSTN.
 Details of Extension Locking and Unlocking.
 Home-working activation/de-activation.
 Home-working Long Call.
 Home-working call details.
 Hot-desking activation/de-activation.
 Hot-desking call details.
 Calling Line Identity (CLI) details
 Invalid PIN keyed.
3.1.5 Order of Record output
At the end of a call phase (see subsection 3.6 for examples of call phases and associated
records), the records associated with that phase of the call are output in the following
order.
 Basic Record.
 Conference Record (if appropriate).
 Continuation Record (if appropriate).
 Exception Record (as appropriate).
Notes:
1. A call may have one or more of the same type of record associated throughout the
various phases (e.g. 3 Basic Records, Basic and Conference Records).
2. If there is more than one “Exception Record”, the sequence in which they are output
is not defined.
3. “Exception Records” not related to a specific call type can also be output (e.g.
Inactivity CIL notification).
3.2 BASIC RECORD FORMAT
Table 3 .2 shown below is given for information only. Table 3 .3 is the format used for all
current software revisions.
Table 3.2
Basic Record format for software revisions 2.1, 2.2 and 2.3
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
2,3 FIRST PARTY NUMBER
4,5 B A
6,7 SECOND PARTY NUMBER
8,9 B FINISH HOUR
10,11 FINISH MINUTE FINISH SECOND
12,13 F7 C D JULIAN DATE
14,15 DURATION SECONDS
16,17 FLAGS F8-F15 ANSWER DELAY (SECS)
18,19 FLAGS F16-F31
20,21 RECORD SEQUENCE # RECORD CHECKSUM
Note: The Bytes are transmitted in order Byte 0 to Byte 21. Each Byte is transmitted
least significant bit first. Unused bits are shown shaded.
Table 3.3
Basic Record format for software revisions 2.4 onwards
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 B E J A
6,7 SECOND PARTY NUMBER
8,9 B FINISH HOUR
10,11 G X FINISH MINUTE H M FINISH SECOND
12,13 F7 C D JULIAN DATE
14,15 DURATION SECONDS
16,17 FLAGS F8-F15 ANSWER DELAY (SECS)
18,19 FLAGS F16-F31
Notes:
1. The Bytes are transmitted in order Byte 0 to Byte 21. Each Byte is transmitted least
significant Bit first. Unused bits are shown shaded.
2. First and second party number fields are extended by 1 bit to allow 256+ trunk
groups. The extra bit is not used for 6 digit extension numbers which continue to fit
into three Bytes.
3. Bit E is not used until software revision 3.4 for DASS.
4. Bit J is Siemens Communications specific and is used for software revision 3.6 only.
5. Bit X is only used in China.
3.2.1 Description of the fields in a “Basic Record”
The following gives an indication to the contents of the fields for a “Basic Record”. In all
TBCD fields, digit 0 is represented as 10 decimal. A null TBCD digit represents nothing. All
TBCD fields are terminated by nulls if less than full. The meanings of the fields contained
in a “Basic Record” are listed below and are not given in order of output.
Where:
Header - Refer to subsection 3.1 for further information.
First/Second Party Numbers - these fields uniquely identify the two parties. The field
format is identical for the first/second party numbers. The fields can take one of the
following forms and are independent of each other. The party type is defined in the
associated B field.
Note: If any further parties are involved in the call, a “Conference Record” associated
with the “Basic Record” is given.
Extension - up to 6 TBCD digits are present, terminated by a null digit if less than 6
TBCD digits are used. These digits represent an extension directory number.
Trunk - two binary fields used to identify the type of trunk, followed by the trunk
number and the main group number (used to identify the route and is useful for IPBX
calls). Two flags give the following information:
T1 0 = IPBX Trunk or
1 = EXCH Trunk.
T2 0 = Incoming Trunk Call or

1 = Outgoing Trunk Call.
The Trunk Main Group Number field consists of 8 bits (99 main groups) for software
revisions 2.1, 2.2, and 2.3. For software revision 2.4 onwards the field consists of 9
bits (allowing for up to 500 main groups). For example:
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
2,3 T1 T2 Trunk number
4,5 Trunk main group number B E J A
6,7 T1 T2 Trunk number
8,9 Trunk main group number B FINISH HOUR
Note: Unused bits are shown shaded.
If the first party encounters a busy trunk main group and the DX is unable to re-route
the call, the original keyed access code is stored in the second party number and flag
26 “Engaged Signal” is set.
Note: A “Continuation Record” is not given.
For DPNSS or APNSS trunks, the trunk number given in CIL is always the last trunk in
use when an optimisation of the trunk circuit has occurred during the call.
Operator - Bit A1 (see below) distinguishes whether the main field holds a console
number or a console group number. A console group number is used in cases where
an incoming call to an operator group clears before a console can be allocated. For
example:
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
2,3 A1 Console number
4,5 B E J A
A1 0 = Console Number (1 - 56).

1 = Console Group Number (0 - 31).
Feature - a binary code is used to indicate the feature used. For example:
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
2,3 Feature number
4,5 Failure/Answer B E J A
Feature codes 27, 28 and 29 can give a failure/answer reason. The following codes
are used to identify:
0 = Answered.
1 = Busy.
2 = No Answer, final attempt.
3 = Unavailable.
4 = No Answer, Not final attempt.
Feature codes 55 and 56 are used to indicate the Hot-desking or Home-working user
password has been changed successfully.
Note: Hot-desking telephones can be on the same node (local) as the office
telephone or on a different node (remote) within the private network.
The features and feature numbers are listed in Table 3 .4 Basic Record feature
numbers and names on the following page.
Table 3.4 Basic Record feature numbers and names
Number Name
1 Do Not Disturb.
2 Cancel Do Not Disturb.
3 Set Extension Abbreviated Dial Number.
4 Extension Camp-on.
5 Cancel Camp-on.
6 Set Call Diversion.
7 Cancel Call Diversion.
8 Cancel and Reset Call Diversion (for another extension).
9 Faultsman's Ring back.
10 Cancel All Extension Restrictions.
11 Invoke Inward Extension Call Restriction.
12 Invoke Outward Extension Call Restriction.
13 Invoke Both Inward and Outward Extension Call Restriction.
14 Bar Extension Access to a Single Trunk Main Group.
15 Re-allow Extension Access to a Single Trunk Main Group.
16 Re-allow Extension Access to all Trunk Main Groups.
17 Set System Time.
18 Set System Date.
19 Ring Back When Next Used.
20 Keyed Clean by Staff (default when no password).
21 Keyed Fixed Ringback.
22 Keyed Cancel Fixed Ringback.
23 Keyed Global Cancel Fixed Ringbacks.
24 Keyed Delayed Ringback.
25 Keyed Cancel Delayed Ringback.
26 Keyed Global Cancel Delayed Ringbacks.
27 Fixed Ringbacks.
28 Delayed Ringback.
29 Re-ring.
30 Display Telephone Call Successful.
31 Display Telephone Call Failed.
34 Keyed Clean by Guest.
35 Keyed Absent Diversion to PSTN.
36 Guest Name Reveal.
49 Change Password for Pull Diversion.
50 Set Pull Diversion.
51 Cancel Pull Diversion.
52 Lock Extension.
53 Unlock Extension.
55 Forced password change.
56 User invoked password change.
57 Home-working session activated
58 Home-working session deactivated
59 Hot-desking session activated
60 Hot-desking session deactivated
61 Join-In Conference
Note: Feature codes 37 to 48 and 54 are not used for general CIL data.
A - Record type. A two-bit field used to indicate the record type (Basic Record = 0).
B - Party type. This field is used to indicate the party type, where: Extension = 0,
Feature = 1, Trunk = 2 and Operator = 3.
C - Origin of Transfer Termination. A three-bit field used to indicate which party was
responsible for transfer terminating of the call (e.g. extension clear down or operator
release).
Note: This field is used only when a transfer termination has occurred (see Flag F7).
The field does not indicate which party terminated the call.
The values in the field are:
If C = 0, and the flag F7 = 1, then the call has been diverted.
If C = 1 or 2, are used to indicate which party in the “Basic Record” caused the
transfer termination (1 - first party number, 2 - second party number).
If C = 3 to 6, are used to indicate which party in the “Conference Record” caused the
transfer termination (3 - third party number, 4 - fourth party number, 5 - fifth party
number and 6 - sixth party number).
If C = 7, then transfer termination occurred as a result of some other event (e.g.

timeout on ringing or hold, or call pick up by a party not shown in the call record). In
these cases, the cause of transfer termination is recorded elsewhere in the CIL
records (e.g. flags F9 to F16 of the “Basic Record”).
D - Rung Party. A three-bit field containing a binary number to identify the rung party
number for calls that arrive at an extension or console (indicated by the “Basic Record” or
“Conference Record”). The field is set to zero for other calls.
In the case where a transfer results in an immediate connection of two parties (no ringing
occurs) the Rung Party field will be blank.
E - Exception Record. A one-bit field is set to indicate there is an associated “Exception

Record” containing additional information for an ISDN call.
Note: This is not used until software revision 3.4.
G - Guest Name Reveal. A one-bit field is set to mark a guest name reveal CIL record.
This type of record is principally intended for the hotel environment.
Note: This facility is provided prior to revision 3.6 via a software patch. These records
are output on call set up rather than termination as is usually the case.
H - Call Metering for Finnish Information System. A one-bit field is set to indicate that the
CIL record is for a metered call (H = 0 - calls not metered, H = 1 - calls metered).
Note: This facility is not currently available in the UK. For further details regarding the
Finnish Information System, contact Siemens Communications.
J - ACD Record. A one-bit field used to indicate a record associated with ACD. This field is
only supported on 3.6 software revision and is obsolete from 3.7 onwards.
At software revision 3.7, the ACD CIL information may either be output from a separate
ACI port or by the use of "Exception Records". These records are Siemens
Communications specific and should be ignored by CIL attachments.
Note: The output of ACD information does not affect the normal CIL output. All calls
made via a DX are reported via normal CIL records as detailed in this document.
M - MFE related call. A one-bit field when set to 1 indicates the call used an MFE trunk,
otherwise this flag is zero.
X - Break in occurred. A one-bit field when set to 1 indicates the PSTN operator has
interrupted a trunk call to a PABX extension. Only used in China.
Finish Hour, Finish Minute, Finish Second - Binary numbers taken from the system time
at termination of the call. The ranges for the fields are: Hour = 0-23, Minute = 0-59 and
Second = 0-59.
Julian Date - a binary number in the range 1-366, at termination of the call. The field is 9
bits wide. The Julian date represents the days of the year in sequential order (i.e. Jan 1st
= 1, December 31st = 365 or 366 in a leap year).
Notes:
1. In a leap year, all dates after day 59 (Feb 28) are displaced by one.
2. The Full CIL output given by the DX contains the date and is given in the Julian
form. The CILE connected to the DX must convert the Julian date given to the
correct year date.
Duration Seconds - This field is a binary number in the ranges:
 1-65,535, see Note 1 or

 1-43,200, see Note 2.
Notes:
1. For revisions of software up to 3.4. Once this value is reached, the field returns to
zero.
2. For revisions of software 3.4 and above, a new call record is issued every time the
duration reaches the 12 hour maximum. This change was introduced to
accommodate CIL for permanent calls.
From this field the start time of a call record may be determined in conjunction with the
given finish time. Duration seconds start to be counted from one of the following events.
For Incoming External Calls, the duration is the time of:
 ringing detection by software in the case of non-DDI PSTN trunks.

 a seizure being detected by software for PSTN DDI and IPBX trunks.
For Internally Originated Calls, the duration is the time of:
 extension seizure being detected by software.

 loop selection by operator being detected by software.
 an extension recall signal being detected by software.
 software detecting further dialling by an operator already connected in a call.
 a transfer caused by a party clear-down.
 increase or decrease in the number of parties in a conference.
 a call being extended by an operator.
 a call being diverted by some timeout actions or by being picked up by an extension.
 an extension going off hook for outgoing trunk calls to trunks without answer
supervision.
For answered calls, the call duration includes the dialling time, ringing time and the
connected time. For unanswered calls, the call duration includes the dialling and the
ringing time.
The time parties were connected together is deduced by subtracting the answer delay
time from the total call duration time.
For calls which contain remote party details (e.g. an “Exception code 20 Record” is added
to the “Basic Record”), the duration always represents the time of the local party in the
call. The time of the remote party is represented at its local DX.
For example, a local PSTN trunk is shown and the duration of 120 seconds is correct for
the occupation of the trunk. However, the remote party details indicate the last connected
party, whose duration may be <120 seconds owing to a call transfer. See Table 3 .5.
Table 3.5 Basic Record call duration examples
Duration at Duration at Duration at

node A node B node C
Extension A connects to PSTN trunk 60 seconds no record no record

C for 60 seconds.
Extension A transfers call to no record 60 seconds 120 seconds

Extension B who talks for 60
seconds, then clears the call.
If the feature code is 24, 25 or 28 then “delay to ringback” is stored in this location.
If the feature code is 21, 22 or 27 then “hours and minutes for ringback” are stored in this
location (hours in the most significant byte, minutes in the least significant) as below:
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
14,15 Hours Minutes
Answer Delay - This field contains an eight bit binary number defining the answer delay of
a call and is measured in units of one second, with a range of 0-255. It defaults to 255 if
longer delays are met. It applies to rung extensions, operators and trunks.
The answer delay value includes both the time taken to dial the wanted party and the time
spent ringing before the call was answered. It is timed from the same event that starts the
Call Duration timer.
Therefore, the answer delay field value must be subtracted from the Duration timer in
order to find the call connection time.
If the outgoing trunk is not able to supply an answer signal the answer delay is always set
to zero.
The two flags F7 (Transfer Terminated) and F8 (Transfer Initiated) can be checked in
cases of the answer delay being zero:
F7 and F8 zero The call was unanswered.
F7 set, F8 set or unset The call was transferred without answer to another
extension on the network, either by pick-up or by Ring-No-
Reply Diversion. A subsequent “Basic Record” with F8 set
and including the calling party will show this.
F8 set, F7 set or unset The call may have been transferred already answered,
following a transfer or a pickup or it may have been
transferred in ringing state or diverted ring no reply and
stayed unanswered at the called extension.
Answer Delay in DPNSS private network calls
Following a transfer where the local party is not an outgoing PSTN trunk, the answer delay
represents the time taken to become connected to the transferred to party. Thus if the
transfer joins together two already answered calls, the answer delay represents the time at
which the transfer occurred. If the transfer results in an unanswered call (because either
the local or remote party is in the unanswered state), the answer delay is zero if the call
remains unanswered and represents the time at which answer occurred if the call is
subsequently answered.
This means that the calculation of connected time as Duration minus Answer Delay is
correct in all cases for the local parties.
Because the answer delay where the local party is an outgoing trunk is unaffected by
transfer, there will be anomalies in the answer delay values given at the two end nodes
following certain types of transfer. For example:
1. Extension on node A rings operator on node B.
2. Operator on node B answers.
3. Operator makes outgoing PSTN call on node C.
4. Rung PSTN party answers.
5. Operator drops out of the call and connects the extension and PSTN party together.
At this stage a CIL record is given at node B detailing the transfer, but at node A no
CIL information is given. Instead the time spent by extension A ringing and connected
to the operator is copied into the answer delay field and the call duration time is left
unaltered. At node C, no CIL information is given and the call timings are not be
altered.
6. Call between the extension and PSTN party is terminated. At node A, the connection
time is correctly deduced by subtracting the answer delay away from the call duration
when the CIL information is output. At node C the answer delay is a true
representation of the time it took the called PSTN party to answer and is a shorter time
than that shown at node A.
If the feature code is 21, 22, 24 or 25 (e.g. when a keying party has set/cancelled a ring
back for a different party) then the digits of the ringback party’s number are saved in the
area occupied by Answer Delay.
Thus:
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
16,17 F8 F9 F10 F11 F12 F13 F14 F15 Answer Delay
18,19 F16 F17 F18 F19 F20 F21 F22 F23
is replaced by:
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
16,17 Digit 1 Digit 2 Digit 3 Digit 4
18,19 Digit 5 Digit 6
These figures are in TBCD.
If the feature code is 30 or 31 (i.e. display whether or not the call was successful), then the
number of the party for which the ringback failed is saved here.
If the feature code is 27, 28 or 29 (i.e. fixed or delayed ringback or re-ring) then the
answer delay is set up normally.
Record Sequence Number - Refer to subsection 3.1 for further information.
Call Record Checksum - Refer to subsection 3.1 for further information.
Flags
F1 to F6
These flags no longer exist.
F7 Transfer Terminated
Set for record terminated as a result of some type of transfer. The Termination field
displays which party effected the transfer, or whether another action caused it. Timeout on
ringing or held calls may also cause flag F7 to be set.
F8 Transfer Initiated
Set for record initiated as a result of a call transfer or other action that brings two or more
parties into a speech or calling state where one party has not dialled the other in the
duration of the call record.
F9 Enquiry
This flag indicates that a call record was commenced as a result of, an extension or
operator dialling a call with another call held. If answer delay is zero, then the first party
always represents the dialling party.
F10 Conference
Set if a conference call has been created and a “Conference Record” is associated with
the “Basic Record”.
F11 Night Bell
1. Set if the second Party is an operator and the call was routed to the Night Bell. The
Second Party number field contains either a console group number or is blank. Rung
party field is zero and call record duration shows how long the Night Bell rang. Flag
F7 is set if an extension picks up the call.
2. Set if a Party answered the Night Bell. The pick-up Flag F18 is also be set, with
Rung Party and Answer Delay fields zero. Flag F8 is set.
F12 Dedicated Night Answer
Set if the second Party is an extension being called as the result of an incoming call being
diverted from operator consoles by the dedicated night answering service. The Rung Party
is always set when this flag is set.
F13 Dedicated
Set if an extension has either made a dedicated outgoing call or has received a dedicated
incoming call.
F14 Ring No Reply Diversion
Set if the call record commenced as a result of No answer diversion. If answer delay is
zero, flag F7 informs whether the first party cleared or was picked-up by some other
extension.
F15 Busy Diversion
Set if the second Party received the call as a result of the engaged state of another
extension.
F16 Pre-set Diversion
Set if the second party received the call as a result of a pre-set call diversion.
F17 Data
Set if the call is known by the DX to be a data call.
F18 Pick-up
Set if the record was initiated by an extension using the call pick-up feature. Flag F8 is
also set.
F19 Group Pick-up
Similar to Flag F18, but group pick-up was used. Flag F8 is also set.
F20 Transfer on Hold
Set in a call record initiated by a Transfer on Hold (Park) extension operation, or by an

Operator camp-on operation. Flag F8 is also be set. The Rung party field contains the
identity of the parked-upon extension and Answer delay field contains the delay to a first
connection.
F21 On Hook Hold
Set in any call record in which Hang-up hold feature was used. If the Hold condition timed-
out and resulted in a transfer on holding party busy, then Flag F7 would be set.
F22 Comm Group Dialling
Set if a communications group number was used to access the rung Party, which must be
an extension.
F23 Hunt Group/Distribution Group
This flag is set to 1 if the pilot number of a hunt or distribution group was used to access
the rung party. For answered calls to a hunt or distribution group, the called party field
contains the directory number of the party answering the call. For unanswered calls to a
hunt or distribution group, the group number is stored in the second party field of the
“Basic Record”.
F24 Comm Group Camp-on
Set when an extension used the camp-on code to camp-on an engaged extension after
using the COMM group code for dialling. The calling party is then held by the extension
camped onto and must stay off-hook for the camp-on to be effective.
F25 Executive Intrusion (also DND Override)
Set when an Intrusion code has been used. The first Party type may be either an operator
or an extension. This flag is only set in the CIL record associated with the intruding party.
The same CIL record is maintained through to the end of the intrusion. Conference flag is
not set.
F26 Engaged Signal
Engaged signal met at end of initial dialling causes the setting of this flag. If the signal is
received because of trunk group engaged condition, the dialled un-optimised trunk access
code (TBCD digits) is in the second party number field of a trunk number (no “Continuation
Record” will be appended). A Continuation Record (with sent digits) and an Exception
Record (with remote party details) is generated when a connection is attempted to an
engaged party over a trunk group. If the engaged signal occurs from a hunt/distribution
group engaged condition, the pilot number of the group is in the second party number
field. Normally an extension number is in the second party number field.
F27 Privacy
Set if privacy (Intrusion barred) is invoked by either party during the course of the call.
F28 Switchover
The CIL record represents only the part of the call after a processor switchover or restart.
The call duration may not therefore represent the total duration of the call and the record is
subject to inaccuracies.
F29 Priority to Operator
Set if a call was set up to the operator with priority access. Three cases are covered: the
call was made using a specific console number; the calling party had executive priority
access; the calling party had a trunk held while dialling an operator assistance call.
F30 Operator Extended
Set if a CIL record was created after the operator extended a call by means of Release,
Join or Camp-on. Flag F8 is also set.
F31 Timeout on Hold
Set in all CIL records initiated by an on-hold timeout; typically where the holding party is
busy so that the held party is diverted to the operator. Flag F8 is set in the new record.
3.3 CONTINUATION RECORD FORMAT
Table 3.6
Continuation Record format for software revisions pre-6.1, or
Revision 6.1 onwards with SPCAC set to 0 and SPACO set to 1
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
2,3 TRUNK ACCESS CODE
4,5 METER PULSES A
6,7 TRUNK
8,9 ROUTING
10,11 DIGITS
12,13
14,15 FLAGS F1 – F8
16,17 CALL ACCOUNT
18,19 CODE DIGITS
least significant bit first.
Table 3.7
Continuation Record format for software revisions 6.1 onwards
SPCAC set to 1
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
2,3 TRUNK ACCESS CODE
4,5 METER PULSES A
6,7
8,9
10,11 TRUNK
12,13 ROUTING
14,15 DIGITS
16,17
18,19 FLAGS F1 – F8
3.3.1 Description of fields in a “Continuation Record”
The following gives an indication to the contents of the fields for a “Continuation Record”.
In all TBCD fields, digit 0 is represented as 10 decimal. A null TBCD digit represents
nothing. All TBCD fields are terminated by nulls if less than full. The meanings of the fields
contained in a “Continuation Record” are listed below and are not given in order of output.
Where:
Trunk Access Code - This TBCD field contains the digits (maximum of 4) dialled when
accessing a trunk route on a DX.
Meter Pulses - Accumulated meter pulses are provided on outgoing PSTN calls. When
not provided, the field is null. The maximum value this field can contain is 16,383 pulses
and provides several hours of call duration capacity (depending on the call charging
rates).
For calls made to DASS2 trunks this field used if call units are provided.
The record of meter pulses of an outgoing PSTN call that has been transferred several
times, are recorded in the “Continuation Record” associated with the last phase.
If meter pulses are not provided by the PSTN, it is still possible to calculate the call
charge, from the trunk routing digits field (also in the “Continuation Record”), the answer
delay field and the call duration field (both in the “Basic Record”).
A - Record Type. A two-bit field used to indicate the record type (Continuation Record =
1).
Trunk Routing Digits - This field contains the TBCD digits sent out by the DX for onward
routing by a public local exchange or by a private network exchange.
The digits contained in this field can be:
 dialled by the caller.

 translated by the DX (which may have no effect on the original digits).
 stored digits accessed by a feature (e.g. Abbreviated Dial or Repeat Dialled Number
invocation, or Abbreviated Dialling).
 translated after successful Route Optimisation, Alternative Routing or Least Cost
Routing attempt.
Note: Digits represented include 0-9, and E and F in hexadecimal (E and F represent *,
#).
The digits contained in this field can be sent over a remote non-DPNSS trunk. In the case
of a remote public network trunk, the digits are prefixed by a simulated access code
(System Parameter SPOPD). These digits are used to overwrite the local routing digits
whenever there is a difference between them.
For example, the caller dialling a network operator over DPNSS, who then routes the call
to PSTN and dials the outgoing call before transferring the PSTN call to the caller. The
Routing digits field at the caller’s PBX contain the PSTN call digits, just as if the caller had
self-dialled the PSTN call.
Note: If * or # are included in any dialling sequence, the *, # and any digits following
them are not included in the CIL record.
Up to 18 digits are included prior to 6.1, or at 6.1 and onwards with SPCAC set to 0.
Numbers longer than 18 digits are not supported and calls may fail.
From software revision 6.1 onwards, the software allows for more than 18 digits in a call.
Where longer numbers are required, the system parameter SPCAC to must be set to 1
(allows up to 26 digits to be routed, including any private network and carrier routing digits
as well as the destination digits).
Call Account Code - This field is not included at 6.1 and onwards if SPACO is set to 0.
Up to 8 TBCD digits may be input against a call for subsequent call accountancy. This field
is also used to store the account code associated with mobile TAC. If both the mobile TAC
account code and the call account coding feature are being used, the mobile TAC account
code takes priority in this field.
Department Codes or Cost Centre Billing (For additional information)
The CIL account code feature is invoked by the user dialling a feature code [default *2].
Before revision 3.5.301, this feature could be invoked only when a call was in progress (or
receiving Ring Tone). Revision 3.5.301 introduced the possibility of pre-dialling *2 CIL
account codes before making a level 9 call.
Software revision 6.1 introduced the possibility of dialling an account code at any time,
before, during and after any type of call. Also, account codes can be up to 20 digits long.
With parameters SPCAC set to 0 and SPACO set to 1, account codes up to 8 digits which
are dialled before the end of an outgoing level 9 PSTN call or an inter-PBX call can be
recorded in the “Continuation Record”. See also the description of “Exception Record” 21
in subsection 3.5.14.
Software revision 3.5.301 also introduced the option of the transmission of a departmental
code to an external carrier by use of the CIL account code feature. With the Integral Smart
Box option, cost centre information can be sent to the Mercury 2200 service (or an
equivalent indirect access service supplied by any other network provider) from the DX, for
billing purposes. The CIL account code keyed by the caller is translated by a “CIL cost
centre” table into a (1 to 8 digit) cost centre code. If a match cannot be found or the CIL
account code feature was not invoked, then the default cost centre code can be sent to
the carrier. This cost code, sent to the carrier is included with the billing information
provided by the network provider.
Refer to the MMI commands ACDT (Add to CIL Department Code Table) and LCDT (List
CIL Department Code Table). The CIL account code keyed appears in the DX CIL record.
A fixed CIL account code can be forced by dedicating (DED) the extension using the REO
(Revision Extension Operation) customer command to *2<CIL account code>. When a
level 9 call is now made the CIL account code configured appears in the DX CIL record
and if the service is being invoked via the Integrated Smart Box an appropriate cost centre
can be forwarded to the network provider. The extension user is unaware that the CIL
account code has been added. When an extension dedicated (DED) to *2 CIL account
code makes an internal call the DX system ignores the configured CIL account code and
proceeds with the call, prior to release 6.1.
From 6.1 onwards, the call account code for an internal call is logged in an “Exception
Record 21”. Therefore, a large number of such records are created when the extensions
are dedicated as described above.
Flags
F1 System Abbreviated Dial
Set when the calling party used one of the System Abbreviated Dial numbers.
F2 Extension Abbreviated Dial
Set when the calling party used one of the Extension Abbreviated Dial numbers.
F3 Repeat Last Dialled Number
Set when the calling party used the Repeat Dialled Number facility. Not used on software
revision 6.1.101 and onwards.
F4 Save Dialled Number
Set when the calling party has saved the dialled number for subsequent repeat dialling.
Not used on software revision 6.1.101 and onwards.
F5 Route Optimisation
Set when the trunk routing digits and the trunk access code have been changed by use of
the Route Optimisation feature.
F6 Alternative Routing
Set when the trunk routing digits and the trunk access code have been changed by
Alternative Routing feature.
F7 Direct Trunk Selection
Set when Direct Trunk Selection has been used to access a particular trunk whose
number appears in the “Basic Record”. Trunk Access Code field may be blank.
F8 Absent Diversion to the PSTN
Set when the call is diverted to the PSTN using the Absent Divert to PSTN feature
introduced at revision 3.5.
3.4 CONFERENCE RECORD FORMAT
Table 3 .8 shown below is given for information only. Table 3 .9 is the format used for all
current software revisions.
Table 3.8
Conference record format for software revisions 2.1, 2.2, 2.3
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
2,3 THIRD PARTY NUMBER
4,5 B A
6,7 FOURTH PARTY NUMBER
8,9 B
10,11 FIFTH PARTY NUMBER
12,13 B
14,15 SIXTH PARTY NUMBER
16,17 B
18,19
Table 3.9
Conference record format for software revisions 2.4 onwards
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
2,3 THIRD PARTY NUMBER
4,5 B A
6,7 FOURTH PARTY NUMBER
8,9 B
10,11 FIFTH PARTY NUMBER
12,13 B
14,15 SIXTH PARTY NUMBER
16,17 B
18,19
Notes:
1. The Bytes are transmitted in order Byte 0 to Byte 21. Each Byte is transmitted least
significant bit first. Unused bits are shown shaded.
2. Party Number Fields are extended by 1 Bit to allow 256+ trunk groups. The extra Bit
is not used for 6 digit extension numbers that continue to fit into three Bytes.
3.4.1 Description of the fields in a “Conference Record”
The following gives an indication to the contents of the fields for a “Conference Record”. In
all TBCD fields, digit 0 is represented as 10 decimal. A null TBCD digit represents nothing.
All TBCD fields are terminated by nulls if less than full. The meanings of the fields
contained in a “Conference Record” are listed below and are not given in order of output.
Where:
Third/Fourth/Fifth/Sixth Party Number - these fields identify the parties (extension, trunk
or an operator). For further details refer to the “Basic Record” First/Second Party Numbers
in subsection 3.1.1.
A - Record Type. A two-bit field used to indicate the record type (Conference Record = 3).
B - Party Type. This field is used to indicate the party type, where:
Extension = 0, Feature = 1, Trunk = 2 and Operator = 3.
3.5 EXCEPTION RECORD FORMATS
Several events that are not related to any particular call are reported via the CIL port in the
form of “Exception Records”. If there is more than one “Exception Record” given, the
sequence of the record output is not defined.
The following codes indicate “Exception Records” that may be used by peripheral call
logging equipment.
Table 3.10 Exception Record codes
Code Record/Event
1 System Date Change
2 System Time Change
3 System Date and Time Change
4 CIL halted by MMI request - call records lost
5 CIL resumed after type 4 halt
6 ISDN/DASS OLI/TLI
7 Packet Switching Record
8 Packet Switching Record
10 Inactivity Record
11 Restart Record
15 Faulty Trunk Report
16 R2 Calling Line Identity
17 iSPS Information
18 iSPS Information
19 iSPS Information
20 Remote Party details for network CIL
21 CIL Account code
22 Virtual Directory Number
23 Malicious Call Trace - Terminating end
24 Malicious Call Trace - Originating end
25 Diverting Party (on diversion to PSTN)
26 Extension Lock/Unlock
27 Home-working activation
28 Home-working de-activation
29 Home-working long call
30 Hot-desking activation
31 Hot-desking de-activation
32 Home-working call details
33 Hot-desking call details
34 Calling Line Identity (CLI) details
102 Invalid PIN Keyed
The following exception record codes represent Siemens Communications specific records
and should be ignored by any call logging equipment attached to the DX.
Exception codes 9, 12, 13, 14, 101, 201 and 202.
In addition, “Exception Record 201” is always accompanied by two “Continuation

Records”, and “Exception Record 202” is always accompanied by one “Continuation
Record”. These records should also be ignored by CIL attachments. The “Exception
Record 201” and “Exception Record 202” are only given for software revisions 3.6.001 and
3.6.201.
3.5.1 Description of the fields in “Exception Records”
All “Exception Records” contain the following fields. Where “Exception Records” have
different fields, further descriptions for the fields are given on the following pages.
Exception Code - This field contains a binary number (code) to identify the type of
exception record. See Table 3 .10 Exception Record codes.
A - Record Type. A two-bit field used to indicate the record type (Exception Record = 2).
Exception Details - (Bytes 4 to 19). The format in which the information is contained
varies according to the exception code. Structures for the various “Exception Records”
which can be used by CIL attachments are given on the following pages.
3.5.2 Exception Record (codes 1 to 5)
Table 3.11 Exception Record format for exception codes 1 to 5
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
2,3 EXCEPTION CODE = 1 to 5
4,5 A
6,7 OLD JULIAN DATE
8,9 NEW JULIAN DATE
10,11 OLD HOUR OLD MINUTE
12,13 OLD SECOND
14,15 NEW HOUR NEW MINUTE
16,17 NEW SECOND
18,19
Exception Details
Exception codes 1 to 3 cover changes in the time and date. Exception codes 4 and 5
cover CIL halt and resumption after MMI request.
Julian Date - Refer to subsection 3.2 for further information.
Exception Code 1
Bytes 6 and 7 contain the old date in binary.

Bytes 8 and 9 contain the new date in binary.
Bytes 10 to 17 are null.
Exception Code 2
Bytes 6 to 9 are null.

Bytes 10, 11 and 12 contain the old hours, Minutes, and Seconds in binary.
Byte 14, 15 and 16 contain the new Hours, Minutes and Seconds in binary.
Exception Code 3
Bytes 6 and 16 are used as in codes 1 and 2.
Exception Codes 4 and 5
Provide details of MMI request to halt (HCIL) and resume CIL (RCIL) output. Refer to the
Realitis Electronic Publications or the Distributors’ Command Manual for further
information on MMI commands.
3.5.3 Exception Record for ISDN (code 6)
Table 3.12 Exception Record format for exception code 6
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
2,3 EXCEPTION CODE = 6
4,5 INDEX A
6,7 Originating/Terminating Line Identity (TBCD), digits 1 to 4
14,15 O/TLI (as above) Digits 17 and 18
16,17 Units of cost for Call Charging (e.g. Pounds, Dollars)
18,19 Sub Units of CC (Pence, Cent)
Exception Details
On a call involving the public network, where the number of the public network subscriber
is available at the non gateway end of the private network part of the call, the public
network number is given in the same manner as it is given at the gateway PBX.
This “Exception Record” is only given when the configurable system parameter CILEX=1.
Output of this record can, therefore, be suspended when the DX is connected to CIL
equipment not capable of recognising this CIL record. When produced, the Originating
Line Identity (OLI) associated with an outgoing call to an ISDN trunk is only added if the
digits are different from the routing digits stored in the “Continuation Record”.
If the system parameter CILEX is set to 0, then the routing digits in the “Continuation
Record” is overwritten by the Terminating Line Identity (TLI).
A new flag at bit 3 of byte 5 in the “Basic Record” (bit E in Table 3 .3), is set to indicate
that there is an associated “Exception Record” containing the additional information.
Index - This field contains a number in the range 1 to 6 to indicate the party in the “Basic
Record” or “Conference Record” to which the record refers.
Call Charging - The contents of bytes 16, 17 and 18 (reserved for call charging
information) are not determined by the DX CIL subsystem, but, received via the ISDN link
for the PSTN network, and remain transparent to the DX CIL subsystem.
3.5.4 Exception Record for Packet Switching (code 7)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 A
6,7 CALLING DNIC (TBCD)
8,9 CALLING NTN (TBCD)
10,11 CALLING NTN (TBCD)
12,13 CALLING SA (TBCD) CALLED DNIC (TBCD)
14,15 CALLED DNIC (TBCD) CALLED NTN (TBCD)
16,17 CALLED NTN (TBCD)
18,19 CALLED NTN (TBCD) CALLED SA (TBCD)
Where:
DNIC - Data Network Identification Code (4 digits).
NTN - Network Terminal Number (8 digits).
SA - Sub-address optional (2 digits).
This forms the absolute address from the Packet Switch Device (PSD).
3.5.5 Exception Record for Packet Switching (code 8)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 JULIAN DAY FINISH HOUR A
8,9 DURATION DAYS DURATION HOURS
10,11 DURATION MINUTES DURATION SECONDS
12,13 NUMBER OF SEGMENTS RECEIVED (TBCD)
16,17 NUMBER OF SEGMENTS SENT (TBCD)
Number of Segments range: 0 to 99,999,999.
Exception Details for “Exception Records” 7 and 8
In order to bring to together the information needed to charge for all types of call, the CIL
output is enhanced for the Integral Packet Switch iSPS. At the end of each virtual call, two
records are given to indicate the number of segments sent and received to the calling and
called DNICs, the virtual call duration (days, hours, minutes and seconds) and the date
and the time that the record was output. The DNICs, duration, segments sent and
received values are as sent from the Packet Switch Device (PSD).
Where the Packet Switch supports the BTs Packet Switchstream Service (PSS) call
charging system, the information is the same as sent from BT's PSS. Where the Packet
Switch does not support PSS charging, the values are derived by the PSD. The CIL
device is responsible for ensuring that the records are correctly correlated. For each
“Exception Record” type 7 there is a corresponding record type 8 and vice versa.
The format of the days and times are in binary. Julian Day occupies 9 bits. No “Basic
Record” is given.
3.5.6 Exception Record for CIL inactivity (code 10)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 A
6,7 INACTIVITY TIMEOUT VALUE (SPITO)
8,9 YEAR
10,11 DAY
12,13 HOUR MINUTE
14,15
16,17
18,19
Exception Details
Note: This record is only available from DX software revision 3.5.301 onwards.
This “Exception Record” is given when no CIL records have been given from the DX for a
configurable period of time. A configurable and revisable system parameter SPITO defines
CIL inactivity time out period in seconds. An exception record for inactivity is also given
whenever the time out period is revised.
The fields Year, Day, Hour and Minute are derived from the system clock.
3.5.7 Exception Record for System Restart (code 11)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 B A
6,7 CODE
8,9 ERR TYPE
10,11 ERROR NUMBER
12,13
14,15
16,17 HOUR JULIAN DATE
18,19 MINUTES SECONDS
Exception Details
This record is only given on system restart.
Code - This defines the type of restart. The codes are: 1 - Switchover (software),
2 - Switchover (hardware), 3 - System reload, 4 - First restart, 5 - Second restart.
Error Type - This takes a value of 1 to 4 indicating a restart error letter, A to D.

If Error type = 0, then no restart code is applicable.
Error Number - This gives the error number associated with the previous error type,
e.g. B104.
The fields Julian date, Day, Hour and Minute are derived from the system clock.
3.5.8 Exception Record for Faulty Trunk Reporting (code 15)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 B A
6,7 X Y TRUNK NUMBER
8,9 TRUNK GROUP NUMBER
10,11 REPORTING EXTENSION NUMBER
12,13
14,15
Exception Details
This record is given when a faulty trunk is reported by an extension.
B - This field is always 1 for this record.
X - This field is set to, 0 - for IPBX trunk, or, 1 - for Exchange trunk.
Y - This field is set to, 0 - for incoming trunk call, or, 1 - for outgoing trunk call.
Reporting extension number - This field consists of 6 TBCD digits identifying the
extension that the fault was reported on.
The fields Julian date, Day, Hour and Minute are derived from the system clock.
3.5.9 Exception Record for R2 CLI (code 16)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 INDEX A
6,7 CALLING LINE IDENTITY (TBCD), DIGITS 1 TO 4
12,13
14,15
16,17
18,19
Exception Details
Index - This field is a party number in the range 1 to 6. A party number of 1 or 2 relates to
the subscriber slots 1 or 2 in the “Basic Record” respectively. A party number of 3 to 6
relates to the ‘third’ to ‘sixth’ party field of an associated “Conference Record” respectively.
3.5.10 Exception Record for iSPS Packet Switching (code 17)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 CALLING ADDRESS A
6,7 CALLING ADDRESS
8,9 CALLING ADDRESS
10,11 CALLING ADDRESS
12,13 CALLING CALLED ADDRESS
14,15 CALLED ADDRESS
Exception Details
This exception record was introduced at software revision 3.7.001.
Calling/Called Address - These fields each contain up to 11 TBCD digits, identifying the
Called and Calling parties.
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 JULIAN DATE FINISH HOUR A
8,9 DURATION DAYS DURATION HOURS
10,11 DURATION MINUTES DURATION SECONDS
Exception Details
New Julian Date - Refer to subsection 3.2 for further information.
Finish Hour, Minute, Second - Refer to subsection 3.2 for further information.
Segments sent and received - These fields contain binary values representing the
number of Segments sent and/or received.
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 A
6,7 SEQUENCE NUMBER
8,9 CLEARING CAUSE
10,11 NUI
12,13 NUI
14,15 NUI
16,17 A0 A1
18,19
Exception Details
Sequence Number - This binary number identifies the sequence in which the calls are
sent over the PSD, thereby indicating if any call data has been lost by overflow of the PSD
link.
Clearing Cause - Two TBCD digits identify the cause of the call clearance.
A0 - This flag indicates whether the call was a Fast Select Call (i.e. A call of only a few
packets of data, with minimal call set up and cleardown). For Fast select calls, the
segment count fields in exception record 18 are null filled. If a call that was set up as a
Fast Select Call is then lengthened into a normal iSPS call, then this flag remains set to 1.
For fast select calls that become full iSPS calls, then the segment count fields do not
include packets related to call set up and clear down. Such calls are charged on a ‘per
call’ basis, rather then by call metering.
A1 - Reverse Charging Requested - Not currently supported.
NUI - Not currently supported.
3.5.13 Exception Record for DPNSS Remote Party Details (code 20)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 TYPE INDEX A
6,7 Node ID or first four digits of the network number
8,9 Trunk Group number or second four digits of the network number
10,11 Trunk circuit number or third four digits of the network number
12,13 TYPE INDEX
14,15 Node ID or first four digits of the network number
16,17 Trunk Group number or second four digits of the network number
18,19 Trunk circuit number or third four digits of the network number
Exception Details
This exception record was introduced at software revision 4.2/5.2.
Type - A two-bit field indicating the type of remote party:
0 = remote extension,
1 = remote operator,
2 = remote trunk.
Index - Party number in the range: 0 to 6. A zero in byte 13 indicates that there are no
remote party details in bytes 14 to 19 (i.e. the record contains details of only one remote
party). Otherwise the index field contains the party number with 1 referring to the first party
in the associated “Basic Record”, 3 referring to the ‘third party’ field of an associated
“Conference Record”, etc.
Unused digit positions are coded as null (decimal value zero).
If the remote party type is extension or operator, the six bytes containing the remote party
details (bytes 6 to 11 and 14 to 19) contain left justified TBCD digits indicating a network
number of up to 12 digits in length.
If the remote party type is a trunk the following is indicated. Bytes 6,7 or 14,15 contain up
to four left justified TBCD digits indicating the remote node. Bytes 8,9 or 16,17 contain up
to four left justified TBCD digits indicating the remote trunk group number. Bytes 10,11 or
18,19 contain up to four left justified TBCD digits indicating the remote trunk circuit
number.
The remote node identifier is the result of the received node address (as configured in
system parameter SPNAD at the breakout node) after it has gone through reverse digit
translation (the digit translation table number is configured against the trunk main group).
It is possible to see both parties in a two party call from either end of the call, in CIL terms,
where the private network circuits in use are totally DPNSS/APNSS. For conference calls,
it is only be possible to see all parties at the node where the conference was built. Unused
digit positions are coded as null (decimal value zero).
The remote party details are given in this CIL exception record whenever a DPNSS trunk
circuit is one of the parties identified in a “Basic Record” or “Conference Record” and the
remote party details are available. This only applies to end PBXs; no further information is
given at DPNSS transit PBXs.
The Exception record contains information for up to two parties. On a normal two party call
involving DPNSS, only one remote party is indicated, assuming the remote party details
are available. However in conference cases there may be details available for more than
one remote party. If more than two remote parties are involved in a call more than one
record is required. Where no remote party details are available on calls involving DPNSS
trunks, no new exception records are given.
Remote dialled digits
For calls that breakout of the network on a remote node, the dialled digits field in the
“Continuation Record” (on the originating node) indicate the digits sent out of the network.
If the information was not forthcoming from the gateway node, then the dialled digits field
contains the digits sent over the DPNSS circuit if the call started off as an outgoing call. If
the information was not forthcoming and the call started off as an incoming call but
became an outgoing call (owing to a transfer by a remote third party to an outgoing trunk),
the dialled digits field is empty.
Since the digits sent back by the remote gateway PBX are the digits sent out of the
network, it is necessary in the case of remote PSTN or ISDN calls (but not remote decadic
calls) to prefix the digits with a simulated access code. The reason for this is to maintain
compatibility with existing CIL equipment that has to deduce that the call is a remote PSTN
breakout call by looking for a PSTN access code (e.g. 9) on the front end of dialled digits
associated with inter-PBX trunks.
The simulated access code consists of up to four digits and is set using the system
parameter SPOPD. The SPOPD parameter can be revised or listed using the RSSP/LSSP
MMI commands.
3.5.14 Exception Record for CIL Account Code (Code 21)
This Exception record is created to hold a CIL account code. The CIL record is given in
conjunction with a CIL “Basic Record” at the end of a call, or by itself. In both cases the
record should be considered to contain the account code to the party's previous call. A
parameter SPACO determines whether an account code only appears in this “Exception
Record” (SPACO = 0) or whether it also appears in the “Continuation Record” (SPACO =
1), in cases where the account code was dialled before the end of the call.
Note: SPACO and SPCAC are incompatible when both are set to 1. For further details
refer to subsection 3.3.
More than one “Exception Record” may be given for each call (e.g. more than one account
code may be associated with the previous call from that party).
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 MINUTES SECONDS TYPE A
8,9 B HOURS
10,11
12,13
14,15 ACCOUNT CODE
16,17 (Maximum 20 TBCD digits left justified)
18,19
Exception Details
This exception record was introduced at software revision 6.1.
Hours, minutes, seconds – These fields indicate the time the record was produced.
Type - This field indicates the source of the account code:
1 = CIL account code feature,

2 = PIN feature.
3 = Mobile TAC feature.
B - This field indicates the party type. 0 = extension, 3 = operator. Codes 1 and 2 are not
used.
First Party Number - This field follows the structure described in the “Basic Record”, see
subsection 3.2 for further information.
3.5.15 Exception Record for Virtual Directory Numbers (Code 22)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 B C A
6,7 Extension Number for Virtual Directory Number
8,9 D
10,11 Extension Number for Physical (terminal) Directory Number
12,13 D
14,15
16,17
18,19
Exception Details
B - This field is used to indicate VDN of subscriber involved.
C - This field is used to indicate the party number of the VDN, range 1 to 6, representing
the VDN party.
D - This field indicates the subscriber type, 00 = extension.
If a VDN is used for either the calling or connected parties, the terminal DN from which the
VDN was used is given this “Exception Record” together with the VDN in use. The two
fields are both in the format of up to 6 TBCD digits, left justified.
This record can follow a “Basic Record” that contains the VDN of either party one or party
two. This occurs where the calling or connected party is a keysystem terminal using VDNs
on additional Line keys. These additional Line keys are able to generate and receive calls
and may be on more than one keysystem terminal. It is also possible for the VDN to be
contained in a “Conference Record” associated with the “Basic Record”.
This record can also be given following other “Exception Records” (e.g. Invalid PIN Keyed
or MCT) where the extension number in the record is a VDN.
3.5.16 Exception Record for Malicious Call Trace (code 23)
This record gives information for the Malicious Call Trace (MCT) terminating party.
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 JULIAN DATE HOUR A
6,7 EXTENSION NUMBER OF TERMINATING PARTY
8,9 (CALLED PARTY)
10,11
12,13 CALLED PARTY DIGITS
14,15
16,17
Exception Details
Whenever a Malicious Call Trace request is attempted, two “Exception Records” (code 23
and 24) are given. This record identifies information with regard to the Terminating Party
(the user who received the Malicious Call).
Hour, Minute, Second - Refer to subsection 3.2 for further information.
Extension Number - (Bytes 6,7 and 8,9) give the Extension Number of the user who
entered the MCT feature code. This may be a maximum of 6 TBCD digits, left justified.
Called Party Digits - (Bytes 10,11, 12,13, 14,15 and 16,17) give the Network Number of
the Extension connected to Malicious Call. This is different to the Extension number when
an extension has entered a MCT request on behalf of another extension. This may be a
maximum of 12 TBCD digits, left justified, to include a network node identifier (SPEID)
(6 TBCD digits) plus extension number (6 TBCD digits). This allows for the extension to be
on a collocated switch or on the local switch.
There is no SPEID code for a local extension number.
Note: The SPEID parameter can be revised or listed using the RSSP/LSSP MMI
commands.
3.5.17 Exception Record for Malicious Call Trace (code 24)
This record gives information for the Malicious Call Trace (MCT) originating party.
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 JULIAN DATE HOUR A
6,7 TRUNK INDEX

or
8,9 EXTENSION NUMBER OF ORIGINATOR
10,11
12,13 CALLING LINE IDENTITY
14,15
16,17
Exception Details
Whenever a Malicious Call Trace request is attempted, two “Exception Records” are given.
This record identifies information with regard to the Originating Party (the Malicious Call)
and immediately follows an “Exception Record” code 23.
Hour, Minute, Second - Refer to subsection 3.2 for further information.
Trunk Index or Extension Number - (Bytes 6,7 and 8,9) give the Extension Number of
the Malicious call if the call was internal or the trunk number if the call was external. This
may be a maximum of 6 TBCD digits (Operators are indicated by the assigned extension
number). If this field contains only null digits, then the MCT request occurred after the
Malicious call terminated and the DX had deleted details of the call. Call details can
therefore be discovered from the previous “Basic Record” for the Called Party defined in
“Exception Record 23”.
Calling Line Identity - (Bytes 10,11, 12,13, 14,15 and16,17) give the CLI (if known) of the
Malicious Caller. Up to a 16 digit number can be given. In general, DPNSS and QSIG
trunks always support CLI, while ISDN. DASS2 and R2 usually support CLI.
Both of these fields will be empty if the MCT request occurs after the call is finished, since
the DX does not retain this information after the end of a call.
3.5.18 Exception Record for Diversion to PSTN (code 25)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 A
6,7 Network Number of divert from extension, digits 1 to 4
12,13
14,15
16,17
18,19
Exception Details
This exception record is given at the originating and terminating (breakout) nodes in
addition to the standard CIL output indicating the calling party and the diverted to route.
The record is not given at the divert-from party’s node if this becomes a DPNSS transit
node as a result of the diversion.
The intention of the record is to allow the cost of the call diverted to the PSTN to be
allocated to the extension from which the diversion to the PSTN takes place.
3.5.19 Exception Record for Extension Lock/Unlock (code 26)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 B A
6,7 EXTENSION NUMBER OF INVOKING PARTY
8,9
10,11 EXTENSION NUMBER LOCKED/UNLOCKED
12,13
14,15
16,17
18,19
Exception Details
B - This field is used to indicate the action (0 = Unlock, 1 = Lock).
Notes:
1. Locking an extension sets its COS and TAC to a system defined “Alternative COS
and TAC”. Unlocking an extension restores its normal COS and TAC.
2. In the case of First Party Invocation, where the Lock/Unlock is performed on the
extension itself, only the Extension Number of Invoking Party is included. In the case
of Third Party Invocation, where the Lock/Unlock is performed by a different
extension or an operator, both Extension Numbers are included.
3.5.20 Exception Record for Home-working activation (code 27)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 A
6,7 Personal number, digits 1 to 4
10,11 Network number of the home telephone, digits 1 to 4
Exception Details
On activation of the home-working feature by the home-worker, a privileged extension or

an operator with PVG COS, an exception record is output at the office node where the
personal number (VDN) for each user has been configured.
Personal number - These fields contain the personal number (VDN) of the user involved,
range 1 to 6 digits.
Network number - These fields contain the public network number (including the external
access code) of the destination telephone to which calls are directed, range 1 to 20 digits
(e.g. 901159123456).
Note: An additional “Basic Record” with the feature number 55 is output when users are
required to change their password on activation of the home-working feature.
3.5.21 Exception Record for Home-working de-activation (code 28)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 A
10,11
12,13
14,15
16,17
18,19
Exception Details
On de-activation of the home-working feature by the home-worker, a privileged extension,

an operator with PVG COS or the DX MMI, an exception record is output at the office
node where the personal number (VDN) for each user has been configured.
3.5.22 Exception Record for Home-working Long Call (code 29)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 A
10,11 Duration in seconds
12,13
14,15
16,17
18,19
Exception Details
Duration - The duration is the length of the call in seconds.
This exception record is only output when the system parameters TMLC1 and TMLCR
have been set using the MMI command RSSP. The first record is output by the system
when TMLC1 has been reached and the output is repeated at the TMLCR value for the
duration of the call. Refer to the Realitis Electronic Publications or the Distributor’s
Command Manual for further information (RSSP).
3.5.23 Exception Record for Hot-desking activation (code 30) and de-activation (code 31)
Table 3.32 Exception Record format for exception codes 30 and 31
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
2,3 EXCEPTION CODE = 30 or 31
4,5 A
6,7 Personal number (VDN), digits 1 to 4
12,13 Network number of the hot-desk telephone, digits 1 to 4
18,19
Exception Details
On activation/de-activation of the hot-desking feature by the user, a privileged extension,

an operator with PVG COS or the DX MMI, an exception record is output at the office
node where the personal number (VDN) for each user has been configured. If the hot-
desking telephone is at a remote node an exception record is also output for that node.
Attempting to activate a personal number that is already active at another hot-desking
telephone causes a de-activation exception record to be output and a new activation
exception record for the new hot-desking telephone destination.
given as a network number in the range 1 to 12 digits (e.g. 7805432).
Network number - These fields contain the hot-desk number (including the required
network code) of the destination hot-desking telephone to which calls are directed, range 1
to 12 digits (e.g. 7801234).
Note: An additional “Basic Record” with the feature number 55 is output when users are
required to change their password on activation of the home-working feature.
3.5.24 Exception record for Home-working call details (code 32)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 C B A
10,11 PSTN number of the home telephone, digits 1 to 4
Exception Record Details
This exception record was introduced at software revision 8.0 - Application pack 2.
When a call has been made to or from a home-worker, this exception record will be output
detailing all home-workers in the call. The exception record is output at the office node
where the personal number (VDN) for each user has been configured.
B - This field is used to indicate the subscriber number of the home-worker, range 1 to 6,
representing the home-worker Personal number (PN) subscriber slot in the basic or
conference record.
C - if set then the call is the home-working leg of the call detailing the home-worker in the
public domain (i.e. the physical representation of the call), else it is a call to or from the PN
(i.e. the virtual representation of the call)
PSTN number - These fields contain the public network number (including the external
access code) of the destination telephone to which calls are directed, range 1 to 20 digits
(e.g. 901159123456).
3.5.25 Exception Record for Hot-desking call details (code 33)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 B A
16,17
18,19
When a call has been made to or from a hot-desking user then this exception record will
be output detailing both the PN and the telephone where the hot-desking session resides.
B - This field is used to indicate the subscriber number of the person who is hot-desking
(range 1 to 6) representing the hot-desking PN’s subscriber slot in the basic or conference
record.
Network number - These fields contain the network number of the hot-desking telephone.
3.5.26 Exception record for Calling Line Identity (CLI) details (code 34)
Bit No.
Byte
No.
00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 Calling Line Identity, digits 1 to 4
14,15
16,17
18,19
This exception record enables a user, on initiating a call to the public network, to influence
the Calling Line Identity (CLI) that is sent to the called party.
Calling Line Identity - These fields contain the Calling Line Identity digits sent to the
public network, range 1 to 19 digits (e.g. 01159123456).
3.5.27 Exception Record for Invalid Pin Keyed (code 102)
Byte Bit No.
No. 00 01 02 03 04 05 06 07 00 01 02 03 04 05 06 07
0,1 HEADER
4,5 B A
6,7 KEYING EXTENSION NUMBER
8,9
10,11 INVALID PIN KEYED
12,13
14,15
Exception Details
This record is only given when an invalid PIN number is keyed at an extension.
B - This field is always 1 for this record.
Finish Hour, Minute, Second - Refer to subsection 3.2 for further information.
3.6 EXAMPLE CALLS TO ILLUSTRATE THE OUTPUT OF CIL RECORDS
The following tables provide examples of calls with the effect on CIL records output by a
DX system. The time at which records are ouput for an event (e.g. at the end of a call or at
the end of each phase of the call) is indicated by a dotted line in the “Action” column.
3.6.1 PSTN call to an Operator
Action CIL Records given
Operator answers the Basic Record.

call. PSTN trunk No.
Operator
Rung Party: Operator
Termination Party: Operator
Answer Delay > 0
Flags Set: Transfer Term.
Operator dials Basic Record

Extension A. Operator
Extn A.
Operator release Rung Party: Extn A
before Extn A Termination Party:
answers. Operator
End of phase. Flags Set: Transfer Term.
Extn A answers.
Basic Record
PSTN Trunk No.
Extn A
Rung Party: Extn A
Termination Party: Blank
Answer Delay > 0
Extn A clears and Flags Set: Transfer Initiated
PSTN trunk released. Operator
End of phase. Extended
3.6.2 Extension call to the PSTN
Extn A dials a call Basic Record and

through PSTN and is Continuation Record
connected to a trunk Extn A
by the DX. PSTN Trunk No.
(Access code & routing digits
in Continuation record).
Rung Party: Blank
Term. Party: Blank
Answer Delay: Blank
Flags Set: None.
Extn A makes enquiry Basic Record

call to Extn B which Extn A
answers. Extn B
Rung Party: Extn B
Extn A recalls and Termination Party: Blank
reconnects to PSTN Answer Delay > 0
trunk. Flags Set: Enquiry.
Extn B clears while

Held by Extn A.
End of phase.
Extn A clears and

PSTN trunk released.
End of phase.
3.6.3 Extension to extension call
Extn A dials Extn B Basic Record

which answers. Extn A
Extn B
Rung Party: Extn B
Termination Party: Extn A
Answer Delay > 0
Flags Set: Transfer Term.
Extn A makes enquiry Basic Record

call to Extn C which Extn A
answers. Extn C
Rung Party: Extn C
Extn A clears to Term. Party: Extn A
transfer Extn B to Extn Answer Delay > 0
C. Flags Set: Enquiry
End of phase. Transfer Term.
Basic Record
Extn B
Extn C
Rung Party: Blank
Term. Party: Blank
Extn C Clears. Answer Delay: Blank
End of phase. Flags Set: Transfer Initiated
3.6.4 Extension call to the PSTN, including Conference

Extn A dials a call Basic Record and

through PSTN which is Continuation Record
answered and there is Extn A
an answer signal on PSTN Trunk No.
the trunk. (Access code & routing digits
in Continuation record)
Extn A makes enquiry Rung Party: Blank Basic Record
call to Extn B. Answer Delay: > 0 Extn A
Flags Set: Transfer Term. Extn B
Rung Party: Extn B
Term. Party: Extn A
Answer Delay > 0
Extn B answers. Flags Set: Enquiry
Extn A recalls and Basic Record, Extra output 7.1 onwards:

creates a 3-way Conference Record and Basic Record,
conference. Continuation Record Conference Record,
End of phase for 7.1 Extn A Indicating 3 parties with
onwards. Extn B zero call duration
End of phase. PSTN Trunk No.
Rung Party: Blank
Answer Delay: Blank
Flags Set: Transfer Initiated
Conference
Transfer Term.
Extn A recalls and Basic Record

makes enquiry on Extn Extn A
C which answers. Extn C
Rung Party: Extn C
Term. Party: Extn A
Answer Delay > 0
Flags Set: Enquiry
Transfer Term.
Extn A recalls and Extra output 7.1 onwards:

makes a 4-way Basic Record,
conference. Conference Record
End of phase and new Indicating 4 parties with
end of phase for 7.1 zero call duration
onwards.
Continued on the next

page.
Extension call to the PSTN, including Conference (Continued)
Basic Record,
Conference Record and
Continuation Record
Extn A
Extn B
Extn C
PSTN Trunk No.
Rung Party: Blank
Term. Party: Extn A
Answer Delay: Blank
Extn A Clears down. Flags Set: Transfer Initiated
End of phase. Conference
Basic Record,
Conference record and
Continuation Record
Extn B
Extn C
PSTN Trunk No.
Rung Party: Blank
Term. Party: Extn C
Extn C clears down. Answer Delay: Blank
End of phase. Flags Set: Conf.
Basic Record and

Continuation Record
Extn B
PSTN Trunk No.
Rung Party: Blank
Term. Party: Extn B
Extn B clears down. Answer Delay: Blank
End of phase. Flags Set: None
3.6.5 Operator call to the PSTN, extends to Extension and releases
Operator dials the Basic Record Basic Record and

PSTN and extends the Operator Continuation Record
call to Extn A. Extension PSTN Trunk No.
Rung Party: Extension (Access code & routing
Termination Party: Operator digits in Continuation
Answer Delay 0 record & Account Code)
Flags Set: Enquiry Operator
Operator release Transfer Term. Rung Party: Blank
before Extn A Term. Party: Operator
answers. Answer Delay: Blank
End of phase. Flags Set: None.
Extn A answers.
Basic Record and

Continuation Record
PSTN Trunk No.
in Continuation record &
Account Code)
Extn A
Rung Party: Extn A
Answer Delay > 0
Extn A clears and the Flags Set: Enquiry
3.6.6 Operator call to the PSTN, extends to Extension (waits for answer)
Operator dials the Basic Record Basic Record

PSTN, extends the call Extension PSTN Trunk No.
to Extn A and waits for Operator (Access code & routing
answer. Rung Party: Extension digits & Account Code)
Termination Party: Operator Operator
Answer Delay: Blank Rung Party: Blank
Operator clears call Flags Set: Enquiry Term. Party: Operator
when Extn A answers. Transfer Term. Answer Delay: Blank
End of phase. Flags Set: Enquiry
Extn A answers.
Basic Record and

Continuation Record
PSTN Trunk No.
Account Code)
Extn A
Rung Party: Extn A
Extn A clears and the Answer Delay > 0
PSTN trunk released. Flags Set: Operator
3.6.7 Extension call to the Operator
Extn A calls the Basic Record Basic Record and

operator and requests Extension Continuation Record
a PSTN connection. Operator PSTN Trunk No.
Rung Party: Operator (Access code & routing
Answer Delay: > 0 record & Account Code)
Flags Set: Transfer Term. Operator
Rung Party: Exch
Term. Party: Operator
Answer Delay > 0
Operator release Flags Set: Enquiry
before Extn A Transfer Term.
answers.
End of phase.
Basic Record and

Continuation Record
Extension
PSTN Trunk No.
Account Code)
Rung Party: Blank
Answer Delay > 0
Extn A clears and the Flags Set: Transfer Initiated
3.6.8 Extension call to the Operator (Both and Release buttons pressed)
Extn A calls the Basic Record Basic Record and

operator and requests Extension Continuation Record
a PSTN connection. Operator PSTN Trunk No.
Rung Party: Operator (Access code & routing
Answer Delay: > 0 record & Account Code)
Flags Set: Transfer Term. Operator
Rung Party: Exch
Operator presses the Term. Party: Operator
Both and Release Answer Delay > 0
buttons. Flags Set: Enquiry
Basic Record and

Continuation Record
Extension
PSTN Trunk No.
Account Code)
Rung Party: Blank
Answer Delay: 0
Extn A clears and the Flags Set: Operator
PSTN trunk released. Extended
End of phase. Transfer Initiated.
4 Textual CIL
SECTION 4
TEXTUAL CIL RECORDS
4.1 INTRODUCTION
Prior to revision 3.6.201 of the DX software, there was only one form of output for CIL
records, “Full CIL” as described in this document, refer to Section 3 for further information.
In “Full CIL” the output from the DX is presented in the form of binary and TBCD records.
The interpretation of this information requires sophisticated and often expensive CIL
equipment.
The type of CIL used is configurable by the system parameter SPCIT (0 = Full (normal)
CIL, 1 = Textual CIL). The configuration can be changed at the maintenance terminal.
Refer to the Command Manuals and Servicing Manuals for further information on system
MMI commands and settings.
Note: Only one type of CIL (Full CIL or Textual CIL) can be output from a DX at any one
time. It is not advised to set the option for Textual CIL on systems that have a
high volume of calls as CIL output may be lost due to lack of flow control on the
output devices.
From software revision 3.6.201 onwards, a basic subset of the Full CIL records can be
given in the form of ASCII characters. This format allows the CIL information to be
displayed on a simple printer or VDU.
Textual CIL records are produced for the following types of call:
 Outgoing IPBX (e.g. DPNSS or APNSS) or a PSTN (Public Switched Telephone

Network, e.g. DASS or ISDN) trunk calls originated from a DX system.
 Outgoing calls from another DX connected by IPBX circuits (DPNSS) to that node, then
to the PSTN or to another PABX.
Textual CIL records are generated when:
 A call terminates.
 A call is transferred to another extension (enquiry).
Textual CIL records can contain the following information:
 Calling party number.

 Called party number.
 Call start time.
 Call duration.
 Message.
 Account code.
 Meter pulses.
Section 4 : Textual CIL Records Realitis DX Call Information Logging (CIL) Supplement
4.2 TEXTUAL CIL OUTPUT
The CIL output has the following format:
ORIG: <originator>
CALLED: <access> <route> TK <no.> <message>
TIME: <hh:mm:ss dd/mm/yy> DUR: <hh:mm:ss> A/C: <code> METER: <pulses>
Each record is terminated with a line feed and a carriage return. All fields are left justified
and filled with spaces.
Where:
The “ORIG:” field identifies the type of device that originated the call,
<originator> this field defines the Originating subscriber type:
EX <no.> Extension number for a telephone.

OC <no.> Operator Console.
OG <group no.> Operator Group.
TK <no.> Trunk.
The “CALLED:” fields are used to identify the called subscriber:
<access> Access code dialled to obtain the trunk. Space characters are
appended to this field to give a fixed length of 4 digits.
<route> Routeing digits applied to the call following any translations that may
have occurred due to least-cost routing, alternative routing, system
abbreviated dialling, etc.
TK<no.> Outgoing trunk number.
<message> Message associated with the call. Normally blank, except under the
following circumstances:
CONFERENCE - If more than two parties are involved in a call at the
time the call record is generated.
TRANSFER - The call has been transferred to another party, or a call
involving such a transfer has been terminated.
TIME: The time fields <hh:mm:ss dd/mm/yy> give the start time and date of a
simple call, or transfer time and date of a transferred call. If a CIL
record is generated before the system time and/or date has been set
(via MMI) then the digits in this field will be replaced by ‘?’ characters
(e.g., TIME: ??:??:?? ??/??/??). If a CIL record is generated after a
software restart but before the time and date have been set, the
contents of this field will be replaced by the text UNKNOWN.
Note: The format of the year field is two digits (yy). This means, the years are
numbered 99 for 1999, 00 for 2000, 01 for 2001, etc. (the pivot date for a DX is
1980/81).
Realitis DX Call Information Logging (CIL) Supplement Section 4 : Textual CIL Records
DUR: This field <hh:mm:ss> gives the total duration of the call, or duration of
the call since being transferred. If a CIL record is generated after a
software restart but before the time and date have been set, the
contents of this field will be replaced by the text UNKNOWN.
A/C: This field <code> gives the account code associated with the calling
party. If no account code is available the field is left blank and the text
“A/C” is removed from the output.
METER: This field <pulses> gives the total number of meter pulses, for that call,
registered since the previous call logging output.
4.2.1 Textual CIL example
The following example contains two simplified call logging print outs associated with the
same call:
ORIG: OC2181
CALLED: (90 ) 0602384094 TK0105 TRANSFER
TIME: 07:30:05 07/01/95 DUR: 00:03:17 METER: 00032
ORIG: EN2510
CALLED: (90 ) 0602384094 TK0105 TRANSFER
TIME: 07:33:22 07/01/95 DUR: 00:01:30 METER: 00010
The first describes a call from an Operator Console (OC extension number 2181) to 0602
384094 (using access code 90) on trunk 105, originated at 7:30:05 am on 7th January
1995. The call is transferred to extension 2510 after 3 minutes and 17 seconds having
registered 32 meter pulses, which causes the first call logging printout.
The call lasts a further 1 minute and 30 seconds and registers a further 10 meter pulses
before it is cleared down. This causes the second CIL output to be generated.
Section 4 : Textual CIL Records Realitis DX Call Information Logging (CIL) Supplement

CIL Spec Issue 5

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

CIL Spec Issue 5

Caricato da

Copyright:

Formati disponibili

1QHA 50491 AAW

Telephone: Nottingham (0115) 943 0300

DATE SIG. ISSUE CHANGE

1 ABOUT THIS SUPPLEMENT.......................................................................1-1

1.1 SCOPE......................................................................................................... 1-1

1.2 CONDITIONS OF USE.................................................................................1-2

1.3 UPDATE POLICY.........................................................................................1-2

1.4 EXCLUSION OF LIABILITY..........................................................................1-2

2.1 OVERVIEW OF CIL......................................................................................2-1

2.2 SOFTWARE REVISION INFORMATION......................................................2-2

3 FULL CIL RECORDS...................................................................................3-1

4.2 TEXTUAL CIL OUTPUT...............................................................................4-2

ACD Automatic Call Distribution.

ACI Advanced Connectivity Interface. A descriptive name used when

APNSS DPNSS where signalling is carried on a discrete signalling circuit to

ASCII American Standard Code for Information Interchange. ASCII is the

CIL Call Information Logging.

CILE Call Information Logging Equipment.

CLI Calling Line Identity.

CPU Central Processing Unit.

DLI Digital Link Interface.

DPNSS Digital Private Network Signalling System.

DX Digital eXchange. A generic term use to describe the Realitis and

EXCH Exchange (e.g. PSTN) trunk.

HCIL MMI command to halt CIL output.

IP Internet Protocol. A network protocol used to send messages requiring

IPBX Inter PABX trunk.

ISDN Integrated Services Digital Network.

iSDT Integrated Services Digital Terminal.

iSPS Integrated Services Packet Switching.

LAN Local Area Network. A data communications network within a limited

MCT Malicious Call Trace.

Mobile TAC Mobile Trunk Access Class of service.

NUC Nailed Up Call.

OLI Originating Line Identity.

PABX Private Automatic Branch Exchange.

PBX Private Branch Exchange.

PIN Private Identity Number.

PSD Packet Switched Device.

PSTN Public Switched Telephone Network.

PTO Public Telephone Operator.

R2 CCITT Line and Register Signalling System.

RAD Recorded Announcement Device.

RCIL MMI command to resume CIL output.

Realitis DX An EMC approved digital exchange.

Realitis DX150E A single cabinet EMC approved digital exchange supporting up to 6

Realitis DX150R A one- or two- unit system designed to be mounted in a 19-inch

Realitis DXR* The name of a one- or two-unit PABX designed to be mounted in a

RS-232C RS-232C is a standard that describes the physical interface and

TAC Trunk Access Class.

TBCD Telephonic Binary Coded Decimal. In all TBCD fields, digit 0 is

TCP Transmission Control Protocol. The transport protocol used to

TLI Terminating Line Identity.

UPI Universal Peripheral Interface card. The UPI functions as an MMI

V.24 Part of the series of ITU interface specifications.

VDN A Virtual Directory Number, one which has no physical channel

VDU Visual Display Unit.

 Realitis DX (Digital Exchange);

This supplement is not intended as a stand-alone document and must be used in

 5.2 and earlier - for iSDX-series only.

This supplement is divided into four Sections:

 Section 1 : About this supplement - provides a description of the contents of this

1.2 CONDITIONS OF USE