Filter
Top Products
ReadiVoice Administration & Maintenance Guide
152 Proprietary & Confidential
12 Answer the phone, listen to the message, and then hang up.
For each call, you hear three numbers indicating the card, span, and
channel being used for the call (or, in an IP system, a single number
indicating the card).
The details of each test call are recorded in the log file, so you need only
note a channel if it has audio problems, such as static.
13 Choose one of these options:
— Continue answering the phone each time it rings, listening to the
message and then hanging up, until the bridge stops calling you.
— To stop the dial-out test process before it completes, type
CTRL + C. This
also stops the updating of the diagnostic log file.
14 View the diagnostic log file (by default,
/rahome/bin/TTU.log
).
A line for each test call shows the card, channel, and span numbers, and
the outcome of the call. For a successful test of channel 13 on span 0, card
3 of the bridge you tested, the log file would contain the line:
3/0/13 SUCCESS
In an IP system, the line for each test call shows the bridge and card
numbers and the outcome of the call. For a successful test of card 0 of
bridge 1, the log file would contain the line:
1/0 SUCCESS
Dial-In Channel Testing
A dial-in channel test script runs automatically when you set the
LOG_CHAN_DEBUG
parameter in the
ive.ini
file to
1
. By default, this parameter
is set to
0
.
Caution!
If you find telephony problems, such as any outcome other than “SUCCESS,” print
the file for your records or save the file under a new name or in a safe location. To
enable Polycom Global Services to help you, be sure have this file available to send
us.
Caution!
Don’t enable dial-in channel testing on a live conferencing bridge or bridges. When
dial-in testing is turned on, callers hear a debug message (stating the card, span,
and channel numbers—card only for IP—on which their call has reached the
bridge) before the standard welcome message.