Submitting Call Attempt Records

compliance manager can check the call data against call attmpt rules that all you to suppress contacts based on the results of previous attempts.

When OCS attempts a call, it sends the call attempt record, which contains all data related to the call attempt, to an external system, such as Compliance Manager, which check it against contact attempt rules and history suppression.

Question: Should I continue to refer to it as the 'external system' or 'Compliance Manager' ??

The purpose of submitting call attempt record to external system is to provide the data that may be required for compliance management based on "Contact Attempt rules" which are defined as the rules that allow you to suppress contact attempts based on the history of previous attempts.

Scenario: Successful HTTP Post

1. A campaign is started/loaded in any dialing mode.
2. An outbound call is dialed.
3. OCS sends a call attempt record (HTTP POST with GSW_OCS_SEQUENCE_NO: 0) to the external system.
4. OCS stores the record posted to the external system while it waits for confirmation from the external system that the record was saved.
5. The external system receives the record and sends a 200 OK response to OCS. The log check confirms that the call attempt record was saved.
6. The agent-customer call is established.
7. The agent releases the call.
8. OCS sends another call attempt record (HTTP POST with GSW_OCS_SEQUENCE_NO: 1) to the external system, this time containing the GSW_CALL_RESULT parameter.

The GSW_OCS_SEQUENCE_NO: 1 record overwrites the GSW_OCS_SEQUENCE_NO: 0 record when dialing rules are applied.

Question: Does the external system send only one response?

Feature Configuration

Add the following configuration options: send-history
history-uri
history-wait-condition-threshold
history-wait-recovery-timeout
validation-race-condition-call-result
send-history-key
history-es-report-events

Scenario: Record Cancelled

Scenarios Record Cancel Resubmitting after 404