Mitel SX-200 DIGITAL Pabx General Description Manual

							Station Message Detail Recording
TABLE
2-1
3-l5-lCHART
2-I
LIST OF TABLES
TITLE.
PAGESummary of Fields In SMDR Records , . D . m
 
n . s 0
 n , 0 m 2-2
Character Set . . a . . . . . . . . . . a
 q
 m . . , m li . . 0 . 0
 0
 m
 
s s . 3-2
CDE-Selected SMDR Class of Service and
System Options . . . . 
m . a
 D m . . . s . a D
 s 0 D . 0
 o 0 m
 s e D . 5-2
LIST OF CHARTS
iv 
						

							Station Message Detail Recording
1. INTRODUCTION
General1.01This document describes the Station Message Detail Recording
(SMDR) feature of the 
SX-200@ DIGITAL Private Automatic
Branch Exchange (PABX). 
T.he document includes a detailed description
of the feature, its programming and its operational parameters. 
iheinstallation of the external devices (e.g., printer) should be obtained
from the product-related documentation.
Reason for issue
1.02 This Section is issued to describe the SMDR feature of the
SX-200@ DIGITAL PABX with Generic 1000 or Generic 1001
software and its associated options. This practice was formerly Sec-
tion 
MITL9108-093-451-NA, Issue 1. The numbering has been changed
as part of a documentation rationalization program. Change bars have
been included to show the changes from the last issue of Section
MITLS 108-093-45 1 -NA.
Brief Description
1.03The Station Message Detail Recording, or “call detail recording”,
feature of the 
SX-ZOO@ DfGlTAL PABX, is an integral part of the
system which generates a descriptive call record for every incoming
and outgoing trunk call made via the PABX. These call records can be
routed to an RS-232 port for processing or printing. They allow the
customer to evaluate the use of the system’s trunks and hence deter-
mine whether the quantity and type of trunks is the most economical
mix for the traffic being handled by the PABX. In addition, the customer
can analyze the use of the trunk network by corporate personnel.
Misuse can then be corrected through modifications to the toll control
assignment.
Page 
l-l/% 
						

							Station Message Detail Recording
2. DETAiLED DESCRIPTION
General
2.01The SMDR data collection process is initiated every time a trunk
(incoming or outgoing) is seized. The collection process forms
part of the system’s call processing routines; as such, data is collected
on a per-call basis for the duration of each call. The data is formatted
into an SMDR record and is routed to an RS-232 output port. The
records can be routed directly to the output port as described in Part 3
of this Practice.
2.02When SMDR (outgoing and incoming) is selected, a record is
generated for every trunk call regardless of the call duration,
the identity of the originating party or whether the call is completed.
When two or more trunks are involved in a call, a separate record is
generated for each trunk, thus allowing each trunk to be analyzed for
costing purposes. When a station which is involved in a trunk call
invokes a transfer to another station, only one record is generated,
however, the number of the second station appears in the SMDR call
record.2.03An SMDR record is not generated for: (1) calls which encounter
busy trunks; (2) internal calls between stations or between a
station and the Attendant; or (3) calls made from stations or going to
trunks whose class of service includes SMDR disable.
Recorded Information
2.04Each SMDR call record occupies a single line comprising 85 or
88 characters; the latter accommodates a 3-digit system iden-
tifier. The information which can be included in a call record is as
foliows:
Call Start time
Calling party
Called party
Call duration
Call completion status (e.g., called number busy)
Digits dialed on the trunk (maximum 26 digits)
Meter pulses (optional)
Outgoing and incoming trunk numbers
System identity (optional)
Long calls identified
Time to answer incoming calls
identifies the second station in a transfer or in a conference
Identifies conferences and transfers
Indicates when the Attendant was involved in the call.
The definition of the data and its position in the record is given
in Table 2-l. The table has five columns: the first identifies the
data; the second defines the data’s position within the record; the third
indicates the format of the data; the fourth describes the data; and the
fifth provides additional notes.
Page 2-l 
						

							Station Message Detail Recording
TABLE 2-1
SUMMARY OF FIELDS IN SMDR RECORDS
Name-0ng Cail
IateSpacer
Startrime
Spacer
IIuration
of call
Spacer
Calling
Party
Spacer
Attendant
Leading
Digits
Time to
Answer
(Alternate)
Digits
Dialed on
the trunkColumns
12-6
7
8-13
14
15-2223
24-27
28
29
30-33
30-32
34-59Format
2
mm/ddhh:mm
h:mm:ss
PPPPf
I3999ttt
xx. . . .xDefinition
- = 5-9 min
% = lo-29 min
+ = 30 or more min
= Month
irn= Day
-- 
=Space
hh 
= Hours
mm= Minutes
-- 
=Space
hh:mm:ss= duration
in 
hours:minutes:seconds-- 
=Space
cccc 
= Extension Number
Tnnn =Trunk Number
(CO)Xnnn = Trunk Number
(Non-CO)
mmmm= Attendant Console
Directory Number
-- 
=Space
= Attendant
--
= Attendant not involved
cccc
= Access Code
(outgoing and tandem
calls only)
ttt = Time in seconds
(000-999)
***= Call unanswered
Up to 26 (20 if
metering) digits dialed
on the trunkNotes
mm= 01-12
dd = 01-31
80-23DO-59
hh 
= 00-18, mm = 00-59
and ss= 00-59
c= o-9, *, #nnn= 000-999
m = O-9
Attendant answered or
initiated the call, then
transferredit to an
extension
6 = o-9, *, #Left-justified.
Leading zeroes output.
Incoming calls only.
x = O-9, *, or #private speed call numbers
are mot recorded.
Page 
2-Z 
						

							Station Message Detail Recording
TABLE 2-1 (CONT’D)
SUMMARY OF FIELDS IN SMDR RECORDS
Name
Meter
(Optional)CallCompletion
Status
Speed Callor Call
Forward
FlagsCalled Party
Transfer/
Conference
Call
SpacerThird Party
SpacerAccount
Code(Optional)
Spacer(Optional)
System
Identifier
(Optional)Format
mmmm
h
C,R, or
F.
Krrrr
aa .-se a
.a.III
IDefinitionINotes
mmmm = Number ofmmmm = 00000 to 6400
meter pulsesLeading zeroes outputted
A= Answer Supervision
B = 
Callee is Busy
E = Caller Error
T = TAFAS answered
C=Number was Speed
called (ARS implied)
F= Forwarded through
External Call Forward
R=default (ARS implied)
cccc= Extension Number
Tnnn = Trunk Number
(CO)Xnnn =Trunk Number
(Non-CO)
mmmm= AttendantConsole
Directory NumberOutgoing
Incoming Direct/Dial-In
Incoming/Dial-In Incoming
Incoming/Outgoing
Outgoing
All trunk calls are
ARS by default.
c = o-9, *, #
nnn= 001-200
m = O-9
T = Supervised Transfer
X = Unsuperwised Transfer
C = 
S-Way or
Conference
-- 
=Spacecccc = Extension Number
-- 
0Spacec = o-9, 
*, #
Length of 
1 to 12
digits
-- 
=SpaceEntered by System IDa = 
9-9 space-filled
i 
= O-9..oIII= 000-999
000 = “No Code entered”
Page 2-3 
						

							Station Message Detail Recording
2.06A description of the call record fields detailed in Table 2-l is as
follows:
Long Call Indicator (z). This optional field contains a dash (-)for calls of duration 5 to 9 minutes 59 seconds, a percent
symbol 
(%) for calls of duration 10 to 29 minutes 59 seconds,
or a plus symbol (+) for calls of 30 or more minutes. This is
useful when records are to be scanned manually.
Date 
(mm/dd). The date is reported numerically as a 2-digitmonth followed by a 2-digit day. The year is 
net reported.
Start Time 
(hh:mm). The start time of a call is reported in hours
and minutes. A 24-hour format is employed.
Duration of Call 
(hh:mm:ss). The call duration is reported in
hours,minutes and seconds. Leading zeroes are output
(Maximum time = 23 hours, 59 minutes, 59 seconds).
Calling Party (pppp). This is the identity of the party that origi-
nated the call. If a 
5-digit extension numbering plan is used,
only the last four digits will be used by SMDR to identify the
calling party. It may be a station, the Attendant, or an incoming
trunk, as described below:
(a) Station Number as Calling Party (cccc). A station number may
be one to four digits (O-9, 
*,#) which are left-justified; i.e., no
leading zeroes.
(b) Attendant as Originating Party. Calls originated by the Atten-
dant, which do not involve a third party, report a calling party of
the console directory number. When the console number is in
the range 
19 through 99, the format is modified to be ATmm. If
the Attendant calls an outside party on behalf of an station or
trunk, that station or trunk is reported as the caller but the
Attendant Flag symbol
* appears in the “Attendant was In-
volved” field.
wTrunk Number as Calling Party (Tnnn or Xnnn). When the origi-
nating party is an incoming CO trunk, “Tnnn” appears on the
record, where “nnn” is the number of the trunk. When the
originating party is an incoming non-CO trunk, “Xnnn” appears
in the record trunks. The 
‘7” or “X” ensures that this number
and CO Attendant trunks may be distinguished from tie trunks.
The trunk number is the trunk ID specified during customer data
entry in the Trunk Assignment tables
Attendant 
(6). This l-digit field contains an asterisk (*) when a
call is originated by or initially answered by the Attendant. This
flag will not appear when a call is transferred to the Attendant.
Time to Answer (ttt). This is the number of seconds from the
time the incoming trunk is seized, until the call is answered. If
the call is never answered, this field displays 
***. It applies to
Page 2-4 
						

							Station Message Detail Recording
incoming calls only. Leading zeroes are output and the field
remains at 255 when an overflow is reached.
Leading Digits (up to 5 ARS leading digits}. This field applies to
outgoing calls. For incoming calls this field reports Time to
Answer (see above). Leading digits correspond to digits pro-
grammed in the ARS digit string form during CDE. Leading
digits reported may be from one to four digits long (O-3, *, #)(only the first 4 of 5 digits are reported). The field is 
left-justified and space filled.
Digits Dialed on the Trunk (xxx---x). The maximum number of
digits (O-9, 
*,#) recorded is 25. When the SMDR Meter Pulse On
option is selected, this number is reduced to 
20. This field does
not include the trunk group access code on outgoing calls. The
digits recorded are the actual digits outpulsed on the trunk
after digit modification has been performed. On dial-in trunk
calls, the digits dialed in on the trunk are recorded. When more
than 25 digits are dialed, the 25th digit is overwritten.
Meter Pulses (mmmmm). The number of reversals (i.e., meter
pulses) received from an outgoing trunk can be recorded when
this option is selected. The range is 0 to 64000. Leading zeroes
are output. The maximum number of digits recorded reduces
from 26 to 20. The trunk group must be programmed for
“Answer Supervision”. Meter pulses are not recorded for other
trunk groups.
Call Completion Status (h) (Outgoing Calls). This field is used
to report the completion status of an outgoing call in so far as
the PABX is able to determine it. When the trunk group is
programmed to receive “Answer Supervision” and a supervision
is received, an “A” is reported.
Call Completion Status (h) (Incoming Calls). The PABX can
monitor the outcome of the call, and thus, can provide a com-
prehensive report on the calls completion. From a dial-in trunk,
but not a direct-in-line trunk, if the station or hunt group to
which the call is directed is busy, a “B” is recorded. When an
incoming dial-in trunk dials an invalid number and receives
reorder tone, an “E” is reported. The field is blank for incom-
plete calls. A “T” is reported if the incoming trunk is answered
with TAFAS. When an incoming call is forwarded by the Atten-
dant to a busy station, a “B” appears in the call completion
status field, the number called appears as the third patty, and
the Attendant appears as the called party.
Speed Call or Call Forward Flags 
(C,R, or F). This field contains
a “C” when the number is speed dialed, and an F when the call
is 
fonn;arded through the external call forward feature; other-
wise, R will appear.Called Party (qqqq). This is the party to whom the call is
directed. It may be an station number, the Attendant or for
Page 2-5 
						

							Station Message Detail Recording
outgoing calls, the number of the trunk. The format in which the
called party is output is identical to that used for the calling
party. See Calling Party (pppp). For incoming calls to the Atten-
dant, the called party is recorded as the Attendant unless the
Attendant transfers it to a station. For direct-in lines, it would
be the station number. On outgoing calls handled by the Atten-
dant, the called party would be the trunk number which the call
went out on.
Transfer/Conference Call (K). This field identifies calls that
involve three or more parties. It contains a 7” for supervised
transfers,“X” for unsupervised transfers (Le., dead transfer or
transfer into busy) and a “C” for 3-way conversations and con-
ferences.
Third Party (rrrr). The third party field contains the number of
the station to which a trunk call has been transferred. 
VVhenseveral transfers take place during a trunk call, the first party is
the only one reported. The format is identical to that of the
Calling Party (pppp).
Account Code (aa...a). Account codes are typically used to
charge the cost of calls either to 
internsi departmental cost
centers or to project accounts for billing to specific projects. An
extension may have the option, or be forced to enter an ac-
count code for trunk calls. The account code may be 
l-12digits (the default value is six digits).
System identifier (iii). This optional S-digit field may contain
values from “000” to “999”.“000” indicates that no identifier has
been entered.Call Record Examples
2.07Examples of typical SMDR call records are shown in Chart 2-l.
Page 2-6 
						

							Station Message Detail Recording
CHART 2-1SMDR PRINTOUTS
0
1234567
89123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
EXAMPLE 1: 
Z-PARN OUTGOING CALL
-06/13 11:42 00:08:29 214 916135922122ART054000
On June 13th at 
11:42 AM, Extension 214 obtained Trunk Number 54 and dialed
“1-613-592-2122”. Answer supervision was provided. The conversation lasted 3 minutes, 29
seconds.
0
1234567891234567890123456789012345678901234567890123456789~1234557890123456789012345678901234567890
EXAMPLE 2: Z-PARTY OUTGOING CALL
05/17 IO:51 00:01:52 213 9201\ARX082
000
On May 17 at 
IO:51 AM, Extension 213 accessed an identified trunk group, then 201 to obtain an
extension in the other PABX. The other PABX provided supervision and the conversation lasted 1minute, 52 seconds. The trunk number was 082.
0I234
567a9123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
EXAMPLE 
3; 2-PARTY INCOMING CALL
01/30 1510‘ 00:02:22 T102 008 201
201000
On January 30 at 3:10 
Ph!, incoming Direct-in Trunk Number 102 rang in to Extension 20’1. The
extension answered after 8 seconds and they talked for 2 minutes, 22 seconds.
01234567I39123456789012345678901234567890123456789012345678901234567890~23456789012345678901234567890
EXAMPLE 4: 2-PARTY INCOMING CALL
03/12 09:ll 00:01:12 X116 007 63
224000
On March 12 at 
9:ll AM, Dial-in Tie Trunk 116 dialed Hunt Group with Access Code “63”.
Extension 224 answered after 7 seconds, and the conversation lasted 1 minute, 12 seconds.
0
12345678912345678Y01234567890123456789012345678901234567890123456~89012345678901 2345678901234567890
EXAMPLE 5: ATTENDANT-HANDLED CALL 
- OUTGOING TRUNK
+01/30 15:27 00:35:11 201 “916545996951
ART052000
On January 30, Extension 201 
dialed.the Attendant and asked for an outside line. The Attendant
dialed 1-654-599-6951. At 3:27 PM, the other party answered and the conversation lasted 35
minutes, 11 seconds. Trunk Number 52 was used.
Page 
2-7 
						

							Station Message Detail Recording
CHART 2-l
SMDR PRINTOUTS (CONT’D)
01234
56769123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
EXAMPLE 6: ATTENDANT-HANDLED CALL 
- INCOMING TRUNK
N/O5 13:42 00:00:31 TO90 0091234000
.On April 15th at I:42 PM, Trunk 90 rang into the Attendant. After 9 seconds, the Attendant at
1234 answered. The trunk party spoke to the Attendant for 31 seconds, then hung up.
0
1234569891234567890123456789012345678901234567890123458789012345678901234567890~2345678901234667890
EXAMPLE 7: CALLING EXTENSION TRANSFER CALL
04/0209:36 00:04:55 103 95922122RTl62TlOO000
On April 2nd at 
9:36 AM, Extension 103 dialed a trunk access code followed by 592-2122. The
called party answered, and after conversing the caller transferred the called party to Extension
100. After further conversation Extension 100 hung up. The total period for both conversations
was 4 minutes, 55 seconds. Trunk Number 162 was used for the call.
0
1234567891234567890123456789012345678909234567890123456789012345678901234567890~234567890~234567890
EXAMPLE 8: CALLED EXTENSION TRANSFER CALL
03/12 07:42 00:03:06 i162 “003241T 215000
On March 12th at 
7:42 AM, Trunk 162 rang the console and requested to speak to Extension 241.
The Attendant took 3 seconds to answer the call. After speaking to Extension 241, the latter
extension then transferred the call to Extension 215. The total conversation lasted 3 minutes, 6
seconds.
Call Timing
2.08 The timing functions which apply to incoming and outgoing
calls are described as follows:
Incoming Call 
-Three aspects, related to the timing of an
incoming call, are recorded on a SMDR call record; i.e., the date,
the time taken for the called party to answer and the duration
of the call. The time to answer is the difference between the
time when the called device is seized and the time when the
called party answers. The duration of the call is the difference
between the time when the call is answered and the time when
the call is released; 
i.e., call cleardown.
Outgoing Call 
-Three aspects, related to the timing of an
outgoing call, are recorded on an SMDR call record; i.e., the
date, the call start time and the call duration. The latter is only
recorded for calls which are answered. The call start time 
isrecorded as either the time when the called device is seized, or,
Page 2-8