Installation guide

Dialogic
®
System Release 6.1 CompactPCI for Windows
®
Release Update 159
Speed control on Dialogic
®
DM3 Boards using 6 kHz coders
The following coders are now supported and should be added to Section 9.1, Speed
and Volume Control Overview:
• OKI ADPCM 24 kbps (6 kHz 4-bit)
• G.711 PCM A-law 48 kbps (6 kHz 8-bit)
• G.711 PCM mu-law 48 kbps (6 kHz 8-bit)
3.4.20 Dialogic
®
Voice API Library Reference
Functions not supported
The r2_creatfsig( ) and r2_playbsig( ) functions, which were previously provided for
backward compatibility only, are no longer supported. All references to these
functions should be deleted. R2MF signaling is typically accomplished through the
Dialogic
®
Global Call API.
Update to dx_getdig( ) (IPY00038453)
For Dialogic
®
DM3 Boards, the return value of dx_getdig( ) in synchronous mode has
been changed to return 0 instead of 1 when there are no digits in the buffer. The
NULL character in the digit string ‘dg_value’ is no longer counted as a digit. Similarly,
when dx_getdig( ) returns the number of digits, the terminating NULL is no longer
added to the number of digits. (The NULL was previously counted in the numdig
return value calculation, but since it is not a digit, the NULL is no longer included.)
For Dialogic
®
Springware Boards, the terminating NULL is included in the number of
digits. So for Springware Boards, dx_getdig( ) still returns 1 when there are no digits
in the buffer.
Update to dx_OpenStreamBuffer( ) (IPY00044981)
The following caution should be added for dx_OpenStreamBuffer( ):
• When using Dialogic
®
DM3 Boards, the dx_open( ) function must be called on a
board, channel, or physical board before dx_OpenStreamBuffer( ) is called.
Failure to do so would prevent the DM3 library from loading, and
dx_OpenStreamBuffer( ) would fail.
Update to dx_rec( ), dx_reciottdata( ), dx_recvox( ), and dx_recwav( )
The dx_rec( ), dx_reciottdata( ), dx_recvox( ), and dx_recwav( ) 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, voice channels
must be listening to a TDM bus time slot in order for voice recording functions,
such as dx_reciottdata( ) and others, to work. The actual recording operation will
start only after the voice 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 a voice recording function for that device handle, and the
dx_listen( ) has to be called from the same process as the voice recording
function. If not, the voice recording function will return TDX_ERROR with
EDX_SH_MISSING as the termination reason.