You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cognitive-services/Speech-Service/custom-commands.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.author: travisw
16
16
17
17
[Voice assistants](voice-assistants.md) listen to users and take an action in response, often speaking back. They use [speech-to-text](speech-to-text.md) to transcribe the user's speech, then take action on the natural language understanding of the text. This action frequently includes spoken output from the assistant generated with [text-to-speech](text-to-speech.md). Devices connect to assistants with the Speech SDK’s `DialogServiceConnector` object.
18
18
19
-
**Custom Commands (Preview)** is a streamlined solution for creating a voice assistant. It provides a unified authoring experience, an automatic hosting model, and relatively lower complexity versus other assistant creation options like [Direct Line Speech](direct-line-speech.md). This simplification, however, comes with a reduction in flexibility. So, Custom Commands (Preview) is best suited for task completion or command-and-control scenarios.
19
+
**Custom Commands (Preview)** is a streamlined solution for creating a voice assistant. It provides a unified authoring experience, an automatic hosting model, and relatively lower complexity versus other assistant creation options like [Direct Line Speech](direct-line-speech.md). This simplification, however, comes with a reduction in flexibility. So, Custom Commands (Preview) is best suited for task completion or command-and-control scenarios. It's particularly well-matched for Internet of Things (IoT) and headless devices.
20
20
21
21
For complex conversational interaction and integration with other solutions like the [Virtual Assistant Solution and Enterprise Template](https://docs.microsoft.com/azure/bot-service/bot-builder-enterprise-template-overview) you're encouraged to use Direct Line Speech.
Copy file name to clipboardExpand all lines: articles/cognitive-services/Speech-Service/faq-voice-assistants.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ If you can't find answers to your questions in this document, check out [other s
24
24
25
25
**Q: Should I use Custom Commands (Preview) or Direct Line Speech? What's the difference?**
26
26
27
-
**A:**[Custom Commands (Preview)](custom-commands.md) is a lower-complexity set of tools to easily create and host an assistant that's well-suited to task completion scenarios. [Direct Line Speech](direct-line-speech.md) provides richer, more sophisticated capabilities that can enable robust conversational scenarios. See the [comparison of assistant solutions](voice-assistants.md#comparing-assistant-solutions) for more information.
27
+
**A:**[Custom Commands (Preview)](custom-commands.md) is a lower-complexity set of tools to easily create and host an assistant that's well-suited to task completion scenarios. [Direct Line Speech](direct-line-speech.md) provides richer, more sophisticated capabilities that can enable robust conversational scenarios. See the [comparison of assistant solutions](voice-assistants.md#choosing-an-assistant-solution) for more information.
28
28
29
29
**Q: How do I get started?**
30
30
@@ -36,6 +36,17 @@ If you can't find answers to your questions in this document, check out [other s
36
36
37
37
## Debugging
38
38
39
+
**Q: Where's my channel secret?**
40
+
41
+
**A:** If you've used the preview version of Direct Line Speech or you're reading related documentation, you may expect to find a secret key on the Direct Line Speech channel registration page. The v1.7 `DialogServiceConfig` factory method `FromBotSecret` in the Speech SDK also expects this value.
42
+
43
+
The latest version of Direct Line Speech simplifies the process of contacting your bot from a device. On the channel registration page, the drop-down at the top associates your Direct Line Speech channel registration with a speech resource. Once associated, the v1.8 Speech SDK includes a `BotFrameworkConfig::FromSubscription` factory method that will configure a `DialogServiceConnector` to contact the bot you've associated with your subscription.
44
+
45
+
If you're still migrating your client application from v1.7 to v1.8, `DialogServiceConfig::FromBotSecret` may continue to work with a non-empty, non-null value for its channel secret parameter, e.g. the previous secret you used. It will simply be ignored when using a speech subscription associated with a newer channel registration. Please note that the value *must* be non-null and non-empty, as these are checked for on the device before the service-side association is relevant.
46
+
47
+
48
+
For a more detailed guide, please see the [tutorial section](tutorial-voice-enable-your-bot-speech-sdk.md#register-the-direct-line-speech-channel) that walks through channel registration.
49
+
39
50
**Q: I get a 401 error when connecting and nothing works. I know my speech subscription key is valid. What's going on?**
40
51
41
52
**A:** When managing your subscription on the Azure portal, please ensure you're using the **Speech** resource (Microsoft.CognitiveServicesSpeechServices, "Speech") and *not* the **Cognitive Services** resource (Microsoft.CognitiveServicesAllInOne, "All Cognitive Services"). Also, please check [Speech service region support for voice assistants](regions.md#voice-assistants).
> The steps in this tutorial do not require a paid service. As a new Azure user, you'll be able to use credits from your free Azure trail subscription and the free tier of Speech Services to complete this tutorial.
37
+
> The steps in this tutorial do not require a paid service. As a new Azure user, you'll be able to use credits from your free Azure trial subscription and the free tier of Speech Services to complete this tutorial.
38
38
39
39
Here's what this tutorial covers:
40
40
> [!div class="checklist"]
@@ -61,21 +61,21 @@ Here's what you'll need to complete this tutorial:
61
61
The client app that you'll create in this tutorial uses a handful of Azure services. To reduce the round-trip time for responses from your bot, you'll want to make sure that these services are located in the same Azure region. In this section, you'll create a resource group in the **West US** region. This resource group will be used when creating individual resources for the Bot-Framework, the Direct Line Speech channel, and Speech Services.
62
62
63
63
1. Sign in to the [Azure portal](https://portal.azure.com).
64
-
2. From the left navigation, select **Resource groups**. Then click **Add** to add a new resource group.
65
-
3. You'll be prompted to provide some information:
64
+
1. From the left navigation, select **Resource groups**. Then click **Add** to add a new resource group.
65
+
1. You'll be prompted to provide some information:
66
66
* Set **Subscription** to **Free Trial** (you can also use an existing subscription).
67
67
* Enter a name for your **Resource group**. We recommend **SpeechEchoBotTutorial-ResourceGroup**.
68
68
* From the **Region** drop-down, select **West US**.
69
-
4. Click **Review and create**. You should see a banner that read **Validation passed**.
70
-
5. Click **Create**. It may take a few minutes to create the resource group.
71
-
6. As with the resources you'll create later in this tutorial, it's a good idea to pin this resource group to your dashboard for easy access. If you'd like to pin this resource group, click the pin icon in the upper right of the dashboard.
69
+
1. Click **Review and create**. You should see a banner that read **Validation passed**.
70
+
1. Click **Create**. It may take a few minutes to create the resource group.
71
+
1. As with the resources you'll create later in this tutorial, it's a good idea to pin this resource group to your dashboard for easy access. If you'd like to pin this resource group, click the pin icon in the upper right of the dashboard.
72
72
73
73
### Choosing an Azure region
74
74
75
75
If you'd like to use a different region for this tutorial these factors may limit your choices:
76
76
77
-
* Ensure that you use a [supported Azure region](https://docs.microsoft.com/azure/cognitive-services/speech-service/regions#voice-assistants).
78
-
* The Direct Line Speech channel uses the text-to-speech service, which has standard and neural voices. Neural voices are [limited to specific Azure regions](https://docs.microsoft.com/azure/cognitive-services/speech-service/regions#standard-and-neural-voices).
77
+
* Ensure that you use a [supported Azure region](regions.md#voice-assistants).
78
+
* The Direct Line Speech channel uses the text-to-speech service, which has standard and neural voices. Neural voices are [limited to specific Azure regions](regions.md#standard-and-neural-voices).
79
79
* Free trial keys may be restricted to a specific region.
80
80
81
81
For more information about regions, see [Azure locations](https://azure.microsoft.com/global-infrastructure/locations/).
@@ -140,14 +140,18 @@ Now that you've created some resources, let's build a bot. We're going to start
3. From the toolbar, select **File** > **Open** > **Project/Solution**, and open the project file of the Echo Bot that's been configured for use with Direct Line Speech channel:
4. After the project is loaded, press `F5` to run the project.
152
156
153
157
### Test with the Bot Framework Emulator
@@ -158,11 +162,12 @@ The [Bot Framework Emulator](https://github.com/microsoft/botframework-emulator)
158
162
2. Launch the Bot Framework Emulator and open your bot:
159
163
***File** -> **Open Bot**.
160
164
3. Enter the URL for your bot. For example:
165
+
161
166
```
162
167
http://localhost:3978/api/messages
163
168
```
164
-
4. Use the UI to communicate with your bot using typed text. Confirm that you get a response.
165
169
170
+
4. Use the UI to communicate with your bot using typed text. Confirm that you get a response.
166
171
167
172
## Deploy your bot to an Azure App Service
168
173
@@ -172,26 +177,30 @@ The next step is to deploy the Echo Bot to Azure. There are a few ways to deploy
172
177
> Alternatively, you can deploy a bot using the [Azure CLI](https://docs.microsoft.com/azure/bot-service/bot-builder-deploy-az-cli) and [deployment templates](https://github.com/microsoft/BotBuilder-Samples/tree/master/experimental/directline-speech/csharp_dotnetcore/02.echo-bot/DeploymentTemplates).
173
178
174
179
1. From Visual Studio, open the Echo Bot that's been configured for use with Direct Line Speech channel:
2. In the **Solution Explorer**, right-click the **EchoBot** solution and select **Publish...**
179
-
3. A new window titled **Pick a publish target** will open.
180
-
3. Select **App Service** from the left navigation, select **Create New**, then click **Publish**.
181
-
5. When the **Create App Service** window appears:
184
+
185
+
1. In the **Solution Explorer**, right-click the **EchoBot** solution and select **Publish...**
186
+
1. A new window titled **Pick a publish target** will open.
187
+
1. Select **App Service** from the left navigation, select **Create New**, then click **Publish**.
188
+
1. When the **Create App Service** window appears:
182
189
* Click **Add an account**, and sign in with your Azure account credentials. If you're already signed in, select the account you want from the drop-down list.
183
190
* For the **App Name**, you'll need to enter a globally unique name for your Bot. This name is used to create a unique bot URL. A default value will be populated including the date and time (For example: "EchoBot20190805125647"). You can use the default name for this tutorial.
184
191
* For **Subscription**, set it to **Free Trial**
185
192
* For **Resource Group**, select **SpeechEchoBotTutorial-ResourceGroup**
186
193
* For **Hosting Plan**, select **SpeechEchoBotTutorial-AppServicePlan**
187
-
6. Click **Create**
188
-
7. You should see a success message in Visual Studio that looks like this:
194
+
1. Click **Create**
195
+
1. You should see a success message in Visual Studio that looks like this:
196
+
189
197
```
190
198
Publish Succeeded.
191
199
Web App was published successfully https://EchoBot20190805125647.azurewebsites.net/
192
200
```
193
-
8. Your default browser should open and display a page that reads: "Your bot is ready!".
194
-
9. At this point, check your Resource Group **SpeechEchoBotTutorial-ResourceGroup** in the Azure portal, and confirm there are three resources:
201
+
202
+
1. Your default browser should open and display a page that reads: "Your bot is ready!".
203
+
1. At this point, check your Resource Group **SpeechEchoBotTutorial-ResourceGroup** in the Azure portal, and confirm there are three resources:
195
204
196
205
| NAME | TYPE | LOCATION |
197
206
|------|-------|----------|
@@ -250,12 +259,12 @@ At this point, check your Resource Group **SpeechEchoBotTutorial-ResourceGroup**
250
259
Now it's time to register your bot with the Direct Line Speech channel. This channel is what's used to create a connection between your echo bot and a client app compiled with the Speech SDK.
251
260
252
261
1. Locate and open your **SpeechEchoBotTutorial-BotRegistration** resource in the [Azure portal](https://portal.azure.com).
253
-
2. From the left navigation, select **Channels**.
262
+
1. From the left navigation, select **Channels**.
254
263
* Look for **More channels**, locate and click **Direct Line Speech**.
255
-
* Review the text on the page titled **Configure Direct line Speech**, then click **Save**.
256
-
*As part of creation, two **Secret keys** were generated. These keys are unique to your bot. When you write a client app using the [Speech SDK](https://docs.microsoft.com/azure/cognitive-services/speech-service/), you'll provide one of these keys to establish a connection between the client app, the Direct Line Speech channel, and your bot service. In this tutorial, you'll use the Direct Line Speech Client (WPF, C#).
257
-
* Click **Show** and copy one of the keys somewhere you'll be able to easily access it. Don't worry, you can always access the keys from the Azure portal.
258
-
3. From the left navigation, click **Settings**.
264
+
* Review the text on the page titled **Configure Direct line Speech**, then expand the drop-down menu labeled "Cognitive service account."
265
+
*Select the speech resource you created earlier (e.g. **SpeechEchoBotTutorial-Speech**) from the menu to associate your bot to your speech subscription key.
266
+
267
+
1. From the left navigation, click **Settings**.
259
268
* Check the box labeled **Enable Streaming Endpoint**. This is needed to enable a communication protocol built on web sockets between your bot and the Direct Line Speech channel.
0 commit comments