search

Azure-Samples / Cognitive-Services-Voice-Assistant

Welcome to the Microsoft Voice Assistant samples repository! Here you will find samples to help you get started building client application for your bot or Custom Command service. You will also be able to easily deploy a working Custom Command based Voice Assistant to your own Azure subscription
MIT License
102 stars 99 forks source link

Azure cognitive speech to text API failing - bad request 400 #580

Closed carbonrider closed 2 years ago

carbonrider commented 2 years ago

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Using sample program (Java) to evaluate Speech to Text service

Any log messages given by the failure

Following log message is dispalyed WebSocket upgrade failed: Bad request (400). Please verify the provided subscription details and language information.

Expected/desired behavior

Should able to invoke Speech To Text API

OS and Version?

Windows 11

Versions

Azure cognitiveservices speech - 1.20.0

Mention any other details that might be useful

I verified the keys and region in Azure portal and everything is correct.

Thanks! We'll be in touch soon.

dargilco commented 2 years ago

@carbonrider Can you use the same speech key and region in the speech recognition Java sample to verify that things work there? For example, the recognitionWithMicrophoneAsync() sample https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/samples/java/jre/console

chschrae commented 2 years ago

closing as this has been waiting for a response for more than 14 days

carbonrider commented 2 years ago

Thanks, it didn't work. The error continued and we shifted to RevAI. We have been using AWS, GCP AI etc services and it doesn't have so much of hassle.

chschrae commented 2 years ago

@carbonrider I'm sorry you weren't able to get it to work. If you would like to continue debugging it with us, we would be happy to try and figure out the issue. Otherwise, I'm happy you were able to find a solution and I will just leave the issue closed.