Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide
4-73
Cisco ICM Software CTI OS Developer’s Guide Release 6.0(0)
Chapter 4 Building Your Application
Deployment of Custom CTI OS Applications
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.
development platform, need the following COM Dynamic Link Libraries.
•
CTIOSClient.dll
•
Arguments.dll
•
CtiosSessionresolver.dll (only if used – see previous discussion)
•
ATL.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.
ccnsmt.dll is needed. If the 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).
is done by using the Windows utility regsvr32.exe providing the dll name (i.e.,
regsvr32 ctiosclient.dll).
ATL.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.
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.
Deployment of C++ Applications
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.
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.