Tomi Paananen

This problem is caused by the mismatch of the Bot Builder version - the Nuget package of [Bot Message Router](https://github.com/tompaana/bot-message-routing) uses an older version. I will try to update the...

 Worked for me.

@prats69 In a nutshell: 1. Make Skype the aggregation channel (`MessageRouterManager.RoutingDataManager.AddAggregationChannel()`) 2. Call `MessageRouterManager.ConnectAsync()` for all parties (in Slack) whose messages you want to send to Skype.

@mutanttech @scorpfromhell The call center scenario would indeed be a completely different product/platform. I believe I should close this issue here. This project is merely a sample on how to...

@mutanttech For instance, [LiveEngage](https://www.liveperson.com/tags/liveengage) is one that has routing capabilities out-of-the-box, but can be enhanced with custom code. I have implemented a [simple connector for LivePerson](https://github.com/tompaana/liveperson-bot-adapter) service (Node.js). [Ibex Dashboard](https://github.com/Azure/ibex-dashboard)...

@smartchatco Good catch, thanks! Would timeouts for requests and connections fix the issue? We could have something like `MessageRouterManager.CleanExpiredRequestsAndConnections()` method.

There will be a massive overhaul to this project happening next week - this will be one issue that must be fixed.

Aye. We simply need to record/update the time of the last activity in respect to a connection. With requests the time the request was made should suffice.

Just to clarify: When I originally created the commands it was just so that it would be easy to take the bot "out for a spin". The means for managing...

@garypretty @daltskin You do make an excellent point/points.