MDR 2000

[NorstarOption]

How do I check what's the ip address assigned to the cdr box so I can access it?

 

[acewarlock]

The only MDR2000 i've seen are serial, no IP.

 

[Telecomlady]

I agree. The MDR2000 that we had was serial with a direct connect. Is it for MAT?

 

[GR8NORTH]

MDR2000e has a IP network port.

Just telnet to it, login, and ...

You'll have to go in via the serial port. The MDR web site might have a downloadable manual.

 

[aweshucks]

MDR-2000 Intelligent Storage Unit
User’s Reference Manual
(Major Release 3)
The information in this document is subject to change without notice and should not be construed as a
commitment by MDR Switchview Global Networks Inc. MDR Switchview Global Networks Inc.
assumes no responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may be used or copied only in
accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied by
MDR Switchview Global Networks Inc. or its affiliated companies.
The information in this manual reflects version 3.S01.G44 of the MDR-2000 software.
Copyright (c) 1990 - 2001 by MDR Switchview Global Networks Inc.
All rights reserved.
MDR-2000 V3 User’s Reference Manual
FCC Class B Digital Device or Peripheral - User’s Notice
Notice
This equipment has been tested and found to comply with the limits for a Class B digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference in a residential installation. This equipment generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance with the instruction
manual, may cause harmful interference to radio communications. However, there is no
guarantee that interference will not occur in a particular installation. If this equipment does cause
harmful interference to radio or television reception, which can be determined by turning the
equipment off and on, the user is encouraged to try to correct the interference by one or more of
the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
• Consult the dealer or an experienced radio/TV technician for help.
Warning
Changes or modifications not expressly approved by MDR Switchview Global Networks Inc.
could void the user’s authority to operate the equipment.
MDR-2000 V3 User’s Reference Manual
Table of Contents
Table of Contents
Chapter 1 Introduction
Chapter 2 Overview
2.1 Description .............................................................................................................. 2-1
2.2 Feature Cross-Reference ......................................................................................... 2-4
Chapter 3 Data Collection
3.1 CDR Data Collection .............................................................................................. 3-1
3.1.1 Input/Output Records ............................................................................................. 3-1
3.1.2 Data Selection ......................................................................................................... 3-5
3.1.3 Data Translation ..................................................................................................... 3-6
3.2 Alarm Annunciation ................................................................................................ 3-6
3.3 External Alarm Generation ..................................................................................... 3-8
3.4 Internal Alarm Generation ......................................................................................... 3-8
3.5 Modem Setup ........................................................................................................ 3-9
Chapter 4 Communications
4.1 Computer-To-Computer Commands ...................................................................... 4-1
4.2 Protocol .................................................................................................................. 4-5
4.3 Discrete Polling ....................................................................................................... 4-7
4.4 Large Blocksize Polling ............................................................................................ 4-8
4.5 Data Transmission .................................................................................................. 4-9
4.6 LED Indicators ....................................................................................................... 4-9
Chapter 5 Interactive Monitor
5.1 Command Processor ............................................................................................... 5-1
5.2 Command Descriptions ........................................................................................... 5-2
5.2.1 Set Command Details ............................................................................................. 5-9
5.2.2 Show Command Details ....................................................................................... 5-15
5.2.3 Customize Command Details ................................................................................ 5-16
5.2.4 Digits Table Command Details ............................................................................. 5-18
5.2.5 Alarm Table Command Details ............................................................................. 5-19
5.2.6 Test Command Details .......................................................................................... 5-20
5.3 Messages .............................................................................................................. 5-20
MDR-2000 V3 User’s Reference Manual
Table of Contents
Chapter 6 Troubleshooting
6.1 Preliminary Considerations ..................................................................................... 6-1
6.2 Physical Examination .............................................................................................. 6-2
6.3 Interactive Examination .......................................................................................... 6-3
6.4 Reporting A Problem ................................................................................................ 6-7
Chapter 7 Hardware
7.1 Hardware Overview ................................................................................................ 7-1
7.2 Cables ..................................................................................................................... 7-2
Appendix A ASCII Equivalents
Appendix B User Notes
MDR-2000 V3 User’s Reference Manual
Introduction
1-1
Chapter 1
INTRODUCTION
This manual describes the operational characteristics of the MDR-2000 Intelligent Storage Unit. All
aspects of the operational capability of the MDR-2000 are covered including details for unit setup,
operation and trouble shooting.
Generally reference to this manual will only be required when programming applications software to
interface with the MDR-2000. This information is provided in chapter 4. In addition, reference during
field setup may be required to properly adjust the option settings. This information is found in chapters
3, 5, 6 and 7. Chapter 5 provides details on the Interactive Monitor used for remote setup of the unit.
Chapter 6 provides details on troubleshooting and chapter 7 on the cabling conventions.
For information on sizing the MDR-2000 to meet anticipated storage requirements please refer to the
document entitled ‘MDR-2000 Data Collector Capacity Calculations’. Electrical, physical and
environmental specifications are provided on the MDR-2000 Data Collector brochure. Both of these
documents are available from MDR or your MDR Distributor.
MDR-2000 V3 User’s Reference Manual
Overview
2-1
Chapter 2
OVERVIEW
The purpose of this section is to provide a general description of the MDR-2000 Intelligent Storage
Unit. Each of the features discussed in this section will be further described in later sections of the
manual.
2.1 Description
The MDR-2000 is a compact, highly versatile data collection device. It is designed for maintenance
free operation with reliability features to ensure data integrity and low support and service costs.
The MDR-2000 can be installed quickly. It requires a minimum of space and has no environmental
requirements other than those normally found in the office or equipment room.
Once in operation the MDR-2000 will collect call detail record (CDR) data and optionally image data
from the PBX for later transmission and downstream processing. As part of the data collection
process, the MDR-2000 formats the call detail records into an Expanded MDR Standard Record
format. The use of the Expanded MDR Standard Record format means that records collected from
different types of PBXs are presented in a consistent format to simplify downstream processing.
As part of the formatting process, call records can be retained or discarded based on the number of
digits dialed, the duration of the call, and whether it is incoming or internal. This feature facilitates
discarding of incomplete calls and local calls. By varying these parameters fine tuning of the collected
data is made possible. In addition, the MDR-2000 will deduct the duration selected from the time
reported for each call. This feature assists downstream processing accuracy by eliminating circuit
connection and ringing delays.
When collecting maintenance records the MDR-2000 can be set up to report alarms or error conditions.
On these systems the MDR-2000 is used to record this information and optionally alert a
downstream processing facility when preprogrammed alarms occur.
The MDR-2000 is microprocessor based. This approach provides flexibility in keeping the MDR-2000
current with PBX manufacturers’ changing specifications. It also means reliability and maintainability.
The MDR-2000 has diagnostic features to aid in problem determination. As well, keep-alive circuitry
and battery backup are provided to ensure that the MDR-2000 keeps running during power failures.
The MDR-2000 communicates with the PBX via an RS232-C compatible port. Communications with
downstream processing facilities is made possible by using another RS232-C port via direct connection
MDR-2000 V3 User’s Reference Manual
Overview
2-2
or modem. The MDR-2000 can be setup to communicate at speeds up to 19200 Baud, but is limited
by the data capability of the downstream facilities to accept the data at the higher speeds, the modem
equipment and the quality of the transmission lines.
To ensure data integrity, the data transmitted to the downstream processing unit is encapsulated in a
data packet. The packet contains byte count and checksum information to provide error detection
capability. If an error is detected by the software the MDR-2000 is requested to send the packet again.
This feature is important in ensuring the integrity of the downstream report processing.
While the MDR-2000 is transferring data downstream it continues to collect and process information
from the PBX. This facility means that prime-time data collection from the MDR-2000 is practical.
The unique design of the MDR-2000 incorporates the use of hardware and software to isolate internal
data integrity violations. This means that the data stored in the MDR-2000 is interrogated upon
transmission to downstream facilities to ensure that what was originally stored in the MDR-2000’s
large buffer memory is in fact unaltered when selected for transmission.
Commands by the downstream processing unit to the MDR-2000 or by technicians for remote
diagnosis are very simple. Commands exist in two command structures, computer-to-computer and
interactive.
By using groups of computer-to-computer commands the MDR-2000 will perform all of the functions
necessary for automatic data collection. These commands provide the functionality listed below.
Communications Commands:
o Send the current record or block of records to the downstream processing system.
o Advance to the next record or block of records.
o Clear all of the previously transmitted records. This command makes room for new records.
o Reset to the beginning of the buffer. This command helps recover records lost due to downstream
processing failures.
o Doorbell. This command returns a simple ‘Hello’ response to ensure that a connection to the
MDR-2000 has been made.
o Specify which type of records to transmit, CDR or Image records, or both.
MDR-2000 V3 User’s Reference Manual
Overview
2-3
Maintenance/Support Commands:
o Pass data from the PBX to the communications port for dynamic monitoring of PBX activity.
Data is still processed and retained by the MDR-2000.
o Send a maintenance record consisting of pointer values, indicator LED values, serial number, and
memory size over the communications port.
o Send an ASCII test sequence over the communications port.
o Commands to reset the MDR-2000’s PBX port, the entire MDR-2000, or the MDR-2000 buffer
memory.
o Test commands to verify the integrity of stored data and check the RAM memories.
o View the last record rejected by the MDR-2000.
o Send an MDR-2000 identification message indicating the PBX type, MDR-2000 generic, and
software revision and serial number.
o Enter the Interactive Monitor (Described later in this document).
The interactive commands are provided by a software module called the Interactive Monitor. It
provides most of the functionality described above but in a more humanly engineered format. Its
purpose is for operational control of the unit. All options are set by the Interactive Monitor to provide
complete control and configuration of the MDR-2000 remotely.
MDR-2000 V3 User’s Reference Manual
Overview
2-4
2.2 Feature Cross-Reference
The following table is a feature cross-reference for the more popular PBX and keysystems. It specifies
the call record characteristics by PBX. The terms ‘n/a’ or ‘No’ in the table mean that the feature is not
supported by the PBX or that the MDR-2000 does not currently support it (Usually due to a lack of
information about the PBX data format).
There are many PBX and keysystems on the market sold under various brand names and features can
vary by country, supplier and revision. The MDR-2000 is continually being revised and updated as
new PBXs are supported and features of existing PBXs change. If the PBX or keysystem in question
is not on this list, or you have questions about the information in the table, please contact MDR for the
latest available status.
MDR-2000/PBX Feature Cross-Reference
(Part 1 of 2)
PBX Type Digits
Dialed
Account
Code
Digits
Auth.
Code
Digits
Access
Code
Suppr.
Duration
Accuracy
(Secs)
Meter
Pulse
Ring
Time
Amtelco Generic 16 8 8 Yes 6 No No
AT&T Legend/Merlin 18 n/a 16 No 1 No No
AT&T 75 15 5 7 Yes 6 No No
CBX-I/CBX-II See Rolm-8000/Rolm-9000
Citation 28 8 n/a No 1 No No
Dimension FP Series 18 5 7 Yes 6 No No
Ericsson MD110 20 15 6 Yes 6 Yes Yes
Focus II/III 20 15 n/a Yes 1 No No
Fujitsu 9600 25 15 6 Yes 1 Yes No
Fujitsu Starlog 20 15 n/a Yes 1 No No
GTD-1000 20 8 n/a No 1 No No
GTD Omni 20 11 n/a No 60 No No
Hitachi EX-10 15 n/a n/a Yes 6 No No
IDS-128 26 6 n/a No 60 No No
InterTel 32/128 24 8 n/a No 60 No No
iSDX V2.x Series 18 8 n/a Yes 1 Yes Yes
Isotech 36 20 10 n/a No 1 No No
MDR-2000 V3 User’s Reference Manual
Overview
2-5
MDR-2000/PBX Feature Cross-Reference
(Part 2 of 2)
PBX Type Digits
Dialed
Account
Code
Digits
Auth.
Code
Digits
Access
Code
Suppr.
Duration
Accuracy
(Secs)
Meter
Pulse
Ring
Time
ITT 3100L 15 5 7 Yes 6 No No
Iwatsu 26 12 n/a No 60 Yes No
Lexar 18 10 10 Yes 6 No No
Lucent Generic 14 14 6 Yes 1 No No
Meridian 1 Series 28 10 10 No 2 No No
Mitel SX Series 23 12 n/a No 1 Yes Yes
Mercury-1000 16 6 4 Yes 1 No No
Neax-12A 15 5 n/a Yes 6 No No
Neax-2400 24 10 8 Yes 1 No No
Nec Electra 22 14 n/a No 1 No No
Norstar 28 10 n/a No 2 No No
Panasonic Keysystems 36 8 n/a No 1 Yes No
Perception 18 12 n/a Yes 1 No No
Phillips VOX 16 8 6 Yes 1 Yes No
Plessey K1 12 6 n/a No 1 No No
Plessey K2 16 6 n/a Yes 1 No No
Prodigy 21 10 n/a Yes 6 No No
Rockwell Galaxy 16 6 n/a No 1 Yes Yes
Rolm 8000 15 10 n/a Yes 60 No No
Rolm 9000 16 10 12 Yes 6 No No
Siemens Saturn Series 16 11 4 Yes 1 Yes No
Siemens SD192 15 4 n/a No 60 No No
Toshiba Strata Series 28 8 n/a No 1 No No
Telrad 20 10 n/a No 1 No No
Tie 16/48 22 9 n/a No 1 No No
Tie 24/64 19 n/a n/a No 1 No No
Tie Meritor 16 8 n/a No 1 No No
Tie Ultracom 16 8 n/a No 60 No No
Trillium Panther 20 12 n/a No 1 No No
Vantage-48 20 10 n/a No 1 No No
Voldavi Series 22 9 n/a No 60 No No
Win Comm. Generic 18 11 11 No 60 No No
580 DSS 22 7 n/a Yes 1 No No
MDR-2000 V3 User’s Reference Manual
Data Collection
3-1
Chapter 3
DATA COLLECTION
The purpose of this section is to describe the data collection process as well as the contents and format
of the data used by the MDR-2000.
3.1 CDR Data Collection
This section describes the details of call detail record collection on the MDR-2000. It covers the
conversion of PBX CDR records to Expanded MDR Standard Format, the available data selection
options, and the data translation defaults that are used.
Information on the Expanded MDR Standard Format is provided to assist in downstream processing
applications.
All data is collected from the PBXs over a 300 to 19200 Baud, RS232-C compatible port. This is
generally achieved by requesting the PBX supplier to enable the port on the PBX. In general, the PBX
CDR port must be configured for a standalone hardcopy terminal. That is how the MDR-2000 looks
to the PBX.
3.1.1 Input/Output Records
A variety of PBXs are supported by the MDR-2000 and new ones are added to the list as required.
Each individual PBX requires a custom ROM (Read-Only Memory) chip for that PBX generic. The
differences that exist between ROM versions is entirely limited to the translation software. The
translation software is that component of the MDR-2000 that converts PBX specific data into the
Expanded MDR Standard Format CDR records.
Each record sent from the PBX is terminated by, or preceded by, a carriage-return/linefeed pair, and
one or more of the following characters; NUL, DEL, DC1, DC2, or DC3. These special characters are
ignored, the carriage-return is required.
MDR-2000 V3 User’s Reference Manual
Data Collection
3-2
The following information must be output by the PBX in order for it to be a suitable device for MDR-
2000 and downstream processing:
Field Name Description Minimum
Size
Maximum
Size
ORGID The originating trunk/extension. 1 7
TERID The destination trunk/extension. 1 7
STARTIME The time the call began. 4 6
DATE The date of the call. 4 6
DURATION The length of the call. 4 6
METER Meter pulses (where applicable). 0 5
RING Ring time (where applicable). 0 3
DIGITS The actual digits dialed. 0 PBX Max.
ACCOUNT An optional account code. 0 14
AUTHCODE An optional authorization code. 0 10
The time fields are in a format that provides for hours, minutes and seconds. If seconds are not
available then the accuracy of the reported data will be to the minute. The MDR-2000 defaults
unavailable seconds fields to zero.
The date field requires month and day, or the Julian date which is the day of the year. The year field is
not used.
In the digits field there is no absolute minimum. However, if digits dialed are not output then the CDR
information is of limited value in downstream processing applications. The MDR-2000 can be
programmed to accept as few digits as required.
Any records that do not match the format as described in the PBX specific ROM will be discarded.
The MDR-2000 provides no error recovery for corrupt records from the PBX.
The output record from the MDR-2000 is in Expanded MDR Standard Format which is described in
the following table:
MDR-2000 V3 User’s Reference Manual
Data Collection
3-3
Field Name Starting
Position
Length
(Bytes)
Type Comments
Record Type 1 A X or B
Record Number 2 3 9 Modulo 1000
Customer Number 5 2 9 Usually 00
ID Type 7 1 A T, D, A or I
Originating ID 8 7 9
ID Type 15 1 A T, D or A
Terminating ID 16 7 9
Date 23 4 D mmdd
Time 27 4 9 hhmm
Duration 31 6 T hhmmss
Flag Byte 37 1 9 (0 - 7)
Meter Pulse 38 5 9
Digits 43 9 See Notes Below
ID Type: The ID type field indicates the type of originator or terminator of a call. ‘T’ for trunk, ‘D’ for
extension, or ‘A’ for attendant. If the ID type for the Originating ID is an ‘I’ then this record is an
image record and not a CDR record.
Flag: The Flag Byte is PBX specific and is designed to provide additional information about the call
record. It is presented as a single digit from 0 - 7 which is interpreted as a bit pattern. Flag byte
definitions are PBX specific, and as such may change depending on the PBX, the following bit
definitions which have been assigned are; Bit 0 (Hex 1) indicates an expensive route was detected by
the PBX, Bit 1 (Hex 2) indicates the call utilized the Answer Supervision capability, and Bit 2 (Hex 4)
indicates that the call record was a transfer from an original call.
Meter Pulse: The Meter Pulse field will always be zero on systems which do not utilize the Meter
Pulse feature.
Digits Field: The digits field has a variable length limited by the capacity of the PBX digits dialed field.
This field also includes the ring time, account code, authorization code, and calling line identification
fields. These fields are made part of the digits field because of their greatly varying attributes among
different PBX’s. On smaller systems none of them may be found. The following paragraphs describe
each of the digits dialed subfields:
MDR-2000 V3 User’s Reference Manual
Data Collection
3-4
Ring Time: The ring time, if present, will always be the first field in the digits dialed. It can be
detected by the presence of a ‘T’ which is followed by the 3 digit ring time in seconds. If no ‘T’ is
detected as the first character then there is no ring time field. Ring time is always reported if
supported by the PBX.
Account Code: The account code is separated from the digits dialed by an ‘#’. The position of the
account code may vary, and its presence is optional, therefore the downstream processing system must
parse the digits field for the ‘#’ and following digits.
Authorization Code: The authorization code is separated by a ‘A’. The position of the authorization
code may vary, and its presence is optional, therefore the downstream processing system must parse
the digits field for the ‘A’ and following digits.
Calling Line Identification: The calling line identification is denoted by a ‘D’. The position of the
calling line identification may vary, and its presence is optional, therefore the downstream processing
system must parse the digits field for the ‘D’ and following digits.
Fields are defined by their starting position in the record, the length in bytes and the type. Types are
one of the following:
A Alphabetic character (A through Z).
9 Numeric field (digits 0 through 9 and ‘.’).
T Time field in the format ‘hhmmss’.
D Date field in the format ‘ddmm’.
Variable Fields: There is potential for other fields to be included in some models of the MDR-2000
and in data streams used as input to downstream processing. To facilitate these fields the ‘I’ designator
in the Digits Dialed field has been employed.
If an ‘I’ is detected in the Digits Dialed field it will be followed by an indicator from ‘0’ to ‘9’. The
indicator specifies the type and length of the data to follow. Several indicators have been implemented
as of this writing, as follows:
When ‘I0’ is detected in the Digits Dialed field the three digits following it are the Hold Time for the
call. For example, if the string ‘I0002’ is found in the Digits Dialed field then this call has been on hold
for 2 seconds.
When ‘I1’ is detected in the Digits Dialed field the three digits following it are the Extended Duration
Hours digits for calls 100 hours and longer. These three digits concatenated with the two hour digits
MDR-2000 V3 User’s Reference Manual
Data Collection
3-5
on the duration field can be used to construct a duration field in the format of ‘99999:99:99’ for
downstream processing.
‘I9’ is an optional field terminator. ‘Ix’ fields can be terminated based on several criteria. Firstly,
the field may be of a fixed length, such as the ‘I0’ field. Secondly, the field may be at the end of the
Digits Dialed field and therefore is terminated by the end of the record. Thirdly, the field may be
variable length and have to be terminated by the presence of the ‘I9’ designator. In any event, any
parsing routines should always detect ‘I9’ or the end of the record as the end of the current field.
Other Notes: If the record type is ‘X’ then this indicates a normal Expanded MDR Standard Format
record. If the record type is ‘B’ then the MDR-2000 has detected an internal error on transmitting the
record that has resulted in the record’s contents being changed. The record can be discarded by the
host system to avoid processing errors. In addition the MDR-2000 error indicator (LED CR4) is
turned on. The presence of ‘B’ type records is symptomatic of a hardware malfunction in the MDR-
2000.
If the record type is an ‘N’ then this indicates an older MDR Standard Format record which will be
found in major release 1 and major release 2 version units. Please refer to the earlier MDR-2000
Reference Manual for details on this record format and the MDR-2000 capabilities.
3.1.2 Data Selection
As calls are received by the MDR-2000 they are scanned to ensure that they conform to the PBX
specific format. If they do, then they are translated to Expanded MDR Standard Format, compressed
and stored in the buffer storage.
Conformance includes two additional constraints. Firstly, the call duration must exceed the selected
‘Minimum Call Duration’, and secondly the number of digits dialed must exceed the ‘Minimum Digits
Dialed’ value. These values are set using jumpers on the MDR-2000 or by commands to the
Interactive Monitor which are described later in this manual.
An exception to the ‘Minimum Digits Dialed’ constraint are those calls with digits dialed whose
beginning digits match the values set with the ‘DIGITS TABLE’ command in the Interactive Monitor.
These sequences ignore the ‘Minimum Digits Dialed’ constraint.
If records do not conform they are discarded or may be stored in image format if image collection is
enabled (see Interactive Monitor). Records that are discarded because they failed to meet the
minimum constraints but are otherwise in the correct format are not collected by the image collection
when discarded, only records that did not meet the PBX’s CDR format are saved.
MDR-2000 V3 User’s Reference Manual
Data Collection
3-6
3.1.3 Data Translation
The actual process of translating PBX specific records into Expanded MDR Standard Format is
relatively straight forward. Each field of an incoming record is analyzed as necessary to derive the
information for the output record. The translation is dependent on the PBX being supported. Any
fields which are not present, that can be defaulted, are set to specific values.
The customer number is defaulted to ‘00’, the record number is assigned a sequential 3 digit number,
and the auxiliary ID is defaulted to spaces. In addition, incomplete fields, such as a time field with no
seconds, has the seconds field set to ‘00’.
Finally, the originating and terminating ID fields are right justified and zero filled if they are shorter than
the maximum size. The digits dialed/account code field is terminated by a Carriage-Return/Linefeed
pair.
3.2 Alarm Annunciation
When alarms are enabled the Alarm Table (see Interactive Monitor, Set Alarm, Set Primary Phone, Set
Secondary Phone and Alarm Table commands for details) is scanned for each image record that is
processed. When an entry in the table matches the starting characters of the image record then the
repeat count for that entry is decremented. When the repeat count reaches zero it is reset and an alarm
is raised. The MDR-2000 will then use the telephone number stored with the Set Primary Phone and
Set Secondary Phone commands to dial a Hayes compatible modem and then dump an alarm message.
Note that these records are only retained in the MDR-2000’s buffer if image collection is enabled (See
Set Image command).
In order to successfully use this capability there must be a dedicated modem and computer at the
receiving end to accept the alarm message. The MDR-2000 will output the formatted message when
the modem at the receiving end answers the telephone.
The message is output with the standard MDR-2000 protocol layered around the alarm message as
follows:
MDR-2000 V3 User’s Reference Manual
Data Collection
3-7
Field # Example Description
1 X Record type ‘X’ for expanded record.
2 01/19 Date of the alarm taken from the MDR-2000 (mm/dd).
3 12:42 Time of the alarm taken from the MDR-2000 (hh:mm).
4 012345 MDR-2000 serial number.
5 01 Site Number of the MDR-2000 (see Set Site command).
6 REMOTE1 Site Name of the MDR-2000 (see Set Name command). This field is
20 bytes in length, blank filled.
7 ERR009 Alarm code as generated by the PBX. The format is variable
depending on the PBX. The MDR-2000 outputs codes in the form
M2Kxxx: for internally detected alarm conditions.
8 Pwr. Failure Alarm description in freeform as output by the PBX.
The Alarm Code and description fields will contain the exact string that caused the alarm. The Site
Number field is used in cases where the receiving application may wish to poll the MDR-2000. This
enables the application to determine the files in which to store the alarm data.
Note that this record format is compatible with MDR’s Maintenance and Alarm Reporting System
(MARS) which is the downstream processing module used with the MDR-2000 alarm features.
The MDR-2000 follows a specific algorithm in reporting its alarms and the host system (MARS) must
accommodate this algorithm.
When an alarm occurs the MDR-2000 determines if an alarm is already being reported. If there is one
in progress then the second alarm is not reported. The theory is that if one alarm is being reported for
a PBX then successive messages within a short timeframe need not be annunciated. If their recording
is important then image collection must be enabled.
If no alarm reporting is in progress then the MDR-2000 checks the Primary Phone Number field, and if
valid begins the dialing process. When the line is busy or some other error is detected the MDR-2000
will retry autodialing up to the number of retries specified in the ‘Set Retries’ command (default 5). If
the Primary Phone Number field is empty then it assumes a direct connection and simply sends the
alarm record in the format previously listed with the appropriate protocol layer (see the Protocol
section later in this document for details).
When the record has been sent as determined by the Primary Phone Number, it then directs its
attention to the Secondary Phone Number. The MDR-2000 uses the Secondary Phone Number in
MDR-2000 V3 User’s Reference Manual
Data Collection
3-8
exactly the same way as the Primary Phone Number except that if the entry is empty no action is taken.
This is the means to suppress the reporting of an alarm to a secondary destination.
After the record is sent the MDR-2000 waits for an ACK character (06H) to be sent by the host. If no
ACK is sent in approximately 2 seconds the record is retransmitted. Any character other than the ACK
also causes the record to be retransmitted. The retransmission will occur up to 10 times after which
the MDR-2000 will simply disconnect.
3.3 External Alarm Generation
On certain models of the MDR-2000, those with 24 external jumpers labeled ‘A’ through ‘X’,
detection of external events is possible. When power is first applied to the MDR-2000 it retrieves and
stores the status of the 24 jumpers for reference. When the condition of one of the jumpers changes
this generates an alarm.
The alarm is reported with a condition code of ‘M2KEXT:’ followed by the letter corresponding to the
jumper. If multiple jumpers change simultaneously then they will all be reported on the same alarm
message.
These jumpers report a change in the condition of the jumpers, and give no indication of the open or
closed status of the jumper. Therefore it is incumbent on the implementers of the system to ensure that
the initial condition of the jumpers is what is expected as normal. The change in jumper condition must
be held for a least 1/2 second, a feature incorporated to help reduce nuisance alarms and also to help
with the circuit debouncing logic.
In designing circuitry to open or close the jumpers the implementers must be careful not to apply any
voltage or current to the jumpers that may damage the MDR-2000. As a guideline, the circuit must be
equivalent to a dry reed relay contact closure.
3.4 Internal Alarm Generation
The MDR-2000 has the capability of reporting internally generated alarms which result when certain
conditions internal to the unit occur. These messages are reported in the same format as the external
and PBX generated messages described in the previous sections. The following is a description of the
internally generated alarms:
MDR-2000 V3 User’s Reference Manual
Data Collection
3-9
Code Message Description
M2KTHR Storage Threshold Exceeded The threshold set with the Set Threshold
command has been exceeded
M2KIDL PBX Idle Time Threshold Exceeded This alarm indicates that the PBX has not output
any information to the MDR-2000 in the interval
specified with the Set PBX Idle command.
M2KPBD M2K Possible Battery Depletion Indicates that a possible depletion of the internal
backup batteries has been detected (specially
equipped units only).
M2KCCD Contact Closure Detected Indicates that an internal contact closure has been
detected (specially equipped units only).
3.5 Modem Setup
The MDR-2000 is usually not aware of the type of modem that is connected or if in fact it is connected
to a modem or directly to the host computer. When a modem is used it must meet certain criteria in
order for successful operation with the MDR-2000.
The modem must be asynchronous and support the standard ‘AT’ modem command set, which is also
known more commonly as the Hayes command set. The modem must be configured for ‘Full Word’
or ‘Verbal’ responses. These are sometimes referred to as results codes. This is the default setting for
most modems, but can be set by entering the commands ‘ATQ’ or ‘ATQ0’ to enable results codes, and
‘ATV1’ to setup the modem for ‘Full Word’ responses.
Character echo to the ‘AT’ commands must be suppressed. This is done by entering the command
‘ATE’ or ‘ATE0’. The default is ‘ATE1’ which causes the modem to echo characters. As well the
modem must be set to auto-answer mode. This permits the modem to answer the telephone line when
the host computer’s modem is dialing to collect data. The command to enable auto-answer mode is
‘ATS0=1’. The sets the modem to answer the telephone after 1 ring. The default is to disable autoanswer
mode so this command is essential.
These options must be setup before the modem is placed in the field. They are saved by entering the
command ‘AT&W’. Whenever the modem is reset by an ‘ATZ’ command or powered up the settings
stored by the ‘AT&W’ are used.
MDR-2000 V3 User’s Reference Manual
Data Collection
3-10
If your modem has jumper settings make sure that the modem is not set for ‘dumb’ mode operation. If
it is none of these commands will work. If you are unsure of the status of the settings you can restore
the original factory defaults by entering the command ‘AT&F’.
MDR-2000 V3 User’s Reference Manual
Communications
4-1
Chapter 4
COMMUNICATIONS
The purpose of this section is to describe the commands and protocols used to control and
communicate with the MDR-2000. Commands are necessary to operate the MDR-2000, while the
protocols are used to ensure data integrity over transmission lines.
The MDR-2000 supports a two level command structure. The first level, described here, is used
primarily for computer-to-computer communications. The commands are structured to enable the
MDR-2000 to transfer large volumes of call data to a host computer for downstream processing.
The second level of commands is implemented in the Interactive Monitor and these commands are
designed for human interaction. The commands are structured to provide remote operation and
diagnosis of the MDR-2000. The Interactive Monitor is described in Section 5.
4.1 Computer-To-Computer Commands
The MDR-2000 operates over full duplex lines at speeds up to 19200 Baud. This full duplex capability
is essential for remote control of the MDR-2000. Commands to the MDR-2000 are used to specify a
single operation to be performed by the unit.
Commands utilize a very simple protocol when being transmitted to the MDR-2000. Each command is
preceded by a SYN (ASCII 16H, or Control-V) character and terminated by a carriage-return (ASCII
0DH). The commands themselves are all two characters long.
Commands partially entered in error can be eliminated by simply typing the SYN character followed by
the correct command. The normal keyboard editing characters such as Delete or Backspace have no
meaning. The command does not echo on the user’s terminal. This is consistent with the operation
under program control, which is the normal case.
The computer-to-computer commands are as follows:
BE - The ‘BEgin’ command moves the buffer pointers to the beginning of the current data storage
buffer. This command must be used with caution since it may result in duplicate data in the
downstream processing facility. There is no reply from the MDR-2000 to this command.
MDR-2000 V3 User’s Reference Manual
Communications
4-2
CA - The ‘Collect All’ command indicates that both CDR and Image data are to be transmitted
sequentially, as they occur in the buffer, to the data collection software. This is the default mode of
operation. An ‘OK’ message is returned when the command is received and executed properly, and an
‘ERR’ message if SET DESCRETE COLLECTION FUNCTIONS is not enabled. The ‘OK’ and
‘ERR’ messages are encapsulated in the same protocol used for data transmission.
CC - The ‘Collect CDR’ command indicates that only CDR data will be transmitted to the host.
Image data records will be skipped. An ‘OK’ message is returned when the command is received and
executed properly, and an ‘ERR’ message if SET DESCRETE COLLECTION FUNCTIONS is not
enabled. The ‘OK’ and ‘ERR’ messages are encapsulated in the same protocol used for data
transmission.
CI - The ‘Collect Image’ command indicates that only Image data will be transmitted to the host.
CDR data records will be skipped. An ‘OK’ message is returned when the command is received and
executed properly, and an ‘ERR’ message if SET DESCRETE COLLECTION FUNCTIONS is not
enabled. The ‘OK’ and ‘ERR’ messages are encapsulated in the same protocol used for data
transmission.
CL - The ‘CLear’ command causes the erasure of data from the beginning, up to but not including the
current buffer pointer location, in the currently selected data storage buffer. A ‘CLR’ message is
returned when the clear action is complete. The ‘CLR’ message is encapsulated in the same protocol
used for data transmission. This command also causes the ‘ERR’ LED to be reset.
If the SET DESCRETE COLLECTION FUNCTIONS option is selected and ‘CC’ or ‘CI’ is in effect
then this command has additional functions. Under these circumstances it will force a ‘BE’ command
followed by a ‘CA’ command. The result is to move the data collection pointers to the beginning of
the buffer and then advance to the first non-deleted record, either CDR or image type. If there are
none then it simply moves to the end of the buffer which is exactly the same function that it has when
SET DESCRETE COLLECTION FUNCTIONS is disabled.
For example, to collect CDR data followed by image data the host data collection software can send a
‘CC’ command and then collect all of the CDR data. When the ‘CL’ command is issued followed by a
‘CI’ command the MDR-2000 will be positioned so that the host data collection software can now
collect the image data.
CT - This command causes a short diagnostic message to be displayed indicating the hardware
platform for which the microcode resident in the EPROM has been generated. This command is useful
in the manufacturing process to ensure that the correct EPROM has been installed on a particular
platform.
MDR-2000 V3 User’s Reference Manual
Communications
4-3
DB - The ‘Door Bell’ command causes an immediate ‘HE’ response, followed by a Carriage
Return/Linefeed pair, from the MDR-2000. It is used to ensure that the MDR-2000 is active and
waiting for commands. This command also cancels an active ‘DU’ command and issues a ‘CA’
command to cause collection of both CDR and Image data.
DU - The ‘DUmp’ command causes all data received on the PBX port to be immediately output over
the modem port. Data continues to be collected normally. The data dumped over the modem port is
unedited. When the Interactive Monitor is activated this command is canceled. There is no reply from
the MDR-2000 to this command. Note that execution of the ‘IM’, ‘SD’, ‘FD’ or ‘DB’ commands
causes cancellation of the dump.
FD - The ‘Formatted Dump’ command causes the MDR-2000 to output formatted CDR records
automatically over the modem port as they are processed. These records are in exactly the same
format as those output by the ‘XT’ command including the protocol information. This command is
useful for ‘trickle transmit’ applications where the MDR-2000 will be on-line at all times. Note that
execution of the ‘IM’, ‘SD’, ‘DU’ or ‘DB’ commands causes cancellation of the formatted dump.
ID - The ‘IDentification’ command outputs several lines of text containing information about the
MDR-2000 including the PBX generic supported, software revision, serial number, and copyright
notice. No protocol is used with this output.
IM - The ‘Interactive Monitor’ command invokes the Interactive Monitor, if present. When invoked,
an active ‘DU’ command is canceled. Data collection proceeds as usual. Any other computer-tocomputer
command, preceded by the requisite SYN character, will cause the Interactive Monitor to
exit.
MR - The ‘Master Reset’ command is used to reset the entire MDR-2000 system. This command
causes an immediate hardware reset with the loss of all data. There is no reply from the MDR-2000 to
this command.
OK - The ‘OK’ command is used to advance the buffer pointer to the next logical record in the
currently selected data storage buffer. There is no reply from the MDR-2000 to this command. Its
successful reception by the MDR-2000 can be tested by transmitting a data record and comparing it to
the previously transmitted record. If they are the same the ‘OK’ command was not received by the
MDR-2000 correctly.
Note: If the SET DESCRETE COLLECTION FUNCTIONS option is selected and the ‘CI’ or ‘CC’
commands are in effect then the ‘OK’ command is destructive. Any records which are passed over
by the ‘OK’ command are marked as deleted and cannot be recovered by using a ‘BE’ command and
MDR-2000 V3 User’s Reference Manual
Communications
4-4
recollecting. In practice the ‘BE’ command is seldom used for this purpose so that this characteristic
of the ‘OK’ command is of little practical value.
RB - The ‘Repeat Block’ command is used in conjunction with the ‘XB’ command to retransmit a
block of records. Only a single ‘RB’ can be used and it can only be used after an ‘XB’ command. It is
only required if the downstream data collection facility detected an error in a block of records sent
using the ‘XB’ command.
RN - The ‘Reset NVR’ command will force initialization of the non-volatile RAM (NVR) to the
factory settings. There is no reply from the MDR-2000 to this command.
RP - The ‘Reset Port’ command initializes the PBX port, clearing any errors that may have caused the
port to cease operation. There is no reply from the MDR-2000 to this command.
SD - The ‘Stop Dump’ command cancels the DU command. This command is automatically invoked
when the Interactive Monitor is activated. There is no reply from the MDR-2000 to this command.
SM - The ‘Send Maintenance’ command is used to transmit an MDR-2000 maintenance record to the
host system. This record is not the same as a PBX maintenance record; it pertains to the MDR-2000
itself and not the PBX. The record is encapsulated in the same protocol used for data transmission.
TE - The ‘TEst’ command causes a single line of test characters to be dumped over the modem port.
No protocol is used with this output.
VW - The ‘VieW’ command displays the last invalid record received on CDR configurations. If no
invalid records have been received, the word ‘Empty’ will be issued. No protocol is used with this
output.
XB - The ‘Transfer Block’ command send a block of records at the current buffer pointer location in
the currently selected data storage buffer. Each record is individually encapsulated in the protocol
described in the next section. An ‘END’ message is returned when the buffer is empty or the pointers
have been advanced past the last block of records in the buffer. Advancement of the pointers to the
next block of records is automatic. Therefore successive ‘XB’ commands return successive blocks of
records. Use the ‘RB’ command to repeat a block if an error is detected in the transmission of any
record in the block. If insufficient records are stored for a complete block then a partial block will be
sent.
XT - The ‘Transmit’ command sends the record at the current buffer pointer location in the currently
selected data storage buffer. This record is encapsulated in the protocol described in the next section.
MDR-2000 V3 User’s Reference Manual
Communications
4-5
An ‘END’ message is returned when the buffer is empty or the pointers have been advanced past the
last record in the buffer by the ‘OK’ command.
19 - Sets the modem and PBX port baud rates to 19200 temporarily. This command is used for
automated testing of the MDR-2000. The MR command causes them to reset to their previous values.
4.2 Protocol
The MDR-2000 utilizes protocols to ensure the integrity of the data transmitted to the host system.
There is no protocol used between the MDR-2000 and the various PBXs. The following paragraphs
describe how the collection process should be handled by any third-party utility that is designed to
download data from the MDR-2000. The process described is for transferring data a single record at a
time. Refer to the section on ‘Large Blocksize Polling’ for details on downloading multiple records per
transfer request.
The first level of protocol applies to the coordination of communications between the MDR-2000 and
the host system. This protocol is basically summarized by the fact that the MDR-2000 transmits data
only when requested by the host. The MDR-2000 never initiates data transmission. Even when it dials
the host system for alarm conditions the host must initiate the transmission of data.
In some cases proper reception of commands from the host to the MDR-2000 must be inferred. For
example, if the ‘ID’ message is returned, then one can safely infer that the ‘ID’ command was properly
received by the MDR-2000.
A more difficult situation is the ‘OK’ command. To ensure its correct reception the previous record
transmitted as the result of an ‘XT’ command must be compared to the current record transmitted. If
they are different then it is a proper assumption that the ‘OK’ command was properly received and
processed by the MDR-2000.
There are some commands for which proper reception cannot be inferred. These are the ‘XT’ and the
‘CL’ commands. To ensure accurate communications with the MDR-2000 these commands return
values, encapsulated in a data packet.
This second level of protocol, which uses the data packet, applies to the transmission of call records
from the MDR-2000 to the host system only. In addition, the ‘CL’ command responds with a ‘CLR’
message which is also sent as a data packet.
The packet consists of the data message encapsulated in the protocol. The data is preceded by two
SYN (ASCII 16H) characters, an 8-bit byte count, a 3 byte modulo 1000 sequence number, and the
MDR-2000 V3 User’s Reference Manual
Communications
4-6
Customer Number which is usually ‘00’. The data follows the byte count and it is followed by 2 8-bit
characters containing a 16-bit checksum of the data.
The first byte in the checksum is the low order digit and the second byte the high order digit. The
highorder bit (bit 7) of both checksum bytes is always ‘0’. The checksum is an arithmetic sum of the
data portion of the packet. If either byte calculates to a ‘0DH’ then that byte is incremented by ‘1’.
The last byte in the message is always a Carriage-Return which is used as a record terminator in
packet-switched networks.
In the case of blocks of records transmitted by the ‘XB’ command, each record retains the same format
described above. This includes the two SYN characters and the terminating Carriage-Return on each
record in the block. It is the responsibility of the downstream processing facility to process each record
in the block.
All retransmission is handled by the host system, as it is responsible for testing the checksum and,
because the MDR-2000 never initiates communication, it is the host system’s responsibility to handle
error conditions by requesting retransmission.
In the case of CDR data the data collection routine should check the first character for a ‘X’ (Normal
expanded record) or ‘B’ (Bad record) and take appropriate action. When the record is stored, a record
terminator (Carriage-Return/Linefeed) may have to be appended depending on the recording device
and method.
A collection routine can determine if the information from the MDR-2000 is CDR or image data by
examining the ID Type following the Customer Number. If this is an ‘I’ then the remainder of the
record constitutes the image data received from the PBX (or other device).
4.3 Discrete Polling
Under normal circumstances the MDR-2000 collects call detail (CDR) data which is preprocessed and
optionally any non-CDR data which it stores in an unprocessed image format. When polled by a host
system the CDR and image data records are transmitted in the order they arrived from the PBX. The
host system can separate the two formats of data by testing the record type affixed by the MDR-2000
when it processes the data records. This is done automatically by the downstream data collection
modules found in MDR products.
Certain users may find it necessary to collect CDR data at one site, or on one downstream machine,
and image data on another. For these applications descrete polling of CDR or image data has been
MDR-2000 V3 User’s Reference Manual
Communications
4-7
implemented in the MDR-2000. With the descrete polling commands it is possible for polling modules
on host computer systems to collect either CDR or image data and have other processes on another
host computer collect the remaining type of data.
The descrete polling commands are all covered under sections of this manual dealing with the
commands and details on them can be found there. The commands used in discrete polling are SET
DESCRETE COLLECTION FUNCTIONS found in the Interactive Monitor, and the computer-tocomputer
commands; CL, CA, CI, CC, OK, DB and BE.
The process of discrete polling is implemented by the cooperative effects of the MDR-2000 and the
downstream polling module. Firstly, the MDR-2000 must have the descrete polling capability enabled
by using the SET DESCRETE COLLECTION FUNCTIONS command in the Interactive Monitor.
Then when polling is initiated the host collecting CDR data must issue the ‘CC’ command before it
begins collecting. This command indicates that the downstream facility only wishes to receive the
CDR data.
When the end of the data is reached the downstream facility must issue a ‘CL’ command to clear the
buffer. This has the effect of moving the MDR-2000’s pointers back to their values before data
collection began and then advanced to the first image record. When the second downstream process
begins collecting it must issue a ‘CI’ command to indicate that it only requires the image data.
It is noteworthy that the ‘DB’ command used to determine if an MDR-2000 is active always issues an
automatic ‘CA’ command to effectively disable descrete collection. As well the ‘OK’ command that is
used to advance the MDR-2000’s pointers to the next record for collection now skips over any record
of the wrong type, and flags the last transmitted record as deleted. This operation is largely invisible to
the user or programmer interfacing with the MDR-2000. Finally, it should be noted that if descrete
collection is in progress and only one type of record is being collected (say CDR for example) then the
MDR-2000 may become full with image records and deleted CDR records even though the data
collection process reveals that the buffer is empty of records.
Also in this case the residual deleted CDR records will still be reflected in the ‘Number of Records
Stored’ and ‘Records to be Collected’ fields of the SHOW STATUS command in the Interactive
Monitor. Therefore these fields remain accurate indicators of the storage utilized in the MDR-2000
but not necessarily true indicators of how many valid records remain.
MDR-2000 V3 User’s Reference Manual
Communications
4-8
4.4 Large Blocksize Polling
Polling records in blocksizes greater than one can significantly improve data transmission rates at
higher baud rates, but is more prone to errors since the blocks of data are larger. The larger blocks
means that if an error occurs the entire block must be retransmitted. Using this feature is usually not
necessary but has been included with the MDR-2000 for large installations, such as service bureau
operations, where the elapsed time for overnight data collection is sometimes a constraint.
The MDR-2000 must be configured to transmit data in blocksizes greater than 1 record per block.
This is done by using the SET XFER BLOCK command in the Interactive Monitor. Blocksizes from 1
through 255 may be specified.
Two dedicated computer-to-computer commands are used to transmit large blocks of records. These
are the ‘XB’ and ‘RB’ commands which are both described in the section on ‘Computer-to-Computer
Commands’. Using the Transfer Blocksize does not affect the used of the regular computer-tocomputer
commands, ‘XT’ and ‘OK’, used in downloading single record blocks.
The ‘XB’ command is used as a replacement for the ‘XT’ command to transmit a block of records.
Each record in the block has a complete protocol as described in the section ‘Polling’ in this manual.
Successive ‘XB’ command download successive blocks of records, the ‘OK’ command is not used and
there is no replacement for it when working with large blocks.
If an error is detected in any of the records in a block then the entire block must be retransmitted.
Since the MDR-2000 has already indexed to the next block after the completion of the previous ‘XB’
command it is necessary to issue an ‘RB’ to reset the pointers to the previous block. Only one ‘RB’
command can be used, they cannot be stacked to move backwards multiple blocks.
When the end of the recorded data has been reached a partial block may be transmitted. This will be
followed by one more block which contains the ‘END’ record. The ‘CL’ command should then be
used to erase the downloaded data from the MDR-2000 thereby freeing up the storage for new data
from the PBX.
4.5 Data Transmission
The MDR-2000 utilizes asynchronous data transmission techniques. It is programmed for 8 data bits,
no parity, and 1 stop bit. Except for the specific cases described below, only 7 of the 8 data bits are
actually used, the high order bit being removed under software control. Note however that the MDRMDR-
2000 V3 User’s Reference Manual
Communications
4-9
2000 is programmed to receive 8 data bits and therefore any communications equipment interfacing
with the MDR-2000 must be programmed accordingly.
In the situation where parity is forced on the data, and therefore only 7 data bits are possible (as in
some public packet switching services), communications with the MDR-2000 is still possible. This is
accomplished by noting that the MDR-2000 never sends a packet larger than 127 data bytes in any of
its current configurations. This means that the byte count never occupies more than 7 bits. In addition
the two 8-bit checksum bytes (16-bit checksum) can be treated as two 7-bit checksum bytes.
4.6 LED Indicators
To provide immediate diagnostic and operational feedback a series of 8 LED indicators are used by the
MDR-2000. These indicators are designated CR2 thorough CR9 on the circuit boards. Their
meanings are listed on the table below. On units where they are externally visible the external labels are
denoted in the table.
When all of the LEDs are on simultaneously the MDR-2000 is in the initialization sequence. The
troubleshooting section of this manual contains more information on the interpretation of these LED’s.
When CR7 is flashing, but not constantly on, the MDR-2000 has reached its call threshold setting (see
SET THRESHOLD command in Chapter 5). When CR7 is constantly on then the buffer is full and
calls are being discarded.
Mnemonic LED Value Description
MSD CR2 ON Modem port transmitting to host
MRD CR3 ON Host system transmitting to modem port.
ERR CR4 ON MDR-2000 hardware error has occurred.
PBX CR5 ON PBX transmitting to PBX port.
BMT CR6 ON
OFF
MDR-2000 buffer empty.
MDR-2000 buffer not empty, call records are being stored.
BFL CR7 ON
Flashing
OFF
MDR-2000 buffer full, additional call records are being
discarded.
Preset threshold reached, buffer not full.
MDR-2000 buffer not full.
INT CR8 ON MDR-2000 processing a hardware interrupt.
RUN CR9 ON
OFF
MDR-2000 running in non-interrupt mode.
MDR-2000 not operational.
MDR-2000 V3 User’s Reference Manual
Interactive Monitor
5-1
Chapter 5
INTERACTIVE MONITOR
The purpose of this section is to describe the operation of the Interactive Monitor. The Interactive
Monitor provides interactive access to the MDR-2000 hardware for maintenance, diagnostic and
inquiry purposes.
The Interactive Monitor may be viewed conceptually as a distinct software component that probes the
various data areas of the MDR-2000 and provides results or modifies data. It does not affect the data
collection, except that it can modify the operating parameters.
Some of the commands provided by the Interactive Monitor are identical to those provided by the
computer-to-computer commands of the MDR-2000. They are provided again in the Interactive
Monitor for convenience.
To invoke the Interactive Monitor the ‘IM’ command must be issued and the option must be installed
on the MDR-2000. If the option is not installed then the command is ignored. When the Interactive
Monitor is in operation the commands of the standard command processor are not active. If dump
mode (‘DU’ command) is in effect it is canceled.
Data collection is performed while the Interactive Monitor is active except during certain test functions.
When the data collection is disabled the Interactive Monitor will indicate this with a message.
5.1 Command Processor
The Interactive Monitor’s command processor is engineered for human operation as opposed to the
standard MDR-2000 command processor which is engineered for computer-to-computer
communications.
When the Interactive Monitor is invoked, a short signon banner is printed on the terminal. This is
followed by the command processor’s prompt ‘M2K>‘ indicating it is ready to accept commands. The
display appears as follows:
MDR-2000 V3 User’s Reference Manual
Interactive Monitor
5-2
MDR-2000e Interactive Monitor
Copyright (c) 2001 MDR Switchview
M2K>
As commands are typed to the Interactive Monitor they are echoed on the user’s terminal. When a
command, or field, is recognized as unique by the command processor it is automatically carried out on
the user’s terminal. Arguments or options can then be selected. Arguments are terminated by pressing
the <Enter> key. Some command strings must be terminated by pressing the <Enter> key to execute
the command, others execute immediately when recognized.
When a mistake has been made, pressing <Control-C> (Press the <CTRL> key while simultaneously
pressing the character ‘C’) will result in the command line being discarded. The command processor
will print the message ‘Canceled’ on the user’s terminal as an indicator that the command has been
discarded.
Whenever a character is typed that is illegal in the current context, then the character is ignored and the
<Bell> is echoed. The <Bell> is a signal to the user that an invalid character has been entered.
The execution of any command can be interrupted by typing <Control-C> at any time.
5.2 Command Descriptions
The following paragraphs describe the individual commands and their associated options. Generally
each command can have 0, 1 or 2 options. These options may be keywords or arguments.
Keywords are entered and recognized by the command processor as commands. That is, when the
system recognizes what keyword is being entered, the option is completed automatically by the
command processor.
Arguments are one of three types: numeric, ASCII, or MDR BCD.
Numeric arguments fall into 3 classes: addresses, values, or repeat counts. Addresses range from 0 to
FFFFFF hexadecimal, values range from 0 to FF hexadecimal, and repeat counts range from 0 to
65,535 decimal. Unless otherwise noted, omitted numeric arguments default to 0.
ASCII arguments can be any character that the keyboard can generate. Characters that are not
printable are echoed as ‘.’, the period. When an ASCII argument is omitted the default is NULL.
MDR-2000 V3 User’s Reference Manual
Interactive Monitor
5-3
MDR BCD is a special subset of characters used for internal storage of CDR data. MDR BCD
arguments consist of the digits plus the characters ‘D’, ‘A’, ‘T’, ‘#’, and the space.
ADVANCE - This command advances the current record pointer forward one record. If the pointer is
at the end of the buffer, no action is taken.
ALARM TABLE - This command is used to enter and modify the alarm condition table for alarm and
maintenance applications.
BEGIN - This command moves the record pointer to the first logical record. Since the pointer is
moved to the beginning of the buffer the effect is to permit those records to be collected again.
Duplicate records may occur in the downstream processing if this command is used without regard for
data already collected. The ADVANCE command can be used to reduce the data duplication
possibilities.
CLEAR - This command causes the Logical Error Count and the I/O Interrupt Status to be set to
zero. In addition the ERR LED is cleared. This command is not the same as the ‘CL’ command
described in the computer-to-computer communications section.
CUSTOMIZE - This command is used to enter the field settings and PBX customization options
when minor adjustments are required to translate PBX data into Expanded MDR Standard Format.
DIGITS TABLE - This command is used to enter and modify the call exception table for CDR
applications.
DUMP <Addr> <Repeat> - This command prints the contents of memory locations beginning at the
address specified and repeating as indicated. The RAM command is used to select which memory is
accessed, either processor or buffer memory. The MODE command determines the format of the data.
The address is printed in the leftmost column followed by 16 bytes of data.
HELP - This command provides a display of the commands available through the Interactive Monitor.
IDENT - This command prints the MDR-2000 identification message which contains the PBX
generic, revision numbers and copyright notice. This information is extremely useful in isolating data
collection problems. The following is an example of the output:
MDR-2000 Plus
Meridian 1 Generic
Rev. 3.S34.G41
MDR-2000 V3 User’s Reference Manual
Interactive Monitor
5-4
Ser. 003423
Copyright (c) 2001 MDR Switchview
MODE - This command sets the mode for DUMP and PUT command value arguments. It executes
automatically when recognized by the monitor and toggles the mode between hexadecimal, ASCII and
MDR BCD input and output. The default is hexadecimal.
OPEN LINK - This command causes the MDR-2000 to permit two way communications from the
modem port to the PBX port which in effect makes the MDR-2000 act as a direct cable. This allows
the user to interactively communicate with their PBX for maintenance related tasks. The command is
terminated by pressing either <Control-C> or <Control-V>. Data collection and alarm annuciation are
disabled during an Open L