Cisco Cisco Computer Telephony Integration Option 9.0 Troubleshooting Guide
2-5
Cisco ICM Software CTI OS Troubleshooting Guide Release 6.0(0)
Chapter 2 Resolutions to Common Problems
Incorrect Configuration of the Peripheral ID in the Connection Profile
•
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.
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\ <CTIOSInstanceName>\ <CTIOSServerName>\
Server\Peripherals on the server with which the client application is
connected.
Systems, Inc.\CTIOS\ <CTIOSInstanceName>\ <CTIOSServerName>\
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.
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.
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.
Incorrect Configuration of the Peripheral ID in the
Connection Profile
Connection Profile
When the client attempts to login using a specific connection profile, the client
application associates itself with the Peripheral ID contained in the connection
profile. The client application then waits for CTI OS server to signal that the
peripheral associated with that Peripheral ID is online before it attempts to login
to that peripheral. If the connection profile contains the incorrect Peripheral ID,
the client application may receive this notification prematurely or not at all. In the
former case the login will fail with no indication to the user. In the latter case, the
user will be informed that the system is offline and that the login attempt will be
queued until the system comes online. 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. To modify the Peripheral ID in the connection
profile:
application associates itself with the Peripheral ID contained in the connection
profile. The client application then waits for CTI OS server to signal that the
peripheral associated with that Peripheral ID is online before it attempts to login
to that peripheral. If the connection profile contains the incorrect Peripheral ID,
the client application may receive this notification prematurely or not at all. In the
former case the login will fail with no indication to the user. In the latter case, the
user will be informed that the system is offline and that the login attempt will be
queued until the system comes online. 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. To modify the Peripheral ID in the connection
profile: