Cisco Cisco Computer Telephony Integration Option 10.5 Troubleshooting Guide
1-3
CTI OS Troubleshooting Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.1(1)
Chapter 1 Problems and Symptoms
CTI OS Server Problems
For example, on IPCC there can be multiple PIMs (peripheral interfaces)
running on one PG at the same time. In this case, CTI OS will be able to access
all of these co-located PIMs via one CTI Server.
running on one PG at the same time. In this case, CTI OS will be able to access
all of these co-located PIMs via one CTI Server.
To be able to login a CTI OS softphone to a peripheral, the CTI OS Server
must be configured with the PeripheralID (from ICM configuration) and
PeripheralType (see
must be configured with the PeripheralID (from ICM configuration) and
PeripheralType (see
for a list of supported
Peripheral Types) of each Peripheral on the PG. This information is stored in
the registry on the CTI OS Server computer under
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems,
Inc.\CTIOS\CTIOS_<InstanceName>\ctios1\Server\Peripherals. This
registry entry is a table, where each entry is named by a Logical Name (e.g.
IPCC ACD1). Each entry contains the PeripheralID and PeripheralType for
the peripheral specified by the Logical Name.
the registry on the CTI OS Server computer under
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems,
Inc.\CTIOS\CTIOS_<InstanceName>\ctios1\Server\Peripherals. This
registry entry is a table, where each entry is named by a Logical Name (e.g.
IPCC ACD1). Each entry contains the PeripheralID and PeripheralType for
the peripheral specified by the Logical Name.
If you are using the out-of-box softphone or controls, you also need a valid
connection profile for each peripheral.
connection profile for each peripheral.
Refer to the CTI OS System Manager's Guide for Cisco ICM/IPCC Enterprise
& Hosted Editions for a complete explanation of configuring peripherals and
connection profiles in the CTI OS Server.
& Hosted Editions for a complete explanation of configuring peripherals and
connection profiles in the CTI OS Server.
Symptom
Secure CTI OS server can’t connect to a peer CTI OS server
Possible Cause
This symptom may have multiple causes:
–
Make sure that security is enabled in the peer CTI OS server. If security
is On, then SecurityEnabled registry value is 1, otherwise it is 0. This
registry value exists under
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems,
Inc.\Ctios\CTIOS_<customer-instance>\CTIOS1\server\security
is On, then SecurityEnabled registry value is 1, otherwise it is 0. This
registry value exists under
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems,
Inc.\Ctios\CTIOS_<customer-instance>\CTIOS1\server\security
–
Make sure that the certificates on both servers are configure correctly and
that are signed by the same certificate authority (CA). Refer to the CTI
OS system manager guide for CTI OS Security configuration.
that are signed by the same certificate authority (CA). Refer to the CTI
OS system manager guide for CTI OS Security configuration.