About Siebel Communications Server Architecture

The following figure illustrates the overall architecture of the communications infrastructure for the Siebel Business Applications, in particular for Siebel CTI deployments. For information about how email, fax, and paging are integrated into the communications infrastructure, see Siebel Email Administration Guide.

Note: The Siebel Developer Web Client is supported for administration, development, and troubleshooting usage scenarios only.

Architecture of Communications Infrastructure. In this image, Siebel Web Client connects to Web Server. Web Server is connected to Siebel Server (Application Object Manager/SWE, Communications Server, Adaptive Communications API). Siebel Developer Web Client is connected to Communications Server (Comm. Session Manager). Siebel Database is connected to Siebel Server (Application Object Manager/SWE), Siebel Developer Web Client and Siebel Developer Web Client. Channel-Specific Communications drivers is connected to Siebel Server (Adaptive Communications API) and to Email, Fax, Paging, and CTI/Voice Middleware. CTI/Voice Middleware is connected to ACD/PBX and to Siebel Developer Web Client. ACD/PBX is connected to the cloud. Customers are connected to the cloud.