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 167
Global Tone Detection and Generation, and Cadenced Tone Generation
• To generate a continuous, non-cadenced signal, you can use dx_playtoneEx( ) and
TN_GENCAD to specify a single segment with zero off-time and with an infinite number of
cycles and/or an infinite on-time.
Alternatively, you could use dx_playtone( ) and TN_GEN to generate a non-cadenced signal.
The following non-cadenced call progress signals could be generated by the dx_playtone( )
function if you defined them in a TN_GEN: 1) Dial Tone, 2) Executive Override Tone, and 3)
Busy Verification Tone Part A.
• Note that the Intercept Tone consists of alternating single tones.
• Although the TIA/EIA Standard describes the Busy Verification Tone as one signal, the two
segments are separate tones/events: Part A is a single burst almost three times longer than Part
B and it alerts the parties before the attendant intrudes; Part B is a short burst every 9 seconds
continuing as long as the interruption lasts. The TIA/EIA Standard does not define an off-time
between Part A and B. Therefore, the application developer is responsible for implementing
the timing between the two parts of this signal.
• The TIA/EIA Standard specifies the range of permissible power levels per frequency for 1) the
Central Office trunk interface and 2) all other interfaces (including off-premise stations and tie
trunks). The Intel implementation adopted the approximate middle value in the acceptable
range of power levels for applying the signals to the CO trunk interface. These power levels
were more restrictive than those for the other interfaces. According to the following statement
in the TIA/EIA Standard, additional requirements and considerations may apply:
“Studies have shown that the lower level tones that are transmitted over trunks should be 6 dB
hotter at the trunk interface (than at the line interface) to compensate for increased loss on the
end-to-end connection. In the case of tones used at higher levels, the 6 dB difference is not
used since power at trunk interfaces must be limited to -13 dBm0 total when averaged over any
3-second interval to prevent carrier overload. Maximum permissible powers listed are
consistent with this requirement taking into account the allowable interruption rates for the
various tones. Uninterrupted tones, such as Dial Tone and Intercept Tone, shall be
continuously limited to -13 dBm.”
For related power level information, see also Note 1 for Tables 29 and 30, Section 5.9, and
Section 6.3.5.