I am using Twilio to make calls to my clients to remind them of certain dates. Since some people dont pick up these calls, I would like to make my Twilio leave a voice message on their answering machines.
Is that possible? If yes how?
Thanks
From the RestAPI docs about the IfMachine parameter:
If Twilio detects that a machine, not a human, has answered the call, Twilio will make a request to your application URL setting 'AnsweredBy' to 'machine'. The call flow will proceed as normal, and your application can choose to customize the content of the call for a recorded greeting. Twilio will wait until the familiar "BEEP" of an answering machine to begin executing your call flow, so the machine (or voicemail) will capture <Play> or <Say> content. Keep in mind that if a machine answers you'll want to avoid using <Gather> or <Record> because they require user input.
Also note:
Answering machine detection is an experimental feature, and support is limited.
Related
I would like to replace the cryptographic key used in the Microsoft Teams by my own.
I am thinking about the master SRTP key, the web client or the stand alone one on Microsoft Windows.
I guess it is somewhere inside the javascript code (on the web client) ?
Is it possible, or is it protected in some way ? Where is it located ? Is there an api to get/set it ?
What you are asking is not really possible.
I think you are asking to wrong question.
If you want the audio/video streams for a meeting call, there is only one way:
Create a stateful call bot using the Cloud communications API.
The problem is getting the bot into the call to see the streams. Either the bot "starts" the call or the bot has to be invited into the call somehow. The how is up to you.
The other option is to use the Teams policy-based recording to get your bot invited into the call as part of call setup. Becareful of this option as it does come with a overhead. One to one calls will now go through the conference server to allow the third leg to be involved in the call. This I have found to have call startup overhead.
Turning to all you smart people out there for help, tips and trix :)
I want to connect my NodeRed instance to the Sonos API to control my speakers in various ways. During the OAUTH process however, after logging in with my username and password for my account, the auth code being sent back to me through my redirect_uri seems to be too short? In the developers' guide the example auth code looks like this:
f10072fa6-2134-4fe1-93fd-ca5b9cffa738
where in my case, I just receive the first part up until the first dash sign. Eg.:f10072fa6
At first I ran the connection through a NetScaler, then I changed to using a Nginx Reverse Proxy thinking that the Netscaler might have truncated the URL (for some very odd reason), but the result turned out the same..
Ideas anyone?
The Authorization code you received is correct. The Authorization code format was recently changed and the documentation needs to be updated to reflect this. This question was also answered in Authorization code has different structure than example code.
Thanks!
-Mark
You can also use nodered-sonos to control your speakers. No need to setup oauth2 and using the cloud based api, if you can also have super fast local control of your speakers.
I'm using a combination of the following tools for total control of the speakers:
MQTT server of your choice in Docker (I'm using emqx)
Sonos2mqtt, my own app to connect sonos to mqtt in docker
Node red with normal mqtt in/out flows.
My Favorite flows:
Join playbar to group if group starts playing
Pause group is playbar leaves group (it leaves if I turn on the TV, that should stop the music)
Play ring sound (on all speakers) if someone presses the doorbell
Announce (text-to-speech) when the backdoor is opened
I am trying to build an application which works this way: I as a user want to start a call with another user. The way I want the connection be made is by random. So it will connect to one of the many clients out there by random. Also when other clients try to make a call, it should connect to another random client and so on. I want those phone calls be made via application(such as WhatsApp) not as a phone call.
Now, the question is; is Twilio a good approach for this purpose?
If yes can you tell me which of their feature would fit my app the best?
Thanks for any suggestions!
Twilio developer evangelist here.
I can answer that Twilio would be a good approach for you to do this within your own application. I'd recommend using Twilio Video to build this as it allows cross platform communication via audio or video (in your case, you may not need the video, but this will give you the best audio quality).
As an example, my colleague Dominik built a video roulette application. It is the case that the interface was built in JavaScript for the web, but the idea would be the same for a native app. The code for the server side part of the application should give some insight into how to connect random pairings.
It's also possible to integrate Twilio Video with CallKit and Connection Services so that you can make outbound calls to other devices that ring like a real incoming call.
When I get a chat message from someone on FB or Gmail, how do I go about creating a program that detects the message and then executes some commands accordingly, all programmatically?
Solutions in C++, Java or Python would be useful.
A suggestion
Use java & jabber (also called xmpp) protocol
Install the smack library (jabber library for java, really good!)
Read about the jabber protocol, in your case pay special attention to the "<presence>" message. The "<presence>" messages will tell you whenever someone connects/disconect/change status on a jabber server.
Code
You need to use an API for Gmail in a language of your choice. Facebook uses Jabber (XMPP) which, again, has APIs in many languages.
You are unlikely to simply receive a solution here, this site works more on a basis of helping you with some code that you've already written.
Is there any way to test SMS messaging without having a texting plan?
There isn't any way to setup the equivalent of a mock email server for the purposes of testing an SMS service is there? Are there any other ways to accomplish the task? Perhaps setting up something like a GrandCentral account that can receive text messages?
I am looking to test SMS messages to multiple accounts without having to find multiple people with texting plans and coordinating the effort.
Google now has the answer for which I seek. With the roll-out of their new Google Voice (previously GrandCentral) they added the ability to received text messages to the phone number (which currently is free). While technically somewhat of a text plan, one could theoretically sign up for a few accounts and be able to test multiple phone numbers.
http://www.google.com/voice/
Update (Nov 2010):
Perhaps an even better way to do this now is to use either Tropo (tropo.com) or Twilio (twilio.com). Both of them offer low cost SMS messaging and Tropo is free for development. I've been using Tropo and it's very quick and easy to setup and write and code for.
It would depend on the method of how you're sending out the SMS messages. If you're using the email method (<ten digit number>#<cell provider's doman>) you can fake it with a regular email account that can be purged automatically. If you're using an actual SMS publisher your best bet would be to refactor the design so that you can test that your function gets called the expected number of times, but doesn't actually send the messages. Then when you want to test the production-ready code you actually round up a group of people and try it out.
Having a provider that doesn't charge for incoming text messaging (like US Cellular) comes in handy for situations like that.
SMS text can be done under a few different protocols. I've had success with SMPP using the Easy SMPP .NET library and this java-based SMPP server simulator. It saved me a bunch of overpriced service charges.
you can send email to their phone:
18005551212#txt.att.net (IIRC)