User's Manual
Table Of Contents
- Contents
- Figures
- Tables
- Revision History
- About This Publication
- 1. Product Description
- 2. Programming Models
- 3. Device Handling
- 4. Event Handling
- 5. Error Handling
- 6. Application Development Guidelines
- 7. Call Progress Analysis
- 7.1 Call Progress Analysis Overview
- 7.2 Call Progress and Call Analysis Terminology
- 7.3 Call Progress Analysis Components
- 7.4 Using Call Progress Analysis on DM3 Boards
- 7.5 Call Progress Analysis Tone Detection on DM3 Boards
- 7.6 Media Tone Detection on DM3 Boards
- 7.7 Default Call Progress Analysis Tone Definitions on DM3 Boards
- 7.8 Modifying Default Call Progress Analysis Tone Definitions on DM3 Boards
- 7.9 Call Progress Analysis Errors
- 7.10 Using Call Progress Analysis on Springware Boards
- 7.11 Call Progress Analysis Tone Detection on Springware Boards
- 7.12 Media Tone Detection on Springware Boards
- 7.13 Default Call Progress Analysis Tone Definitions on Springware Boards
- 7.14 Modifying Default Call Progress Analysis Tone Definitions on Springware Boards
- 7.15 SIT Frequency Detection (Springware Only)
- 7.15.1 Tri-Tone SIT Sequences
- 7.15.2 Setting Tri-Tone SIT Frequency Detection Parameters
- 7.15.3 Obtaining Tri-Tone SIT Frequency Information
- 7.15.4 Global Tone Detection Tone Memory Usage
- 7.15.5 Frequency Detection Errors
- 7.15.6 Setting Single Tone Frequency Detection Parameters
- 7.15.7 Obtaining Single Tone Frequency Information
- 7.16 Cadence Detection in Basic Call Progress Analysis (Springware Only)
- 8. Recording and Playback
- 8.1 Overview of Recording and Playback
- 8.2 Digital Recording and Playback
- 8.3 Play and Record Functions
- 8.4 Play and Record Convenience Functions
- 8.5 Voice Encoding Methods
- 8.6 G.726 Voice Coder
- 8.7 Transaction Record
- 8.8 Silence Compressed Record
- 8.9 Recording with the Voice Activity Detector
- 8.10 Streaming to Board
- 8.11 Pause and Resume Play
- 8.12 Echo Cancellation Resource
- 9. Speed and Volume Control
- 10. Send and Receive FSK Data
- 11. Caller ID
- 12. Cached Prompt Management
- 13. Global Tone Detection and Generation, and Cadenced Tone Generation
- 13.1 Global Tone Detection (GTD)
- 13.1.1 Overview of Global Tone Detection
- 13.1.2 Global Tone Detection on DM3 Boards versus Springware Boards
- 13.1.3 Defining Global Tone Detection Tones
- 13.1.4 Building Tone Templates
- 13.1.5 Working with Tone Templates
- 13.1.6 Retrieving Tone Events
- 13.1.7 Setting GTD Tones as Termination Conditions
- 13.1.8 Maximum Amount of Memory for Tone Templates
- 13.1.9 Estimating Memory
- 13.1.10 Guidelines for Creating User-Defined Tones
- 13.1.11 Global Tone Detection Application
- 13.2 Global Tone Generation (GTG)
- 13.3 Cadenced Tone Generation
- 13.3.1 Using Cadenced Tone Generation
- 13.3.2 How To Generate a Custom Cadenced Tone
- 13.3.3 How To Generate a Non-Cadenced Tone
- 13.3.4 TN_GENCAD Data Structure - Cadenced Tone Generation
- 13.3.5 How To Generate a Standard PBX Call Progress Signal
- 13.3.6 Predefined Set of Standard PBX Call Progress Signals
- 13.3.7 Important Considerations for Using Predefined Call Progress Signals
- 13.1 Global Tone Detection (GTD)
- 14. Global Dial Pulse Detection
- 14.1 Key Features
- 14.2 Global DPD Parameters
- 14.3 Enabling Global DPD
- 14.4 Global DPD Programming Considerations
- 14.5 Retrieving Digits from the Digit Buffer
- 14.6 Retrieving Digits as Events
- 14.7 Dial Pulse Detection Digit Type Reporting
- 14.8 Defines for Digit Type Reporting
- 14.9 Global DPD Programming Procedure
- 14.10 Global DPD Example Code
- 15. R2/MF Signaling
- 16. Syntellect License Automated Attendant
- 17. Building Applications
- Glossary
- Index

122 Voice API Programming Guide — June 2005
Send and Receive FSK Data
acknowledge and the data transmission (and/or reception) will then be initiated. Once the data
transmission/reception is complete, the devices switch back to voice mode.
This newer implementation of ADSI is supported through the dx_RxIottData( ),
dx_TxIottData( ), and dx_TxRxIottData( ) functions. This implementation is referred to simply
as “ADSI Support” or “Two-Way ADSI.” This newer ADSI support provides for both one-way and
two-way ADSI transmission and is the recommended method for implementing either one-way or
two-way ADSI in an application program. The older one-way ADSI support can be used but is not
recommended. Future enhancements to ADSI feature and functionality will not be made to the
dx_play( ) and dx_playf( ) functions. See Section 10.9, “Modifying Older One-Way ADSI
Applications”, on page 133 for information on converting from the older to the newer method for
using ADSI.
10.2 ADSI Protocol
ADSI is a superset of the caller ID and call waiting functions. ADSI is built on the same protocol as
caller ID and shares the same ADSI Data Message Format (ADMF). The ADSI protocol requires a
Bell 202/V.23 1200 bps FSK-based modem for data transmission.
The ADSI protocol supports a variable display size on a display-based telephone. An ADSI
telephone can work in either voice mode or data mode. Voice mode is for normal telephone audio
communication, and data mode is for transmitting ADSI commands and controlling the telephone
display (voice is muted in data mode). An ADSI alert tone is used to verify that the hardware is
connected to an ADSI telephone and to alert the telephone that ADSI data will be transferred.
The ADSI protocol consists of three defined layers, as follows:
message assembly layer
assembles the body of the ADMF message
data link layer
generates the checksum, which is used for error detection, and sends it to the driver
physical layer
transports the composite message via the modem to the CPE on a transparent (bit-for-bit) basis
Intel provides only the physical layer and a portion of the data link layer of the ADSI protocol. The
user is responsible for creating the ADSI messages and the corresponding checksums.
The ADSI data must conform to interface requirements described in Telcordia Technologies
Generic Requirements GR-30-CORE (formerly TR-NWT-000030), Voiceband Data Transmission
Interface Generic Requirements. For information about message requirements (how the data
should be displayed on the CPE), see Generic Requirements GR-1273 (formerly TR-NWT-
001273), Generic Requirements for and SPCS to Customer Premises Equipment Data Interface for
Analog Display Services. To obtain a copy of these technical references, call 1-800-521-2673 (from
the U.S. and Canada) or +1-732-699-5800 (worldwide), or visit http://www.telcordia.com. Note
that Telcordia Technologies was formerly known as Bellcore.