1. CTI Administration Guide
  2. Loading Communications Drivers

Loading Communications Drivers

The process of loading a communications driver is as follows:

  1. The channel manager invokes the driver handle method APIVersion, to check the driver’s API version. The API version defined in the driver’s header file must match the API version for Communications Server. For more information, see APIVersion.

  2. The channel manager invokes the driver handle method CreateISCDriverInstance, to create the driver instance. The channel string passed to this method is collected from the driver record that is created in the Communications Drivers and Profiles view, in the Administration - Communications screen. For more information, see CreateISCDriverInstance.

  3. The channel manager invokes the driver handle method RequestCommandEventList, to retrieve the list of events and commands this driver supports. For more information, see RequestCommandEventList.

  4. The channel manager invokes the driver handle method RequestService, to create a service object. For more information, see RequestService.

If any listed step fails, then the driver loading fails. If multiple driver profiles must be loaded, then the process is repeated for each profile.