Gone are the days of having your customer enter their phone number into your website for a click-to-call application! Using Voxeo’s PhonoSDK, you can connect the caller (web customer) to any SIP-based application for FREE! Using Teleku or Tropo, you can transfer your SIP call from Phono to any PSTN “real” phone number in the world or simply interact with the web user with speech recognition and text-to-speech and even record and transcribe browser conversations or interact with multiple users via a browser-based conference call!
Since Teleku also supports hosting Twilio applications running TwiML (and SIP), you could easily run your Twilio application on Teleku’s Ninja platform for FREE and simply have Phono call your Teleku/Twilio extension at sip:firstname.lastname@example.org.
Give it a try! We would love to hear your feedback on placing calls to your Teleku, Twilio, and Tropo applications!
Teleku and Tropo go together like chocolate and peanut butter. Since Teleku was already running on Tropo’s network, there was no integration work required to bring these services together. We are working on Product roadmaps and have identified a number of features that make sense to add to both platforms. In the mean time, customers are free to move across platforms at the same rates as their application needs dictate.
In the process of evaluating the differences between Teleku and Tropo, we have gained a greater appreciation for the Tropo platform and the shear depth and architecture of Voxeo’s private voice cloud. If you are serious about keeping pace with viral growth of your telephony application or handling call volumes that scale from 1 simultaneous call to literally a 100,000 simultaneous calls, Tropo is the platform for you!
Teleku’s Ninja application running on Amazon EC2 was a good experiment in cloud communications running on public cloud computing. For the most part this environment is very stable but we have learned that Amazon’s cloud is optimized for Web traffic not Voice traffic. There is no QoS (Quality of Service) in place for prioritizing voice packets over web packets which causes VoIP jitter and latency at times. Perhaps this will get better in the future. In the mean time, Ninja will continue to remain free with SIP support only.
Tropo’ private Voice cloud is designed to optimize Voice over Web traffic and yield the prioritization of Voice packets over Web packets. The network is also built from the ground up to convert everything to SIP the moment it hits the network. Both Teleku and Tropo support SIP natively which also allows for even lower latency and reduced routing costs of phone calls around the world - even HD voice!
While Teleku and Tropo do not currently offer SLAs, these platforms are running on the same network as half of the Fortune 500 companies’ voice applications which are supported by 100% Voice and SMS uptime SLAs by Voxeo (our parent company). This means that everything other than the Teleku and Tropo Web and Media servers are being powered by the same technology! At $03 per minute and $.02 per SMS message, these platforms are truly great values.
The teams have also adjusted to working well with each other and even started a new project together called THE NEXT BIG THING! We can’t wait to share more information about this game-changing new project in the upcoming months and how it will allow Teleku and Tropo to leap-frog the market. Stay tuned for more details!!!
Voxeo Gobbles Up Teleku is the lead story on GigaOm at the moment. This is awesome news for existing Teleku customers because your existing Teleku apps now have the full scaling potential of half of the Fortune 100 companies that already run in Voxeo’s incredible network! You can find out more about today’s acquisition on Tropo’s website.
Chris Matthieu, Teleku’s Founder, is now the Director of Business Development for both the Teleku and Tropo cloud communication platforms. We now have access to over 150 Voxeo Engineers in three countries and some of the most amazing next generation technologies in Voxeo Labs!
This code was heavily inspired by a blog post located at http://www.tutorialspoint.com/ruby-on-rails/rails-file-uploading.htm and you must comment out protect_from_forgery line in application controller to avoid the token error caused by the data coming from another application (Teleku). You could probably just override/disable forgery protection on this one controller or action.
I am using tunnlr to test it with extension 388 (http://teleku.com/extensions/388) over SIP using my Blink SIP client for the Mac. The data gets stored in the public/data directory but you could redirect the files to either your own database or S3.
A Twilio customer came to us today with the following GNARLY nested Twilio Markup script. They ran it on our platform without any changes and were pleasantly surprised that their phone application could run on Teleku without being ported and that they also were able to interact with their TwiML application using speech recognition and even better sounding text-to-speech!
Here’s their TwiML example (with the names changed to protect the innocent):
Twilio, one of our competitors in the cloud communications space (covered by Jason Kincaid of TechCrunch), released an open-source, web-based PBX application called OpenVBX. The name is a little misleading as only the OpenVBX PHP web application that let’s you administer the PBX is open-sourced while the platform is designed to only run exclusively on Twilio’s services at $.03-$.05 per minute - UNTIL NOW!
By releasing OpenVBX, Twilio helped Teleku more than they currently realize. We have always supported the Twilio Markup Language (TwiML). We just needed a good test application that had extensive coverage of the Twilio API to finish our ability to test Teleku’s support for Twilio’s API and TwiML (in addition to our own easier API and PhoneML).
Teleku’s implementation of the Twilio API and TwiML has been enhanced and now more than 90% of OpenVBX’s features running on Teleku with no changes to the OpenVBX code base except for changing the URL of the API from https://api.twilio.com to http://api.teleku.com. This means that OpenVBX is now - well “open”. Customers are no longer “locked” into Twilio hosting to use OpenVBX. Since Teleku ultimately translates PhoneML and TwilML to VoiceXML, OpenVBX now runs on any carrier’s platform such as Voxeo!
So what are the differences? Teleku does not yet support transcriptions but we are working with PhoneTag and MyCaption to implement this feature soon. We also do not store recorded voice files on Amazon S3 rather we form post or email them to the developer to manage (this is a business decision that may change in the near future). Our phone number provisioning API currently does not support toll free numbers but it does support local numbers (just not by area code yet).
On the upside, Teleku runs on any telecom carrier’s network which means that you could deploy your OpenVBX application to Voxeo, XO Communications, I6NET/Asterisk, Plum, Syntellect, TellMe, Genesys, etc. Teleku supports speech recognition on all menu prompts and has many text-to-speech engine options that sound much better than Twilio’s robot voice. We also have a free SIP-based platform (Ninja), that allows free calls from any SIP client (in and out of the platform) as well as cool hacks like routing your GoogleVoice number through Gizmo (SIP Gateway) to Ninja (OpenVBX) for free calling. Our SIP support also allows you to use SIP Gateways such as VoxBone and VoIPJet (or any SIP Gateway provider internationally) to get a phone number (DID) that links to a SIP address for as little as $.01 per minute to run calls through Teleku/OpenVBX. Also, by linking your Voxeo developer account to your instance of OpenVBX running on Teleku, you get your own DID, SIP, Skype, and iNum numbers that ring right into your instance of OpenVBX. Again it’s as easy as doing a search and replace (3 hits) on https://api.twilio.com with http://api.teleku.com before installing the app or by updating the PHP source and twilio_endpoint database record in the settings table of OpenVBX.
We have registered http://OpenVBX.biz and directed our VoiceXML to Voxeo and we are able to place outbound calls, send outbound SMS messages, provision phone numbers (local), add mobile devices, create call flow scripts, link call flow scripts to numbers, and receive inbound calls and SMS messages that execute the associated call flow scrips which are running in TwiML. Other features such as creating tenants and sales/support workflows work as well.
For the good of the telecom industry, we hope that Twilio will allow Teleku to contribute code to this exciting new open source initiative, OpenVBX! We believe that for an application to be considered truly “open”, the customer should not be “locked” into a vendor’s platform. Teleku solves this problem by allowing developers to run ALL of their Twilio applications on any carrier they desire as well as by using lower-cost SIP alternatives to deliver game changing telecom solutions.
Check out this video demo of OpenVBX running on Teleku!