Have you heard about Phono, our open source Javascript Phone API project?
Posts Tagged ‘sip’
Meet Phono – Tropo’s Web Phone
Monday, January 23rd, 2012The Conference Pop-In Timer
Thursday, July 21st, 2011
Have you ever wanted to set a timer on a conference call and pop-in at a certain time to either:
Tropo Powered Virtual Call Center in 10 Minutes
Thursday, July 7th, 2011A few months ago, my colleague Dave Hoff and I blogged about a CouchDB based solution to enable a virtual call center powered by Phono – the jQuery extension that lets you build telephone and instant messaging clients inside a web browser.
ASR-as-a-Service
Saturday, May 21st, 2011
Automated Speech Recognition (ASR) as-a-Service can be powered via Tropo and SIP using this simple open source code provided below. This service is perfect for adding speech recognition to your existing Asterisk, FreeSwitch, YATE, or enterprise app from the stone ages.
Extending GoogeVoice with Tropo
Friday, May 13th, 2011
We are always excited to see developers using Tropo to extend GoogleVoice functionality and features by adding things like SIP and Call Forwarding and Call-In enhancements. Terry Swanson (@FunnyBoy243) is one of these cool developers who wrote 2 of these extensions and opensourced them for others to share and contribute: (more…)
How to Build a VoIP-Based Baby Monitor
Thursday, February 17th, 2011
Asterisk & Tropo and a Single Adhearsion Dialplan
Friday, October 8th, 2010
A key goal of Tropo AGItate is to allow you to use Tropo seamlessly with an existing Asterisk server. With AGItate you may add any Tropo feature to your existing Asterisk server without installing additional Asterisk modules and using the AGI protocol you already know. These features include: (more…)
Dial Multiple Phone and SIP Numbers & First to Answer Wins
Wednesday, May 19th, 2010
How-To: Distinguish PSTN, Skype, iNum, and SIP in your Tropo applications
Tuesday, February 23rd, 2010Here at the secret layers of Tropo Support we often see similar questions raised by our developer base. We pay attention to these trends, since they often indicate that something may be lacking in our documentation. If we do find something is lacking we of course want to address by expanding on concepts or adding additional examples to help shore up our doc sets and help out our developers.
