Nortel CTI ToolKit, User Manual, Page: 50 / 108

PeriProducer CTI Toolkit User’s Guide for M1
Page 50 Nortel Networks Confidential # P0606089 Ver: 1.1
The following information pertains to the use of the Send TAPI Call Data block:
• This block requires two prerequisites as it manages its own resource needs.
The
CTI Initialize block (see page 32 ) should be used early in the application
to set up appropriate error handling. Also, the Set Event Handling block (see
page 37 ) should be used before trying to send data. This is usually best done
right after the call is answered to synchronize the CTI services and their data
stores with the actual phone device state. The usual state to wait for is
Established
.
• The values required for the this CTI block are stored in the folders
CTI.AVCalldata.Avpairs.Key()
and
CTI.AVCalldata.Avpairs.Value().
•
CTI.EventData.csrsmstatdata
(a structured array[folder] that includes
datakey and datavalue in each of 40 elements) is the return location for the
data.
• The CTI.status parameter is set to 0 if the request was successful and set to 1
if the request fails.
• For examples of applications that use this block, see Appendix Example
Applications — Send TAPI CallData/Send TAPIsccs CallData on page 70 .
• For example log files showing the internal functions of this block, see
Appendix
Example Log Files — Send TAPI Call Data CSTAPI and
CSTAPILS Log Files on page 89 .
Send TAPI Call Data
The TAPI block sends screen pop information about the
current call from the IVR application to the Symposium
TAPI Server via the
IVR.DLL
protocol. This block uses
the
cstapi
resource.