Siebel Communications Server Administration Guide > Configuring Events and Commands > Event Logs >

Event Log Examples


Table 19 shows an example of an event log for Siebel CTI Connect. This example shows how a new activity is created. The activity is linked with the current contact and its account because the current contact is the result of a screen pop.

Table 19. Event Log: LogIncomingCallContactFound
Parameter Name
Parameter Value

AfterWork.'ACD Call Duration'

{@WorkDuration}

AfterWork.'Planned Completion'

{@Now}

BusObj

Contact

BusComp

Action

Display

FALSE

LogField.Type

Call - Inbound

LogField.'Account Id'

{Contact.'Account Id'}

LogField.'Contact Id'

{Contact.Id}

LogField.Description

Inbound call

LogField.'Call Id'

{refId}

LogField.'Planned'

{@WorkStartTime}

Communications Simulator. Table 20 shows an example of an event log. A definition like this could be used when the inbound caller is not found in the database.

Table 20. Event Log: LogIncomingCallContactNotFound
Parameter Name
Parameter Value

BusObj

Contact

BusComp

Action

LogField.Type

Call - Inbound

LogField.Comment

{refId}

LogField.Description

Unknown Caller ({ANI})

AfterWork.'ACD Call Duration'

{@WorkDuration}

If you choose a View Call command after answering a simulated call, you go to the Activity Attachments view to see information about the current call. Notice that the description of the call starts with Unknown Caller, followed by the phone number from which the call was dialed.

You can change the LogField.Description parameter value to display other text here. For example, "Unknown Phone Number: {ANI}" displays the text "Unknown Phone Number:" followed by the phone number corresponding to the ANI event data field.

Siebel Communications Server Administration Guide