On February 14, 2018, Twilio Client 1.1 & 1.2 will reach their end of life and will no longer be supported. At the end of life date you can expect the following:
- Connections made with the deprecated library will be refused.
- Twilio Support will no longer address questions on deprecated libraries.
To find if you are using Twilio Presence or Device Sounds, search your code for:
If you do not use Twilio Presence or Device, then advance to Step 2.
If you do use Twilio Presence or Device Sounds, read on:
If you are using Twilio.Device.sounds, note that this functionality still exists but has been moved onto the AudioHelper object on Twilio.Device.audio. Any references to Twilio.Device.sounds.incoming, Twilio.Device.sounds.outgoing or Twilio.Device.sounds.disconnect should be updated to Twilio.Device.audio.incoming, Twilio.Device.audio.outgoing and Twilio.Device.audio.disconnect, respectively.
There are two approaches you can take to manage presence:
1) Manage agent presence with Task Router.
If you are using Twilio Presence to manage contact center agent presence, we recommend TaskRouter to manage agent state and call distribution.
You can get started with TaskRouter here: https://www.twilio.com/docs/api/taskrouter
1) Manage user presence with Twilio Sync.
If you are using presence to manage 'Buddy lists' we recommend using Twilio Sync, our new state synchronization product that you can use to manage endpoint state (i.e. Presence) across devices.
You can get started with Twilio Sync here: https://www.twilio.com/docs/api/sync
Making calls through Flash results in a poor user experience. Therefore it is not something we recommend. So with better technologies available (WebRTC), we are not supporting Flash going forward.
What browser versions support WebRTC?
For the latest WebRTC browser compatibility see: http://caniuse.com/#search=webrtc
If your browser does support WebRTC, go to Step 3.
If you are currently using a non-WebRTC supported browser you need to make sure your browsers are updated to the latest version or a WebRTC supported version.
Specifically for the case of Internet Explorer please follow Microsoft's recommendation to upgrade to Microsoft Edge.
Include the following script in the
<head> tag of your web page.
Simply include the twilio.js library within the
<head> of your HTML:
You should use HTTPS to serve your page. Starting with Google Chrome 47, HTTP applications will no longer be allowed to call
getUserMedia() and will not be given access to the user's camera and microphone.
Make sure to search your code to find any other instances where the old libraries are used, update them and you are good to go.