Cisco Cisco Computer Telephony Integration OS 8.5 Developer's Guide

2-7

CTI OS Developer’s Guide for Cisco Unified Contact Center Enterprise

Release 8.5(3)

Chapter 2 CTI OS Client Interface Library Architecture

CIL Object Model

Methods that Call AddRef()

The following tables detail the various methods that call AddRef(). To prevent memory leaks, C++
and COM application developers that call these methods in their applications must be aware of the
impact of these methods on the reference count and must appropriately release the reference when no
longer using the object:

Table 2-1

SessionLib (C++)

Object Name

Method Name

Explanation

CAgent

GetSkillGroups(),

GetMonitoredCall()

The client application must call
Release() on the returned object
when the object is no longer
needed.

CILRefArg

CreateInstance(),

GetValue()

The client application must call
Release() on the returned object
when the object is no longer
needed.

CILRefArg

SetValue(),

operator=

These methods increment the
reference count on the passed in
object. When the CilRefArg is
deleted the reference count of the
enclosed object is decremented.

CCtiOsSession

SetCurrentCall()

This method increments the
reference count on the passed in
object. The previous "current"
call's reference count is
decremented. If an end call event
is received for the current call, its
reference count is decremented
one extra time.

CCtiOsSession

DestroyWaitObject()

This method call decrements the
reference count on the passed in
object.

CCtiOsSession

CreateWaitObject()

The client application must call
DestroyWaitObject() on the
returned object when the object is
no longer needed.

CCtiOsSession

DestroySilentMonitor
Manager()

This method decrements the
reference count of the passed in
object.

CCtiOsSession

CreateSilentMonitor
Manager()

The client application must call
DestroySilentMonitorManager ()
on the returned object when it is no
longer needed.