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
Voice API Programming Guide — June 2005 123
Send and Receive FSK Data
10.3 ADSI Operation
ADSI data is encoded using a standard 1200 baud modem specification and transmitted to the
telephone on the voice channel. The voice is muted for the data transfer to occur. Responses from
the ADSI telephone are mapped into DTMF sequences.
ADSI data is sent to the ADSI telephone in a message burst corresponding to a single transmission.
Each message burst or transmission can contain up to 5 messages, with each message consisting of
one or more ADSI commands.
The ADSI alert tone causes the ADSI telephone to switch to data mode for 1 message burst or
transmission. When the transmission is complete, the ADSI phone will revert to voice mode unless
the transmission contained a message with the “Switch to Data” command.
After the data is transmitted, the ADSI telephone sends an acknowledgment consisting of a DTMF
“d” plus a digit from 1 to 5 indicating the number of messages in the transmission that the ADSI
telephone received and understood. By obtaining this message count and comparing it with the
number of messages transmitted, you can check for errors and retransmit any messages not
received. (If you send 4 messages and the telephone receives 2, you must resend messages 3 and 4.)
You can send more than one transmission during a call. After the initial transmission of a call, you
do not have to re-establish the handshaking (sending the alert tone or receiving the
acknowledgment digit) as long as you have left the ADSI telephone in data mode using the ADSI
“Switch to Data” command. This is useful for performing additional data transmissions during the
same call without needing to send the alert tone or receive the acknowledgment digit for each
transmission.
10.4 One-Way ADSI
One-way ADSI support enables Intel telecom boards to be used as ADSI servers and to support
ADSI features such as visual voice mail. One-way ADSI allows for the one-way transmission of
data from a server to a customer premises equipment (CPE) device, such as a display-based
telephone. The phone (CPE) sends dual tone multi-frequency (DTMF) messages to the server,
indicating whether the data was received successfully.
For a more detailed description of the one-way ADSI data transfer process, see Section 10.8,
“Developing ADSI Applications”, on page 127.
ADSI data can be transferred only to display-based telephones that are ADSI compliant. Check
with your telephone manufacturer to find out if your telephone is a true ADSI-compliant device.
An ADSI alert tone, referred to as a CAS (CPE Alerting Signal), is sent by the server to query a
CPE device, such as an ADSI display phone. The device responds appropriately and, if the device
is ADSI-compliant, the ADSI data transfer is initiated.
Note: ADSI-compliant phones are also referred to as "Type 3 CPE Devices" by Telcordia Technologies
and by the Electronic Industry Association/Telecommunications Industry Association (EIA/TIA).