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/tutorial-voice-enable-your-bot-speech-sdk.md
+10-12Lines changed: 10 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: nitinme
8
8
ms.service: cognitive-services
9
9
ms.subservice: speech-service
10
10
ms.topic: conceptual
11
-
ms.date: 02/21/2020
11
+
ms.date: 02/25/2020
12
12
ms.author: dapine
13
13
---
14
14
@@ -150,7 +150,7 @@ Now that you've created some resources, let's build a bot. We're going to start
150
150
4. After the project is loaded, press <kbd>F5</kbd> to build and run the project.
151
151
5. A browser should launch and you'll see a screen looking similar to this.
152
152
> [!div class="mx-imgBorder"]
153
-
> 
153
+
> [](media/tutorial-voice-enable-your-bot-speech-sdk/echobot-running-on-localhost.png#lightbox)
154
154
155
155
### Test the bot sample with the Bot Framework Emulator
156
156
@@ -167,7 +167,7 @@ The [Bot Framework Emulator](https://github.com/microsoft/botframework-emulator)
167
167
and press "Connect".
168
168
4. The bot should immediately greet you with "Hello and welcome!" message. Type in any text message and confirm you get a response from the bot.
169
169
5. This is what an exchange of communication with an Echo Bot instance might look like:
@@ -184,13 +184,14 @@ The next step is to deploy the Echo Bot to Azure. There are a few ways to deploy
184
184
185
185
1. In the **Solution Explorer**, right-click the **EchoBot** project and select **Publish...**
186
186
1. A new window titled **Pick a publish target** will open.
187
-
1. Select **App Service** from the **Azure services** navigation, select **Create New**, then click **Publish**.
187
+
1. Select **App Service** from the **Azure services** navigation, select **Create New**, then click **Create Profile**.
188
188
1. When the **Create App Service** window appears:
189
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.
190
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.
191
191
* For **Subscription**, set it to **Free Trial**
192
192
* For **Resource Group**, select **SpeechEchoBotTutorial-ResourceGroup**
193
193
* For **Hosting Plan**, select **SpeechEchoBotTutorial-AppServicePlan**
194
+
* For **Application Insights**, leave as **None**
194
195
1. Click **Create**
195
196
1. You should see a success message in Visual Studio that looks like this:
196
197
@@ -228,12 +229,9 @@ Now that you've created an Azure App Service to host your bot, the next step is
228
229
> [!NOTE]
229
230
> If you'd like to learn more about how bots leverage channels, see [Connect a bot to channels](https://docs.microsoft.com/azure/bot-service/bot-service-manage-channels?view=azure-bot-service-4.0).
| SpeechEchoBotTutorial-Speech | Cognitive Services | West US |
255
253
256
254
> [!IMPORTANT]
@@ -267,7 +265,7 @@ Now it's time to register your bot with the Direct Line Speech channel. This cha
267
265
* Select the speech resource you created earlier (e.g., **SpeechEchoBotTutorial-Speech**) from the menu to associate your bot to your speech subscription key.
268
266
* Click **Save**.
269
267
270
-
1. From the **Azure services** navigation, click **Settings**.
268
+
1. From the **Bot management** navigation, click **Settings**.
271
269
* 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.
272
270
* Click **Save**.
273
271
@@ -306,6 +304,7 @@ If your issue isn't addressed in the table, see [Voice assistants: Frequently as
306
304
Every bot sends and receives **Activity** messages. In the **Activity Log** window of Direct Line Speech Client, you'll see timestamped logs with each activity that the client has received from the bot. You can also see the activities that the client sent to the bot using the [`DialogServiceConnector.SendActivityAsync`](https://docs.microsoft.com/dotnet/api/microsoft.cognitiveservices.speech.dialog.dialogserviceconnector.sendactivityasync) method. When you select a log item, it will show the details of the associated activity as JSON.
307
305
308
306
Here's a sample json of an Activity the client received:
307
+
309
308
```json
310
309
{
311
310
"attachments":[],
@@ -392,7 +391,6 @@ You can chose from any one of the languages mentioned in the [speech-to-text](la
392
391
2. Close the settings page, and click on the Reconnect button to establish a new connection to your echo bot.
393
392
3. Click on the microphone button, and say a phrase in German. You will see the recognized text and the echo bot replying with the default German voice.
394
393
395
-
396
394
### Change the default bot voice
397
395
398
396
Selecting the text-to-speech voice and controlling pronunciation can be done if the Bot specifies the reply in the form of a [Speech Synthesis Markup Language](speech-synthesis-markup.md) (SSML) instead of simple text. The echo bot does not use SSML, but we can easily modify the code to do that. In the example below we add SSML to the echo bot reply, such that the German voice Stefan Apollo (a male voice) will be used instead of the default female voice. See list of [Standard Voices](language-support.md#standard-voices) and [Neural Voices](language-support.md#neural-voices) supported for your language.
0 commit comments