Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide
4-9
CTI OS Developer’s Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted
Release 8.0(1)
Chapter 4 Building Your Application
Using The CTI OS ActiveX Controls
Figure 4-2
Microsoft Visual Basic .NET Screen with the CTI OS ActiveX controls.
On the very left, the Toolbox is visible showing some of the CTI OS ActiveX RCWs icons. On the form,
the AxCallGrid has been dragged and dropped.
the AxCallGrid has been dragged and dropped.
For a complete description of the ActiveX controls see
shows the CTI OS Toolkit Agent Desktop application, which is also included as a sample on
the CTI OS CD.
Figure 4-3
CTI OS Toolkit Agent Desktop (see CD) Built with CTI OS ActiveX Controls
Once all ActiveX controls are placed on the phone, you can create an executable in Visual Basic .NET
via Build->Build Solution or selecting <F7>.
via Build->Build Solution or selecting <F7>.
Adding a Hook for Screenpops
This agent desktop application did not require any Visual Basic .NET coding. A user may choose to add
some custom code to add a hook for screenpops. For example, a user may want to retrieve CallVariables,
which are passed along with certain call events.
some custom code to add a hook for screenpops. For example, a user may want to retrieve CallVariables,
which are passed along with certain call events.
CTI OS SessionResolver
A CTI OS Client application connects to CTI OS with a Session object (see
). Depending on the application, a client can use one or more Session objects. For most agent
desktop applications, however, it is useful to employ only a single Session object.