User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 405
Dialogic Corporation
event is reported. On both types of boards a DE_TONEOFF event is reported when the tone is no
longer present.
Update to Section 13.1.9, Guidelines for Creating User-Defined Tones (IPY00006580
= PTR# 34546)
The following guideline should be added to this section:
On Dialogic
®
DM3 Boards, building and adding tones of zero frequency values to a tone
template can cause firmware failures.
Update to Section 13.1.10.2, Detecting Leading Edge Debounce Time (IPY00006581
= PTR# 35616)
The values currently listed in this section apply to Dialogic
®
DM3 Boards. The
following text should be added for Dialogic
®
Springware Boards:
On Dialogic
®
Springware Boards, to detect leading edge debounce time, specify the following
values for the dx_bldstcad( ) or dx_blddtcad( ) function parameters listed below:
For ontime, specify the desired debounce time.
For ontdev, specify 3.
For offtime, specify 0.
For offtdev, specify 0.
For repcnt, specify 1.
Update to Section 14.3, Enabling Global DPD
Because of a new feature in the Service Update, it is no longer necessary to order a
separate GDPD enablement package to enable Global Dial Pulse Detection on a
board. Information about the GDPD enablement package should be removed from
this section. See Section 1.7, “Global DPD Enabled on Dialogic
®
Springware Boards”,
on page 54of this Release Update for further information.
Update to Chapter 17, Building Applications (PTR# 32966)
Run-time linking using the source code in the CLIB subdirectory is no longer
supported. Run-time linking can be accomplished using Windows
®
functions. In the
Dialogic
®
Voice API Programming Guide, Section 17.2.3, Run-time Linking, should
be revised as follows:
Run-time linking resolves the entry points to the Dialogic
®
DLLs when the application is loaded
and executed. This allows the application to contain function calls that are not contained in the
DLL that resides on the target system.
To use run-time linking, the application can call the Windows
®
LoadLibrary( ) function to load a
specific technology DLL and a series of GetProcAddress( ) function calls to set up the address
pointers for the functions.
3.5 Demonstration Software Documentation
This section contains updates to the following documents (click the title to jump to the
corresponding section):
Dialogic
®
IP Multicast Client (IPML) Demo Guide
Dialogic
®
IP Multicast Server (IPML) Demo Guide