•When recording VOX files, the data format is specified in DC_XPB rather than through the dx_setparm( ) function.
•Voice data files that are specified in the DX_IOTT structure must be opened with the O_BINARY flag.
•If both time slots transmit a DTMF digit at the same time, the recording will contain an unintelligible result.
•Since this function uses dx_listen( ) to connect the channel to the first specified time slot, any error returned from dx_listen( ) will terminate the function with the error indicated.
•This function connects the channel to the time slot specified in the SC_TSINFO data structure sc_tsarrayp[0] field and remains connected after the function has completed. Both sc_tsarrayp[0] and sc_tsarrayp[1] must be within the range allowed in SC_TSINFO. No checking is done to verify that sc_tsarrayp[0] or sc_tsarrayp[1] has been connected to a valid channel.
•Upon termination of the dx_mreciottdata( ) function, the recording channel continues to listen to the first time slot (pointed to by sc_tsarray[0]).
•The application should check for a TDX_RECORD event with T_STOP event data after executing a dx_stopch( ) function during normal and transaction recording. This will ensure that all data is written to the disk.
•When using dx_mreciottdata( ) and a dial tone is present on one of the time slots, digits will not be detected until dial tone is no longer present. This is because the DSP cannot determine the difference between dial tone and DTMF tones.
•Tone termination conditions such as DTMF and TONE apply only to the primary input of the function; that is, the TDM time slot specified in the SC_TSINFO data structure sc_tsarrayp[0] field.
Errors
If the function returns
EDX_BADDEV Invalid device handle
EDX_BADIOTT
Invalid DX_IOTT entry
EDX_BADPARM
Invalid parameter passed
EDX_BADTPT
Invalid DV_TPT entry
EDX_BUSY
Busy executing I/O function
EDX_SYSTEM
Error from operating system
HMP Linux 1.2 Release Update, Rev 05 — September 2006September 2006 | 36 |