6. Compatibility Issues

The following compatibility issues necessitate changes to applications developed using the NetTSC embedded stack implementation in order to run on the host-based stack implementation in System Release 6.0:

• The config.val file is no longer being used. Parameters previously configurable in config.val are now configurable using Global Call API functions. See Chapter 4. config.val File Redundancy for more information.
• In the embedded stack implementation, when using gc_OpenEx( ), the protocol identifier in the numberstr parameter is P_H323_R and each IP Media device (ipmBxCy) is bound to the corresponding IP network device (iptBxTy), that is BxCy = BxTy. In the host-based stack implementation, the protocol identifier is P_H323 and the IP Media device is not bound to a corresponding IP network device.
• The gc_SetConfigData( ) function uses different target types and target IDs in the different implementations as follows:
  • In the NetTSC embedded stack implementation, the target type is GCTGT_PROTOCOL_SYSTEM and the target ID (protocol ID) had to be retrieved using the gc_QueryConfigData( ) function.
  • In the host-based stack implementation, the target type is GCTGT_CCLIB_NETIF and the target ID is the board device ID.
  
  In addition, parameter settings apply not only to newly opened devices but also to devices already opened. See the Global Call IP Technology User's Guide for more information.

• In the NetTSC embedded stack implementation, the GCEV_EXTENSION event had a dual role acting as the completion event for the gc_Extension( ) function and as an unsolicited event. In the host-based stack implementation, the completion event for gc_Extension( ) is GCEV_EXTENSIONCMPLT. The GCEV_EXTENSION event is reserved for unsolicited events only.
• In the NetTSC embedded stack implementation, the number of IP network devices allocated depended on the number and type of Intel® NetStructureTM DM/IP boards in the system. In the host-based stack implementation, the number of IP network devices that will be allocated is configurable using the IPCCLIB_START_DATA structure associated with the gc_Start( ) function. See Section 4.1. Setting Stack Allocation Parameters for more information.
• In System Release 6.0, the usage of IPPARM_UII_ALPHANUMERIC is different than in the NetTSC embedded stack implementation. See Section 6.4. UII Alphanumeric Parameter Usage below for more detail.

Click here to contact Telecom Support Resources