TwilioCon 2013 - Communications Without Boundaries

376 views

Published on

Guidance for deploying Twilio applications outside of the US and Canada. This deck covers Global Low Latency, Unicode, E164 formatting, and reducing fraud risk.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
376
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

TwilioCon 2013 - Communications Without Boundaries

  1. 1. #TWILIOCON Communicationswithout Boundaries - PreparingyourApp forGlobal Use ANDREW JORDAN, SALES ENGINEER, @ TWILIO
  2. 2. #TWILIOCON Hi. I’m Andrew Jordan. I’m a Sales Engineer at Twilio. My Twitter handle is @andrewkirk
  3. 3. #TWILIOCON Going Global. Avoiding Common Pitfalls. Four common issues my team encounters & how to avoid them. 1. Optimizing Call Latency 2. Delivering Unicode encoded SMS 3. Formatting Phone Numbers 4. Preventing Telecom Fraud
  4. 4. GLOBAL LOW LATENCY
  5. 5. #TWILIOCON Global Low Latency Oregon Virginia Sao Paulo Dublin Tokyo Singapore
  6. 6. #TWILIOCON Global Low Latency Virginia
  7. 7. #TWILIOCON Global Low Latency Virginia
  8. 8. #TWILIOCON Global Low Latency Dublin
  9. 9. #TWILIOCON Implementing GLL PSTN <Dial> PSTN REST PSTN <Record> <Client> <Conference> 2012 2013
  10. 10. CHARACTER ENCODING
  11. 11. #TWILIOCON Character Encoding: GSM GSM is the standard encoding for SMS. Using GSM, you can send up to 160 characters per message. Basic Character Set. (7 Bits, 128 Characters)
  12. 12. #TWILIOCON Character Encoding: UCS-2 Much larger than GSM. Covers 110,000 characters (each character is 16-bit). Maximum SMS sizes drops to 70 characters.
  13. 13. #TWILIOCON Unicode + Twilio.We’ve got your back. out how to encode your message for delivery. All our client libraries do this by default. Send us a UTF-8 encoded request and we’ll figure
  14. 14. #TWILIOCON Character Encoding: Common Pitfalls MAXIMUM CHARACTERS If all your characters are GSM, you’ll have 160 maximum characters per message - otherwise you only get 70. DATABASE STORAGE Make sure your database connections speak UTF-8. If you’re using MySQL, make sure your columns are stored in utf8mb4 if you want emoji or other 4 byte characters. HTTP PARAMETERS Make sure your language / framework interprets percent escaped HTTP parameters as UTF-8, not Latin-1.
  15. 15. NUMBER FORMATTING
  16. 16. #TWILIOCON Number Formatting: E.164 The E.164 specification is awesome for machines, but not people. We don’t really use it in our day-to-day lives, so it’s difficult for us to understand. Ex. 0844 809 0200 vs. +44 844 809 0200
  17. 17. #TWILIOCON Design your interfaces to help your users
  18. 18. #TWILIOCON
  19. 19. #TWILIOCON
  20. 20. #TWILIOCON
  21. 21. #TWILIOCON Libphonenumber
  22. 22. #TWILIOCON •It’s great for number formatting but also will do the following: •Parse phone numbers •Tell you if they’re valid or even possible •Geocode numbers and tell you their locale in various languages •Bindings for Java, JS, C#, Obj-C, Python, Ruby, and PHP Libphonenumber
  23. 23. #TWILIOCON Oppa Demo Time.
  24. 24. FRAUD
  25. 25. #TWILIOCON Telecom Fraud: Traffic Pumping. 1. BUY NUMBERS Attackers buy telephone numbers (or blocks of them). Typically these have a high per-minute charge. 2. DRIVE TRAFFIC Attackers then drive as much traffic as possible to the numbers. 3. PROFIT Carriers that receive calls are paid by the carrier where the call terminates. Typically, attackers are associated with (or are) carriers.
  26. 26. #TWILIOCON Telecom Fraud: Protecting Yourself You have to be proactive to protect yourself from Telecom Fraud. Make sure you setup sanity checks & limits. Don’t allow unauthenticated users to make an unlimited number of phone calls, and charge users in real time, not after the fact.
  27. 27. #TWILIOCON Telecom Fraud: Twilio’s Anti-Fraud Measures Twilio works hard to prevent fraud before it happens. We use algorithms to detect suspicious behavior and maintain internal blacklists of known bad or risky routes. You can also setup International Permissions let you whitelist places where you do business. Usage triggers allow you to setup alerts.
  28. 28. #TWILIOCON Conclusion. Try these at home! • Use GLL resources to reduce call latency. • Encode your requests in UTF-8. We’ll pick the right the encoding. • Encourage correct Phone Number input & validate with libphonenumber. • Be aware of Telecom Fraud & protect yourself with Twilio’s tools.
  29. 29. QUESTIONS?

×