I tried to connect a bot built using Microsoft botframework to Microsoft team with no luck.
If I use other channels like webchat it works like a charm ! , I've tried to create new simple bot using Azure Bot services. In a matter of fact, I left the generated echo bot code as is , when I tried to connect to Teams channel I got an error message "Oops something went wrong" as you can see in this screen capture
Bot Service Azure Error
tried to use the Microsoft ID and add the bot to MS teams app package however the same behavior applies (bot is never responding)
if the bot is running locally using ngrok there is no message been logged to ngrok endpoint at all as if msteams client is not sending the conversation at all.
I suspect there is a problem with bot registration.
P.S. Skype channel is not working as well.
Thanks,
Amr
Related
I've created a bot based on the following sample:
https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/typescript_nodejs/57.teams-conversation-bot
Everything looks well so far and worked in my first bot. But with my second bot I've created when I start a conversation with the bot, I get a "Failed to send" error in Microsoft Teams on my desktop.
When I use teams in the web I can see in the dev tools the following error message for the request:
https://emea.ng.msg.teams.microsoft.com/v1/threads
Error:
One or more of the user ids provided are not valid.
I'm lost on what could be wrong. Any hint would be highly appreciated.
I was seeing the same error after creating a second bot for testing and realized I had forgotten to setup the Teams channel in Azure configuration.
So double-check that the Microsoft Teams channel is running:
I am feeling a little bit lost with Microsoft.
https://dev.skype.com/webcontrol
Skype is telling me that I need a Bot ID (also known as Microsoft App ID).
At the same website is a link labeled with Microsoft App ID pointing to
https://learn.microsoft.com/en-us/azure/bot-service/?view=azure-bot-service-4.0
Do I have to "Create a bot with the Azure Bot Service" so that I get a Microsoft App ID that works with Skype?
Or can I get a Microsoft App ID that is independent from Azure?
In order to have a bot that works with Skype, you need to have a bot channels registration. If you already have a bot hosted elsewhere and you would like to use the Bot Service to connect it to channels such as Skype, Twilio, Messenger etc., you will need to register your bot with the Bot Service. A Bot Channels Registration bot service allows you to use Bot Service functionality. A registration bot lets you connect your bot to channels. You cannot get a Microsoft App ID that is independent from Azure.The Microsoft AppID is the same as the Bot ID that skype wants for the webchat bubble.
I have created Microsoft Bot and hosted on azure with proper microsoft appid and password.
In Bot Channel, I have registred the hosted app service(bot).
My bot is working with emulator. but when i tried to work with other channel such as webchat, direct line, it is not working, it is showing error as "Sorry, my bot code is having an issue"
Please assist me to resolve the issue
I am using Microsoft Botframework to publish a bot (Channel Registration). When I try enabling the channels , I see the bot to be working in Slack , Skype, MS Teams & Web chat . However (despite following the steps to enable bot in SFB) I could not get the bot working in Skype for Business. I keep getting the error.
"Sorry, we ran into a problem at our end."
Neither do I see any log to debug.
Waited more than 24 hrs to ensure it is not the sync issue. But issue still remains. Any help appreciated !!
I am not clear with the error as to from which end it is being thrown.
I need you to follow the below steps:
Publish Bot in azure as an app service, through VS if you are coding through c#.
Create a "Bot channel registration" in azure and connect the above app service and Bot channel registration(simple use the URL of the app service append it with /api/messages and insert the same as messaging endpoint in Bot channel registration).
use the app id and app secret in bot solution and republish the app service.
Inside Bot channel registration click on channel and enable it for Skype for business(you will find your BOT in SFB using the credentials you have used to create the bot channel registration).
Finally got it working. What i noticed is the following
I faced the issue when I used the SIP URI as somebot#mydomain.com to register the bot in my tenant.
And i got it working when I used the SIP URI as somebot#mydomain.onmicrosoft.com.
Unsure on the reasoning though :)
And btw thanks #Tanmoy for your answer aswell !!
I have registered an MS bot on over Skype for business channel, the bot was searchable and responding for few days but no I am getting below error in "Bot Channel registration">channels> issues
"There was an error sending this message to your bot: HTTP status code NotFound".
On SFB I get error
"Error happened in Skype for Business service when reaching bot service".
Bot is hosted over azure in web API working and fine in Web channel, whereas with SFB its not hitting the API endpoint.
Every time I send a message from skype for businesss, I get the same error on bot channel registration.
Environment is a hybrid of Lync 2010 and Skype for business online and after registration bot was searchable and responding to users on SFB online.
What could be the possible reason for this error?
For my situation I realized that if I dont change messaging endpoint area everything goes well.I mean I was adding Microsoft App Id to my endpoint like https://myendpoint/{{MicrosoftAppId}} after bot created .It is because you can have your microsoft app id after you create the bot.What is awkard is that despite messaging endpoint looks an editable area when I change it I am falling into error place where my endpoint is never called[again webchannel works fine , it looks Skype For Business needs some refactoring]. However I found that if I dont change this endpoint url bot works fine for Skype For Business and my endpoint is hit successfully .So keep your messaging endpoint constant and set it only when creating your bot.