|Bookshelf Home | Contents | Index | PDF|
For more information about interactive drivers, see Interactive Drivers.
Events and commands you define in the views in the Administration - Communications screen must be based on what the interactive communications driver supports. Commands, command parameters, events, and event data fields will vary among communications drivers, just as they vary among vendors of communications systems, such as CTI middleware vendors.
You can retrieve driver parameter values from the Siebel Database. Storing the parameters you need in the Siebel Database allows the administrator to set parameter values appropriately for your communications driver.
You can write a communications driver to support the driver parameters you require. If you have created a custom driver to function in place of a Siebel-provided driver, you must then create all the driver parameters in the views in the Administration - Communications screen and assign values to them. If you have created a custom driver as an aggregate driver, to extend a Siebel-provided driver, then you can use parameters defined by Siebel Systems.
The communications driver and the Siebel system software, such as Siebel business services and server components, work together to implement the desired communications behavior for the Siebel application.
|Siebel Communications Server Administration Guide|