Attention: Please upgrade to the latest version of twilio.js to avoid breaking changes. Google Chrome will introduce these changes by the end of 2019. Versions prior to 1.7.1 will be impacted. See this advisory for details.
The Twilio Client JS SDK (twilio.js) allows you to make voice calls to and from a web browser and a Twilio TwiML Voice Application. This means you can open inbound and outbound audio connections to Twilio for building softphones, walkie-talkies, conference calls, click-to-talk systems, and more, all from the browser.
Want to get started right away? Jump right in with our Twilio Client Quickstart!
You setup your device and establish a connection to Twilio. Audio from your device's microphone is sent to Twilio, and Twilio plays audio through your device's speakers, like on a normal phone call. But with Twilio Client, your device need not be a phone.
When you initiate a connection using Twilio Client, you're not connecting to another phone directly. Rather, you're connecting to Twilio and instructing Twilio to fetch TwiML from your server to handle the connection. This is analogous to the way Twilio handles incoming calls from a real phone. All the same TwiML verbs and nouns that are available for handling Twilio Voice calls are also available for handling Twilio Client connections. We've also added a new
<Client> noun for dialing to a Client.
Because Twilio Client connections aren't made to a specific phone number, Twilio relies on a TwiML Application within your account to determine how to interact with your server. A TwiML Application is just a convenient way to store a set of URLs, like the
SmsUrl on a phone number, but without locking them to a specific phone number. This makes TwiML Applications perfect for handling connections from Twilio Client (which is actually why we created them in the first place).
So when your device initiates a Twilio Client connection to Twilio, a request is made to the
VoiceUrl property of an Application within your account. You specify the Application you're connecting to with an Access Token. Twilio uses the TwiML response from its request to that Application's
VoiceUrl to direct what happens with the Client connection.
The following table indicates the browsers supported by Twilio Client JS. We support the most recent (N) and the two previous (N-2) versions of these browsers unless otherwise indicated.
|Chrome||Firefox||Safari**||Edge (Legacy*** & Chromium)|
Mobile browsers lack the ability to receive or maintain call connectivity whilst in the background and they do not allow GSM call interruption handling. These lead to poor user experience. To create the best user experience, Twilio recommends understanding these limitations when creating mobile Voice Applications. Twilio also recommends evaluating the iOS and Android SDKs for creating mobile Voice Applications.
* Chrome and Firefox for iOS do not have access to WebRTC APIs, unlike Safari for iOS.
** WebRTC support in Safari started with Safari version 11
*** We recommend migrating to the new Chromium Edge as soon as possible as we will stop supporting Microsoft Edge Legacy (ORTC) on the 1st of September 2020. See this advisory for more details
Twilio Client JS is also supported on the latest Electron version
|Signaling||TLS (Secure Web Socket)|
As of 1.3, Twilio.js has been strictly following SemVer: minor-level updates only contain feature updates and are completely backward compatible with 1.3.0 and newer. Documentation for the current Twilio.js SDK API can be found here.
Support for Twilio.js 1.1 and 1.2 ceased on February 14, 2018.
Please use the Migration Guide to upgrade to the newest version of Twilio.js.