Twilio

From Wildsong
Revision as of 19:54, 2 November 2015 by Brian Wilson (talk | contribs) (Created page with "== Take aways from Signal Conference == === Move stuff into Asterisk === Lots of stuff in Twilio space could be implemented in Asterisk space ie TWIML could be used to desig...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Take aways from Signal Conference

Move stuff into Asterisk

Lots of stuff in Twilio space could be implemented in Asterisk space

ie TWIML could be used to design IVR / autoattendant systems in Asterisk. Doing this could make it easy to implement a failover, primary would be Asterisk but if * is down then the same code would fire up and run in Twilio.

What Twilio is doing

What Twilio is doing is building a big company by (1) doing only the back end, no applications. They provide only APIs and you write your own applications. (2) Using cloud. Everything they do lives in Amazon. Based on that there must be some backend to connect to carriers that does not require anything but IP. :-) That is, they don't have big server rooms full of HT503's

They have that big giant corporation mentality. But they do make their services available to little fleas like us. I can buy one phone line for $1 a month.

What does it take to build a basic PBX in the cloud?

  1. Set up SIP phone and provision it
  2. Give the SIP phone an extension
  3. Allow VOIP extensions to call each other
  4. Set up a receptionist line
  5. Create an after hours autoattendant
  6. Voicemail
  7. Tracking usage of extensions at receptionist station

Now that I have a PBX, how can I extend it?

  1. SMS support
  2. WebRTC
  3. Text to Speech
  4. Speech to Text
  5. Presence detection
  6. Softphones
  7. Mobile softphones

What can Asterisk do that Twilio CANT and vice versa