Revision as of 18:33, May 28, 2018 by Pmcknigh (talk | contribs) (Feature Configuration)
Jump to: navigation, search

Campaign Group Status Reporting

All New

Outbound Contact Server can store data about Campaign Groups in an external system, such as Elasticsearch, to support feature-rich reporting. The data is communicated to the external system using HTTP POST. The following states and information can be reported:

  • Campaign Group loaded
  • Campaign Group started
  • Campaign Group stopped
  • Campaign Group unloaded
  • Campaign Group dial mode change
  • Campaign activity and Campaign Group statistics--generated periodically

Feature Configuration

To configure this feature, use the following configuration options:

OCS uses the following options to retrieve connection information about the configuration:

Log Messages

OCS uses the following new Trace-level log messages to report that notifications have been sent. No actions are required in response to these events.

ID Level Text Attributes Description
81000 TRACE Sending HTTP status notification %s for Campaign Group %s to %s &s

status (for example, CampaignRunning)

&s Campaign Group name

&s URI to which the notification has been sent.

An HTTP status notification has been sent to an external system that the status of a Campaign Group has changed. For information included in the body of the notification, see HTTP POSTs to External System, below.
81001 TRACE Sending periodic HTTP status notification %s for Campaign Group %s to %s &s

CampaignActive status (for example, Campaign Running)

&s Campaign Group name

&s
URI to which the notification has been sent.

A periodic HTTP status notification has been sent to an external system that the activity of a Campaign Group. For information included in the body of the notification, see HTTP POSTs to External System, below.

Error Handling

There is no error-handling carried out by this feature. If the HTTP POST to the external system fails, no post-processing or retries are executed.

HTTP POSTs to External System

The specific information sent to the external system is described in the Outbound Contact Reference Manual here, and differs between scenarios.

The fields in the table below are passed by OCS in the body of the HTTP notification to the external system. All fields are sent, but fields not relevant to the status change or periodic activity scenario are left unassigned or set to a default value:

Attribute Type Description
GSW_USER_EVENT String Set to CampaignGroupState
GSW_DATE_TIME String Timestamp when action occurred; UTC time as seconds, with msec precision.
GSW_TENANT_NAME String Defaults to Unknown if not set.
GSW_TENANT_CCID String Defaults to Unknown if not set.
GSW_CAMPAIGN_GROUP_NAME String
GSW_CAMPAIGN_GROUP_GUID String
GSW_GROUP_NAME String
GSW_CAMPAIGN_NAME String Defaults to Unknown if not present in configuration
GSW_CAMPAIGN_TEMPLATE_NAME String Defaults to Unknown if not present in configuration
GSW_QUEUE_NAME String Name of the Voice Transfer Destination DN
GSW_DIAL_MODE Integer Use CfgDialMode enum values. Defined only for running Campaign Groups
GSW_CAMPAIGN_GROUP_STATE Integer Use CM_GrpCampState enum values
GSW_CAMPAIGN_GROUP_ACTION Integer

Identifies client request which has caused message generation. Use CM_ReqSetDialingMode when dial mode is changed.

Use CMMessageType enum values CM_ReqLoadCampaign, CM_ReqUnloadCampaign, CM_ReqStartDialing, CM_ReqStopDialing, or CM_ReqSetDialingMode

GSW_CAMPAIGN_GROUP_ACTOR Integer Distinguishes action caused by OCS Client or automatic action taken by OCS itself (either per Schedule or per internal Campaign Group condition). Valid values are:

0 (zero) -- Actor Type unknown
1 -- Actor Type OCS Client (actions invoked by direct OCS Client connected via CM Library protocol)
2 -- Actor Type COMM Client (actions invoked by Communication DN Client connected via 3rd party Comm DN protocol)
3 -- Actor Type Self (actions invoked by Campaign Group internal logic)
4 -- Actor Type Schedule (actions invoked by Schedules)
5 -- Actor Type Sequence (actions invoked by Sequences)

Comments or questions about this documentation? Contact us for support!