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
124 Voice API Programming Guide — June 2005
Send and Receive FSK Data
10.5 Two-Way ADSI
Two-way ADSI includes several enhancements to one-way ADSI, including two-way frequency
shift keying (FSK). The following topics discuss two-way ADSI:
• Transmit to On-Hook CPE
• Two-Way FSK
10.5.1 Transmit to On-Hook CPE
The transmit to on-hook customer premises equipment (CPE) feature allows messages to be sent to
an ADSI phone when the phone is either on-hook or off-hook.
This feature supports the transmission of FSK data burst messages to CPE devices that are kept in
the on-hook state by either the Central Office (CO) or the PBX/KTS. This allows an ADSI/Caller
ID phone to receive and potentially display messages while it is in the on-hook state. For example,
ADSI phones can be configured, accessed, and downloaded with features, outside of regular
business hours while the phone is on-hook, without ringing and without subscriber intervention.
Note: The transmit to on-hook CPE feature works only if the CO supports this feature.
10.5.2 Two-Way FSK
The two-way frequency shift keying (FSK) feature allows users to send and receive character or
binary data at 1200 bits/second between the server and compatible devices, such as certain ADSI
phones with keyboards. The two-way FSK feature supports applications such as off-line e-mail
editing and sending FSK Caller ID data to a customer premises equipment (CPE) device.
FSK (frequency shift keying) is a modulation technique used to transfer data over voice lines. The
basic ADSI capability supports only FSK Transmit (one-way FSK), in which an FSK message is
sent from the server to an ADSI display phone, with the phone in the off-hook state. The phone
(CPE) sends dual tone multi-frequency (DTMF) messages to the server. As DTMF messages are
sent to the server, the effective data rate is very slow, approximately 6 characters per second
maximum. This speed is satisfactory for ACK/NAK signaling but it is not usable for any bulk data
transport in the inbound direction from the CPE.
FSK data reception uses a DSP-based Bell 202/V.23 low speed (1200 baud) modem receiver. A
1200 baud modem does not need to train for data transmission, and therefore is faster than a high-
speed modem for short data bursts.
Two-way FSK for ADSI supports the transmission and the reception of FSK data between the
server and the CPE. The server initiates the reception of data from the CPE by sending a CAS to
tell the CPE to switch to data mode, followed by a message that tells the CPE to switch to
peripheral mode. Once it is in peripheral mode, the CPE can send FSK messages to the server using
the ADSI Data Message Format (ADMF), instead of the slower DTMF-based scheme.
See Section 10.8, “Developing ADSI Applications”, on page 127 for a more detailed description of
how to use library functions to develop two-way ADSI data transfer applications. For more