Information Technology Reference
In-Depth Information
Table 17-8 shows chat script failures and suggested actions.
Table17-8
Chat Script Failure
Output from debug chat Shows:
Suggested Action
No matching chat script found
for [number]
A chat script has not been configured. Add one.
Chat script dialout finished,
status = Connection timed out;
remote host not responding
The modem is not responding to the chat script.
Verify communication with the modem (see Table
16-2 in Chapter 16).
Timeout expecting: CONNECT
Possibility 1
: The local modem is not actually
placing the call. Verify that the modem can place
a call by using reverse Telnet to the modem and
manually initiating a dial.
Possibility 2
: The remote modem is not
answering. Test this by dialing the remote modem
with an ordinary POTS telephone.
Timeout expecting: CONNECT
(continued)
Possibility 3
: The number being dialed is
incorrect. Verify the number by dialing it
manually, and correct the configuration, if
necessary.
Possibility 4
: The modem trainup is taking too
long or the TIMEOUT value is too low. If the
local modem is external, turn up the modem
speaker volume and listen to the trainup tones. If
the trainup is abruptly cut off, try increasing the
TIMEOUT value in the
chat-script
command. If
the TIMEOUT is already 60 seconds or more, see
the section “Modem Trainup,” earlier in this
chapter.
ISDN Outbound Calling
The first thing to check at the first suspicion of an ISDN failure, either on a BRI or a PRI, is the output
from
show isdn status
. The key things to note are that Layer 1 should be Active and Layer 2 should be
in a state of MULTIPLE_FRAME_ESTABLISHED. See the section “Interpreting
show isdn status
Output,” in Chapter 16, for information on reading this output and for corrective measures.
