Bookshelf Home | Contents | Index | PDF |
Siebel CTI Administration Guide > Developing a Communications Driver > Adaptive Communications Design > Adaptive Communications Event and Command ModelSiebel Adaptive Communications, when it is used to write interactive drivers, such as those used with CTI middleware, uses the concept of events and commands:
For more information about interactive drivers, see Interactive Drivers. Once you have written a communications driver, you configure Siebel Communications Server, as described in Configuring Siebel CTI and Configuring Events and Commands. Events and commands that 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 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 that 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 that you require. If you have created a custom driver to function in place of a driver provided with Siebel Business Applications, then 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 driver, then you can use parameters from the Siebel driver. The communications driver and the Siebel CRM software, such as Siebel business services and server components, work together to implement the communications behavior for the Siebel application. |
Siebel CTI Administration Guide | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |