Mitel SX 200 DIGITAL Pabx General Descriptions Manual

							Station Message Detail Recording
1. INTRODUCTION
General1 .OlThis document describes the Station Message Detail Recording
(SMDR) feature of the 
SX-200’ DIGITAL Private Automatic
Branch Exchange (PABX). The document includes a detailed description
of the feature, and its operational parameters. The installation of exter-
nal devices (e.g., printer) should be obtained from the product-related
documentation.
Reason for Reissue
1.02This Section is reissued to describe the SMDR.feature of the
SX-200 DIGITAL PABX with Generic 1002 and Generic 1003
software and its associated options.I
Brief Description
1.03The Station Message Detail. Recording, or “call detail recording”,
feature of the SX-200 DIGITAL 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 are 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.
1.04DATA SMDR provides a record of each data call which is made
within the PABX so that all data-related traffic may be analyzed.
1.05ACD SMDR provides a record of each ACD call made, so that
ACD activity can be analyzed. The ACD 
TELEMARKETERTM Re-
porting System and its associated ACD SMDR are not available with
Generic 1002.I
Page 1 
						

							SECTION MITL9109-094-221-NAPage 2 
						

							Station Message Detail Recording
2. DETAILED DESCRIPTION - TRUNK SMDR
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 4
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.
Trunk Call Record Buffers
2.04The PABX has 200 buffers which store call record information; if
all buffers become full, there are two options: overwrite the
oldest record or do not allow trunk calls until buffers are available.
Recorded Information
2.05Each SMDR call record occupies a single 85 character line (88 if
a 3-digit system identifier is included). The information which
may be included in a call record is as follows:
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
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
ARS leading digits
Page 3 
						

							SECTION MITL9109-094-221 -NA
lAccount code (optional)
aSystem identity (optional).
2.06The 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.
2.07A 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-digit month
followed by a 2-digit day separated by a 
(/) slash. The year is not
reported.
Start Time (hh:mmp). The start time of a call is reported in hours and
minutes. System option “24 Hour 
CLock” determines whether a 12-houror 24-hour format is used; p indicates pm in 12-hour format.
Duration of Call (hh:mm:ss). The call duration is reported in hours,
minutes and seconds with leading zeroes being output (maximum time
that can be recorded is 18 hours, 12 minutes, 15 seconds).
Calling Party (pppp). This is the identity of the party that originated
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:
lStation 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.
eAttendant 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. If the Attendant calls an outside
party on behalf of a station or trunk, that station or trunk is
reported as the caller but the Attendant Flag symbol 
* appears
in the “Attendant was Involved” field:
lTrunk 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.
Page 4 
						

							Station Message Detail Recording
Attendant (f). 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 incoming calls only.
Leading zeroes are output and the field remains at 255 when an
overflow is reached.
i: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 programmed in the
ARS digit string form during CDE. Leading digits reported may be from
one to four digits long (O-9, 
*,#) (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 26. 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 26 digits are dialed, only the first 26 are
recorded; the rest are ignored.
Meter Pulses (mmmmm). The number of reversals (i.e., meter pulses)
received from an outgoing trunk can be recorded when COS Option
247 (SMDR 
-Record Meter Pulses) is enabled. However, the maximum
number of digits dialed on a trunk that are recorded is reduced from
26 to 20. The range is 0 to 65535, with leading zeroes being output.
The trunk must be programmed for “Answer Supervision”. Meter pulses
are not recorded for other trunks. Meter pulses are used most fre-
quently in Hotel/Motel applications, where each call generates a pulse,
and for outside North America, where a number of meter pulses is
generated for each toll call, proportional to the distance and duration
of the call.
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 comprehensive 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 incomplete calls. A 
7” is reported if the incoming trunk is an-
swered 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. Recall no answer is indicated by an N or an R; an “N”
Page 5 
						

							SECTION MITL9109-094-221 -NA
indicates that a transferer did not answer a recall, and an “R” indicates
that the transferer did answer the recall.
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 forwarded
through the external call forward feature; otherwise, R will appear
(routed via ARS 
- default for outgoing trunk calls).
Called Party (qqqq). This is the party to whom the call is directed. It
may be a station number, the Attendant or for 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 Attendant, 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
Attendant, 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 “T” for supervised transfers, “X” for
unsupervised transfers (i.e., dead transfer or transfer into busy) and a
“C” for 3-way conversations 
.and conferences.
Third Party (rrrr). The third party field contains the number of the
station to which a trunk call 
,has been transferred. When several trans-
fers 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 internal departmental cost centers or to project
accounts for billing to specific projects. An extension may have the
option, or be forced to enter an account code for trunk calls. The
account code may be 
1-12 digits (the default value is six digits). If COS
Option 246 (SMDR Extended Record) is enabled, up to 12 digits of the
Account Code are recorded. Otherwise only the first eight digits of the
Account Code are recorded.
System Identifier (iii). This optional 3-digit field may contain values
from “000” to “999”. “000” indicates that no identifier has been entered.
The system identifier is printed only if the COS Option 246 (SMDR 
-Extended Record) is enabled.
Page 6 
						

							Station Message Detail Recording
TABLE 2-l
SUMMARY OF FIELDS IN TRUNK SMDR RECORDSNameLong CallColumns FormatDefinition
Notes
1i!- = 5-9 min
% =
lo-29 min
+ = 30 or more min
Date.2-6mm/dd. mm = Month
= 01-12
dd = Day
dmdm_ 01-31
Spacer
7Start Time
8-‘13hh:mmp hh = Hours
00-23
mm = Minutes
00-59
P= PM (12-hour clock)
Spacer
14Duration of call 15-22hh:mm:ss 
hh:mm:ss = duration inhh= 00-18, mm = 00-59,
hours:minutes:seconds
ss =
00-59 (maximum =
18:12:15)Spacer23
Calling Party24-27
.PPPPcccc= Extension Numberc = o-9, *, #
Tnnn =Trunk Number (CO)
nnn= 001-200
Xnnn
= Trunk Numberm= o-9, *, #
(Non-CO)
mmmm = Attendant
Console
Directory Number
Spacer28
4ttendant29f
* = AttendantAttendant answered or
-- =Attendant not involved initiated the call, then
transferred it to an
extension
Leading Digits30-33cccccccc 
=Access Code
c = o-9, *,#, left-justified
(outgoing and
>tandem calls only)
Time to answer 30-32tttttt
= time in seconds
(Alternate)leading zeroes output,
***= Call unansweredincoming calls only
ltt= 000 - 255
Digits dialed on 34-59
xx . . . . xUp to 26 (20 if metering)x = o-9, *,or #; private
the trunk
digits dialed on the trunkspeed call numbers are not
recorded.
Meter
55-59mmmmm mmmmm = number ofmmmmm
= 00000 to 65535
[Optional)meter pulses
leading zeroes outputted
Page 7 
						

							SECTlON MITL9109-094-221 -NA
TABLE 2-l (CONT’D)
SUMMARY OF FIELDS IN TRUNK SMDR RECORDS
Name
Call
Completion
StatusColumns FormatDefinitionNotes
60
hA = Answer SupervisionOutgoing
B = 
Callee is BusyIncoming Direct/Dial-In
E = Caller ErrorIncoming/Dial-In
T = TAFAS answeredIncoming
R = Incoming call recalledIncoming/Outgoing
and was answered by
transferer
N = Incoming call recalled
and was not answered
by transferer
Speed Call or 61C,R, or FC = Number was SpeedOutgoing
- All trunk calls
Call Forwardcalled (ARS implied)are ARS by default.
FlagsF = Forwarded through
External Call Forward
R 
= default (ARS implied)
Called Party62-65
9999cccc = Extension Numberc = o-9, *, #
Tnnn =Trunk Number (CO)nnn= 001-200
Xnnn= Trunk Numberm = O-9, *, #
(Non-CO)
mmmm= Attendant
Console Directory
Number
Transfer 
/66KT = Supervised- Transfer
ConferenceX = Unsupervised Transfer
CallC 
= 3-Way or Conference
Spacer67
Third Party68-71rrrrcccc =Extension Numberc = o-9, 
*, #
Tnnn =CO Trunk Numbern = 001 
- 200
Xnnn = Non-CO Trunkm = 0 
- 9, *, #
Number
mmm= Attendant
Spacer72
Account Code73-84 
aa ..,. alength of 1 to 12 digitsa = O-9 space-filled
(Optional)
Spacer
(Optional)85
System
Identifier
(Optional)86-88 iiiEntered by System IDi = O-9
. . .III= 000-999
000 =“No Code entered”
Page 8 
						

							Station Message Detail Recording
Trunk SMDR Call Record Examples
2.08Examples of typical trunk SMDR call records are shown in Ch.art2-l. The column indication included with each example is not
repeated for each message in a regular printout.
Call Timing
2.09 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 patty 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 is recorded as either the time when
the called device is seized, or, in the case of answer supervision, the
time when the called device is answered. Call answer is determined by
an answer supervision signal provided by the trunk. The call duration is
the difference between the time when the call is answered and the
time when the call is released; i.e., call cleardown.
CHART 2-l
TRUNK SMDR PRINTOUTS
P-PAR-R 
CUTGOIffi CALL
0123456789123456789012345678901234567890723456789012345678901234567890~234567~9012345678901234567890
-06/1311:4200:08:29214916135922122ART054000
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 8 minutes, 29 seconds.
2-PARPI WTGOING CALL
01234
561234567890123456789012345678901234567890~234567~90~234567~901234567~9~,234567~9~1~34567~9~
05/17 lo:51 00:01:52 213 9201ARX082000On May 17 at 
lo:51 AM, Extension 213 accessed an identified trunk group, then dialed 201 to
obtain an extension in the other PABX. The other PABX provided answer supervision and the
conversation lasted 1 minute, 52 seconds. The trunk number was 082.
Page 9 
						

							SECTION MITL9109-094-221 -NA
CHART 2-l (CONT’D)
TRUNK SMDR PRINTOUTS
2-PARTY INCOMING CALL
01234567a9123456789012345678901234567890123~56789012345678901234567890123456789012345678901234567890
01/30 15:lO 00:02:22 T102 008 201201000On January 30 at 
3:lO PM,incoming Direct-in Trunk Number 102 rang in to Extension 201.The
extension answered after 8 seconds and they talked for 2 minutes, 22 seconds.
2-PART-Y INCOMING CALL
0123456789123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
03/12 09:ll00:01:12 X11600763224000On March 12 at 
9:ll AM, Dial-in Tie Trunk 116 dialed Hunt Group with Access Code “63”. Extension
224 answeredafter 7 seconds,andtheconversationlasted1minute,12seconds.
AlTENDANT-HWJDLED CALL - OUTGOING TFtU’JK
01234567
89123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
+01/30 15:27 00:35:11 201“9 16545996951ART052000On January 30, Extension 201 dialed the Attendant and asked for an outside line. The
Attendant dialed 1-654-599-6951. At 
3~27 FM, the other party answered and the conversation
lasted 35 minutes, 11 seconds. Trunk Number 52 was used.
ATTENDANT-I-WQLED CALL - INCOMING TRUVK
0123456789123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
04105 13:42 00:00:31 TO90 0091234000On April 5th at 
1: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.
CALLING EXTENSION TRANSFER CALL
0123456789123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
04/02 09:36 00:04:55 103 95922122RT162T 100
000
On April 2nd at 
9:36 AM, Extension 103 dialed ARS leading digit 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.
Page 10