Avaya Client Services API Reference (Windows)
Avaya Client Services API Reference (Windows)
Avaya.ClientServices
CallLogService Class
CallLogService Properties
CallLogService Methods
CallLogService Events

CallLogService Class

Call Log Service provides history entries for calls that have been made or received on the client.
Inheritance Hierarchy
System
Object
Avaya.ClientServices
CallLogService

Namespace: Avaya.ClientServices
Assembly: AvayaClientServices (in AvayaClientServices.dll) Version: 592.1.30.0
Syntax
C#
Copy

    public class CallLogService

The CallLogService type exposes the following members.

Properties

| Name | Description
--- | --- | ---
| AddCallLogsCapability | Capability describing whether call logs can be added by client using AddCallLogItems(CallLogOperationData, CallLogService CallLogActionCompletionHandler). Allowed when NetworkCallLogsCapability is not allowed. A client cannot add call logs when 24x7 Call Journaling is enabled on the server and allowed by PpmConfiguration.
| CallLogs | Contains currently cached call log items.
| MarkCallLogsAsReadCapability | Capability describing whether call logs can be marked as read using MarkAllCallLogItemsAsRead(CallLogService CallLogActionCompletionHandler). Disabled during network outage or when server does not have ability to provide read status.
| NetworkCallLogsCapability | Capability describing whether 24x7 Call Journaling is enabled
| RemoveCallLogsCapability | Capability describing whether call logs can be removed using RemoveCallLogItem(CallLogOperationData, CallLogService CallLogActionCompletionHandler). Disabled while network outage.

Top
Methods

| Name | Description
--- | --- | ---
| AddCallLogItems | The client can create specific call log objects and request the call log service to add it.
| MarkAllCallLogItemsAsRead | Process the client's request to mark all the existing call logs as read.
| RemoveAllCallLogItems | Process the client's request to remove all existing call log items. This call will permanently remove all call log items from both runtime and persistent storage. Both completion handler and the data set update notification will provide a full or subset of those call log items objects managed by the client. Both "equals" and "==" operation on those returned objects should provide correct results against those objects managed by the client.
| RemoveCallLogItem | The client can select specific call log objects and request the call log service to remove them permanently.
| ResynchronizeCallLogItems | This operation reloads all call log items from the persistent storage. CallLogItems contains all call log items loaded from the storage. Check OperationStatus for the status of the operation - success or failure.

Top
Events

| Name | Description
--- | --- | ---
| CallLogsAdded | Occurs when new call log item(s) are added to the system.
| CallLogServiceCapabilitiesChanged | Occurs when the Call Log Service capabilities changed. Check the Call Log Service capabilities when the event is triggered.
| CallLogsLoaded | Occurs when loading persistent call log items into the system is completed. Status reported in CallLogServiceEventArgs indicates if Call Log Service has been correctly initialized. A failure status in this event may mean unexpected Call Log Service behavior going forward. At a minimum, new call log items will not be persisted.
| CallLogsRead | Occurs when call log item(s) are read.
| CallLogsRemoved | Occurs when call log item(s) are removed.
| CallLogsUpdated | Occurs when an existing call log item is updated in the system.

Top
Remarks

The full path to the call log file should be provided by setting UserConfiguration.LocalCallLogFilePath to a platform dependent file path. The path should be unique for each user logging in on the client.

Currently only local call logs are supported. This means that if call events happen when a user is logged off there will be no call logs captured.

See Also

#### Reference

Avaya.ClientServices Namespace

© 2017 Avaya LLC. All Rights Reserved.