• 4.6.1. Support and Scenarios for Call Analysis with dx_dial( )

4.6. Voice API Call Progress Analysis Support

The voice API supports Call Progress Analysis as follows:

• The R4 voice API on DM3 supports Call Progress Analysis through the dx_dial( ) function.
• The dx_dial( ) function does not support dial tone detection. Therefore, the PerfectCall dial tone detection tone definitions are not used: TID_DIAL_LCL, TID_DIAL_INTL, and TID_DIAL_XTRA.
• The supported special control characters in the dial string are T (DTMF tone dial mode, default), M (MF tone dial mode), and comma (, pause for 2 seconds). The other special control characters--&, P, L, I, and X--are either ignored or return an error. For example, P (Pulse dial mode) returns an error; the others (L, I, X) are ignored. All valid DTMF (0-9, a-d, *, #) and MF (0-9, a-c, *, #) are supported. dx_dial( ) fails if 'd' is present in MF dial string (as d is not a valid MF character).

  NOTE:

  MF is supported for dialing, but not for detection.

• Only the following fields of the DX_CAP structure are supported:

Field Name	Default
ca_intflg	DX_OPTEN
ca_noanswer	3000 Units: 10 ms
ca_cnosig	4000 Units: 10 ms
ca_pamd_failtime	400 Units: 10 ms

• The default PerfectCall Call Progress Analysis tones that are used by dx_dial( ) cannot be modified (for example, BUSY, BUSY_FAST, and so on). That is, dx_chgdur( ), dx_chgfreq( ), dx_chgrepcnt( ), and dx_initcallp( ) are not supported. Note that these default tones differ from those used in R4 and previous releases of R4 on DM3. Complete data on the supported tone templates can be found in Appendix A.

The extended attribute functions that provide call analysis information and are supported on R4 on DM3 do not return information related to functionality that is not supported by R4 on DM3; for example:

• ATDX_CONNTYPE( ) connection type CON_LPC
• ATDX_CPTERM( ) termination reason CR_NODIALTONE

4.6.1. Support and Scenarios for Call Analysis with dx_dial( )

Table 9 provides information on what specific Call Analysis scenarios are supported with the voice function dx_dial( ). To invoke dx_dial( ) under CAS, your application must wait for the connected event. This method is available regardless of the protocol being used; however, some restrictions apply when using DM3 CAS protocols. The restrictions are due to the fact that the voice capability is shared between the network device and the voice channel during the call setup time.

NOTE:

The information in this section also applies to DI products, which are considered to use CAS protocols.

Table 9. dx_dial( ) Call Analysis Support

CA Feature	dx_dial( ) Support in R4 on DM3	Comments
Busy	Ö	CAS protocols: not supported
No Ringback	Ö	CAS protocols: not supported
SIT	Ö	CAS protocols: not supported
No answer	Ö	CAS protocols: not supported
Cadence break	Ö	CAS protocols: not supported
Discarded	None
NA	None
Unknown	None
PVD	Ö	CAS protocols: Wait for the GCEV_CONNECTED event. Only the following fields of the DX_CAP structure are supported: ca_intflg, ca_cnosig, ca_noanswer, and ca_pamd_failtime.
PAMD	Ö	CAS protocols: Wait for the GCEV_CONNECTED event. Only the following fields of the DX_CAP structure are supported: ca_intflg, ca_cnosig, ca_noanswer, and ca_pamd_failtime.
FAX	Ö	CAS protocols: Wait for the GCEV_CONNECTED event. Only the following fields of the DX_CAP structure are supported: ca_intflg, ca_cnosig, ca_noanswer, and ca_pamd_failtime.
In progress	None

For information on using GlobalCall for Call Analysis, see Section 5.6. Call Progress and Call Analysis.

Click here to contact Dialogic Customer Engineering