I'm looking for a way to create a bot initiated group conversations with MS botframework on Skype channel (or Skype for Business although there is no channel for it :).
From researching so far in BotBuilder C# space far looks like the only channel officially supporting it is "Email channel".
The question is, does any one knows an alternative way?
Related
I understand that this question has been asked before, but those topics are dated 4 years ago, so I wonder if anything changed.
TL;DR:
I understand the concern that sending messages via phone number would make users vulnerable for spam. But there is something I discovered that makes me reconsider this. If I /start a chat with Telegram Bot, chat_id is generated. Interesting thing is, this chat_id is the same for my conversations in other chats. I might be wrong here, but it seems that spam issue should be handled in a different way. Thus, I wonder if there is a possibility to send messages straight to user's phone number.
Thank you for your time.
No, you can't. Each user's ID is unique and not changing during conversation/chats. But you can't send the message to user if he did not accepted it by starting your bot as i know. Also, phone number can be shared only from user side. You can't find users by phone number, at least, official api doesn't provide such methods.
I'm working with Microsoft's Bot Development Framework. They've released a calling API to handle taking calls, but what I'd really like to do is call a user on Skype (i.e. initiate the call). I don't believe they can do this currently, so if not are there plans to add this?
Skype doesn't offer this functionality at this time. I don't have any information about plans to implement bot calling the user with voice, but I will pass on the request to the Skype bot team.
My employer has recently switched to using Skype for Business. Aside from a somewhat painful user experience on the Mac, its not so bad. However, several of us have noticed that certain employees can join meetings without being listed amongst the attendees. I don't mean anonymously- I mean the attendee count doesn't even register the additional bodies.
Is this some kind of audit feature that allows certain users the ability to secretly join a meeting? Or perhaps its just a feature that allows someone to slip in late without disturbing the flow? Or maybe just a bug?
I don't mean to sound paranoid but this activity only seems to occur for division heads, which is why several of us have taken notice.
The short answer is yes.
But "normal" people can't do it directly, as the only type of participant that can be hidden is a UCMA trusted application, using a trusted application endpoint.
For "normal" Skype clients to connect hidden, is to connect to a UCMA trusted application endpoint that does a B2BUA call into the conference.
You can see an example of this in Microsoft's UCMA reference Call Center application.
I saw on internet that there is some programs that can use Telegram CLI.
I want to choose between them
for Telegram bot API there is much more documents explaining its functionality, but for CLI there isn't much that explains its features
it seems the only way to know about is to experiment with it.
unfortunately i don't have a linux distro installed on my pc so experimenting isn't an option right know.
so I thought to ask from people who already used it
I know about Telegram bot api, its powers and its limitations
here is my questions:
what can I do using Telegram CLI that I can't do with with bot api, and vice versa?
Telegram bot API:
do not require to register new Telegram account, so you don't need to have another phone number;
bot cannot write to user first, only after user sends a first message to bot;
already has the commands interface (/command);
can do stuff by simple HTTP POST (by sending request via cURL, for example). So you can hook to this tons of stuff (notifications about new articles at the website or so);
you can rather easily create lots of them;
you can write you own implementation in almost any programming language;
you have a list of bots you have created (thanks to #BotFather). If you have lost somehow control of your bot - just revoke the token via #BotFather and it's yours again;
pretty simple to use.
Telegram client application (in this case - CLI):
requires new Telegram account registration with phone number;
acts like any other actual Telegram user (can write to other users first, without invitation). Well, that's a good thing;
not really good cross-platform abilities for now (some lack of CLI-realisations);
not really easy to install and use;
you have to implement the commands handling part;
if you have lost your phone number - pretty much you lose this account, because it's not like you would make some precautions for CLI client account. So you will have to register a new one and repeat the setting procedure for client.
In conclusion, bots actually got rid of CLI clients, in my opinion. I had CLI account right to the moment the bots appeared. After that I deleted it and created a bot. And not just one :)
So, bots are for the "robot" stuff, and real accounts are for the real people.
The Telegram CLI library interacts directly with their MTproto protocol, which means it's like their desktop/mobile app...but for the console. You can send messages from one phone number to another. This means that when authenticating with the CLI application, you use your real number as if you were logging into the mobile application.
I wouldn't suggest using it for bot behavior as you have to write an application that wraps the Telegram CLI and parses the log file as it is displayed...since it doesn't implement all the MTproto methods and the outputs for the log file are custom...it can be quite annoying and different than what you would expect.
With Telegram CLI you can send a number to another Telegram user without having them initiate the conversation first (since it functions just like a normal Telegram client) where the Bot API requires the user to add the Bot and start interaction before the Bot knows you are there.
previous answers are almost correct. Two different interfaces for different purposes:
Telegram Bot API allows to develop a Telegram Bot.
Telegram CLI (as this one, as an implementation example: https://github.com/vysheng/tg) are telegram client implementations, running from command line, based on MTproto protocol, as Chris Brand said.
As a bot developer, I'm interested to have a TG CLI interface (2) to automatize dialogs tests, with bash scripts, with a bot made with (1).
My team uses skype group chat, and I would love to have a tool that could post notifications to our group chat.
I would like to avoid relying on an RSS feed, but it may come down to that. But even that it seems hard to find -- there seems to have been a tool called Anothr that perhaps went out of existence.
I would also prefer to not have a 3rd party (outside of Skype) that receives the messages -- e.g. I don't want a bot that is hosted by a third party on a server somewhere, with their bot sitting in our group chat.
You did not state what kind of build server you use.
If you are happy with Jenkins, there is a plugin for that:
https://wiki.jenkins-ci.org/display/JENKINS/Skype+Plugin
I did not check whether it can send groupchat messages, though.