INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN
INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS
ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER
INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, or life sustaining applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
This Voice API for Windows Operating Systems Library Reference as well as the software described in it is furnished under license and may only be
used or copied in accordance with the terms of the license. The information in this manual is furnished for informational use only, is subject to change
without notice, and should not be construed as a commitment by Intel Corporation. Intel Corporation assumes no responsibility or liability for any
errors or inaccuracies that may appear in this document or any software that may be provided in association with this document.
Except as permitted by such license, no par t of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any
means without express written consent of Intel Corporation.
Voice API for Windows Operating Systems Library Reference – November 20039
Revision History
This revision history summarizes the changes made in each published version of this document.
Document No.Publication DateDescription of Revisions
05-1832-002November 2003Function Summary by Category chapter : Added functions to I/O Functions category;
added a section for Streaming to Board category; added functions to the Call
Progress Analysis category; added a function to the Configuration category.
Voice Function Support by Platform table : Added new functions to table.
dx_cacheprompt( ) function reference: Removed statement from the Cautions
section about cached prompts not being flushed and added new information.
dx_close( ) function reference: Removed oflags parameter.
dx_CloseStreamBuffer( ) function reference: New function.
dx_createtone( ) function reference: New function.
dx_deletetone( ) function reference: New function.
dx_getfeaturelist( ) function reference: Added support for board device as an
argument in addition to channel device. Added new bullet item in the Cautions
section about returning front end information.
dx_GetStreamInfo( ) function reference: New function.
dx_OpenStreamBuffer( ) function reference: New function.
dx_pause( ) function reference: New function.
dx_PutStreamData( ) function reference: New function.
dx_querytone( ) function reference: New function.
dx_ResetStreamBuffer( ) function reference: New function.
dx_resume( ) function reference: New function.
dx_RxIottData( ) function reference: Added caution for Springware boards in
Cautions section.
dx_setevtmsk( ) function reference: Added DM_UNDERRUN bitmask for streaming
to board feature.
dx_setparm( ) function reference: Added parameters for ETSI Compliant Frequency
Shift Keying (FSK) and automatic gain control (AGC) in Voice Channel
Parameters (DM3) table.
dx_SetRecordNotifyBeepTone( ) function reference: New function.
dx_SetWaterMark( ) function reference: New function.
dx_setsvcond( ) function reference : Added support for pause/resume play feature.
CT_DEVINFO data structure: Revised structure with new fields.
DV_TPT data structure : In tp_termno field description, added restriction on use of
DX_IDDTIME on DM3 boards; added usage note on DX_MAXTIME and
DX_IDDTIME. In tp_flags field description, indicated that TF_SETINIT is now
supported on DM3 boards; added new TF_IMMEDIATE bit for DM3 boards only.
DX_IOTT data structure: New io_type field value for streaming to board feature.
DX_STREAMSTAT data structure: New data structure for streaming to board
feature.
DX_SVCB data structure: Added new values for pause/resume play feature.
DX_XPB data structure : Added 8 kHz linear PCM to Linear PCM Voice Coder
Support Fields (DM3) table.
Voice API for Windows Operating Systems Library Reference — November 200310
Revision History
Document No.Publication DateDescription of Revisions
05-1832-002November 2003TONE_DATA data structure: New data structure for call progress analysis
05-1832-001November 2002Initial version of document. Much of the information contained in this document was
enhancements.
Events chapter: Added section for unsolicited events returned by streaming to board
functions.
previously published in the Voice Software Reference Programmer's Guide for
Windows, document number 05-1456-003.
Voice API for Windows Operating Systems Library Reference — November 200311
Revision History
12Voice API for Windows Operating Systems Library Reference — November 2003
About This Publication
The following topics provide information about this publication:
• Purpose
• Intended Audience
• How to Use This Publication
• Related Information
Purpose
This publication provides a reference to all voice functions, parameters and data structures in the
voice API, also called the R4 voice API, supported on Windows* operating systems. It is a
companion document to the Voice API Programming Guide, the Standard Runtime Library API Programming Guide, and the Standard Runtime Library API Library Reference.
Intended Audience
This information is intended for:
• Distributors
• System Integrators
• Toolkit Developers
• Independent Software Vendors (ISVs)
• Value Added Resellers (VARs)
• Original Equipment Manufacturers (OEMs)
How to Use This Publication
This document assumes that you are familiar with and have prior experience with Windows*
operating systems and the C programming language. Use this document together with the
following: the Voice API Programming Guide, the Standard Runtime Library API Programming Guide, and the Standard Runtime Library API Library Reference.
The information in this guide is organized as follows:
• Chapter 1, “Function Summary by Category” introduces the various categories of voice
functions and provides a brief description of each function.
• Chapter 2, “Function Information” provides an alphabetical reference to all voice functions.
Voice API for Windows Operating Systems Library Reference — November 200313
About This Publication
• Chapter 3, “Events” provides an alphabetical reference to events that may be returned by the
voice software.
• Chapter 4, “Data Structures” provides an alphabetical reference to all voice data structures.
• Chapter 5, “Error Codes” presents a listing of error codes that may be returned by the voice
software.
• Chapter 6, “Supplementary Reference Information” provides additional reference information
on topics such as DTMF Tone Specifications, and MF Tone Specifications.
A glossary and index are provided for your reference.
Related Information
See the following for more information:
• For information about voice library features and guidelines for building applications using
voice software, see the Voice API Programming Guide.
• For details on the Standard Runtime Library, supported programming models, and
programming guidelines for building all applications, see the Standard Runtime Library API
Programming Guide. The Standard Runtime Library is a device-independent library that
consists of event management functions and standard attribute functions.
• For details on all functions and data structures in the Standard Runtime Library library, see the
Standard Runtime Library API Library Reference.
• For information on the system release, system requirements, software and hardware features,
supported hardware, and release documentation, see the Release Guide for the system release
you are using.
• For details on compatibility issues, restrictions and limitations, known problems, and late-
breaking updates or corrections to the release documentation, see the Release Update.
Be sure to check the Release Update for the system release you are using for any updates or
corrections to this publication. Release Updates are available on the Telecom Support
Resources website at http://resource.intel.com/telecom/support/releases/index.html.
• For details on installing the system software, see the System Release Installation Guide.
• For guidelines on building applications using Global Call software (a common signaling
interface for network-enabled applications, regardless of the signaling protocol needed to
connect to the local telephone network), see the Global Call API Programming Guide.
• For details on all functions and data structures in the Global Call library, see the Global Call
API Library Reference.
• For details on configuration files (including FCD/PCD files) and instructions for configuring
products, see the Configuration Guide for your product or product family.
• For technical support, see http://developer.intel.com/design/telecom/support/. This website
contains developer support information, downloads, release documentation, technical notes,
application notes, a user discussion forum, and more.
• For product and services information, see http://www.intel.com/network/csp/.
14Voice API for Windows Operating Systems Library Reference — November 2003
1.Function Summary by Category
This chapter describes the categories into which the voice library functions can be logically
grouped. This chapter also includes a table listing function support on various platforms (DM3,
Springware) as well as synchronous/asynchronous support.
Device management functions open and close devices, which include boards and channels.
Voice API for Windows Operating Systems Library Reference — November 200315
Function Summary by Category
Before you can call any other library function on a device, that device must be opened using a
device management function. The dx_open( ) function returns a unique voice device handle. This
handle is the only way the device can be identified once it has been opened. The dx_close( )
function closes a device via its handle.
A set of device management functions exists for each Intel® Dialogic® library, such as fax (fx_
functions), modular station interface (ms_ functions), and conferencing (dcb_ functions). See the
appropriate API Library Reference for more information on these functions.
Device management functions do not cause a device to be busy. In addition, these functions will
work on a device whether the device is busy or idle.
For more information about opening and using voice devices, particularly on DM3 boards, see the
Voice API Programming Guide. Also see this guide for more information about naming
conventions for board and channel devices.
Use Standard Runtime Library device mapper functions to return information about the structure of
the system, such as a list of all physical boards, a list of all virtual boards on a physical board, and
a list of all subdevices on a virtual board. This device information is used as input to device
management functions. For more information on device mapper functions, see the Standard Runtime Library API Library Reference.
The device management functions are:
dx_close( )
closes a board or channel device handle
dx_open( )
opens a board or channel device handle
1.2Configuration Functions
Configuration functions allow you to alter, examine, and control the physical configuration of an
open device. In general, configuration functions operate on an idle device. Configuration functions
cause a device to be busy and return the device to an idle state when the configuration is complete.
See the Voice API Programming Guide for information about busy and idle states.
The configuration functions are:
dx_clrdigbuf( )
clears all digits in the firmware digit buffer
dx_GetDllVersion( )
returns the voice dynamic link library (DLL) version number
dx_getfeaturelist( )
returns information about the features supported on the device
dx_getparm( )
gets the current parameter settings for an open device
16Voice API for Windows Operating Systems Library Reference — November 2003
Function Summary by Category
dx_GetRscStatus( )
returns the assignment status of a shared resource for the specified channel
dx_gtsernum( )
returns the board serial number
dx_libinit( )
initializes the voice dynamic link library (DLL)
dx_setchxfercnt( )
sets the bulk queue buffer size for the channel
dx_setdigbuf( )
sets the digit buffering mode
dx_setdigtyp( )
controls the types of digits detected by the device
dx_sethook( )
sets the hook switch state
dx_setparm( )
sets physical parameters for the device
dx_SetRecordNotifyBeepTone( )
specifies the template of the cadenced tone for record notification beep tone
dx_settonelen( )
changes the duration of the built-in beep tone (pre-record beep)
dx_TSFStatus( )
returns the status of tone set file loading
dx_wtring( )
waits for a specified number of rings
Note: The dx_sethook( ) and dx_setdigbuf( ) functions can also be classified as an I/O function and all
I/O characteristics apply.
1.3I/O Functions
An I/O function transfers data to and from an open, idle channel. All I/O functions cause a channel
to be busy while data transfer is taking place and return the channel to an idle state when data
transfer is complete.
I/O functions can be run synchronously or asynchronously, with some exceptions (for example,
dx_setuio( ) can be run synchronously only). When running synchronously, they return after
completing successfully or after an error. When running asynchronously, they return immediately
to indicate successful initiation (or an error), and continue processing until a termination condition
is satisfied. See the Standard Runtime Library API Programming Guide for more information on
asynchronous and synchronous operation.
A set of termination conditions can be specified for I/O functions, except for dx_stopch( ) and
dx_wink( ). These conditions dictate what events will cause an I/O function to terminate. The
Voice API for Windows Operating Systems Library Reference — November 200317
Function Summary by Category
termination conditions are specified just before the I/O function call is made. Obtain termination
reasons for I/O functions by calling the extended attribute function ATDX_TERMMSK( ). See the Voice API Programming Guide for information about I/O terminations.
Note: To send and receive FSK data from an Analog Display Services Interface (ADSI) device, see
collects digits from a channel digit buffer (for up to 31 digits plus the null terminator)
dx_pause( )
pauses on-going play
dx_play( )
plays voice data from any combination of data files, memory, or custom devices
dx_playiottdata( )
plays voice data from any combination of data files, memory, or custom devices, and lets the
user specify format information
dx_rec( )
records voice data to any combination of data files, memory, or custom devices
dx_reciottdata( )
records voice data to any combination of data files, memory, or custom devices, and lets the
user specify format information
dx_resume( )
resumes paused play
dx_setdevuio( )
installs and retrieves user-defined I/O functions in your application
dx_setuio( )
installs user-defined I/O functions in your application
dx_stopch( )
forces termination of currently active I/O functions
dx_wink( )
generates an outbound wink
Notes: 1. The dx_playtone( ) function, which is grouped with global tone generation functions, can also
be classified as an I/O function and all I/O characteristics apply.
2. The dx_playvox( ) and dx_recvox( ) functions, which are grouped with I/O convenience
functions, can also be classified as I/O functions and all I/O characteristics apply.
18Voice API for Windows Operating Systems Library Reference — November 2003
1.4I/O Convenience Functions
Convenience functions enable you to easily implement certain basic functionality of the library
functions. I/O convenience functions simplify synchronous play and record.
The dx_playf( ) function performs a playback from a single file by specifying the filename. The
same operation can be done by using dx_play( ) and supplying a DX_IOTT structure with only one
entry for that file. Using dx_playf( ) is more convenient for a single file playback because you do
not have to set up a DX_IOTT structure for the one file and the application does not need to open
the file. dx_recf( ) provides the same single-file convenience for the dx_rec( ) function.
The dx_playvox( ) function also plays voice data stored in a single VOX file. This function
internally calls dx_playiottdata( ). Similarly, dx_recvox( ) records VOX files using
dx_reciottdata( ).
The I/O convenience functions are:
dx_playf( )
plays voice data from a single VOX file without the need to specify DX_IOTT
dx_playvox( )
plays voice data from a single VOX file using dx_playiottdata( )
Function Summary by Category
dx_playwav( )
plays voice data stored in a single WAVE file
dx_recf( )
records voice data from a channel to a single VOX file without the need to specify DX_IOTT
dx_recvox( )
records voice data from a channel to a single VOX file using dx_reciottdata( )
dx_recwav( )
records voice data to a single WAVE file
1.5Streaming to Board Functions
The streaming to board feature enables real time data streaming to the board. Streaming to board
functions allow you to create, maintain, and delete a circular stream buffer within the library. These
functions also provide notification when high and low water marks are reached. See the Voice API Programming Guide for more information about the streaming to board feature.
The streaming to board functions include:
dx_CloseStreamBuffer( )
deletes a circular stream buffer
dx_GetStreamInfo( )
retrieves information about the circular stream buffer
dx_OpenStreamBuffer( )
creates and initializes a circular stream buffer
Voice API for Windows Operating Systems Library Reference — November 200319
Function Summary by Category
dx_PutStreamData( )
places data into the circular stream buffer
dx_ResetStreamBuffer( )
resets internal data for a circular stream buffer
dx_SetWaterMark( )
sets high and low water marks for the circular stream buffer
The send and receive frequency shift keying (FSK) data interface is used for Analog Display
Services Interface (ADSI) and fixed line short message service (SMS). Frequency shift keying is a
frequency modulation technique to send digital data over voiced band telephone lines.
The functions listed here support both one-way and two-way frequency shift keying (FSK). See the
Voice API Programming Guide for more information about ADSI, two-way FSK, and SMS.
dx_RxIottData( )
receives data on a specified channel
dx_TxIottData( )
transmits data on a specified channel
dx_TxRxIottData( )
starts a transmit-initiated reception of data
1.7Audio Input Functions
The Audio Input (AI) functions are used to provide music or other information on-hold.
ai_open( )
opens an audio input device
ai_close( )
closes an audio input device
ai_getxmitslot( )
gets the TDM bus time slot number of the audio input transmit channel
1.8Transaction Record Functions
Transaction record enables the recording of a two-party conversation by allowing data from two
time division multiplexing (TDM) bus time slots from a single channel to be recorded.
dx_mreciottdata( )
records voice data from two TDM bus time slots to a data file, memory or custom device
20Voice API for Windows Operating Systems Library Reference — November 2003
Function Summary by Category
1.9Cached Prompt Management Functions
The cached prompt management feature enables you to store prompts in on-board memory and
play them from this location rather than from the host disk drive. See the Voice API Programming Guide for more information about cached prompt management.
dx_cacheprompt( )
downloads voice data (prompts) from multiple sources to the on-board memory
dx_getcachesize( )
returns the size of the on-board memory used to store cached prompts
1.10Call Status Transition (CST) Event Functions
Call status transition (CST) event functions set and monitor CST events that can occur on a device.
CST events indicate changes in the status of the call, such as rings or a tone detected, or the line
going on-hook or off-hook. See the call status transition structure (DX_CST) description for a full
list of CST events.
The dx_getevt( ) function retrieves CST events in a synchronous environment. To retrieve CST
events in an asynchronous environment, use the Standard Runtime Library event management
functions.
dx_setevtmsk( ) enables detection of CST event(s). User-defined tones are CST events, but
detection for these events is enabled using dx_addtone( ) or dx_enbtone( ), which are global tone
detection functions.
The call status transition event functions are:
dx_getevt( )
gets a CST event in a synchronous environment
dx_sendevt( )
allows inter-process event communication and sends a specified CST event to a specified
device
dx_setevtmsk( )
enables detection of CST events
1.11TDM Routing Functions
TDM routing functions are used in time division multiplexing (TDM) bus configurations, which
include the CT Bus and SCbus. A TDM bus is resource sharing bus that allows information to be
transmitted and received among resources over multiple time slots.
TDM routing functions enable the application to make or break a connection between voice,
telephone network interface, and other resource channels connected via TDM bus time slots. Each
device connected to the bus has a transmit component that can transmit on a time slot and a receive
component that can listen to a time slot.
Voice API for Windows Operating Systems Library Reference — November 200321
Function Summary by Category
The transmit component of each channel of a device is assigned to a time slot at system
initialization and download. To listen to other devices on the bus, the receive component of the
device channel is connected to any one time slot. Any number of device channels can listen to a
time slot.
Note: When you see references to the SCbus or SCbus routing, this information also applies to the CT
Bus. That is, the physical interboard connection can be either SCbus or CT Bus. The SCbus
protocol is used and the SCbus routing API applies to all the boards regardless of whether they use
an SCbus or CT Bus physical interboard connection.
A set of TDM routing functions exist for each Intel® Dialogic library, such as fax (fx_ functions),
modular station interface (ms_ functions), and conferencing (dcb_ functions). See the appropriate
API Library Reference for more information on these functions.
TDM routing convenience functions, nr_scroute( ) and nr_scunroute( ), are provided to make or
break a half or full-duplex connection between any two channels transmitting on the bus. These
functions are not a part of any library but are provided in a separate C source file called sctools.c.
The functions are defined in sctools.h.
The TDM routing functions are:
ag_getctinfo( )
returns information about an analog device connected to the TDM bus
ag_getxmitslot( )
returns the number of the TDM bus time slot connected to the transmit component of an
analog channel
ag_listen( )
connects the listen (receive) component of an analog channel to the TDM bus time slot
ag_unlisten( )
disconnects the listen (receive) component of an analog channel from the TDM bus time slot
dx_getctinfo( )
returns information about voice device connected to TDM bus
dx_getxmitslot( )
returns the number of the TDM bus time slot connected to the transmit component of a voice
channel
dx_listen( )
connects the listen (receive) component of a voice channel to a TDM bus time slot
dx_unlisten( )
disconnects the listen (receive) component of a voice channel from TDM bus time slot
nr_scroute( )
makes a half or full-duplex connection between two channels transmitting on the TDM bus
nr_scunroute( )
breaks a half or full-duplex connection between two TDM bus devices
22Voice API for Windows Operating Systems Library Reference — November 2003
Function Summary by Category
1.12Global Tone Detection (GTD) Functions
The global tone detection (GTD) functions define and enable detection of single and dual
frequency tones that fall outside the range of those automatically provided with the voice driver.
They include tones outside the standard DTMF range of 0-9, a-d, *, and #.
The GTD dx_blddt( ), dx_blddtcad( ), dx_bldst( ), and dx_bldstcad( ) functions define tones
which can then be added to the channel using dx_addtone( ). This enables detection of the tone on
that channel. See the Voice API Programming Guide for a full description of global tone detection.
The global tone detection functions are:
dx_addtone( )
adds a user-defined tone
dx_blddt( )
builds a user-defined dual frequency tone description
dx_blddtcad( )
builds a user-defined dual frequency tone cadence description
dx_bldst( )
builds a user-defined single frequency tone description
dx_bldstcad( )
builds a user-defined single frequency tone cadence description
dx_deltones( )
deletes all user-defined tones
dx_distone( )
disables detection of user-defined tones
dx_enbtone( )
enables detection of user-defined tones
dx_setgtdamp( )
sets amplitudes used by global tone detection (GTD)
1.13Global Tone Generation (GTG) Functions
Global tone generation (GTG) functions define and play single and dual tones that fall outside the
range of those automatically provided with the voice driver.
The dx_bldtngen( ) function defines a tone template structure, TN_GEN. The dx_playtone( )
function can then be used to generate the tone.
See the Voice API Programming Guide for a full description of global tone generation.
The global tone generation functions are:
dx_bldtngen( )
builds a user-defined tone template structure, TN_GEN
Voice API for Windows Operating Systems Library Reference — November 200323
Function Summary by Category
dx_playtone( )
plays a user-defined tone as defined in TN_GEN structure
dx_playtoneEx( )
plays the cadenced tone defined by TN_GENCAD structure
Note: The dx_playtone( ) and dx_playtoneEx( ) functions can also be classified as an I/O function and
all I/O characteristics apply.
1.14R2/MF Convenience Functions
R2/MF convenience functions enable detection of R2/MF forward signals on a channel, and play
R2/MF backward signals in response. For more information about voice support for R2/MF, see the
Voice API Programming Guide.
Note: R2/MF signaling is typically accomplished through the Global Call API. For more information, see
the Global Call documentation set. The R2/MF functions listed here are provided for backward
compatibility only and should not be used for R2/MF signaling.
r2_creatfsig( )
creates R2/MF forward signal tone
r2_playbsig( )
plays R2/MF backward signal tone
1.15Speed and Volume Functions
Speed and volume functions adjust the speed and volume of the play. A speed modification table
and volume modification table are associated with each channel, and can be used for increasing or
decreasing the speed or volume. These tables have default values which can be changed using the
dx_setsvmt( ) function.
The dx_addspddig( ) and dx_addvoldig( ) functions are convenience functions that specify a digit
and an adjustment to occur on that digit, without having to set any data structures. These functions
use the default settings of the speed and volume modification tables.
See the Voice API Programming Guide for more information about the speed and volume feature in
general, and speed and volume modification tables in particular.
The speed and volume functions are:
dx_adjsv( )
adjusts speed or volume immediately
dx_addspddig( )
sets a dual tone multi-frequency (DTMF) digit for speed adjustment
dx_addvoldig( )
adds a dual tone multi-frequency (DTMF) digit for volume adjustment
24Voice API for Windows Operating Systems Library Reference — November 2003
Function Summary by Category
dx_clrsvcond( )
clears speed or volume conditions
dx_getcursv( )
returns current speed and volume settings
dx_getsvmt( )
returns current speed or volume modification table
dx_setsvcond( )
sets conditions (such as digit) for speed or volume adjustment; also sets conditions for play
(pause and resume)
dx_setsvmt( )
changes default values of speed or volume modification table
1.16Call Progress Analysis Functions
Call progress analysis functions are used to enable the call progress analysis feature and change the
default definition of call progress analysis tones. See the Voice API Programming Guide for more
information about call progress analysis.
Notes: 1. Two forms of call progress analysis exist: basic and PerfectCall (formerly called “enhanced call
analysis”). PerfectCall call progress analysis uses an improved method of signal identification
and can detect fax machines and answering machines. Basic call progress analysis provides
backward compatibility for older applications written before PerfectCall call progress analysis
became available.
2. Throughout this document, call progress analysis refers to PerfectCall call progress analysis
unless otherwise noted.
The call progress analysis functions are:
dx_chgdur( )
changes the default call progress analysis signal duration
dx_chgfreq( )
changes the default call progress analysis signal frequency
dx_chgrepcnt( )
changes the default call progress analysis signal repetition count
dx_initcallp( )
initializes call progress analysis on a channel
dx_createtone( )
creates a new tone definition for a specific call progress tone
dx_deletetone( )
deletes a specific call progress tone
dx_querytone( )
returns tone information for a specific call progress tone
Voice API for Windows Operating Systems Library Reference — November 200325
Function Summary by Category
1.17Caller ID Functions
Caller ID functions are used to handle caller ID requests. Caller ID is enabled by setting a channelbased parameter in dx_setparm( ). See the Voice API Programming Guide for more information
about caller ID.
dx_gtcallid( )
returns the calling line directory number (DN)
dx_gtextcallid( )
returns the requested caller ID message by specifying the message type ID
dx_wtcallid( )
waits for rings and reports caller ID, if available
1.18File Manipulation Functions
These file manipulation functions map to C run-time functions, and can only be used if the file is
opened with the dx_fileopen( ) function. The arguments for these Intel® Dialogic® functions are
identical to the equivalent Microsoft* Visual C++ run-time functions.
dx_fileclose( )
closes the file associated with the handle
dx_fileerrno( )
obtains the system error value
dx_fileopen( )
opens the file specified by filep
dx_fileread( )
reads data from the file associated with the handle
dx_fileseek( )
moves a file pointer associated with the handle
dx_filewrite( )
writes data from a buffer into a file associated with the handle
1.19Echo Cancellation Resource Functions
The echo cancellation resource (ECR) feature is a voice channel mode that reduces the echo
component in an external TDM bus time slot signal. The echo cancellation resource functions
enable use of the ECR feature.
Note: The ECR functions have been replaced by the continuous speech processing (CSP) API functions.
CSP provides enhanced echo cancellation. For more information, see the Continuous Speech Processing API Programming Guide and Continuous Speech Processing API Programming Guide.
dx_getxmitslotecr( )
provides the TDM bus transmit time-slot number of the specified voice channel device when in
ECR mode
26Voice API for Windows Operating Systems Library Reference — November 2003
dx_listenecr( )
enables echo cancellation on a specified voice channel and connects the voice channel to the
echo-referenced signal on the specified TDM bus time slot (ECR mode)
dx_listenecrex( )
performs identically to dx_listenecr( ) and also provides the ability to modify the
characteristics of the echo canceller
dx_unlistenecr( )
disables echo cancellation on a specified voice channel and disconnects the voice channel from
the echo-referenced signal (SVP mode)
1.20Structure Clearance Functions
These functions do not affect a device. The dx_clrcap( ) and dx_clrtpt( ) functions provide a
convenient method for clearing the DX_CAP and DV_TPT data structures. These structures are
discussed in Chapter 4, “Data Structures”.
These functions are used with Intel® Dialogic® products that are licensed for specific telephony
patents held by Syntellect Technology Corporation. For more information, see the Voice API Programming Guide.
li_attendant( )
performs the actions of an automated attendant
li_islicensed_syntellect( )
verifies Syntellect patent license on board
1.22Extended Attribute Functions
Voice library extended attribute functions return information specific to the voice device specified
in the function call.
ATDX_ANSRSIZ( )
returns the duration of the answer detected during call progress analysis
ATDX_BDNAMEP( )
returns a pointer to the board device name string
ATDX_BDTYPE( )
returns the board type for the device
Voice API for Windows Operating Systems Library Reference — November 200327
Function Summary by Category
ATDX_BUFDIGS( )
returns the number of digits in the firmware since the last dx_getdig( ) for a given channel
ATDX_CHNAMES( )
returns a pointer to an array of channel name strings
ATDX_CHNUM( )
returns the channel number on board associated with the channel device handle
ATDX_CONNTYPE( )
returns the connection type for a completed call
ATDX_CPERROR( )
returns call progress analysis error
ATDX _C PT ER M( )
returns last call progress analysis termination
ATDX_CRTNID( )
returns the identifier of the tone that caused the most recent call progress analysis termination
ATDX_DEVTYPE( )
returns device type (board or channel)
ATDX _D TN FAI L( )
returns the dial tone character that indicates which dial tone call progress analysis failed to
detect
ATDX_FRQDUR( )
returns the duration of the first special information tone (SIT) frequency
ATDX_FRQDUR2( )
returns the duration of the second special information tone (SIT) frequency
ATDX_FRQDUR3( )
returns the duration of the third special information tone (SIT) frequency
ATDX_FRQHZ( )
returns the frequency of the first detected SIT
ATDX_FRQHZ2( )
returns the frequency of the second detected SIT
ATDX_FRQHZ3( )
returns the frequency of the third detected SIT
ATDX_FRQOUT( )
returns the percentage of frequency out of bounds detected during call progress analysis
ATDX _F WV ER ( )
returns the firmware version
ATDX_HOOKST( )
returns the current hook state of the channel
ATDX_LINEST( )
returns the current line status of the channel
ATDX _L ON GL OW( )
returns the duration of longer silence detected during call progress analysis
28Voice API for Windows Operating Systems Library Reference — November 2003
Function Summary by Category
ATDX_PHYADDR( )
returns the physical address of board
ATDX_SHORTLOW( )
returns the duration of shorter silence detected during call progress analysis
ATDX_SIZEHI( )
returns the duration of non-silence detected during call progress analysis
ATDX_STATE( )
returns the current state of the device
ATDX_TERMMSK( )
returns the reason for last I/O function termination in a bitmap
ATDX_TONEID( )
returns the tone ID (used in global tone detection)
ATDX_TRCOUNT( )
returns the last record or play transfer count
1.23Voice Function Support by Platform
Table 1 provides an alphabetical listing of voice API functions. The table indicates which platforms
(DM3 or Springware) are supported for each of the functions.
DM3 boards refers to products based on the Intel® DM3 mediastream architecture. Typically DM3
board names have the prefix “DM,” such as Intel® NetStructure™ DM/V2400A-PCI. Springware
boards refer to boards based on earlier-generation architecture. Typically Springware board names
have the prefix “D,” such as Intel® Dialogic® D/240JCT-T1.
Although a function may be supported on both DM3 and Springware boards, there may be some
restrictions on its use. For example, some parameters or parameter values may not be supported.
For details, see the function reference descriptions in Chapter 2, “Function Information”.
Table 1. Voice Function Support by Platform
FunctionDM3Springware
ag_getctinfo( )NSS
ag_getxmitslot( )NSS
ag_listen( )NSS
ag_unlisten( )NSS
ai_close( )SNS
ai_getxmitslot( )SNS
NS = Not supported
S = Supported
* = Variances between platforms; refer to the function reference for more information.
† = Asynchronous and synchronous mode supported (all other functions support synchronous mode only)
‡ = On DM3, call progress analysis is available directly through dx_dial( ).
Voice API for Windows Operating Systems Library Reference — November 200329
Function Summary by Category
Table 1. Voice Function Support by Platform (Continued)
FunctionDM3Springware
ATDX_ANSRSIZ( )NSS
ATDX_BDNAMEP( )SS
ATDX_BDTYPE( )SS
ATDX_BUFDIGS( )SS
ATDX_CHNAMES( )SS
ATDX_CHNUM( )SS
ATDX_CONNTYPE( )SS
ATDX_CPERROR( )SS
ATDX_CPTERM( )SS
ATDX_CRTNID( )NSS
ATDX_DEVTYPE( )SS
ATDX _DTN FAI L( )NSS
ATDX_FRQDUR( )NSS
ATDX_FRQDUR2( )NSS
ATDX_FRQDUR3( )NSS
ATDX_FRQHZ( )NSS
ATDX_FRQHZ2( )NSS
ATDX_FRQHZ3( )NSS
ATDX_FRQOUT( )NSS
ATDX _FW VER( )NSS
ATDX_HOOKST( )NSS
ATDX _LIN EST ( )NSS
ATDX_LONGLOW( )NSS
ATDX_PHYADDR( )NSS
ATDX_SHORTLOW( )NSS
ATDX _SI ZEHI( )NSS
ATDX _STATE( )SS
ATDX _TE RMM SK( )SS
ATDX_TONEID( )SS
ATDX_TRCOUNT( )SS
dx_addspddig( )S *S
dx_addtone( )S *S
NS = Not supported
S = Supported
* = Variances between platforms; refer to the function reference for more information.
† = Asynchronous and synchronous mode supported (all other functions support synchronous mode only)
‡ = On DM3, call progress analysis is available directly through dx_dial( ).
30Voice API for Windows Operating Systems Library Reference — November 2003
Loading...
+ 534 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.