Chapter 8 Testing and Troubleshooting the Cisco ATA 186
Symptoms and Actions
8-4
Cisco ATA 186 Installation and Configuration Guide
OL-1267-01
Symptom The Cisco ATA 186 does not appear to be provisioned by the TFTP
server.
Possible Cause The TftpURL is not correctly set to the URL or IP address of
the TFTP server that is hosting the profile for the Cisco ATA 186.
Action If you are using DHCP to supply the TFTP server IP address, make sure
that TftpURL is set to 0. Make sure that DNS1IP and DNS2IP are properly set
to resolve the TftpURL supplied by DHCP. (If the TftpURL supplied by
DHCP is an IP string, the Cisco ATA 186 does not need to consult with DNS.)
If you want to use DHCP server-assigned DNSes for resolving DNS requests,
make sure that DNS1IP and DNS2IP are set to 0.
Symptom The Cisco ATA 186 contacts the TFTP server more often than specified
in CFGINTERVAL.
Possible Cause The TOCONFIG parameter is not set to 0.
Action The TOCONFIG parameter set to 1 by default. This means that the
Cisco ATA 186 does not yet have a good operating profile. Once the
Cisco ATA 186 has a good operating profile, set the parameter to 0. This is
best done by including this parameter in the profile downloaded from the
TFTP server. If TOCONFIG is not set to 1, the Cisco ATA 186 tries to contact
the TFTP server more often than necessary.
Symptom There is no dial tone.
Possible Cause The Cisco ATA 186 has not successfully registered to the
gatekeeper or Proxy (GKORPROXY). If no GKORPROXY is specified, then
the Cisco ATA 186 is operating in pure IP to IP mode, and the Cisco ATA 186
can be addressed only by IP address.
Action Make sure that UID0 and UID1 are set to the applicable values
(telephone numbers) to get a dial tone on each line.
