Cisco Cisco Computer Telephony Integration Option 9.0 Developer's Guide

Page of 490
   
10-11
CTI OS Developer’s Guide for Cisco Unified Contact Center Enterprise
Release 8.5(3)
Chapter 10      Call Object
Methods
Return Value
Default CTI OS return values. See 
Remarks
As with the Clear method, under certain switches you must make the ClearConnection request via a call 
whose status is LCS_CONNECT or LCS_INITIATE or it fails. Many other switches allow the Clear 
method to be called via a call whose status is LCS_ALERTING or LCS_HOLD. It can never be made 
via a call whose status is LCS_NULL indicating that it is already cleared. 
The following events are received if this request is successful: 
OnClearConnectionConf event
OnCallConnectionlCleared event
If this is a two party call, these events are followed by:
OnCallCleared event
The following events are received if this request fails: 
OnControlFailureConf event
Conference
The Conference method either begins a new conference call or adds an additional call to an existing 
conference call. When it begins a new conference call, it combines an original two-party call with a 
two-party consult call (where the two calls have a common party) into a single three party call. Only the 
common party (which is called the “Conference Controller”) can call this method to make the new 
conference call. You can call this method on either of the Conference Controller’s calls.
Syntax
C++:
int Conference();
int Conference(Arguments& optional_args)
COM:
HRESULT Conference ( /*[in, optional]*/ IArguments *optional_args,    (/*[out, 
retval]*/ int * errorcode )
VB:
Conference([optional_args As IArguments]) As Long
Java:
int Conference(Arguments optional_args)
.NET:
CilError Conference(Arguments optional_args)
Parameters
optional_args
An optional input parameter, which is a pointer or reference to an Arguments array that contains a 
member with the string value that is the UniqueObjectID of the call to which this call is conferenced. 
If this argument is used, add it to the Arguments parameter with the keyword of 
“CallReferenceObjectID”. This is only necessary in an environment where there are multiple held 
calls and the request is made through the talking call. If the request is made through a specific held 
call in this scenario, or if there are only two calls at the device, this parameter is unnecessary.