Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide
10-31
CTI OS Developer’s Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted
Release 7.5(1)
Chapter 10 Call Object
Methods
Syntax
C++:
int Transfer();
int Transfer(Arguments& optional_args)
COM:
HRESULT Transfer ( [in, optional] IArguments *optional_args, (/*[out,
retval]*/ int * errorcode )
VB:
Transfer([optional_args As IArguments]) As Long
Java:
int Transfer(Arguments rArgs)
.NET:
CilError Transfer(Arguments args)
Parameters
optional_args
An optional input parameter containing a member with a string value that is the UniqueObjectID of
the call that is participating in the transfer. If this argument is used, it should be added to the
Arguments parameter with the keyword of “CallReferenceObjectID”. This would only be necessary
in an environment where there are multiple held calls and the request is being made through the
current call. If the request is being made through a specific held call in this scenario, or if there are
only two calls at the device, this parameter is unnecessary.
the call that is participating in the transfer. If this argument is used, it should be added to the
Arguments parameter with the keyword of “CallReferenceObjectID”. This would only be necessary
in an environment where there are multiple held calls and the request is being made through the
current call. If the request is being made through a specific held call in this scenario, or if there are
only two calls at the device, this parameter is unnecessary.
errorcode
An output parameter (return parameter in VB) that contains an error code from
in
Return Values
Default CTI OS return values. See
Remarks
Before making this request, it is necessary for the original call to be in the held state and the consult call
to be in the talking state or the request will fail. Therefore, if the calls are alternated (See Alternate), they
must be alternated again to return the two calls into their appropriate states.
to be in the talking state or the request will fail. Therefore, if the calls are alternated (See Alternate), they
must be alternated again to return the two calls into their appropriate states.
If there are only two calls at the device, call this method using either the current or held call. For switches
that allow more than two calls at a device (for example G3), make this request only through the desired
held call to avoid the ambiguity caused by multiple held calls at the device. Otherwise, indicate the
desired held call by using the optional parameter.
that allow more than two calls at a device (for example G3), make this request only through the desired
held call to avoid the ambiguity caused by multiple held calls at the device. Otherwise, indicate the
desired held call by using the optional parameter.
The Transfer request must be made via a call whose call status is LCS_CONNECT or LCS_HELD or
it will fail.
it will fail.
The following events are received by the transfer initiator if this request is successful:
•
OnCallTransferred event
•
OnCallEnd event
•
OnCallEnd event
•
OnAgentStateChange event
•
OnTransferCallConf event
The following events will be received if this request fails:
•
OnControlFailureConf event