Sequence of Steps When a CTI Enabled User Logs into the Siebel Application (Doc ID 477834.1)

Last updated on MAY 19, 2016

Applies to:

Siebel CTI - Version 7.0.4 [14068] to 8.1.1 [21112] [Release V7 to V8]
Information in this document applies to any platform.
Area(s):Siebel.CRM.CTI
Release(s):V7 (Enterprise)
Database(s):All Supported Databases
App Server OS(s):GENERIC (All Platforms)
Latest release tested against:V7 (Enterprise)
***Checked for Relevance 11-Dec-2014***

Goal

The sequence of steps that you should see in the CTI related log files when a CTI enabled user logs into the Siebel Application.

In the debug SComm_<Siebel User Id>.log file and the Java Runtime trace file the following information is observed and is sent/generated by different pieces/components. Please refer to <Note 476563.1> to verify how to generate these log files with debug information.

If the Siebel Application Object Manager has the component parameter Enable Communications = True and the Siebel User is associated to a valid Communications Configuration the Siebel Browser session will load and execute the Siebel CTI plug-in to initiate the CTI Toolbar, than the following sequence can be observed in log files, for more details about enabling CTI Toolbar please refer to Bookshelf > Siebel Communications Server Administration Guide> Administering Siebel Communications Server > Enabling Session Communications and Simulation chapter:

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms