Siebel Communications Server Administration Guide > About Siebel Communications Server > Process of Configuring Communications Server >

Defining Communications Server Configuration Data

This section describes in general terms how to define or modify Siebel Communications Server configuration data. Do this once all modules have been installed and the server components have been configured. Many of the steps can be performed in a different sequence than that shown here.

For more information about communications configurations, see About Communications Configuration Data. For detailed procedures for working with communications configuration data, see applicable sections in Configuring Session Communications.

NOTE:  When you have finished specifying the communications configuration data, you must exit and restart the Siebel application for the settings to take effect. After Siebel Communications Server has been deployed, any end users who are currently connected must also exit and restart the application for the new or modified configuration data to take effect.

To define Siebel Communications Server configuration data

  1. Start the Siebel application, such as Siebel Call Center, logging in as the system administrator (for example, as the user SADMIN).
  2. Navigate to the Communications Administration screen. To do this, choose View > Site Map from the application-level menu, then choose Communications Administration in the Site Map.

    3. For information about the views in this screen, where you will perform most of the tasks identified here, see Views for Communications Administration.

  3. Configure communications drivers and profiles. As applicable, associate profiles with communications configurations you have already created. See Configuring Communications Drivers and Profiles.
    1. For each communications driver you are using, specify default parameter values.
    2. For each communications driver you are using, create profiles. As appropriate, specify parameter values to override the driver parameters.
    3. If you are not using communications configurations, skip to Step 12.

      4. For more information about modules that use communications configurations, see Communications Configuration Requirements for Siebel Modules.

  4. To support modules such as Siebel CTI and Siebel eMail Response (optional), create a communications configuration. See Creating or Modifying a Communications Configuration.

    5. You can modify an existing communications configuration, or create a new configuration and transfer data into it from an existing configuration.

  5. For the current configuration, specify configuration parameter values. See Specifying Parameters for Communications Configurations.
  6. For the current configuration, associate profiles you created for your CTI driver and User-interactive Email driver. See Creating or Modifying a Communications Configuration.
  7. For the current communications configuration, specify the agents for whom the communications configuration will apply. See Specifying Agents.
    1. Add each agent to one or more configurations. If you add an agent to more than one configuration, specify which configuration is primary for the agent.
    2. Configure the agents, such as (for voice agents) to specify which ACD queues they will use, define ACD agent login and password, and so on.

      3. NOTE:  If you are not defining ACD queues, or if the driver parameter Service:IsQueueRequired is set to FALSE for the CTI driver or for applicable driver profiles associated with the configuration, then the above step is not necessary. For more information, see Siebel CTI Connect Driver Parameters.

    3. If telesets have already been defined (as in Step 8), you can specify the telesets an agent can use.

      4. You do not need to associate agents with telesets that will be used for hoteling, or associate agents with telesets for agents who will not use the voice channel.

  8. If you are using Siebel CTI (voice channel), specify the telesets for your call center. See Specifying Telesets.
    1. If a teleset will be used for hoteling, specify the host name for the hoteling computer.
    2. For each teleset, specify the extensions for the teleset.
    3. For each teleset, you can specify agents that can use the teleset.

      4. In order to associate an agent with a teleset, the agent must have already been added to the configuration (as in Step 7). You do not need to associate agents with telesets that will be used for hoteling.

  9. Specify or verify event handlers and associated event responses and event logs, and associate them with the communications configuration. See Defining Communications Events.
    1. Create the event logs you will specify in your event responses, and associate them with the configuration.
    2. Create the event responses you need, optionally specifying one or more event logs for each event response, and associate the event responses with the configuration.
    3. Create the event handlers you need, specifying an event response for each event handler, and associate the event handlers with the configuration.
  10. Specify or verify commands and associated command data definitions, and associate them with the communications configuration. See Defining Communications Commands.
    1. Create the command data definitions that you will specify in your commands, and associate them with the configuration.
    2. Create the commands that you need, specifying a command data definition for each command, and associate the commands with the configuration.
  11. Optionally, use the Communications Simulator to test your configuration. See Enabling Session Communications and Simulation and Simulating a Communications Environment.
  12. Complete any other needed configuration, customization, or performance-tuning tasks for your Siebel implementation, and test the communications configurations you are using. For example, you may:

After you have verified the configuration, you can put Siebel Communications Server into production.


 Siebel Communications Server Administration Guide 
 Published: 23 June 2003