MDR MDR-2000 - Page 62

MDR-2000
V3
User's Reference Manual
Troubleshooting
MDR
-
2000
Pl
us
Me
ridi
a n 1 Gene
ric
Rev
. 3
.S
34 . G41
Ser
.
003423
Copyright
(c)
1999
MOR
Technologies
Inc
.
The revision level consists of three parts, the ma
jor
revision number, specific edit lev
el
and general
edit leve
l.
By comparing these edit levels of the installed MDR-2000 to those of the latest revisions
a
va
ilable from
MDR
Technologies it can be quickly ascertained as to whether the problems being
encountered are due to the missing edits.
If
so then a new ROM must be installed with the latest
revision
s.
Use the Status command to determine
if
any records are stored in the unit, the communications port
settings and the data collection/filtering settings. An example
of
the Status command output is
shown below:
Date/Time
(mm/dd hh:mm) :
01/01
00 : 01
Option
Settings:
NLN
Number
of
Records
Stored
: 0
Records
to
be
Collected
: 0
Port
Config
(PBX/Modem) :
1200
- 8-
N/
1200
- 8- N Minimum
Duration:
0
Incoming
Calls
:
Yes
Minimum
Digits
: 0
CDR
Collection:
Yes
Meter
Pulse
Detection:
No
Tandem
Conversion
Option:
No
Last
Scan
Error
Position
: 0
Port
Rese
t
Timer
: 15
Logical
Error
Count:
0
Buffer
Memory
Size:
128K
Site
Name:
Primary
Alarm
Phone
No:
Secondary
Alarm
Phone
No
:
Image
Collection
:
No
Multi
Tenant
Detection
:
No
Internal
Calls
(Ext
-
>Ext)
:
No
Alarm
Threshold
: 0
Idle
PBX
Alarm
Threshold:
0
Alarm
Enabled:
No
I/0
Interrupt
Status
:
Clear
Site
# :
The 'Number
of
Records Stored' indicates the total number
ofrecords
retained by the MDR-2000.
The 'Records to be Collected' field specifies
how
may
of
those records have been collected.
Typically when data collection is completed both values will be zero and begin incrementing as
records are received from the PBX.
If
the values are different it likely indicates that the
downstream data collection process was aborted for some reason. The computer-to-computer
command 'CL' will erase the collected records so that both values will be the same.
The Logical Error Count setting indicates that memory parity errors were detected when certain
records were prepared for transmission to the downstream data collection system. This is not a
transmission problem but rather an MDR-2000 memory problem.
6-4
I