The ability to notify your users via SMS is a powerful feature, and one Tropo makes very simple for our developers! To start you need to create a new application, via the ‘Application Manager’ in your Tropo account:
Archive for March, 2010
How-To: Sending an outbound SMS from Tropo
Monday, March 29th, 2010Simplicity and Power
Sunday, March 28th, 2010“Simple things should be simple, complex things should be possible.” – Alan Kay
One of the things we’ve done with Tropo is balanced simplicity and power. We’ve made it easy to build a basic application, including speech recognition. Our API uses intelligent defaults, ensuring that for most applications you don’t have to configure every detail. We’ve done it for you already. And we’ve taken complex concepts like voice recognition grammars and created simpler languages for writing them.
Teaching Your Application to Really Talk
Friday, March 26th, 2010
Speech Synthesis, otherwise known as Text to Speech (TTS), is a technology that quickly synthesizes a human voice using text as input. Speech synthesis is the default behavior for voice calls on the Tropo platform. The Tropo ‘say‘ verb is the one that provides the TTS capability, by taking a string of text and speaking it back. It is of course possible for this verb to take a URL to a ‘wav’ or ‘mp3′ file for pre-recorded audio to be played as well.
Transcriptions: how to do it and use it!
Friday, March 26th, 2010So you have got a great application, it does all this fancy stuff and now you want to add transcriptions, but how? Well its actually quite simple! Transcriptions in Tropo are sent as a XML body, via POST, to the URL specified in the transcriptionOutURI parameter of the recording method. So below I have taken an example from our blog which showed how to actually do a transcription using the the record method.
Testing a Tropo app with Twitter? Remember that Twitter rejects duplicate tweets…
Friday, March 26th, 2010Just a quick note… if you have decided to try building a Tropo app that interacts with Twitter, perhaps based on our blog posts about how to add Twitter to a Tropo app and how to make a Tropo app react differently per channel, you may want to be aware in your testing that Twitter rejects duplicate tweets sent in a quick time period. This Twitter Support ticket has the info: (more…)
An Example of How to Make a Tropo App Respond Differently to Different Channels (including Twitter)
Thursday, March 25th, 2010Would you like to have your Tropo.com app respond differently depending upon which communications channel is used to connect to the app? Would you like to, for instance, have the app provide more of an introduction to voice callers but not for text channels like IM, SMS or Twitter?
How to Add Twitter Support to a Tropo.com App – Step by Step
Thursday, March 25th, 2010Please note, Twitter & IM support have been deprecated, as per this blogpost. Please direct any questions or concerns to support@tropo.com.
Tropo Adds Twitter and goes International
Thursday, March 25th, 2010Tropo is all about making it easy for you to interact with your customers. What if you could write one application and communicate with your customers via voice, instant messaging (IM), text message (SMS) and even Twitter? And what if they could call that application from anywhere in the world and talk with it in their own language?
Meet Tropo at CloudCamp Vancouver
Wednesday, March 10th, 2010Tropo will be at Cloud Camp Vancouver this Saturday talking cloud communications APIs. We’re sponsoring the event and Adam Kalsey will be there, participating in sessions and showing off Tropo’s services for voice, IM, and SMS in the cloud.
Does your cloud provider offer SIP for full interop?
Tuesday, March 9th, 2010What is SIP and why do I care?
Tropo sits in Voxeo’s live communications cloud; an environment specifically designed for real-time voice, instant messaging and SMS applications. On the voice side, a key feature of the Tropo platform is its extensive support for SIP. The Session Initiation Protocol is a Voice over IP (VoIP) technology enabling two ends of a conversation (or session) to negotiate media formats much like the Accepts/Content-Type header does for HTTP.
