-
Notifications
You must be signed in to change notification settings - Fork 188
wrong websocket address #64
Comments
The sample is for using Speech Recognition API(using general-purpose model without customization), so the endpoint "wss://speech.platform.bing.com" is correct. Thanks, |
hello @zhouwangzw, Subsection OPUS |
On the Custom Speech Service Doc, "Send requests by using the Speech Protocol" asks you to replace the endpoint in the sample with your own deployment endpoint:
The OPUS section you mentioned is for the general-purpose speech recognition API (instead of custom speech API), so it uses the "wss://speech.platform.bing.com" endpoint. |
maybe u can help me on my next issue: my 15 seconds test file is working, but when i change to my 3 minutes testfile, cutsom speech service is not recognizing the whole file(stops after 15 sec). Any idea what i can change? i tried recognitionmode dictation and conversation |
For custom speech issues, please contact the custom speech service team. We do not own their service. |
how to contact? |
Our services aren't available right nowWe're working to restore all services as soon as possible. Please check back soon. Ref A: E46EE7F8DE28480E89BA1F908D77D2DC Ref B: PHX01EDGE0217 Ref C: 2018-03-29T15:44:18Z |
See pull request #82 that addresses this issue. |
to make this work i needed to change the websocket address in this line
return Storage.Local.GetOrAdd("Host", "wss://speech.platform.bing.com");
to
return Storage.Local.GetOrAdd("Host", "wss://{your Deployment ID}.api.cris.ai");
i also changed this in my gulped JS file under node_modules/microsoft-speech-browser-sdk/distrib/src/sdk/speech.browser/SpeechConnectionFactory.js
you should change this in your sample, as it is not working at the moment
The text was updated successfully, but these errors were encountered: