• 6.3.1. IPTMAIL_QUIT State
• 6.3.2. Errors from IP
• 6.3.3. Errors from Voice Resources:

6.3. Error Handling

Figure 6. Error Handling-GCEV_DISCONNECTED

Figure 7. Error Handling-GCEV_TASKFAIL

6.3.1. IPTMAIL_QUIT State

The application waits for either a TDX_PLAY or a TDX_RECORD event.

Upon receiving either event, the application gets the termination reason, unroutes the call, and closes the voice and IP devices. If all voice devices are closed, the application exits.

6.3.2. Errors from IP

The error might occur in different phases:

• If the called function returns a <0 , first process the error [by calling: gc_ErrorValue( ), gc_ResultMsg( ) ] and then end the call or exit the application.
• If the function was called successfully, but GCEV_TASKFAIL event is received later, indicating that the function failed, the application will be terminated

6.3.3. Errors from Voice Resources:

• The main error which could be received while calling the R4 function toward the Voice Resources is represented by the TDX_ERROR event
• The IPTMail_R4 demo drops the call after receiving this error.

Click here to contact Dialogic Customer Engineering