I am running in to an error when trying to reach my bot over SfB. The dashboard shows "There was an error sending this message to your bot: HTTP status code MethodNotAllowed" and SfB chat window shows "Error happened in Skype for business when reaching bot service"
The bot works fine on the web control, bot emulator and skype channel. I am running Bot.Builder 3.8.5 . I tried commenting out [BotAuthentication] but then every channel started to fail after that. Any ideas ?
Turns out an update to Bot.Builder was pushed out and took it to version 3.9.0.0 . After that re publish to Azure and it started working
Related
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 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
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.
I have created two bots via the Azure portal today (NodeJS blank & language understanding) and both bots don't work.
If I launch the emulator in the portal and send a message it states "Couldn't send retry" and the console shows the following:
On the Channels tab under Web Chat it shows the following errors:
My previously created bots work however.
Has anyone an idea what I might be missing here?
I've built a Bot using C#. I tested it using the emulator, web chat, direct line and Skype, and it's working as expected.
I followed the steps to register the bot with skype for business, I waited more than 24 hours to see what's happen.
So far, I can see the Bot as a contact, however, when I try to send a message, the error
"Error happened in Skype for business when reaching bot service. We
saved this conversation. You'll see it soon in the Conversations tab
in Skype for Business and in the Conversation History folder in
Outlook."
Looking for some logs or something, I collected some info, that I'm sharing here.
Analytics from BOT that proves that it's reaching it:
The Log for SFB channel said: "There was an error sending this message to your bot: HTTP status code NotFound"
It's look that the Bot endpoint is not available. When I registered it in SFB, I've been using NGROK (to run agains my machine), but later I've change it to a azure site.
"Old" endpoint is used yet today:
So, all I can guess is that Bot End Point was "registered" at the moment that I made the registration of my Bot in SFB, and now it's not possible to change it.
Does it make sense to anyone of you?
My problem seems to be kind of similar to Bot Framework - An error while sending a message from Skype for Business
Adrián
Ok, I'm sure the problem with the bot was the endpoint registration. I found a powershell script that update the endpoint.
I Opened Windows PowerShell as Administrator and run the ff scripts:
Import-PSSession (New-CsOnlineSession -Credential (Get-Credential))
Set-CsOnlineApplicationEndpoint -Uri sip:username#yourdomain.com
Obviously, I changed username#yourdomain.com with my own.
Then, after waiting 8 hours (or so), I was able to communicate with the bot, using SFB as channel.
Bot running as expected
I hope this can be useful for others.