7. Enhanced Functionality

The host-based stack implementation in System Release 6.0 includes the following enhancements over the NetTSC embedded stack implementation:

• Support for both H.323 and SIP protocols
• Support for RFC2833.
• Support for T.38 fax.
• In the host-based stack implementation, both Transmit and Receive coders can be specified. In the NetTSC embedded stack implementation, only Transmit coders could be specified.
• The behavior of the gc_SetUserInfo( ) with the GC_SINGLECALL (per call basis) and GC_ALLCALLS (per device basis) options is different as follows:
  • In the NetTSC embedded stack implementation, only coder information could be set using GC_ALLCALLS (per line device basis); all other information could be set using GC_SINGLECALL only (per call basis).
  • In the host-based stack implementation, all parameters (coder info, conference goal, connection method, display information, nonstandard data, nonstandard control, phone list, tunneling, and user-to-user information) can be set using both GC_SINGLECALL and GC_ALLCALLS.
• In the NetTSC embedded stack implementation, the Proceeding message was sent automatically by the stack. In the host-based stack implementation, the application can determine if the Proceeding message should be sent manually or automatically by the stack. See Section 7.1. Specifying Automatic or Manual Sending of the Proceeding Message below for more detail.
• In the NetTSC embedded stack implementation, routing using gc_Listen( ), gc_UnListen( ) had to be done in synchronous mode, but these functions were non-blocking. In the host-based stack implementation, it is recommended to use gc_Listen( ) and gc_Unlisten( ) in asynchronous mode. Using gc_Listen( ) and gc_UnListen( ) in synchronous mode is supported, but these functions are blocking in the host-based implementation.

Click here to contact Telecom Support Resources