Attaching call data on telephony functions

You can associate data with a call when invoking call control requests that place, transfer, or conference calls. Pega Call provides data transform rules in class ChannelServices-Request-CallOptions-Cisco for use with local and remote CTI links that use Cisco ICM. Copy the relevant data transform to your application ruleset and modify it to set the data that you need to associate with the call. You can review the sample data transform ChannelServices-Request-CallOptions-Cisco.MakeCall.

To set Cisco call variables, use the value-list pyCallVariables (with subscripts 1 through 10). To set Cisco expanded call context (ECC) variables, use the value group pyNamedVariables with the ECC variable name as the subscript. Source data includes references to pages on the user's clipboard.

Named variable aliases

Pega property names and the names of subscripts in value groups cannot use special characters; they must use Java variable naming conventions. If a Cisco ECC variable name includes such a character (for example, user.callerName includes a period character), you can use an alias to represent the variable within Pega Platform. You must then map the alias to the ECC variable name using the value-group pyNamedVariableAlias. these map the variable name used in pyNamedVariables (target) to the actual Cisco ECC variable name (source).

Post routing

If you want to invoke Cisco ICM's post routing feature when you place, transfer, or start conference calls, set the pyPostRoute property to true in the relevant data transform rules in class ChannelServices-Request-CallOptions-Cisco.

If you need to transfer the CPM interaction context with a call (that is, if you use the voice-data transfer feature), you must ensure that the data transforms PegaCallData and PegaAppData are invoked from the data transforms BlindTransfer, TransferInitiate and ConsultationCall in class ChannelServices-Request-CallOptions-Cisco.

Do not modify rules in the ChannelServices-Request-CallOptions-Remote class. These are for internal use only.

Request and Response Events

In addition to the CTI events (agent state, call state) received from the CTI platform, the toolbars use two events for state change requests:

SoftphoneRequest Event

This event captures information related to a call control or agent state change request. The toolbar sends this event to invoke a corresponding call control or agent state change activity on the Pega server. These activities are described in the section Desktop Telephony Functions.

SoftphoneResponse Event

This event is a response to a SoftphoneRequest event. It indicates that the requested activity was invoked on the Pega server. The event includes the result or error returned by the activity. A “Good” result only indicates that the activity was run – it does not indicate that the call or agent state was changed as requested. A separate agent or call state event should follow, indicating the state change.

Extension point for the OFFERING activity

As a rule, do not override any of the activities used to process Pega Call events. If you need to perform any additional processing when a call arrives at a CSR’s phone (that is, as part of the event handling for OFFERING), you can override the activity pyPrefetch in your call class (for example, ChannelServices-Interaction-Call or PegaCA-CTI-Call).