This project provides you with the scripts needed to deploy the necessary resources for a Microsoft Speech Studio demo.
- An Azure subscription.
- PowerShell
-
A new window should pop up that prompts you to log into your Azure account.
-
Once logged in your should be greeted with the below screen:
-
Make sure the correct "Directory" and "Subscription" are selected.
-
Next, you are able to edit the name of "Resource Group Name", "Site Name", and input a value for "Signalr_service_name". Also, choose the "SiteLocation" of "West US 2".
*Recommendation: Make the names easy to remember. You will be using them later. -
Click "Next" at the bottom of the page.
-
The next page will list the Azure resources that will be deployed. Click "Deploy" to continue.
-
It will take a few minutes for all the resources to be deployed, but once it is complete you should see the following page.
-
You are now ready to deploy the Speech Services.
-
Clone the VoiceTest repo to your local machine.
-
In PowerShell, Navigate to the "deployment" folder of the cloned repo and run the createSpeechApp.ps1 script.
\voicetest-master\voicetest-master> cd deployment
.\createSpeechApp.ps1
-
The script will prompt you for the following information(theses resources will be in a resource group named the same as your sitename):
• siteName – whatever you used for the sitename in "Deploying Azure Resources"
• speechResourceKey – the key from the -speech resource
• luisauthoringkey – the key from the -luisauthoringkey resource
• your Azure subscription id
-
Once deployed your should get the following message:
Speech commands have been published.
You should see a SpeechApplicationId and a SpeechSubscriptionKey below the above message. Copy these down! You will need them for testing in the UWP app in the next section.
Once you have all the above resources created and deployed you are able to test using a UWP app.
- Visual Studio
- Clone the SpeechCommandAccelerator repo from GitHub
- The SpeechApplicationId
- The SpeechSubscriptionKey
-
In Visual Studio, open the Microsoft.CognitiveServices.Inventory.sln solution file.
-
In the "Solution Explorer", right click Microsoft.CognitiveServices.Inventory.UWP and select "Set as StartUp Project".
-
Expand the Microsoft.CognitiveServices.Inventory project and open "appSettings.json". Update this file with your SpeechApplicationId and SpeechSubscriptionKey from above.
-
Save
-
Ensure Windows is in Develeper Mode To build and deploy UWP apps locally, Windows needs to be in developer mode. You can ensure you have Developer Mode enabled by doing the following:
-
Back in Visual Studio, run the Microsoft.CognitiveServices.Inventory.UWP by clicking the play button at the top of the screen:
-
A prompt will appear asking for permission to use your microphone. Give it permission.
-
The UWP app should now be running, and if everything it connected proplly you should see "Status: connected" at the top:
-
Open a browser window and go to the website you deployed in "Deploying Azure Resources" section (https://.azurewebsites.net/). This will show your starting inventory.
-
Click the Speak button in the UWP app and say "Delete 2 lattes".
-
You will get a confirmation and see a 2 latte change in the deployed website via the signalR connection.
Once the speech service and the azure resources have been deployed, its time to test!
-
Go to the Speech Studio Portal and login using the same account you used for the above deployments.
-
Once logged in, select -speech( is the name you provided in "Deploying Azure Resources" section) and click "Got to Studio" at the top of the page.
-
Click on -commands
-
Open another browser tab and go to the website you deployed in "Deploying Azure Resources" section (https://.azurewebsites.net/)
-
Go back to the Speech Portal and click "Train" located at the top right of the page. Wait for the message that confirms it has succeeded.
-
Click "Test" located near the "Train" button.
-
In the test bot type 'delete 4 Lattes' • It is currently case sensitive for the drink types.
-
You should see the 4 latte change in the deployed website via the signalR connection.
This project welcomes contributions and suggestions from the community.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.