Tropo is part of CiscoLearn More

S3 Recordings, ring detection, and a heap of improvements

Posted on March 7, 2016 by Adam Kalsey

Today’s Tropo release has bunch of improvements and bug fixes in it. You can read the full change log as usual, but I’m going to highlight two new features here: recording upload to Amazon S3, and a new event that lets your code know when an outgoing call is ringing. All these changes are available now in the developer environment so you can start using them in your applications now. They will be promoted to the production environment in a few weeks.

Tropo’s recording feature currently can upload a recording to your server by FTP, SFTP, HTTP post, or HTTP Put. A popular request is the ability to push a recording to an Amazon S3 bucket, and we’ve in the past published sample code and blog posts showing how to do that by using HTTP Post to your own server and then pushing to S3. Today’s release adds the ability for Tropo to push to your own S3 bucket natively – no middle layer required.

In keeping with Tropo’s API design philosophy, we layered this new S3 support into our existing API so instead of giving you any new API calls to learn, we just taught the ones you already know a new trick. To use S3 as your recording storage, you’ll first need to set up an S3 bucket with Amazon. Then, in your Tropo application, set the record method to “s3” and the recording URL to the S3 bucket plus file name you want to use, for example https://s3.amazonaws.com/your_bucket_name/myrecordng.mp3. Use your AWS Access Key ID as the recording username and the AWS Secret as the recording password.

Here’s a Javascript example showing startCallRecording uploading to an S3 bucket. The recording file name is the caller ID.

startCallRecording("https://s3.amazonaws.com/my_bucket_name/" + currentCall.callerID + ".wav", {
recordUser: "AKUIEKEJOEMG8UZKX3HQ",
recordPassword: "apPetuyEqfmc3mIygtjOU812GClNG+Oh0lJbe1meB",
method: "s3"
});
say("This is a recording test!");
say("Thanks for calling");
stopCallRecording();

Tropo’s new onRinging event is available in the call() or transfer() functions. It is triggered when the number you’re calling begins ringing. This allows applications that want to track state changes on a call to track the ring. For example, if you’re building a web interface that lets a person make calls to a list of people, you might show the status of every call on the interface: ringing, answered, no answer, hung up.

Using onRinging is the same as using other Tropo events such as onAnswer or onBusy: define a function and that function will run when a call enters a ringing state. The onRinging event is only available in Tropo’s Scripting API.

Other changes in this release include an updated Ruby version, some SIP interoperability improvements, and lots of small usability improvements on both the web site and in how Tropo behaves in error conditions. Read the full change log if you’re interested in the details.

Announcing Tropo in Europe

Posted on February 12, 2016 by Team Tropo

EU flagWe are off to a rocking great year fueled by you, our growing customer base, as well as the synergies from the broader Cisco ecosystem. On top of us lowering our domestic prices on the first day of 2016 we have more exciting news for you:

Tropo will be coming to Europe in spring 2016 as http://www.tropo.eu

Tropo.eu is our response to customer requests for tighter alignment to European privacy and data security laws. With this upcoming launch, we’ll be enabling a protected instance of Tropo in the UK serving all of our European customers.

We have leveraged our deep experience putting Tropo in private, highly secure data centers around the world and will release our European instance with your data privacy in mind. Your confidential data will remain within the borders of the EU and we will be able to provide you with the highest call quality and lowest latency for EU to EU calls out of our Tropo.eu portal.

Initially, when we launch this spring, we will have some additional processes in place: For example to get numbers in Germany you have to provide your proof of address.

We will provide more details over the next few months at http://www.tropo.eu. If you cannot find what you are looking for or need more information, please contact support@tropo.eu.

We hope you are as excited as we are that we are finally able to deliver a product that will resonate with companies of all sizes in a very important market to us.

Come see us in action!

For those of you at Cisco Live! Berlin next week, we invite you to stop by the Tropo booth in the DevNet Zone to learn more about this announcement and receive a demo of our voice and SMS offerings. There will also be a series of Tropo API introductory sessions and learning labs available throughout the week. View the session times and locations here.

Be sure to follow us on Twitter @Tropo for the latest information, tips and events that we will be at!

Happy New Year From Tropo: New US Domestic Pricing!

Posted on January 1, 2016 by JP Shipherd

It’s been a busy six months since Tropo joined Cisco and while we’ve been quiet for much of this time there has been a LOT going on.   First and foremost, we should let you know that Cisco is committed to maintaining and growing Tropo. To that end we are announcing new lower pricing for US Domestic calls, messages and phone numbers. US Phone numbers now cost only $1 per month (2$ for toll free) and messages and calls start as low as 3/4 of a cent per message or per minute! As part of Cisco we can apply better economies of scale and we want to pass those savings on to our users. These changes went into effect starting today, January 1, 2016, and will automatically be applied to all customers except for those that have Enterprise contracts with us. Look for changes to our international pricing later in the year!

In addition to growing and expanding Tropo as it exists today, the Tropo team is also helping Cisco grow a more developer friendly culture. This is in Tropo’s DNA and the team at Cisco has asked us to take our experience creating APIs that developer’s love and apply it to the broader Cisco Collaboration offering. You can see the first examples of this at the new Developer portal for Spark. The great news for Tropo developers about this work is that we will be working to make these new collaboration APIs available to Tropo to developers so that they can embed additional real time communication capabilities like video and IP messaging in addition to the voice and SMS capabilities that we have today.