Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide
4-67
CTI OS Developer’s Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted
Release 8.0(1)
Chapter 4 Building Your Application
Deployment of Custom CTI OS Applications
Deploying Applications Using COM (But Not ActiveX Controls)
Custom applications using COM from VB or C++ or any other Com supported development platform,
need the following COM Dynamic Link Libraries.
need the following COM Dynamic Link Libraries.
•
CTIOSClient.dll
When used in a.NET application must include: Cisco.CTIOSCLIENTLib.dll
•
Arguments.dll
When used in a.NET application must include: Cisco.CTIOSARGUMENTSLib.dll
•
CtiosSessionresolver.dll (only if used – see previous discussion)
When used in a.NET application must include: Cisco.CTIOSSESSIONRESOLVERLib.dll
•
ATL80.dll (only if not already available on target system)
•
If the client application will use silent monitoring in monitoring mode, ccnsmt.dll is needed. If the
client application will use silent monitoring in monitored mode, wpcap.dll is also a dependency.
client application will use silent monitoring in monitored mode, wpcap.dll is also a dependency.
The Dll files need to be copied and registered on the target system. Registration is done by using the
Windows utility regsvr32.exe providing the dll name (i.e., regsvr32 ctiosclient.dll).
Windows utility regsvr32.exe providing the dll name (i.e., regsvr32 ctiosclient.dll).
ATL80.dll is a Microsoft Dynamic Link Library implementing the Active Template Library used by CTI
OS. It will usually be available on most Windows client systems in a windows system directory (e.g.
\winnt\syste32 on Windows 2000). Since CTI OS depends on this DLL, it needs to be copied and
registered if it is not already available at the target system.
OS. It will usually be available on most Windows client systems in a windows system directory (e.g.
\winnt\syste32 on Windows 2000). Since CTI OS depends on this DLL, it needs to be copied and
registered if it is not already available at the target system.
Deploying Applications using C++ CIL
Custom C++ applications link to the static CTI OS libraries. With your custom application, you should
also distribute ctiostracetext.exe. For the tracing component to work, you need to register it on the system
where your application will run. To register the trace tool run ctiostracetext /RegServer. Besides
ctiostracetex.exe, there is no need to ship additional components.
also distribute ctiostracetext.exe. For the tracing component to work, you need to register it on the system
where your application will run. To register the trace tool run ctiostracetext /RegServer. Besides
ctiostracetex.exe, there is no need to ship additional components.
SupervisorOnlyCtl.dll
ATL80.dll, ctiosclient.dll, arguments.dll,
buttoncontrol.dll, MSVCP80.dll,
MSVCR80.dll
buttoncontrol.dll, MSVCP80.dll,
MSVCR80.dll
Note
When used in a.NET application must
include:
AxInterop.SupervisorOnlyCtl.dll
Interop.SupervisorOnlyCtl.dll
include:
AxInterop.SupervisorOnlyCtl.dll
Interop.SupervisorOnlyCtl.dll
transferctl.dll
ATL80.dll, ctiosclient.dll, arguments.dll,
buttoncontrol.dll, cticommondlgs.dll,
MSVCP80.dll, MSVCR80.dll
buttoncontrol.dll, cticommondlgs.dll,
MSVCP80.dll, MSVCR80.dll
Note
When used in a.NET application must
include:
AxInterop.TransferCtl.dll
Interop.TransferCtl.dll
include:
AxInterop.TransferCtl.dll
Interop.TransferCtl.dll
Table 4-4
Dependencies of CTI OS ActiveX Controls (continued)
DLL File
Dependencies