Dialogue Cloud

WebChat Dialogue Provider Plugin Settings Overview

Note Additional Anywhere365 WebAgent license required.

Note Enterprise license and higher

Introduction

Below an overview of the available settings for the WebChat Dialogue Provider

 

Plugin Settings

Setting

Value

Description

Enabled

TRUE

The provider will start, and the background tasks will start running. However, when the tasks to process any data are triggered, they will not execute and be skipped.

PollingIntervalInSeconds

1

The provider will look for data to process each x-seconds. The provider will first check whether there are any active sessions, if so, it will query the database for data.

CustomerUriDomain

Example:

mydomain.com

When there is no customer (sip) URI provided with the chat session, an URI will be generated based on the conversation identifier; this domain will be used as post-fix. For example: gerated-id@customerdomain.

DefaultAgentName

Example:

Agent

The default agent name to display to the customer, when the agent's name can not, or has not yet been, retrieved from the database.

WebChatSipUri

Example:

sip:ucc_service_webchat@mydomain.com

The default sip URI that will be used for any purpose when none can be found or none is provided.

ForwardUri

Note: Introduced in WebChat 2.1

Example:

http://FQDN FDQN stands for Fully Qualified Domain Name and specifies the exact location in the tree hierarchy of the Domain Name System (DNS). An example for [hostname].[domain].[top level domain] is [www].[microsoft].[com]/WebchatDialogueProvider2/api/v1/dialogue-manager/ucc/presence

Note: URL needs to be accessible from the Dialogue Manager to the WebChatDialogueProvider2. If on the same machine, you can use localhost.

Used for the Dialogue Manager to forward presence information to the WebChatDialogueProvider

TimeToLiveInMinutes

Note: Introduced in Webchat Dialogue Provider v 1.21.2

0 or higher

default: 0

The time a subscription can stay active in minutes; used to determine when a subscription should be actively closed by the WebChat provider

For example, a new subscription was created, but the client closed their browser window or lost connection. When this value is zero (0) or less, subscriptions will stay active forever (until an agent closes them).

SessionTimeoutInMinutes

Note: Introduced in Webchat Dialogue Provider v 1.21.2

1 or higher

default: 30

The cache sliding-expiration in minutes; used to store conversation-subscription data. Also determines how long a session will exists (stay dormant) on the server when a connection is broken.

A connection can always be re-established when information from the client is available: The connection will be re-built via database request to fetch any missing information.

ReopenHandledSession

Note: Introduced in Webchat Dialogue Provider v 1.23.0

FALSE or TRUE

default: FALSE

Reopen sessions that have been handled by the agent.