tompaana / intermediator-bot-sample

A sample bot, built with the Microsoft Bot Framework (v4), that routes messages between two users on different channels.

Home Page:https://tompaana.github.io/content/chatbots_as_middlemen.html

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Message routing fail if using Skype as Agent

dzeping96 opened this issue · comments

Sorry for my English first..

Skype: Customer Agent
Bot Emulator: User

I found out that when I am using Skype as Agent, it unable to reply message to User, but I can receive message from User. If I am using other Channel other than Skype as Agent, it working fine. And also, I tried to use Bot Emulator as Agent and Skype as User, it is working fine too. I found out the problem is because of this part messageRouterResult = await messageRouterManager.HandleActivityAsync(activity, false);. If we using other Channel as Agent, it will reply OK as result, but if we using Skype as Agent, it will reply NoActionTaken as result. I just download this sample and tested without anything change, hope you can help me to solve this issues. Thanks a lot!

Here is some screenshot:-
Agent on Skype
image

User on Emulator
image

Thank you for reporting this and for the precise issue description! This is an obvious bug that needs to be fixed.

@daltskin Unfortunately that fix broke the functionality for many other channels. I didn't just revert the changes, but added a special case in the code for Skype, but must've missed to test the case where Skype is the agent channel.

@tompaana
No problem. I will wait for your fix. Thank you so much!

Hi @tompaana,

FYI, I found out another problem, which after I publish the sample to Azure App Service plan with Release configuration, the Skype channel won't reply anything at all, it still working fine on any other channel. Is this related with the bug I mentioned in this topic? Thanks!

Hi @daltskin,

Thanks for your assisting, I just found out that Skype require some time to let the Channel online after switching endpoint. Thanks!

Fixed in commit 49c7f08