Cognitive-Services-Voice-Assistant icon indicating copy to clipboard operation
Cognitive-Services-Voice-Assistant copied to clipboard

400 error upon clicking reconnect

Open fadyanwar opened this issue 3 years ago • 4 comments

Please provide us with the following information:

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

Follow instructions as per https://github.com/Azure-Samples/Cognitive-Services-Voice-Assistant/blob/main/clients/csharp-wpf/README.md At step 4 you will get a 400 error

Any log messages given by the failure

Error (BadRequest) : WebSocket upgrade failed: Bad request (400). Please verify the provided subscription details and language information. SessionId: 6cf519fd97c042d4b3db09fe58531548

Expected/desired behavior

Should connect instead as per documentation

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?) Win 10

Versions

WindowsVoiceAssistantClient-20210224.1

Mention any other details that might be useful

The documentation is also not clear on how to connect to the bot itself as it shows only how to configure the Azure Cognitive Services Speech key and region at step 3


Thanks! We'll be in touch soon.

fadyanwar avatar May 06 '21 22:05 fadyanwar

@fadyanwar Have you followed the instructions here to register your bot with Bot Framework's Direct Line Speech Channel? Darren

dargilco avatar May 06 '21 23:05 dargilco

Same issue for me 400: Bad request (400). Please verify the provided subscription details and language information

JasonMcEvoy avatar Mar 15 '22 10:03 JasonMcEvoy

I am facing the same issue. I followed the mentioned tutorial and everything seems to work. WebChat and Bot Framework Evaluater are working fine. After Adding the Voce Assistant Client I just get the error message.

SemanticEdge avatar Jul 15 '22 11:07 SemanticEdge

Hello, I am still facing the same error as above as of today. Any solutions?

devshah096 avatar Mar 31 '23 01:03 devshah096