Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Azure Gov] Cognitive Speech API always points to commercial #154

Closed
p-nagpal opened this issue Mar 4, 2020 · 3 comments
Closed

[Azure Gov] Cognitive Speech API always points to commercial #154

p-nagpal opened this issue Mar 4, 2020 · 3 comments

Comments

@p-nagpal
Copy link

p-nagpal commented Mar 4, 2020

This comes from a customer issue: microsoft/BotFramework-WebChat#2969

Webchat consumes the cognitive-services-speech-sdk-js and we found that the endpoints for STT API always point to commercial cloud. From customer issue report:

Cognitive Speech API in webchat always points to the commercial endpoint. wss://virginia.stt.speech.microsoft.com instead of wss://virginia.stt.speech.azure.us as stated in this link. This is regardless of using "virginia" or "usgovvirginia" as the region parameter when constructing webSpeechPonyfillFactory.

We noticed that SpeechConnectionFactory uses .stt.speech.microsoft.com regardless of the region and perhaps this is the cause of the issue.

Could you advise us on how to use Speech API in Azure Gov clouds?

@rhurey
Copy link
Member

rhurey commented Mar 4, 2020

From the link:
SR in SpeechSDK: config.fromHost("wss://virginia.stt.speech.azure.us", "");

For the Soverign Clouds you need to use the fromHost method to get the right endpoint.

We're investigating more streamlined solutions in the long run, but for now...

@compulim
Copy link
Contributor

Thanks @rhurey for the tips.

This is done on Web Chat side, in this PR, microsoft/BotFramework-WebChat#3040.

The work is only for traditional STT/TTS but not Direct Line Speech.

@rhurey
Copy link
Member

rhurey commented Mar 26, 2020

Closing then

@rhurey rhurey closed this as completed Mar 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants