Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Twilio Best Practices
  • Toc
  • feedback
Twilio Best Practices

Twilio Best Practices

By : Rogers
4.5 (4)
close
Twilio Best Practices

Twilio Best Practices

4.5 (4)
By: Rogers

Overview of this book

If you have experience with at least one programming language and are looking to integrate Twilio into your applications, then this book is for you.
Table of Contents (10 chapters)
close
9
Index

Fixing common errors


Some errors in our application will be particularly common and are likely to be relatively simple to fix in most cases. This section has a quick rundown.

Note

You can find Twilio's full reference of error codes and their meanings at http://www.twilio.com/docs/errors/reference.

112** – HTTP errors

If Twilio has difficulties requesting TwiML from your application; for example, because your server is down, one of the error codes starting in 112 will be triggered.

These errors signify that Twilio hasn't even been able to get the TwiML from your server. Most likely, it is down, incorrectly configured, or otherwise messed up. Alternatively, the DNS records on your domain might be incorrect.

To fix this, take a look at the specifics of the error, and ideally, try placing a request yourself to see what happens.

Note

If you're using ngrok to run your Twilio application locally, then when you restart it, you'll get a new and different URL for your applications by default, which will cause...

bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete