Installation guide
Table Of Contents
- About This Publication
- Document Revision History
- 1. Post-Release Developments
- 1.1 Service Update for Dialogic® System Release 6.1 CompactPCI for Windows®
- 1.2 PDK Support for Automatic Answer and Reject of Inbound Calls
- 1.3 Status Monitor Tool Support for 16 Span Boards
- 1.4 Improvement to Call Progress Analysis
- 1.5 Media Load Support for the Dialogic® DM/V1200A- 4E1-cPCI Board
- 1.6 Handling non-2xx Responses to T.38 Switch
- 1.7 Important Notice about System Release Update Installation
- 1.8 Media LAN Disconnection Alarm Notification for Dialogic® DM/IP Boards
- 1.9 Support for SFTP in Dialogic® Global Call SS7 Call Control Library
- 1.10 New Media Loads for Dialogic® DM/V4800BC Media Boards Using Special Coders
- 1.11 File Management Enhancements for DebugAngel Tool
- 1.12 File Management Enhancements for PDK Trace Tool
- 1.13 Configuring SIP Stack Parameters with Global Call
- 1.14 Disabling Automatic re-INVITE Message when Switching between Fax and Audio
- 1.15 IP Multicast Client Support
- 1.16 Troubleshooting Information for RTF Logs
- 1.17 Remote Diagnostics Package
- 1.18 Enhanced Diagnostics Tools
- 1.19 New QoS Alarms for RTCP and RTP Inactivity
- 1.20 New Operating System Support
- 1.21 Support for Compute Platforms
- 1.22 New Parameter for Adjusting Silence Threshold on Dialogic® DM3 Boards
- 1.23 File Management Enhancements for ISDNtrace Tool
- 1.24 New Media Loads for Dialogic® DM/V2400A-cPCI and DM/V4800BC Media Boards
- 1.25 Modified Alarm Events for Media LAN Disconnect
- 1.26 Enhancement to its_sysinfo Tool
- 1.27 Modify an Existing SIP Call Using re-INVITE for Dialogic® IPT Boards
- 1.28 PDK Log File Detection
- 1.29 Media Channel Reset Capability (Stuck IP Media Channel Recovery)
- 1.30 Dialogic® Global Call API Access to New H.323/Q.931 Message IEs
- 1.31 On-Demand Full Reset of Dialogic® DM3 Boards
- 1.32 New Dialogic® Diagnostics Management Console
- 1.33 New Runtime Trace Facility (RTF) Manager
- 1.34 Support for Reporting Billing Type
- 1.35 Runtime Control of Double Answer for R2MF
- 1.36 Additional Supported Operating System Security Updates
- 1.37 Media Channel Reset Capability (Stuck Channel Recovery)
- 1.38 Notification of Layer 1 Alarm Events on Dialogic® SS7 Boards
- 1.39 Dialogic® Global Call Support for Time Slots on Dialogic® SS7 Boards Running in DTI Mode
- 2. Release Issues
- 3. Documentation Updates
- 3.1 System Release Documentation Updates
- 3.2 Installation and Configuration Documentation Updates
- 3.2.1 Dialogic® System Release 6.1 CompactPCI for Windows® Software Installation Guide
- 3.2.2 Dialogic® DM3 Architecture for CompactPCI on Windows® Configuration Guide
- 3.2.3 Dialogic® IPT Series on Windows® Configuration Guide
- 3.2.4 Dialogic® Global Call Country Dependent Parameters (CDP) for PDK Protocols Configuration Guide
- 3.3 OA&M Documentation Updates
- 3.3.1 Dialogic® System Release 6.1 CompactPCI for Windows® Administration Guide
- 3.3.2 Dialogic® SNMP Agent Software for Windows® Administration Guide
- 3.3.3 Dialogic® System Software Diagnostics Guide
- 3.3.4 Dialogic® Board Management API Library Reference
- 3.3.5 Dialogic® Event Service API Programming Guide
- 3.3.6 Dialogic® Event Service API Library Reference
- 3.3.7 Dialogic® Native Configuration Manager API Programming Guide
- 3.3.8 Dialogic® Native Configuration Manager API Library Reference
- 3.4 Programming Libraries Documentation Updates
- 3.4.1 Dialogic® Audio Conferencing API Programming Guide
- 3.4.2 Dialogic® Audio Conferencing API Library Reference
- 3.4.3 Dialogic® Continuous Speech Processing API Programming Guide
- 3.4.4 Dialogic® Continuous Speech Processing API Library Reference
- 3.4.5 Dialogic® Digital Network Interface Software Reference
- 3.4.6 Dialogic® Fax Software Reference
- 3.4.7 Dialogic® Global Call API Programming Guide
- 3.4.8 Dialogic® Global Call API Library Reference
- 3.4.9 Dialogic® Global Call E1/T1 CAS/R2 Technology Guide
- 3.4.10 Dialogic® Global Call IP Technology Guide
- 3.4.11 Dialogic® Global Call ISDN Technology Guide
- 3.4.12 Dialogic® Global Call SS7 Technology Guide
- 3.4.13 Dialogic® IP Media Library API Programming Guide
- 3.4.14 Dialogic® IP Media Library API Library Reference
- 3.4.15 Dialogic® Modular Station Interface API Programming Guide
- 3.4.16 Dialogic® Modular Station Interface API Library Reference
- 3.4.17 Dialogic® Standard Runtime Library API Programming Guide
- 3.4.18 Dialogic® Standard Runtime Library API Library Reference
- 3.4.19 Dialogic® Voice API Programming Guide
- 3.4.20 Dialogic® Voice API Library Reference
- 3.5 Demonstration Software Documentation Updates
- 3.5.1 Dialogic® Continuous Speech Processing API Demo Guide
- 3.5.2 Dialogic® Global Call API Demo Guide
- 3.5.3 Dialogic® High Availability for Windows® Demo Guide
- 3.5.4 Dialogic® IP Gateway (Global Call) Demo Guide
- 3.5.5 Dialogic® IP Media Server (Global Call) Demo Guide
- 3.5.6 Dialogic® IP Media Gateway (IPML) Demo Guide
Dialogic
®
System Release 6.1 CompactPCI for Windows
®
Release Update 143
3.4.2 Dialogic
®
Audio Conferencing API Library Reference
There are currently no updates to this document.
3.4.3 Dialogic
®
Continuous Speech Processing API
Programming Guide
There are currently no updates to this document.
3.4.4 Dialogic
®
Continuous Speech Processing API Library
Reference
Update to ec_reciottdata( ) and ec_stream( )
The ec_reciottdata( ) and ec_stream( ) function reference pages contain a caution
about channels getting stuck when failing to listen to a TDM bus time slot prior to
invoking a record operation. The caution should be revised: this condition now returns
an error rather than resulting in a stuck channel. The revised caution is:
• On Dialogic
®
DM3 Boards using a flexible routing configuration, CSP channels
must be listening to a TDM bus time slot in order for the ec_reciottdata( ) and
ec_stream( ) functions to work. The actual recording operation will start only after
the channel is listening to the proper external time slot. In other words, you must
issue a dx_listen( ) function call on the device handle before calling
ec_reciottdata( ) or ec_stream( ) for that device handle, and the dx_listen( )
has to be called from the same process as the ec_reciottdata( ) or ec_stream( ).
If not, the ec_reciottdata( ) or ec_stream( ) function will return TEC_STREAM
with EDX_SH_MISSING as the termination reason.
3.4.5 Dialogic
®
Digital Network Interface Software Reference
There are currently no updates to this document.
3.4.6 Dialogic
®
Fax Software Reference
There are currently no updates to this document.
3.4.7 Dialogic
®
Global Call API Programming Guide
There are currently no updates to this document.
3.4.8 Dialogic
®
Global Call API Library Reference
Update to gc_GetFrame( )
In the code example, under
/* Retrieve events from SRL */
change this: