Dialogue Studio Installation
Prerequisites
Licensing prerequisites
Your subscription must include Dialogue Studio. This entitlement may be included in your subscription or provided through AW304, Dialogue Studio.
Contact your AnywhereNow representative if you are unsure whether your subscription includes Dialogue Studio.
Request Dialogue Studio for Dialogue Cloud Neo UCCs
A Dialogue Studio installation can be requested via your AnywhereNow contact or Partner and enabled for one or more A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location.'s. This also applies for enabling additional UCC's to your Dialogue Studio at a later moment.
Note
One Dialogue Studio is the default per customer, per region. This Dialogue Studio will serve and act as the canvas for all of the enabled services and UCC's within that region. Multiple Dialogue Studios within a region can be made available upon request and with consent of our sales and project delivery organization.
Warning
A restart of the service (affecting all your UCC's in that service) is required to enable a (new) UCC for your Dialogue Studio. Please plan this install in a service window for your service.
Your AnywhereNow contact will provide you with the details of the Dialogue Studio:
Connection details depend on the selected node and transport. The service URL, plugin port, and UCC name below describe the HTTP/SignalR Core plugin path. For another transport, use the connection details provided for that path.
| Information provided | Example |
|---|---|
| The editor URL and credentials for opening Dialogue Studio in your browser. This is not the Core node service endpoint. | https://ds-<GUID stands for Globally Unique Identifier (format is always like 2ed153b4-f632-4766-b846-5b2a769b36d1) and is a pseudo random number used in software applications that is assumed to be unique. The total number of unique keys (2<sup>128</sup> of 3.4028×10<sup>38</sup>) is very large and the probability of the creating the same GUID twice is very small, though not 100% guaranteed. The term GUID is generally used by developers working with Microsoft technologies, while UUID is used everywhere else.>-emwet.dialogue.studio/ |
| The Core service URL, including the assigned plugin port, for the Server configuration in your Dialogue Studio Core nodes. Use the HTTP or HTTPS scheme configured for your environment. | http://<GUID>-01.<region>.dialoguecloud.local:<assignedPort> |
|
The plugin listener port assigned to the UCC. Include this port in the Core service URL. |
<assignedPort> |
| The UCC name to enter separately in the Core node Server configuration. | <uccName> |
Tip
If your HTTP/SignalR plugin settings are managed through the Ucc.Creator SharePoint template, retrieve the assigned port from the UCC's Plugin Settings page. This port must match the port in the Core node service URL. If another configuration source is active, use the provisioned connection details from that source.
Before configuring a flow, confirm the selected node's transport and the active configuration source for your environment. Use the connection details provided during provisioning. Applicability depends on that transport and configuration source, not the connect model alone.
For Core nodes using the HTTP/SignalR plugin connection, configure Server with the Core service URL, including the plugin listener port, and the UCC name. Use the HTTP or HTTPS scheme configured for that listener. The editor URL you open in your browser is not this service endpoint. For another transport, use its provisioned connection details rather than assuming these listener settings apply.
For the HTTP/SignalR plugin path, Formerly known as Partner Portal. A redesigned web portal for managing Dialogue Cloud deployments. assigns a separate Dialogue Studio plugin port to each UCC during provisioning. Use the assigned port with the service URL and UCC name. Sharing a listener port is also supported for this plugin path, but is not standard OnePortal provisioning. Do not change an assigned port without coordinating with AnywhereNow. Align all affected connections and dependent network configuration when changing it.
AnywhereNow Authentication
Optionally, AnywhereNow Authentication can be set up, to allow only specified end-users access (read-only or read/write) to your Dialogue Studio Canvas, simply by making them member of a specific group in your Microsoft Entra tenant. See: AnywhereNow Authentication for Dialogue Studio
Core plugin registration and connections
This section describes the HTTP/SignalR Core plugin path. Confirm that your selected nodes use this path before applying its listener settings. Do not infer the transport or configuration source from the connect model alone.
The Dialogue Studio plugin is registered per Unified Contact Center (UCC), not as a service-level plugin registration. Multiple UCCs on the same Core service can share a plugin listener port. Shared listeners must use the same HTTP or HTTPS scheme.
Per-UCC plugin registration, listener ports, and Dialogue Studio instances are separate concepts. A shared listener does not replace per-UCC registration. Separate listener ports do not require separate Dialogue Studio instances.
For connection details, see any-red-config. Dedicated ports do not isolate generic Event Bus events by UCC. See Event Bus.
Configuration Settings for Dialogue Studio in Ucc.Creator SharePoint template
Applies to
Use this procedure when the HTTP/SignalR Core plugin settings are managed through the Ucc.Creator SharePoint template. If another configuration source is active, use that source's provisioning instructions. This does not mean connection setup is unnecessary.
Dialogue Studio plugin
The Dialogue Studio plugin bypasses the UCC's SharePoint Interactive Voice Response, or IVR, is a telephone application to take orders via telephone keypad or voice through a computer. By choosing menu options the caller receives information, without the intervention of a human operator, or will be forwarded to the appropriate Agent. menu and sends the call to Dialogue Studio for processing. You do not need to configure that menu to invoke the plugin. This does not mean that all reusable IVR questions are unnecessary. For more information, see Dialogue Studio User Guide.
For this HTTP/SignalR plugin path, the Ucc.Creator SharePoint Plugin Settings list contains the following entries in the DialogueStudio scope for each UCC. HttpPort and HttpsEnabled configure this plugin's listener; do not assume another transport uses these settings.
| Setting |
Value |
Scope | Comment |
|---|---|---|---|
HttpsEnabled |
|
DialogueStudio | Use the value configured for your environment. false uses HTTP; true uses HTTPS. Match the scheme in the Core node service URL. Internal connectivity does not mean this must always be false. |
HttpPort |
|
DialogueStudio | Use the HTTP/SignalR plugin port assigned to this UCC during provisioning or installation. Valid values are 1 through 65535; ports are not restricted to four digits. For this plugin path, OnePortal assigns a separate plugin port to each UCC by default. Sharing a listener port is also supported, but is not standard OnePortal provisioning. Do not change an assigned port without coordinating with AnywhereNow. Align all affected connections and dependent network configuration when changing it. |
Note
Select Audio/Video in the Filter setting, not IvrQuestion (Audio/Video). Double-click the Incoming call node to check its properties.
Next Steps
-
Browse the complete overview of Dialogue Studio - Dialogue Cloud Core Nodes