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
114 Voice API Programming Guide — June 2005
Speed and Volume Control
dx_addvoldig( )
adds a digit that will modify volume by a specified amount
See the Voice API Library Reference for detailed information about these functions.
9.3 Speed and Volume Adjustment Functions
Speed or volume can be adjusted explicitly or can be set to adjust in response to a preset condition,
such as a specific digit. For example, speed could be set to increase a certain amount when “1” is
pressed on the telephone keypad. The functions used for speed and volume adjustment are:
dx_setsvcond( )
Sets conditions that adjust speed or volume. Use this function to adjust speed or volume in
response to a DTMF digit or start of play.
dx_adjsv( )
Adjusts speed or volume explicitly. Use this function if your adjustment condition is not a digit
or start of play. For example, the application could call this function after detecting a spoken
word (voice recognition) or a certain key on the keyboard.
See the Voice API Library Reference for detailed information about these functions.
9.4 Speed and Volume Modification Tables
Each channel has a speed or volume modification table for play speed or play volume adjustments.
Except for the value of the settings, the table is the same for speed and volume.
Each speed or volume modification table (SVMT) table has 21 entries, 20 that allow for a
maximum of 10 increases and decreases in speed or volume. The entry in the middle of the table is
referred to as the “origin” entry that represents normal speed or volume. The normal speed or
volume is how playback occurs when the speed and volume control feature is not used. See
Table 11, “Default Speed Modification Table”, on page 116 and Table 12, “Default Volume
Modification Table”, on page 117.
The origin, or normal speed or volume, is the basis for all settings in the table. Typically, the origin
is set to 0. Speed and volume increases or decreases by moving up or down the tables. Other entries
in the table specify a speed or volume setting in terms of a deviation from normal. For example, if a
speed modification table (SMT) entry is -10, this value represents a 10% decrease from the normal
speed.
Although the origin is typically set to normal speed/volume, changing the setting of the origin does
not affect the other settings, because all values in the SVMT are based on a deviation from normal
speed/volume.
Speed and volume control adjustments are specified by moving the current speed/volume pointer in
the table to another SVMT table entry; this translates to increasing or decreasing the current
speed/volume to the value specified in the table entry.