I am currently trying to create a bot for several platform : Slack, MS Team and Cisco Spark.
I did some test with gupshup, using their bot : gupshup proxy bot, and it works well on Slack and Spark. But neither my bots nor gupshup proxy bot reply on MS Team.
My admin already enable sideloading app.
Do you have the same issues ?
There is some configuration issue with the proxy bot. We at Gupshup are getting it fixed and it should start working for everyone soon.
Although as a workaround please try publishing your bot on MS teams for testing. This guide's publish section explains the steps which you need to follow.
PS: I work for Gupshup.
Related
I am a newbie to chatbots, and built one agent in dialogflow and written a node server to connect it with my custom UI. Now my next requirement is to integrate this bot with my Microsoft Teams Channel.
For what I have searched there seem to be similar steps being followed as with skype but those didn't make sense to me. Though I am not really clear about it, if anyone can give a step wise points to follow to do the same, it will be great help.
Also just to be clear, can someone confirm if it's really possible to integrate Google's dialogflow with Microsoft's Teams?
I don't know of any official instructions explaining how to connect a Dialogflow bot to Teams, but Skype and Teams both communicate through the Azure Bot Service using the Bot Framework protocol. When a Dialogflow bot connects to Skype what it's really connecting to is the Azure Bot Service, so you should be able to follow the same instructions for any ABS channel, Teams included.
I have a solution that works on Identity and Auth, The solution runs a WhatsApp Bot that ask the user for images doing specific gestures as part of biometrics for authentication. That works great.
Then We are working with to create support for that bot in Microsoft Teams and other Channels using Azure Bot Service / Bot Framework , but We're facing troubles because the documentation explicitly says that file exchange between ms-teams bots and users is not supported on Mobile.
Do you know any workaround or OSS component that could remove this blocker?
Any ideas will be appreciated.
the docs Send and receive files with a bot:
I'm running a bot with Microsoft Teams and have it setup in Azure. It's a demo bot from the bot builder code Microsoft released. I'm pointing it to a local server that has ngrok running. This works fine when I test via Web Chat in Azure but it doesn't work at all when working with Teams.
The app sideloads properly and the manifest is accepted by teams. No response appears to be making it to the server. When I click to show the Bot Channels in Azure some kind of OPTIONS query is being sent to the server and the demo bot throws a 405 error.
The bot id is f22039b8-5400-4569-a0f2-5bdceb8431f2 but I can't talk to it in 1:1 chat either when I specify this ID.
There are no logs in Azure or teams- I don't see any errors, so I have no idea how to start debugging this.
This is a link to someone with the exact same question:
Bot not answering messages in microsoft teams
There is currently a bug in our bot registration code that is causing this. We are currently investigating its root cause.
As a workaround, add the Skype channel and the MS Teams channel to the bot.
Im trying to make a custom bot in MS Teams.
My Admin has not yet enabled "Sideloading", but I have the option to "Create a Custom Bot", yet I cannot find any information between the differences of these 2 options?
Has the "Custom Bot" replaced sideloading? In which case, how can i connect my bot to my team? Its hosted on azure, but it kept saying "Sorry, there was a problem encountered with your request", when I had it set up using the Custom Bot.
The bot works perfectly, using both the emulator and the bot framework.
A custom bot is not a Bot Framework bot - it's really designed as a simple way to send information from Teams to an external application (Slack calls them "Outgoing Webhooks"). It's not designed for real bot conversations in the Bot Framework sense. The feature (and its limitations) are documented in detail here.
You can't use bots in a team without sideloading - that's what sideloading is for. When you sideload an app that contains a bot - more info here - it registers additional information needed for a bot to work in a team, as well as a record of the consent for that bot to operate in a team.
I need to be able to initiate a connection from the bot to a SfB user. The bot will be making the connection as a published Web App on Azure.
The bot can have its own SfB id and will message people from there.
If it can be achieved for Skype instead of SfB, I'd still like to know how I would go about implementing a solution for that.
The Bot term here is misleading me a bit, but from the scenario you mentioned, it sounds like a chat between a Web App using the Skype Web SDK and an SfB client. As long as the Web App is using a SfB creds, that should be possible.
You can't use SfB with bot framework right at the moment. But you can use skype instead. To create a bot which work with the skype please follow the below steps.
First register a new bot inside the bot framework. Click here. Keep in mind that you need Microsoft account for that.(outlook, live)
Then download bot application template from here. Save the zip file to your Visual Studio 2015 templates directory which is traditionally in “%USERPROFILE%\Documents\Visual Studio 2015\Templates\ProjectTemplates\Visual C#"
After that you can download bot emulator to check your bot from here
Add your AppId and AppSecret (You can find that from the bot registration dash board) inside web config file. Then run your application and check whether you get the same wording you send through the emulator.
If all are working you can connect it to the skype like this. First go to dashboard in web. Enable skype and there you can find few steps to follow. If you success with that steps you can see your bot inside your skype where you can communicate. *For publish to public crowd it takes time and your bot go through a quality process which handle by Microsoft.
FYI - Skype for Business was announced as a new channel today on Build 2017 :)