Jump to: navigation, search

Web Callback Channel

When you install Genesys Web Engagement, the Provisioning Tool automatically configures the Backend Server to support working with a voice (web callback) channel.

If you need to, you can configure this manually by completing the "Configuring the Backend Server to Support a Voice (web callback) Channel".

You can also complete the "Configuring Web Callback as the Default Channel of Engagement" to specify web callback as the default channel of engagement. You do this by using the wmsg.connector.defaultEngagementChannel option, which is only intended for development purposes and should not be used in a production environment because it turns off the pacing algorithm.

Configuring the Backend Server to Support a Voice (web callback) Channel

Prerequisites

Start

  1. In Genesys Administrator, navigate to Provisioning > Environment > Scripts and confirm the following:
    • The Web Callback business process is installed:

      The Web Callback business process
    • An Interaction Queue named New exists:

      An Interaction Queue named New
  2. Navigate to Provisioning > Environment > Applications and open the Web Engagement Backend Server application to configure the web callback endpoint.
  3. Select the Options tab.
  4. In the [server:wes] section, set the value of the wes.connector.interactionServer.wcb.queueSubmit option to New.

    Set the wes.connector.interactionServer.wcb.queueSubmit option to New
  5. Make sure that agents who participate in web callback processing belong to the following groups:
    • WebCallback distribution for processing — This group is used in the Web Callback business process as the delivery target for web callback interactions.
    • Web Engagement Voice — This group (or groups) is specified in the pacing.connector.voiceGroup option to support pacing algorithm functionality.

End

Configuring Web Callback as the Default Channel of Engagement

Specifying web callback as the default channel tells the default SCXML strategy to ignore results provided by the pacing algorithm. As a result, the engagement attempt is always activated on the web callback channel and the count of ready agents is ignored. If the wmsg.connector.defaultEngagementChannel option is not specified or specified with empty value, the pacing algorithm is used.

Start

  1. In Genesys Administrator and navigate to Provisioning > Environment > Applications.
  2. Open the application for the Web Engagement Backend Server.
  3. Set the web callback channel as the default channel of engagement. In the [service:wmsg] section, set the value of the wmsg.connector.defaultEngagementChannel option to proactiveVoice.

End

Next Steps

This page was last modified on November 14, 2014, at 16:00.

Feedback

Comment on this article:

blog comments powered by Disqus