Running Communications Session Manager

When the Communications Management component group is enabled, the Communications Session Manager component is started automatically. For any computer on which you do not want to run Communications Session Manager, configure the Siebel Server not to start it.

Communications Session Manager is a batch-mode component. It relies on the services of the Server Request Broker and Server Request Processor server components. These components must be running on the Siebel Server for communications to be processed successfully.

Note: If your CTI middleware server is restarted, then, depending on the third-party vendor requirements, you might also have to restart the Communications Session Manager server component that connects to it.

For more information about configuring, starting, and stopping Siebel Server components, see Siebel System Administration Guide.