RoadRunner
U S E R S G U I D E
62
Troubleshooting
s complex as any audio codec may be, when combined into a
complete system of multiple codecs, terminal adapters or
network adaptation electronics and transmission facilities, it’s a
wonder anything works at all.
But what do you do if something doesn’t work? The first instinct may
be to blame what you can see, that is, the
RoadRunner
. Before you kick
the
RoadRunner
, or even kick the cat, you will need to determine just
what part of the complete system is giving you problems. Although
against your first instincts, you really must consider everything in the
entire system, including the wires, the transmission medium, the
terminal adapters or CSU’s, the local and long distance telephone
companies, all the equipment at the other end, and even pilot error.
Before we step through the process of isolating the problem, there are a
few basic procedures to get out of the way. First, whenever
experiencing any problems, you should reboot not only your
RoadRunner
, but the codec at the other end as well. If rebooting does
not clear the problem, try resetting to factory defaults and
reconfiguring. The procedure for resetting factory defaults can be
found on page 60.
Audio Problems
No Audio in Loopback
Since a ‘1’ reset of all factory defaults sets your
RoadRunner
into a
known, working configuration and also puts it into loopback mode,
you should hear your own audio. If you do have audio I/O in
loopback, you can skip to the next section.
If you have not already performed a factory default reset (see page 60),
do so now. After a reset, your
RoadRunner
should be framed, and
since it is in loopback, audio that is present at the input should be
Chapter
7
A