Siebel Communications Server Administration Guide > Developing a Communications Driver >
Custom Driver Upgrade Issues
This section describes issues that may apply if you are supporting or updating custom communications drivers originally written for a Siebel Business Applications release 7.x that is earlier than version 7.7; that is, for drivers written for version 7.0.x or version 7.5.x.
Communications drivers for prior 7.x releases will not work as is with version 7.7.x, unless you follow the guidelines in this section. Version 7.7.x requires version 2 of the Siebel Adaptive Communications API (as did version 7.5.x).
Requirements that may apply for your custom communications driver are as follows:
- On all supported platforms, for any communications driver written for version 7.0.x, you must compile the driver using the current version of the API. A version 7.0.x communications driver cannot work with version 7.7.x of the Siebel Business Applications, due to version checking. For drivers from version 7.5.x, this requirement will already have been met.
- For drivers on all supported platforms, the driver handle method FreeSCStrParamList must be implemented. For any driver for version 7.0.x or 7.5.x, if you previously did not implement this method to function as described, then you must implement it, and recompile your driver. If you previously implemented this method, then this requirement may not apply. For more information about this method, see Methods of ISC_DRIVER_HANDLE.
- For Sun Solaris platforms, you must use UTF16, in order to support Unicode, rather than UCS4 (as was used in version 7.0.x). For any driver on this platform for version 7.0.x, you must modify your driver code, and recompile your driver. For drivers from version 7.5.x, this requirement will already have been met.