Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide
1-8
CTI OS Developer’s Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.0(0)
Chapter 1 Introduction
Overview of CTI OS
provides out-of-the-box failover recovery: upon recovery from a failure, the
CIL will automatically reconnect to another CTI OS (or reconnect to the same
CTI OS after restart), reestablish the session, and recover all objects for that
session.
CIL will automatically reconnect to another CTI OS (or reconnect to the same
CTI OS after restart), reestablish the session, and recover all objects for that
session.
•
All parameters are key-value pairs. The CTI OS CIL provides helper
classes to treat all event and request parameters as simply a set of key-value
pairs. All properties on the CTI OS objects are accessible by name via a
simple Value = GetValue(“key”) mechanism. Client programmers can add
values of any type to the CTI OS Arguments structure, using the enumerated
CTI OS keywords, or their own string keywords (for example,
AddItem(“DialedNumber”, “1234”)). This provides for future enhancement
of the interface without requiring any changes to the method signatures.
classes to treat all event and request parameters as simply a set of key-value
pairs. All properties on the CTI OS objects are accessible by name via a
simple Value = GetValue(“key”) mechanism. Client programmers can add
values of any type to the CTI OS Arguments structure, using the enumerated
CTI OS keywords, or their own string keywords (for example,
AddItem(“DialedNumber”, “1234”)). This provides for future enhancement
of the interface without requiring any changes to the method signatures.
•
Simple event subscription model. The CTI OS CIL implements a
publisher-subscriber design pattern to enable easy subscription to event
interfaces. Programmers can subscribe to the appropriate event interface that
suits their needs, or use the IAllInOne interface to subscribe for all events.
C++ and COM contain subclassable event adapter classes. These classes
enable programmers to subscribe to event interfaces; they only add minimal
custom code for the events they use and no code at all for events they do not
use.
publisher-subscriber design pattern to enable easy subscription to event
interfaces. Programmers can subscribe to the appropriate event interface that
suits their needs, or use the IAllInOne interface to subscribe for all events.
C++ and COM contain subclassable event adapter classes. These classes
enable programmers to subscribe to event interfaces; they only add minimal
custom code for the events they use and no code at all for events they do not
use.
Illustrative Code Fragments
Throughout this manual, illustrative code fragments are provided both to clarify
usage and as examples. These fragments are written in several languages,
including Java , C++ and Visual Basic (VB). Although .NET (and therefore VB
.NET) are supported, note that the VB code fragments are written using VB 6
syntax.
usage and as examples. These fragments are written in several languages,
including Java , C++ and Visual Basic (VB). Although .NET (and therefore VB
.NET) are supported, note that the VB code fragments are written using VB 6
syntax.