Skip to content

Commit 099f477

Browse files
authored
Merge pull request #105499 from IEvangelist/moreBotTurotialFun
Finalized bot tutorial updates...
2 parents 1163ce0 + 9eadd2a commit 099f477

File tree

1 file changed

+10
-12
lines changed

1 file changed

+10
-12
lines changed

articles/cognitive-services/Speech-Service/tutorial-voice-enable-your-bot-speech-sdk.md

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: nitinme
88
ms.service: cognitive-services
99
ms.subservice: speech-service
1010
ms.topic: conceptual
11-
ms.date: 02/21/2020
11+
ms.date: 02/25/2020
1212
ms.author: dapine
1313
---
1414

@@ -150,7 +150,7 @@ Now that you've created some resources, let's build a bot. We're going to start
150150
4. After the project is loaded, press <kbd>F5</kbd> to build and run the project.
151151
5. A browser should launch and you'll see a screen looking similar to this.
152152
> [!div class="mx-imgBorder"]
153-
> ![echobot-running-on-localhost](media/tutorial-voice-enable-your-bot-speech-sdk/echobot-running-on-localhost.png "EchoBot running on localhost")
153+
> [![echobot-running-on-localhost](media/tutorial-voice-enable-your-bot-speech-sdk/echobot-running-on-localhost.png "EchoBot running on localhost")](media/tutorial-voice-enable-your-bot-speech-sdk/echobot-running-on-localhost.png#lightbox)
154154
155155
### Test the bot sample with the Bot Framework Emulator
156156

@@ -167,7 +167,7 @@ The [Bot Framework Emulator](https://github.com/microsoft/botframework-emulator)
167167
and press "Connect".
168168
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.
169169
5. This is what an exchange of communication with an Echo Bot instance might look like:
170-
![bot-framework-emulator](media/tutorial-voice-enable-your-bot-speech-sdk/bot-framework-emulator.png "Bot Framework emulator")
170+
[![bot-framework-emulator](media/tutorial-voice-enable-your-bot-speech-sdk/bot-framework-emulator.png "Bot Framework emulator")](media/tutorial-voice-enable-your-bot-speech-sdk/bot-framework-emulator.png#lightbox)
171171

172172
## Deploy your bot to an Azure App Service
173173

@@ -184,13 +184,14 @@ The next step is to deploy the Echo Bot to Azure. There are a few ways to deploy
184184

185185
1. In the **Solution Explorer**, right-click the **EchoBot** project and select **Publish...**
186186
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**.
188188
1. When the **Create App Service** window appears:
189189
* 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.
190190
* 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.
191191
* For **Subscription**, set it to **Free Trial**
192192
* For **Resource Group**, select **SpeechEchoBotTutorial-ResourceGroup**
193193
* For **Hosting Plan**, select **SpeechEchoBotTutorial-AppServicePlan**
194+
* For **Application Insights**, leave as **None**
194195
1. Click **Create**
195196
1. You should see a success message in Visual Studio that looks like this:
196197

@@ -228,12 +229,9 @@ Now that you've created an Azure App Service to host your bot, the next step is
228229
> [!NOTE]
229230
> 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).
230231
231-
<!-- https://ms.portal.azure.com/#create/Microsoft.BotServiceConnectivityGalleryPackage -->
232232

233-
1. The first step is to create a new resource for the registration. In the [Azure portal](https://portal.azure.com), click **Create a resource**.
234-
2. In the search bar type **bot**, after the results appear, select **Bot Channels Registration**.
235-
3. Click **Create**.
236-
4. You'll be prompted to provide some information:
233+
1. <a href="https://ms.portal.azure.com/#create/Microsoft.BotServiceConnectivityGalleryPackage" target="_blank">Create an Azure Bot Channels Registration <span class="docon docon-navigate-external x-hidden-focus"></span></a>
234+
2. You'll be prompted to provide some information:
237235
* For **Bot handle**, enter **SpeechEchoBotTutorial-BotRegistration**.
238236
* For **Subscription**, select **Free Trial**.
239237
* For **Resource group**, select **SpeechEchoBotTutorial-ResourceGroup**.
@@ -250,7 +248,7 @@ At this point, check your Resource Group **SpeechEchoBotTutorial-ResourceGroup**
250248
|------|-------|----------|
251249
| EchoBot20190805125647 | App Service | West US |
252250
| SpeechEchoBotTutorial-AppServicePlan | App Service plan | West US |
253-
| SpeechEchoBotTutorial-BotRegistration | Bot Channels Registration | Global |
251+
| SpeechEchoBotTutorial-BotRegistration | Bot Channels Registration | global |
254252
| SpeechEchoBotTutorial-Speech | Cognitive Services | West US |
255253

256254
> [!IMPORTANT]
@@ -267,7 +265,7 @@ Now it's time to register your bot with the Direct Line Speech channel. This cha
267265
* Select the speech resource you created earlier (e.g., **SpeechEchoBotTutorial-Speech**) from the menu to associate your bot to your speech subscription key.
268266
* Click **Save**.
269267

270-
1. From the **Azure services** navigation, click **Settings**.
268+
1. From the **Bot management** navigation, click **Settings**.
271269
* 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.
272270
* Click **Save**.
273271

@@ -306,6 +304,7 @@ If your issue isn't addressed in the table, see [Voice assistants: Frequently as
306304
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.
307305

308306
Here's a sample json of an Activity the client received:
307+
309308
```json
310309
{
311310
"attachments":[],
@@ -392,7 +391,6 @@ You can chose from any one of the languages mentioned in the [speech-to-text](la
392391
2. Close the settings page, and click on the Reconnect button to establish a new connection to your echo bot.
393392
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.
394393

395-
396394
### Change the default bot voice
397395

398396
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

Comments
 (0)