(Page 3 of 5 in this chapter)

1.2 About This Manual

The CT Access Developer's Manual is targeted to developers of telephony and voice applications who are using CT Access. This document defines telephony terms where applicable, but assumes that the reader is familiar with telephony concepts. It also assumes that the user is familiar with the C programming language.
This manual is organized as follows: For Information About the... See... CT Access features and how it operates Chapter 2 - CT Access Architecture Programming models, initialization, version control, parameter management, error handling, and the development environment Chapter 3 - Application Development Switching service and an explanation of its functionality Chapter 4 - Switching Service Voice Message service and an explanation of its functionality Chapter 5 - Voice Message Service Call control and an explanation of its functionality Chapter 6 - ADI Service: Call Control Voice playing and recording functions in the ADI service Chapter 7 - ADI Service: Playing/Recording Functions for analyzing the progression of outbound calls Chapter 8 - ADI Service: Call Progress Tone detection functions Chapter 9 - ADI Service: Tone Detection Tone generation functions Chapter 10 - ADI Service: Tone Generation DTMF collection and detection Chapter 11 - ADI Service: DTMF Collection Energy detector, FSK data, low level call control, on-board timers, and AG board functions Chapter 12 - ADI Service: Auxiliary Functions Demonstration programs and utilities that NMS provides using CT Access Chapter 13 - Demonstration Programs and Utilities Terms used in CT Access Appendix A - Glossary VOX file header format, summary of frame sizes, and the index structure Appendix B - VOX File Format Files and rules associated with the Prompt Builder and detailed information about the commands that can be used to create custom rules Appendix C - Prompt Builder Switching service functions and an example for developing a a Call Center application Appendix D - Switching Application Example
This document uses the following typographical conventions:

Example

Description

arg

Bold italic Times Roman indicate a placeholder for information that must be supplied, such as file names or variables.

xxxDoSomething

Bold Times Roman indicates a function name.

[option]

Square brackets indicate optional items.

int

Helvetica is used for data types and data structure names.

SUCCESS

All uppercase helvetica font indicates parameter names, error codes, return codes, and packet names.

printf

Monospace font indicates a code example or user input.

. . .

Ellipses indicate that part of an example program is intentionally omitted.

file.cfg

Italicized monospace font indicates a file name or the name of a utility.

For Information About the...	See...
CT Access features and how it operates	Chapter 2 - CT Access Architecture
Programming models, initialization, version control, parameter management, error handling, and the development environment	Chapter 3 - Application Development
Switching service and an explanation of its functionality	Chapter 4 - Switching Service
Voice Message service and an explanation of its functionality	Chapter 5 - Voice Message Service
Call control and an explanation of its functionality	Chapter 6 - ADI Service: Call Control
Voice playing and recording functions in the ADI service	Chapter 7 - ADI Service: Playing/Recording
Functions for analyzing the progression of outbound calls	Chapter 8 - ADI Service: Call Progress
Tone detection functions	Chapter 9 - ADI Service: Tone Detection
Tone generation functions	Chapter 10 - ADI Service: Tone Generation
DTMF collection and detection	Chapter 11 - ADI Service: DTMF Collection
Energy detector, FSK data, low level call control, on-board timers, and AG board functions	Chapter 12 - ADI Service: Auxiliary Functions
Demonstration programs and utilities that NMS provides using CT Access	Chapter 13 - Demonstration Programs and Utilities
Terms used in CT Access	Appendix A - Glossary
VOX file header format, summary of frame sizes, and the index structure	Appendix B - VOX File Format
Files and rules associated with the Prompt Builder and detailed information about the commands that can be used to create custom rules	Appendix C - Prompt Builder
Switching service functions and an example for developing a a Call Center application	Appendix D - Switching Application Example

Example	Description
arg	Bold italic Times Roman indicate a placeholder for information that must be supplied, such as file names or variables.
`xxxDoSomething`	Bold Times Roman indicates a function name.
[option]	Square brackets indicate optional items.
int	Helvetica is used for data types and data structure names.
SUCCESS	All uppercase helvetica font indicates parameter names, error codes, return codes, and packet names.
printf	Monospace font indicates a code example or user input.
. . .	Ellipses indicate that part of an example program is intentionally omitted.
`file.cfg`	Italicized monospace font indicates a file name or the name of a utility.

(Page 3 of 5 in this chapter)

Tech_Support@nmss.com