Mitel SX 200 DIGITAL Pabx General Descriptions Manual

							Station Message Detail Recording
CHART 2-1 (CONT’D)TRUNK SMDR PRINTOUTS
CALLED EXTENS 
ICPJ TRANSFER CALL
012
3456789123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
03/12 07:42 00:03:06 T162 “003241T 215000On 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.
ANALOG NETWORKING 
- WTGD ING CALL
012
34.5678
9123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
01/16 09:52 00:02:21 2664 97082664#95921022RX124On January 16th. at 
09:52 AM, extension 2664 accessed a tie trunk and dialed 95921022. The call
lasted 2 minutes and 21 seconds.The Analog Networking feature caused the Analog Network access
code (708 as defined in Modified Digits Table) and the calling extension (2664) to be passed
onto the trunk.
ANALOG NETWORKING 
- INCOMING CALL
01234
56789123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
01/13 15:26 0O:Ol:lB 4300 004 *94300#27772777
On January 
13th, at 3:26 PM, extension 2777 received a call from an incoming tie trunk. The
incoming digits dialed on the trunk were 2777 (the called extension); the Analog Networking
feature added
*9 (network feature access code as defined in CDE) and 4300 (the calling party
identification for that tie trunk).The call lasted 1 minute and 18 seconds.
Page 11 
						

							SECTION MITL9109-094-221 -NA
Page 12 
						

							Station Message Detail Recording
3. DETAILED DESCRIPTION - DATA SMDR
General
3.01The DATA SMDR feature allows the printing out of detailed
records for external and internal data calls in a format similar to
existing trunk SMDR printouts.
3.02 The major differences between a DATA SMDR record and a
TRUNK SMDR record are: the month and day are separated by a
dash (-) rather than a slash 
(/), and the “Digits Dialed on a Trunk” field
is replaced by three fields; “Data Call Indicator”, “Type of Data Call”,
and “Reason for Disconnect”. When an external data call uses a Pooled
modem to interface the internal data device to analog trunks, the DATA
SMDR record shows the call between the data device and the Pooled
Modem, while the TRUNK SMDR record shows the call between the
trunk and the Pooled Modem. An internal modem pooling call shows
the DATA SMDR record between the pooled modem and the data
device.
3.03The DATA SMDR function operates with the trunk SMDR feature
in the PABX. Its printouts may be directed to a specific printer
port by programming it in the Directed 
I/O Form 34. The DATA SMDR
record format is such that an application processor can print the
records with other call records, but not cost them. Through CDE, a.
data user can have the option or be forced to enter a data account
code.
Recorded Information
3.04Each DATA SMDR call record occupies a single line of 85 char-
acters (88 if it includes a 3-digit system identifier). The in-
formation included in a DATA SMDR record includes:
Long Call Indicator
Date
Call Start Time
Duration of Call
Calling Party
Calling Party Disconnect
Data Call Identifier
Data Call Type
Party Which Caused the Disconnect
Call Completion Status
Indication If Call Was Speed Dialed
System Identifier (optional)
Called Party
Called Party Disconnect
External Indicator
Trunk SMDR Indicator
Account Code
I
:
IPage 13 
						

							SECTSBN MITL9109-094-221 -NA
3.05A summary of the fields printed in a DATA SMDR record is
shown in Table 3-l; many of these fields are the same as in a
TRUNK SMDR report.
3.06A description of fields of the DATA SMDR record as listed in
Table 3-1 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, a plus symbol (+) for calls of
30 or more minutes, or a space ( ) for durations less than five minutes.
This is useful when records are to be scanned manually.
Date (mm/dd). The date that the data call was initiated is reported
numerically as a 2-digit month followed by a 2-digit day separated by
a (-) dash. 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 99 hours, 59 minutes, 59 seconds).
Calling Party (ppppp). This is the identity of the party that originated
the call. A 5-digit extension numbering plan is used; the extension
number is a data device (either a data station or a pooled modem)
originating a data call. The pooled modem’s extension number is for an
incoming modem pooling call. Only the last four digits will be used by
SMDR to identify the calling party. It may be a station or an incoming
trunk, as described below:
0Station 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.
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.
Calling Party Disconnect 
-the carat character ( * ) indicates that the
calling party caused the call to be disconnected.
Data Call Indicator 
- (DATA ) indicates a DATA SMDR record.
Type of Data Call 
-field has three possible values; either DTRX, ADL,
or ACD. ACD indicates that a Monitor ACD session originated from
DTRX occurred. This field may be left blank if the data call is an
incoming or internal modem pooling call without DTRX access.
Page 14 
						

							Station Message Detail Recording
Reason For Disconnect -this field reports the reason the data call
was terminated. Table 3-2 gives possible reasons for disconnecting a
data call.
Call Completion Status
- has two values; B (Busy) or E (Error).
The busy flag “B” is set if the called party is busy, and the caller
queues for completion to the called 
dataset. If the caller terminates
while in the queue, the busy flag will be set. If the call is completed
after being queued, the busy flag will not be set.
The error flag “E” is set if the error was “user preventable”. User
preventable errors include:
ldialing the extension of a non-dataset
loriginator’s baud rate not compatible with destination
loriginator, programmed for autobaud, not entering the auto-baud character within 30 seconds
laccessing the wrong Modem Pool
0attempting a call which requires a Pooled Modem, but not
dialing a Modem Pool access code and there is NO default
Modem Pool.
Speed Call Indicator
- flag is set if the data call is dialed via system
abbreviated dial or personal speed call on a 
SUPERSETTM telephone.
Called Party (qqqqq). This is the party to whom the call is directed. It
may be a 5-digit data station number, or a pooled modem number for
outgoing modem pooling calls (the called party may not appear in a
DATA SMDR record which has an error flag set). The format in which
the called party is output is identical to that used for the calling party.
Called Party Disconnect
- the carat character ( A ) indicates that th’ecalled party caused the call to be disconnected.
External Data Call’lndicator 
-“EX” is displayed in this field when the
data call involves a Pooled Modem and a trunk, regardless of the
direction of the call (incoming or outgoing). This indicator is not de-
pendent on the existence of a trunk SMDR record.
lOnly external data calls involving trunks and a Pooled Modem
are flagged; internal data calls using a Pooled Modem are not
indicated in this field.
Trunk SMDR Indicator 
-This field displays an asterisk (*) when there
is a trunk SMDR record associated with this data call. This facilitates
the matching of DATA SMDR records with SMDR records.
Speed Call or Call Forward Flags (S). This field contains an “S” when
the number is speed dialed.
Page 15 
						

							SECTION MITL9109-094-221 -NA
Account Code (aa...a). Account codes are typically used for security
purposes to charge the cost of calls either to internal departmental
cost centers or to project accounts for billing to specific projects. Data
account codes may be optional or a data caller may be forced to enter
an account code when making an internal or an external data call. The
account code may be 
l-12 digits (the default value is six digits).
System Identifier (iii). This optional 3-digit field may contain values
from “000” to “999”. “000” indicates that no identifier has been entered.
TABLE 3-1
SUMMARY OF FIELDS IN A DATA SMDR RECORD
FIELDLong Call
Date
Spacer
Start Time
Spacer
Duration of Call
Spacer
Calling Party
Calling Party Disconnect
Spaces
Data Call Indicator
Spacer
Type of Data Call
Spaces
Reason for Disconnect
Spacer
Call Completion Status
Speed Call Indicator
Called Party
Called Party DisconnectCOLUMNFORMATDEFINITION
1z- = 5 to 9 minutes, 59 seconds
% =10 to 29 minutes, 59 seconds
+ = 30 or more minutes
2-6mm-ddmm= Month dd = Day
78-13hh:mmhh= Hours
mm = Minutes
141.5-22hh:mm:ss hh = Hours
mm= Minutes
ss = Seconds
23
24-28
PPPPPPPPPP= Extension ‘Number
29Indicates that the calling party caused
the disconnect.
30-33
I’34-37DATAFlags a data call
38
39-42XXXXXXXX 
= DTRX or ADL or ACD or blank
(blank only for incoming or internal
modem pooling call)
43-44
45-5814 char’s14 character explanation
59
60
hB = Callee is busy
E 
= Caller error
61SS = Number was speed called
62-66
99944wvwq= Extension NumberA67Indicates that the called party caused
the disconnect.
Page 16 
						

							Station Message Detail Recording
TABLE 3-l (CONT’D)
SUMMARY OF FIELDS IN A DATA SMDR RECORD
FIELD
Spacer
External IndicatorCOLUMNFORMATDEFINITION
68
69-70EXIndicates that this was an external data
call.
Trunk SMDR Indicator
71*
Indicates that there is an associated
SMDR report.
Spacer72
Account Code73-84
aa. . . aa = O-9 space filled; length of 1 -12
digits.
Spacer85
System Identifier (optional)86-88 iii
i= 0 to 9
iii = 000 to 999
000 = “No code Entered”
TABLE 3-2
DATA CALL DISCONNECT REASONS
Reason
ADL DISCONNECT
ANSWER: DTR HI
ANSWER: DTR LO
AT-TN BUT-TON
A-lTN CHARACTER
BREAK DETECTED
BUSIED OUT
BUSYCALL DUR OVFLW
CARD REMOVED
DIALER HANGUP
DISC 
BUT-TONExplanation
ADL disconnect code dialed.
The device is programmed for Auto Answer and has DTR high.
The device is not programmed for Auto Answer and has DTR
low. This may appear on an originator also.
Call/attn button on the dataset or call/attn key on digital
SUPERSET telephone was pressed.
Programmed attention character detected.
Break character detected.
The destination data device is busied out.
The called party is already involved in a call. If the busy indicator
(column 60) does not accompany this reason, then the state of
the device may be transient. Try again. If this reason persists
with no busy indicator then reset the device.
The duration of the Call Timer has overflowed. The call has not
been terminated (the SMDR record has been printed) but this is
to inform the system that there has been a call of long duration
(exceeding the timer limit of 99 hours, 59 minutes, 59 seconds). It
might be advisable to check with the originator.
The digital line card was removed.
DATA originator hangs up the voice line.
Disconnect button on the 
dataset or data disconnect key on
digital 
SUPERSET telephone was pressed.
Page 17 
						

							SECTION MITL9109-094-221 -NA
TABLE 3-2 (CONT’D)
DATA CALL DISCONNECT REASONS_ Reason
DTR DROPPED
HDLC DISC
INACTIVITY
INCOMPATIBLE
INITIAL SETUPExplanation
DTR for one or both parties dropped for longer than the
programmed interval.
Communication has been lost to the 
dataset.Session activity timer expired.
The two data devices are not compatible; one is synchronous,
the other asynchronous.
The call-setup to the data device has failed in the initial stage.
This is an unexpected event and indicates that the PBX and the
dataset disagree as to the state of the device. To recover from
this situation, the 
dataset must be reset.
INTERCONNECTThe two data parties are prevented from being connected by the
interconnection table.
INVALID ACCOUNTThe originator used an invalid account code when making a data
call.
INVALID DEVICEThe Pooled Modem data set is not a 
DATASET 2102 or a
DATASET 2103. The attached device is not a valid dataset;possibly it is a digital 
SUPERSET telephone. If the device is valid,
reset the device.
INVALID NUMBERThe originator of the data call dialed a wrong number OR the
originating data device has an invalid hotline number
programmed.
INVALID POOLThe wrong type of Modem Pool was accessed, or, no modem
pool access code was dialed and there is no default pool.
LINK ABORT 
/ LINK FAILUREAn error has occurred in the data link layer of the datasetcommunication. Repeated occurrences may indicate faulty
hardware, wiring or electrical interference.
MODEM HUNG UPThe Pooled Modem hung up.
NO ACCESSThe user failed to enter a valid access code.
NO ADAPTERThe Pooled Modem is missing its Modem Adapter. This reason
may also appear if the adapter is not a 
MITEL Modem Adapter.
NO ANSWERThe dialed destination has not responded to the programmed
auto-answer stimulus. Check the Data Circuit Descriptor; the
called modem did not respond with answer tone.
NO 
AUTOBAUDThe originator, who is programmed for autobaud, did not enter a
carriage return.
NO CHANNELThere are no available channels. This would indicate a busy
system.
NO JUNCTORThere are no available junctors. This would indicate a busy
system.
Page 18 
						

							Station Message Detail Recording
TABLE 3-2 (CONT’D)DATA CALL DISCONNECT REASONS
Reason
NO SEIZE ACK
ORIGINATE ONLYExplanation
The trunk used in this outgoing data call did not receive a ‘seize
ack’ from the far end telephone office.
The called party has the “Originate Only” Class Of Service
enabled.
PM: DCD LOThe Pooled Modem is programmed to have DCD as
“Communication Established Indicator” and DCD has NOT come
HIGH after 15 seconds from the 
offhook.PM: DSR LOThe Pooled Modem is programmed to have DSR as
“Communication Established indicator” and DSR has NOT come
HIGH after 15 seconds from the 
offhook.PM: NO 
OFFHOOKPM: RI LOThe Pooled Modem has not gone offhook after 10 seconds of
waiting.
Outgoing
- DTR has been raised and the MI/MIC leads have been
toggled with a 2.5 
set ON, 2.5 set OFF cycle.
Incoming
- RI has been detected, DTR has been raised.
The Pooled Modem has had ringing voltage applied to its analog
side for 10 seconds and has not detected RI on the digital side.
Possible faulty RS-232 connection between the modem and the
dataset.
POWERED OFF
RECEIVER FAILSET FAILUREThe dialed destination is not powered up.
At some point in the data call, especially when queuing is
involved, a receiver was not available or did not function as
expected.
The set failed, dropping the call. See Maintenance Logs for
details.
SET POWER UP
SET UNPLUGGED
SETUP FAILUREThe data set went through a power up sequence. This occurs if
there is a power supply problem to the 
dataset.Connection broken or power removed.
The call has failed during setup. The cause is unknown and
probably obscure. In this case it is best that the user try the call
again. If this persists, the data set should be reset. Further
occurrence of this reason code may indicate a faulty data device
or RS-232 connection.
SPEED MISMATCHRanges of baud rates of the two 
datasets are not compatible.
Page 19 
						

							SECTlON MITL9109-094-221 -NA
TABLE 3-2 (CONT’D)
DATA CALL 
DiSCONNECT REASONS
Reason
SYSTEM DISCExplanation
The system has disconnected for one of several reasons, none of
which is a trouble.
The destination is busy and the originator cannot (or did not)
queue.
The connection is not allowed due to invalid tenant
interconnection.
TENANTING
UNDECODABLEThe connection is not allowed due to type of devices involved.
The two data parties are in different tenant groups.
Reason unknown.
JDATA SMDR Call Record Examples
3.07Examples of typical DATA SMDR call records are shown in Table
3-3. The column indication included with each example is not
repeated for each message in a regular printout.
TABLE 3-3
TYPICAL DATA 
SMDR CALL RECORDS (EXCLUDING ACCOUNT CODES AND SYSTEM ID)
DTRX Call From Another Set Which Pressed BREAK Key
012345671234567890123456789012345678901234567890123456789012345678901234567890123456789
03-13 
II:25 00:01:24 1411 -DATA DTRX BREAK DETECTED1410
On March 13th at 
11:25, an originating DTRX call from 1411 was answered by 1410.
Extension 1411 pressed the BREAK key, disconnecting the call.
The call lasted
1 minute 24 seconds.
DTRX Cal I Not Answered
- Te rmi na I Powered Down
03-13 
II:25 00:00:04 1411 -DATA DTRX
On March 13th at 
11:25, Extension 1411 dia
Extension 1411 was queued. Extension 1411
01234
123456789012345678901234567890123456789012567456789012345678901234567890123456789
ANSWER: DTR LO B 1402
ed Extens ion 1402 (which was busy) ;
dropped DTR (termina I powered down).
1Page 20