search

Azure-Samples / SpeechToText-WebSockets-Javascript

SDK & Sample to do speech recognition using websockets in Javascript
MIT License
216 stars 151 forks source link

Abnormal Closure - status code: 1006 #75

Open amenglong opened 6 years ago

amenglong commented 6 years ago

Hi team,

Several times have met below error:

  1. Bing speech: bing speech error

  2. CRIS end point: cris error

What may be the reason? How can I avoid/solve it? Thanks!

rsquizz commented 6 years ago

+1 on Bing speech

mattquinn4 commented 6 years ago

+1 on CRIS

rsquizz commented 5 years ago

If anyone is following, I'm still running into this problem.

AbiJaerltrics commented 5 years ago

I facing this problem too. Any solution?

paimeghna commented 5 years ago

@amenglong @rsquizz Has this issue been resolved yet? I'm in a need for a solution on this one

rsquizz commented 5 years ago

I haven’t run into this lately, but we’ve mostly switched over to the newer Speech API.

On Wed, Dec 26, 2018 at 7:23 AM Meghna Pai notifications@github.com wrote:

@amenglong https://github.com/amenglong @rsquizz https://github.com/rsquizz Has this issue been resolved yet? I'm in a need for a solution on this one

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/Azure-Samples/SpeechToText-WebSockets-Javascript/issues/75#issuecomment-449959238, or mute the thread https://github.com/notifications/unsubscribe-auth/AY8nDVO9LHIU3Hu2atqSC8lk32q8n3Chks5u82pAgaJpZM4SoUav .

SaibabaGajulawar commented 5 years ago

+1 any solution for this one.

Joll59 commented 5 years ago

Resolution I found: verify service region endpoint matches the azure speech service endpoint you provisioned. Once I matched service region, things just worked.