Cisco Cisco Computer Telephony Integration Option 8.5 Guía Para Resolver Problemas
C-3
CTI OS Troubleshooting Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.0(0)
Appendix C CTI OS FAQs
functionality for IPCC includes monitoring and controlling agent states of
monitored agents (logout, make ready), as well as barge-in and intercept
functions.
monitored agents (logout, make ready), as well as barge-in and intercept
functions.
The CTI Toolkit Agent Desktop and CTI Toolkit IPCC Supervisor Desktop are
built upon the Client Interface Library (CIL). Developers can write custom
applications using the published interfaces of CIL. The CIL is available in C++,
COM (called CTIOSClient), .NET and Java, and as Active-X controls.
built upon the Client Interface Library (CIL). Developers can write custom
applications using the published interfaces of CIL. The CIL is available in C++,
COM (called CTIOSClient), .NET and Java, and as Active-X controls.
CTI OS supports a centralized configuration mechanism. Most parameters can be
configured via the system registry on CTI OS server machine. The configuration
settings will be downloaded by the CTI Toolkit application (e.g., the Agent
Desktop), when it connects to CTI OS server and requests them.
configured via the system registry on CTI OS server machine. The configuration
settings will be downloaded by the CTI Toolkit application (e.g., the Agent
Desktop), when it connects to CTI OS server and requests them.
CTI OS will typically be installed in a duplex mode, with two CTI OS servers
running in parallel. CTI OS desktop application will randomly connect to either
server and automatically fail over to the other server if the connection to their
original CTI OS server fails. CTI OS can also run in a simplex mode with all
clients connecting to one server (although the duplex mode is preferred because
it supports fault tolerance).
running in parallel. CTI OS desktop application will randomly connect to either
server and automatically fail over to the other server if the connection to their
original CTI OS server fails. CTI OS can also run in a simplex mode with all
clients connecting to one server (although the duplex mode is preferred because
it supports fault tolerance).
Q.
Which switches are supported by CTI OS? What are PeripheralTypes?
A.
CTI OS provides a switch-independent user interface via its softphone
application. To accomplish this, some parts of the CTI OS Server must be
specialized to support each switch (also referred to as Peripherals or ACDs).
specialized to support each switch (also referred to as Peripherals or ACDs).
To support a switch, the CTI OS system must be configured with the PeripheralID
and PeripheralType of each switch. PeripheralIDs are deployment-specific, and
can be found in the ICM configuration.
and PeripheralType of each switch. PeripheralIDs are deployment-specific, and
can be found in the ICM configuration.
shows switches and their corresponding PeripheralTypes that are
supported in CTI OS Release 7.0(0).
Table C-1
Supported Switches and PeripheralType Values
Peripheral Vendor (Name)
Peripheral Type Value
Cisco IPCC System
23
Cisco IPCC
17
Cisco IPCC Hosted Edition
17