1.13. Controlling the Sending of SETUP_ACK and PROCEEDING

Depending on the board architecture used (DM3 or Springware), the default behavior of the firmware when a SETUP message is received (inbound calls) is different:

• When using DM3 boards, by default, the firmware automatically sends a SETUP_ACK message if there is no sending complete IE in the received SETUP message. When a SETUP message with a sending complete IE is received, the application must use the gc_CallAck( ) function to issue the PROCEEDING message to the other side.
• When using Springware boards, by default, the firmware automatically sends a SETUP_ACK message if there is no sending complete IE in the received SETUP message. When a SETUP message with a sending complete IE is received, the firmware automatically sends the PROCEEDING message to the other side; no intervention by the application is necessary.

A bitmask, that is configurable using the gc_SetEvtMsk( ) function, and is applicable when using both DM3 and Springware boards, allows an application developer to modify the default behavior described above. A set of bitmask values can be ORed to mask or unmask the corresponding events. The following bit mask value can be used to mask both the SETUP_ACK and PROCEEDING events:

    GCMSK_PROC_SEND (0x80)  

To get full control over the sending of SETUP_ACK and PROCEEDING messages, during startup, an application can issue the following function call:

    gc_SetEvtMask(..., GCACT_ADDMSK, ..., (GCMSK_PROC_SEND), ...) 

Then, the application must use gc_CallAck( ) to send the SETUP_ACK message and gc_CallAck( ) again to send the PROCEEDING message. Using this technique will ensure that an application is compatible on both DM3 and Springware boards.

Note: When using Springware boards, on outbound calls, the GCMSK_SETUP_ACK bit mask value can be used to enable or disable the sending of the GCEV_SETUP_ACK to the application. When using DM3 boards, GCMSK_SETUP_ACK is not supported.

Click here to contact Telecom Support Resources