Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Bing API for speech recognition - converts speech to text and vice versa, and also understands the essence of the utterance for a natural answer.

...

Image Removed

2) 
Image Removed

3)To use these API keys on the Webitel you must have a Token for them. To get it you can use any REST client.

Select the region from the link: Image Added

Fig. 1. Pay as You Go (Standard S0)

  • You can obtain a trial key at the following link: https://

...

...

...

In response, you will get your token:
Image Removed

Now you have the key and the token:

...

Below is an example of how to obtain the necessary data using the Free Account as an example.

Sign in. To do this, follow the link https://azure.microsoft.com/en-us/free/ai-services/ and click the Start free button (Figure 2).

Image Added

Fig.2. Start free

After registration, you will be directed to the main page, where you should enter "speech" in the search bar (1), and then select "speech services" from the dropdown menu (2). (Fig.3).

Image Added

Fig.3. Speech services

Next, you need to select Azure AI Services and click on Create (Fig. 4) (1).

Image Added

Fig. 4. Create button

Next (Fig.5) you need to enter the region (1), the name (2), select the Standard S0 pricing tier (3), and click on Review+Create (4) to proceed.

Image Added

Fig.5 Create Speech Services

Info

Important!

Transcription does not work if a trial (demo) key is installed. You must use a commercial key with a connected card.

After passing the validation, you will be prompted to create a voice service. Click on Create.

Your voice service has been successfully created. Next, you need to select the resource you created. To do this, go to the Home page, then click on Speech Services (Fig. 6)

Image Added.

Fig. 6.  Home. Speech Services

To view and manage keys for the service, click on the service you created earlier, then select Key 1 (Fig. 7) to configure the voice profile.

Image Added

Fig.7. Keys and endpoints