Cisco Cisco Computer Telephony Integration Option 9.0 Guida Alla Risoluzione Dei Problemi
Chapter 2 Resolutions to Common Problems
Incorrect or Unreachable CTI OS Server in Connection Profile
2-4
CTI OS Troubleshooting Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.1(1)
–
Check the values of CtiosA, CtiosB, PortA, and PortB. (For clarity, we
will call these machines the "connect machines".) Are these CTI OS
Server names (or addresses) and port numbers correct? If they are
incorrect, enter the correct server names, restart the configuration
machines, restart the client application, and try again.
will call these machines the "connect machines".) Are these CTI OS
Server names (or addresses) and port numbers correct? If they are
incorrect, enter the correct server names, restart the configuration
machines, restart the client application, and try again.
•
If the names (or addresses) of the connect machines are correct, the problem
may be caused by a loss of network connectivity or an inability to resolve the
CTI OS Server name.
may be caused by a loss of network connectivity or an inability to resolve the
CTI OS Server name.
–
From the client application machine, open a console window and attempt
to ping the connect machines. If the system is configured correctly, the
ping succeeds for at least one of the connect machines listed in the
registry.
to ping the connect machines. If the system is configured correctly, the
ping succeeds for at least one of the connect machines listed in the
registry.
–
If the ping succeeded then the problem may be that the CTI OS server is
not running on either of the connect machines. Start the CTI OS server
on those machines and restart the client application.
not running on either of the connect machines. Start the CTI OS server
on those machines and restart the client application.
•
If the ping fails for both connect machines and the connect machine entries
in the registry are not TCP addresses, the problem may be an inability to
resolve the connect machine name into an IP address.
in the registry are not TCP addresses, the problem may be an inability to
resolve the connect machine name into an IP address.
–
Try to ping the IP addresses corresponding to the connect machine names
configured in the registry.
configured in the registry.
–
If the ping succeeds, your DNS server may be down or the "hosts" file on
the client machine may map the hostname to an incorrect address.
Replace the connect machine names in the registry with the associated IP
addresses, restart the download machines, and restart the client
application.
the client machine may map the hostname to an incorrect address.
Replace the connect machine names in the registry with the associated IP
addresses, restart the download machines, and restart the client
application.
•
If pinging the IP address fails, then either the IP address is incorrect or the
network connection between the client application and connected machine is
down. Your TCP/IP network administrator should be able to help resolve this
issue.
network connection between the client application and connected machine is
down. Your TCP/IP network administrator should be able to help resolve this
issue.