Cisco Cisco Computer Telephony Integration Option 9.0 Developer's Guide
4-3
Cisco ICM Software CTI OS Developer’s Guide Release 6.0(0)
Chapter 4 Building Your Application
Integrating your Application with CTI OS via the CIL
applications with a specific stopping point, determine what kind of clean up
needs to be done when the application closes (e.g. disconnect from server,
release resources).
needs to be done when the application closes (e.g. disconnect from server,
release resources).
What Language and Interface to Use
The CTI OS Client Interface Library API comes in programming languages, each
with benefits and costs. The choice of interface is important to direct you through
this developer’s guide, since this guide addresses the CIL API for the C++ and
COM programming environments.
with benefits and costs. The choice of interface is important to direct you through
this developer’s guide, since this guide addresses the CIL API for the C++ and
COM programming environments.
The main decision point in choosing which API to use will depend on your
workstation operating system, your existing applications, and the language skills
of your developers.
workstation operating system, your existing applications, and the language skills
of your developers.
•
ActiveX Controls. The CTI OS ActiveX controls are the appropriate choice
for creating a rapid “drag-and-drop” integration of CTI and third-party call
control with an existing desktop application. The CTI OS ActiveX controls
are appropriate choice for developing a CTI integration with any fully
ActiveX-compliant container, such as Microsoft Visual Basic, Microsoft
Visual C++, or any other container that fully supports ActiveX features (e.g.
Powerbuilder, Delphi, and many third-party CRM packages). The ActiveX
controls will be the easiest to implement in graphical environments, and will
help achieve the fastest integrations by providing a complete user interface.
All CTI OS ActiveX components are distributed via dynamic link library files
(.dll), which only have to be registered once to work on any Microsoft
Windows platform. These components are not appropriate for non-Windows
environments.
for creating a rapid “drag-and-drop” integration of CTI and third-party call
control with an existing desktop application. The CTI OS ActiveX controls
are appropriate choice for developing a CTI integration with any fully
ActiveX-compliant container, such as Microsoft Visual Basic, Microsoft
Visual C++, or any other container that fully supports ActiveX features (e.g.
Powerbuilder, Delphi, and many third-party CRM packages). The ActiveX
controls will be the easiest to implement in graphical environments, and will
help achieve the fastest integrations by providing a complete user interface.
All CTI OS ActiveX components are distributed via dynamic link library files
(.dll), which only have to be registered once to work on any Microsoft
Windows platform. These components are not appropriate for non-Windows
environments.
•
COM. The CTI OS Client Interface Library for COM (Microsoft’s
Component Object Model) is the appropriate choice for developing a CTI
integration with any COM-compliant container, such as Microsoft Visual
Basic, Microsoft Visual C++, or any other container that fully supports COM
features, such as Microsoft Internet Explorer or Visual Basic for Applications
scripting languages. The COM CIL will be the easiest to implement in
scripting environments, and will help achieve the fastest integrations
requiring a custom or non-graphical user interface. All CTI OS components
are distributed via dynamic link library files (.dll), which only have to be
registered once to work on any Microsoft Windows platform. These
components are not appropriate for non-Windows environments.
Component Object Model) is the appropriate choice for developing a CTI
integration with any COM-compliant container, such as Microsoft Visual
Basic, Microsoft Visual C++, or any other container that fully supports COM
features, such as Microsoft Internet Explorer or Visual Basic for Applications
scripting languages. The COM CIL will be the easiest to implement in
scripting environments, and will help achieve the fastest integrations
requiring a custom or non-graphical user interface. All CTI OS components
are distributed via dynamic link library files (.dll), which only have to be
registered once to work on any Microsoft Windows platform. These
components are not appropriate for non-Windows environments.