I am following this guide to develop chatbot:
https://learn.microsoft.com/en-us/azure/bot-service/bot-builder-howto-v4-luis?view=azure-bot-service-4.0&tabs=csharp#test-the-bot
When I tried to test the bot with Bot Framework Emulator, I am unable to get a response.
[15:17:43]Emulator listening on http://[::]:60595
[15:17:43]ngrok not configured (only needed when connecting to remotely hosted bots)
[15:17:43]Connecting to bots hosted remotely
[15:17:43]Edit ngrok settings
[15:17:43]-> conversationUpdate
[15:17:44]POST500directline/conversations/<conversationId>/activities
[15:17:51]-> messagehi
[15:17:51]POST500directline/conversations/<conversationId>/activities
Is this have to do with my company security blocking ngrok?
My Echo bot works fine, but seems like I am having issue with the LUIS function. Is there a way to make it work and link it to MS teams?
Help needed
Related
We are facing issue in Azure chatbot, LUIS is not responding in Test in Web Chat on Azure. Chatbot is working fine Emulator and integration with direct line. My client is testing always from Azure so it is some critical issue for us. We are using Standard LUIS runtime subscription. It would be great if someone can help us. I did below trouble shooting steps.
Subscription key for standard plan and verify keys , it is correct.
Re-deployed
See application Insights error code is 400 only when i run it from Azure Test in Web Chat
I opened MS support ticket for this issue and find same issue was running at support team side as well. There were no code and configuration change after some time it suddenly start functioning.
Thanks
We have set up the following network:
chatbot setup
Our internal chatbot is written in C#, and runs in .NET core linux env.
As of now, we are able to use the Bot Framework's Web Cmd to Send and Receive from our Internal Chatbot. But we are unable to use MS Teams to communicate with our Internal Chat Bot. We have set up App ID and App Password in the MS Team's App via App Studio.
We also enabled External App and Sideloading.
Is there any way to troubleshoot this? or is there something we may have missed?
Thanks in advance
As per this documentation, You need to also enable the Teams channel for your bot in the Azure Portal under Bot Management > Channels, for this to work.
I have developed a bot that works perfectly on my local machine and accessible through all channels via ngrok.
However, the Bot doesn’t work on its deployed Azure url which is https://mybot.azurewebsites.com/api/messages A test with the webchat or bot emulator returns an error 500 without further information on exact cause of the issue. How would I debug so that I can find out more information on what's causing the breakdown?
I have registered my bot application in MS Bot directory. I can able to communicate with my message endpoint using Bot Framework Emulator. but when I tried the same in MS teams and Skype. the bot is not responding to my message.
Yes, it's possible. You need to use a tool like ngrok to create a tunnel to your local environment.
In a nutshell, you need to run (assuming your local bot is running on port 3979):
ngrok http -host-header=rewrite 3979
And then update your bot endpoint in the Bot Framework portal with the url ngrok will provide you.
(source: windows.net)
See this post for all the details
Is it possible to talk to my bot via WebChat like I'm doing it via Emulator, Without registering and publishing the bot on Azure?
You will need to register the bot in the BotFramework portal and enable the WebChat channel. Registering the bot doesn't mean that the bot will be published to the bot directory. You don't need to publish the bot to using it.
Also, you don't need to publish the bot in Azure to use it. Instead, you could use ngrok to create a secure tunnels to localhost.
You can check the following links:
https://docs.botframework.com/en-us/node/builder/guides/core-concepts/#debugging-locally-using-ngrok
https://robinosborne.co.uk/2016/09/19/debugging-botframework-locally-using-ngrok/
Update 21/12
Just remembered that since the WebChat is now open source, you might have an option to run it locally as described in the README.md. Below the relevant portion of the docs.