Cisco Cisco Computer Telephony Integration OS 8.5 Guia De Resolução De Problemas

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. 

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.

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.

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. 

Try to ping the IP addresses corresponding to the connect machine names 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.

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.

When installing the CTI OS server, the system administrator must enter a Peripheral ID and Peripheral 
Type corresponding to the target peripheral. The server uses this information to determine which switch 
behavior to emulate. If the wrong Peripheral ID or Peripheral Type is entered during install, CTI OS may 
attempt to emulate the incorrect switch type or may emulate a generic switch type. This will result in 
incorrect button enablement on the client application. Since the client application randomly selects a 
configuration server each time the client application starts, symptoms of this problem may be sporadic 
if connection profile information is not consistent between configuration servers. Perform the following 
checks to determine where the problem lies:

Note the name of the server with which the client application connected. This information is 
contained in the OnConnection event and is displayed on the status bar control. 

Go to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\

 

Cisco Systems, Inc.\CTIOS\ CTIOS_<InstanceName>\ ctios1\Server\Peripherals on the server with 
which the client application is connected. 

Under this key there are subkeys. Each subkey represents a peripheral with which CTI OS is 
configured to communicate. Find the peripheral to which you are attempting to login. 

Open the corresponding subkey and modify the values of peripheralID and peripheralType so that 
they are correct. The Peripheral ID can be found in the ICM configuration; a list of supported 
Peripheral Types appears in Appendix B.

Restart the CTI OS server.

Restart the client application.

Try to login again.