Directline speech - web socket ends with 200 response
See original GitHub issueScreenshots
Version
4.9.1
Describe the bug
I have enabled directline speech in our bot by using the following example and I am getting the error “Error during WebSocket handshake: Unexpected response code: 200”. I tried both the options of passing token and passing the subscription key and facing the same issue.
https://github.com/microsoft/BotFramework-WebChat/tree/master/samples/03.speech/a.direct-line-speech
Note: Cognitive speech approach works fine.
What could be the possible cause for this?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Direct Line Authentication in Azure Bot Service - Microsoft Learn
A client can authenticate requests to Direct Line API 3.0 either by using a secret that you obtain from ... HTTP/1.1 200 OK...
Read more >WebChat - Direct Line Speech adapter error: WebSocket ...
It says Error: HTTP 400 Bad Request is an error usually occurs when the request body contains invalid audio data. Only WAV format...
Read more >RFC 7118: The WebSocket Protocol as a Transport for the ...
This document specifies a WebSocket subprotocol as a reliable transport mechanism between Session Initiation Protocol (SIP) entities to enable use of SIP in ......
Read more >Voice.AI Gateway - Product Description - AudioCodes
AI Gateway sends a SIP 200 OK response to the user, ... Voice.AI Gateway closes the WebSocket connection upon the end of the...
Read more >WebSockets for fun and profit - Stack Overflow Blog
By the end of this piece, you should feel comfortable discussing how ... response with an associated code, like 200 OK or 403...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Zerryth We followed the same steps in another instance and it worked fine. Not sure what is the issue with this specific bot instance. Thanks for your help.
Here are the steps I am doing:
My setup:
And about 3a, we have an endpoint that generates the token. Also, I have tried the example given by you in https://github.com/microsoft/BotFramework-WebChat/issues/3407#issuecomment-673130903, by passing the speech key and getting the same error.