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

[Tracking] DLSpeech: Proactive message is not supported #2682

Open
compulim opened this issue Dec 6, 2019 · 3 comments
Open

[Tracking] DLSpeech: Proactive message is not supported #2682

compulim opened this issue Dec 6, 2019 · 3 comments
Labels
area-direct-line-speech backlog Out of scope for the current iteration but it will be evaluated in a future release. external-cognitive-services feature-request Azure report label

Comments

@compulim
Copy link
Contributor

compulim commented Dec 6, 2019

If you would want to prioritize this feature work, please vote and optionally, provide a user story.

Feature Request

Proactive message is not supported when using Direct Line Speech.

[Enhancement]

@corinagum corinagum added backlog Out of scope for the current iteration but it will be evaluated in a future release. and removed Pending labels Jan 15, 2020
@corinagum corinagum added feature-request Azure report label and removed Enhancement labels Sep 23, 2020
@birla
Copy link

birla commented Feb 8, 2023

We have achieved this by keeping a reference of the ConnectorClient from the turnState and putting it back into the state in the continue conversation callback. Without the original connector client, there is an error from node-fetch as the service URL in the activity is not an HTTP URI.

@corinagum please suggest if there could be any pitfalls in this approach.

@corinagum
Copy link
Contributor

Hi @birla, I am no longer a member of the Web Chat team. Please get in contact with @compulim

@birla
Copy link

birla commented Feb 14, 2023

We have achieved this by keeping a reference of the ConnectorClient from the turnState and putting it back into the state in the continue conversation callback. Without the original connector client, there is an error from node-fetch as the service URL in the activity is not an HTTP URI.

@corinagum please suggest if there could be any pitfalls in this approach.

@compulim Please have a look. I can share some sample code, if required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-direct-line-speech backlog Out of scope for the current iteration but it will be evaluated in a future release. external-cognitive-services feature-request Azure report label
Projects
None yet
Development

No branches or pull requests

3 participants