Compatibility Guide for the R4 API on DM3 Table of Contents

• 1. Introduction to this Publication
• 1.1. How This Guide is Organized
• 1.2. Related Publications and Information
• 2. The Dialogic R4 API for DM3
• 2.1. Introduction to R4 for DM3
• 2.2. Feature Overview of R4 for DM3
• 2.2.1. Basic System Features Supported
• 2.2.2. Basic SCbus Routing Features Supported
• 2.2.3. Basic Voice Features Supported
• 2.2.4. Basic GlobalCall Call Control Features Supported
• 2.2.5. Basic DTI Network Interface Features Supported
• 2.2.6. Basic Fax Features Supported
• 2.2.7. Basic DCB Audio Conferencing Features Supported
• 2.2.8. Basic MSI Features Supported
• 2.2.9. Basic Audio Input Features Supported
• 2.3. Configuration, Initialization, and Operation
• 2.3.1. Device Initialization Hint
• 2.3.2. Component Interoperation
• 2.3.3. Board Device Names and Numbers
• 2.3.4. Compatibility of Device Names/Numbers
• 2.3.5. Determining Channel Capabilities in Flexible Routing Configurations
• 2.3.6. Getting, Using, and Closing Device Handles in a DM3 Flexible Routing Configuration
• 3. R4 SCbus Routing API for DM3
• 3.1. Basic SCbus Routing Features Not Supported and Partially Supported
• 3.2. SCbus Routing API Function Restrictions
• 3.3. CT_DEVINFO: Channel/Timeslot Device Information Data Structure
• 3.4. CT Bus Timeslot Application Considerations
• 4. R4 Voice API for DM3
• 4.1. Voice API Features Not Supported (By Category)
• 4.1.1. Tone Detection/Generation Features Not Supported
• 4.1.2. Pulse Detection/Generation Features Not Supported
• 4.1.3. Analog Line Handling Features Not Supported
• 4.1.4. Call Management Features Not Supported
• 4.1.5. Play/Record Limitations and Features Not Supported
• 4.1.6. Running Transaction Record
• 4.1.7. Miscellaneous Features Not Supported
• 4.2. Voice API Features Partially Supported
• 4.3. Voice API Function and Parameter Restrictions
• 4.3.1. Voice API Function Restrictions
• 4.3.2. Speed and Volume Control Restrictions
• 4.3.3. DV_TPT Termination Parameter Table Restrictions
• 4.3.4. Device Parameter Restrictions
• 4.4. Coder Enhancements
• 4.4.1. DX_XPB Parameters
• 4.5. New Silence Compression Record Functionality
• 4.6. Voice API Call Progress Analysis Support
• 4.6.1. Support and Scenarios for Call Analysis with dx_dial( )
• 4.7. Support for ADSI 2-Way FSK
• 4.7.1. ADSI_XFERSTRUC: ADSI Data Buffer
• 4.7.2. ADSI API Functions
• dx_RxIottData( )
• dx_TxIottData( )
• dx_TxRxIottData( )
• 5. R4 GlobalCall API for DM3
• 5.1. GlobalCall Features Not Supported by R4 for DM3
• 5.2. GlobalCall Call State Model Restrictions
• 5.3. gc_Open( ) and gc_OpenEx( ) Restrictions
• 5.4. Associating Network and Voice Devices
• 5.5. Analog Call Analysis
• 5.6. Call Progress and Call Analysis
• 5.6.1. Support and Scenarios for Call Analysis with GlobalCall
• 5.7. gc_ResetLineDev( ) Operation
• 5.8. Layer 1 Alarms
• 5.9. ISDN Feature Implementation and Support
• 5.9.1. gc_MakeCall( ) Restrictions
• 5.9.2. gc_GetNetCRV( ) Restrictions
• 5.9.3. gc_SndMsg( ) Restrictions
• 5.9.4. Send and Receive Any IE and Any Message
• 5.9.5. Overlap Send
• 5.9.6. Direct Layer 2 Access
• 5.9.7. D Channel Status
• 5.9.8. B Channel Status
• 5.10. Handling Multiple Call Objects Per Channel
• 5.11. Using E-1 CAS R2MF Protocols with R4 on DM3
• 5.12. Country Dependent Parameter (CDP) Files
• 5.13. Using gc_MakeCall( ) with a DI/0408-LS-A
• 5.14. GlobalCall API Function Restrictions
• 6. R4 DTI API for DM3
• 6.1. DTI Network Interface API Function Restrictions
• 6.2. Detecting Layer 1 Alarms
• 7. R4 Fax API for DM3
• 7.1. Fax Device Information
• 7.1.1. Use Fax Handles Only for Fax Commands
• 7.1.2. Opening Board Devices Not Supported
• 7.1.3. Using Multiple Handles
• 7.2. Fax API Features Not Supported
• 7.3. Fax API Function Restrictions
• 7.4. Fax Data Structure Restrictions
• 7.5. Fax API Enhancements
• 7.5.1. ATFX_CHTYPE( )
• 7.5.2. ATFX_RESLN( )
• 7.5.3. ATFX_WIDTH( )
• 7.5.4. fx_setparm( )
• 7.6. Color Fax
• 7.6.1. Color Fax Features
• 7.6.2. Using the Fax API Library for Color Fax
• 7.7. Support for fx_originate( )
• fx_originate( )
• 7.8. Support for fx_getctinfo( )
• fx_getctinfo( )
• 8. R4 DCB API for DM3
• 8.1. DCB Audio Conferencing API Features Not Supported
• 8.2. DCB Audio Conferencing API Function Restrictions
• 8.2.1. DCB Parameters Restricted and Not Supported
• 8.3. Enhancements for dcb_getbrdparm( )
• 8.3.1. Tone Clamping
• 8.3.2. Retrieving the Interval for Active Talker Notification Events
• 8.4. Enhancements for dcb_setbrdparm( )
• 8.4.1. Tone Clamping
• 8.4.2. Changing the Interval for Active Talker Notification Events
• 8.5. DCB Audio Conferencing API Enhancements for DM3 Boards
• 8.5.1. New DCB Conferencing Party Attribute Parameters
• 8.5.2. New DCB Functions
• dcb_DeleteAllConferences( )
• dcb_GetAtiBitsEx( )
• 9. R4 MSI API for DM3
• 9.1. MSI API Function Restrictions
• 9.1.1. MSI API Parameters Not Supported
• 9.2. New Functions for CallerID
• ms_genringCallerID( )
• ms_SetMsgWaitInd( )
• 10. R4 Audio Input API for DM3
• 10.1. AI API Functions
• ai_open( )
• ai_close( )
• ai_getxmitslot( )
• 10.2. Determining the Number of AI Devices in a System
• 11. Implementing Applications for R4 on DM3
• 11.1. General Considerations for Developing or Porting R4 on DM3 Applications
• 11.1.1. Using GlobalCall for Call Control
• 11.1.2. DTI API versus GlobalCall
• 11.1.3. ISDN Primary Rate API versus GlobalCall
• 11.1.4. Programming Models in Linux
• 11.2. Multi-Threading and Multi-Processing
• 11.3. Initializing an R4 on DM3 Application
• 11.3.1. Initializing the GlobalCall API for DM3 Boards Only (Flexible Routing)
• 11.3.2. Device Discovery for DM3 Boards and Earlier-Generation Boards (Flexible Routing)
• 12. R4 on DM3 Resource Routing and Cluster Configuration
• 12.1. Fixed and Flexible Routing Configurations
• 12.1.1. Selecting a Fixed or Flexible Routing Configuration
• 12.1.2. Overview of DM3 Clusters
• 12.2. Additional API Restrictions in an R4 on DM3 Fixed Routing Configuration
• 12.3. Using the GlobalCall API in an R4 on DM3 Fixed Routing Configuration
• 12.3.1. gc_Open( ) and gc_OpenEx( ) Restrictions (Fixed Routing)
• 12.3.2. Associating Network and Voice Devices (Fixed Routing)
• 12.3.3. ISDN Direct Layer 2 Access (Fixed Routing)
• 12.4. Operating in an R4 on DM3 Fixed Routing Configuration
• 12.4.1. Interoperability with DM3 Application Foundation Code
• 12.4.2. Getting, Using, and Closing Device Handles in a DM3 Fixed Routing Configuration
• 12.5. Implementing Applications in an R4 on DM3 Fixed Routing Configuration
• 12.5.1. Porting an Application to R4 on DM3 with Fixed Routing
• 12.5.2. Initializing an Application Under Different Hardware and API Scenarios (Fixed Routing)
• 12.5.3. Porting the PANSR Demonstration Program to R4 for DM3 with Fixed Routing
• Appendix A
• CPA Default Tone Templates
• Copyright notice