CTI Toolkit Blocks Reference
# P0606089 Ver: 1.1
Nortel Networks Confidential
Page 51
The following information pertains to the use of the
Send TAPI SCCS 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 location for the returned
data.
•
The
CTI.status
parameter is set to 0 if the request is 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 SCCS Call Data CSTAPI and
CSTAPILS Log Files on page 92
.
Send TAPI SCCS Call Data
This TAPISCCS 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
cstapisccs
resource.
Summary of Contents for CTI ToolKit
Page 5: ...Preface...
Page 55: ...Example Applications...
Page 73: ...Example Log Files...
Page 99: ...Index...
Page 101: ...Glossary of CTI Terminology...
