Communications Configuration Requirements for Siebel Modules

Much of the communications configuration data that this chapter is concerned with, particularly for Siebel CTI, involves sets of data organized under a type of record called a communications configuration. Used as a noun, this term (sometimes shortened to configuration) refers to these records and to associated elements such as configuration parameters, agents, telesets, profiles, commands, and events.

For a Siebel CTI deployment, then you must create or use a communications configuration, such as a predefined multichannel configuration. For more information, see About Siebel CTI.

This topic is part of About Communications Configuration Data.

For information about additional kinds of configuration data related to communications, see Types of Communications Configuration Data.

Communications drivers and profiles, through which Siebel Communications Server can interface with external systems, are part of the communications configuration data. Examples of external systems include CTI middleware, chat servers, and email servers. Communications drivers are usually based on library files, such as DLL (Dynamic Link Library) files on Microsoft Windows. Corresponding configuration data in the Siebel database, including driver parameters, is defined to work with each driver. Communications profiles customize driver behavior for particular purposes by allowing driver parameter values to be overridden wherever the profile is in use. Communications configurations have associated profiles.

Every deployment of Siebel Communications Server uses communications drivers and profiles. However, as shown later in this topic, some Siebel modules use communications drivers and profiles but do not use (or might not use) communications configurations. For more information about:

Related Books

Siebel Email Administration Guide

Configuring Siebel Business Applications

Configuring Siebel Open UI

Using Siebel Tools

Siebel Developer's Reference