MDR-2000
V3
User's Reference Manual
Troubleshooting
Chapter 6
TROUBLESHOOTING
The purpose
of
this section
is
to review the various operational characteristics
of
the MDR-2000 to
assist in troubleshooting the more common problems. The MDR-2000 is a comprehensive device
designed for optimal Call Detail Recording storage and pre-processing
of
records. The units have a
proven track record
of
reliable operation but sometimes things do
go
wrong.
Problems are generally in one
of
four functional components; the PBX itself, cables, modems and
transmission equipment or the MDR-2000. The intrinsic diagnostic capabilities
of
the MDR-2000
make diagnosis
of
the problem straightforward.
6.1 Preliminary Considerations
When troubleshooting MDR-2000 problems it
is
important
to
review the nature
of
the device and
its role in the data collection process.
The MDR-2000
is
typically used as a 'slave' device. In this role it performs the following:
• Captures data sent to it from the PBX but does not send any communications to the PBX
• Pre-processes
CDR
data and stores it for later retrieval. Image (or non-CDR data) can be
optionally stored, but no processing is performed.
• Responds to commands from the downstream data collection processor by sending these
preprocessed records.
It
does not initiate communications and only responds when prompted by
specific commands.
The key to understanding the role the MDR-2000 plays is that it does not usually initiate
communications with the outside world (except in its role as an Alarm Annunciator).
Further, he communications ports do not use any flow control or hardware signaling. Therefore
external communications devices such as modems and multiplexors must be configured not
to
expect control signals from the MDR-2000. In addition, these devices must be data transparent.
Modems or multiplexors that respond to '
XON
/OFF' or '
ACK/NAK'
type protocols may
erroneously detect such signals. This
is
because the MDR-2000 uses checksums and byte counts in
6-1
To Next Page
Loading...