Siebel CTI Administration Guide > Developing a Communications Driver >

Custom Driver Upgrade Issues

This topic describes issues that might apply if you are supporting or updating custom communications drivers originally written for a Siebel CRM release 7.x that is earlier than version 7.7; that is, for drivers written for Siebel CRM version 7.0.x or version 7.5.x.

Communications drivers for prior Siebel CRM 7.x releases do not work as is with Siebel CRM version 7.7.x or later, unless you follow the guidelines in this topic. Siebel CRM version 7.7.x or later requires version 2 of the Siebel Adaptive Communications API (as did Siebel CRM version 7.5.x). For more information about custom drivers, see Communications Drivers and Third-Party Systems.

Requirements that might apply to your custom communications driver are as follows:

• On all supported operating systems, for any communications driver written for Siebel CRM version 7.0.x, you must compile the driver using the current version of the API. A Siebel CRM version 7.0.x communications driver cannot work with Siebel CRM version 7.7.x or later, due to version checking. For drivers from Siebel CRM version 7.5.x, this requirement is already met.
• For drivers on all supported operating systems, the driver handle method FreeSCStrParamList must be implemented. For any driver for Siebel CRM 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 might not apply. For more information about this method, see Methods of ISC_DRIVER_HANDLE.
• For Oracle Solaris, you must use UTF16, in order to support Unicode, rather than UCS4 (as was used in Siebel CRM version 7.0.x). For any driver on this platform for Siebel CRM version 7.0.x, you must modify your driver code and recompile your driver. For drivers from Siebel CRM version 7.5.x, this requirement is already met.