Twilio Client JavaScript SDK Changelog

Downloading

(Recommended) The latest version of twilio.js can be found on NPM at https://www.npmjs.com/package/twilio-client

Or you can download it directly from Twilio’s CDN at:

Minified: https://sdk.twilio.com/js/client/v1.14/twilio.min.js
Unminified: https://sdk.twilio.com/js/client/v1.14/twilio.js

We strongly recommend that all customers include twilio.js in their applications via npm before going to production. Using npm ensures that any underlying code updates are verified by your application’s build process before making it into production, while allowing frequent automatic updates to the newest SDK versions.

1.14.0 (Jan 27, 2021)

New Features

Allow Connection specific ICE Servers

Developers can now opt to override rtcConfiguration set within Device.options per specific outgoing and incoming Connections.

To use this feature, a new parameter rtcConfiguration can be passed to Device.connect and Connection.accept. The function signatures are now described as below.

Device.connect(params?: Record<string, string>,
               audioConstraints?: MediaTrackConstraints | boolean,
               rtcConfiguration?: RTCConfiguration);

Connection.accept(audioConstraints?: MediaTrackConstraints | boolean,
                  rtcConfiguration?: RTCConfiguration);

Passing the rtcConfiguration parameter to these functions will override any previously set rtcConfiguration within Device.options but not affect any other members set within Device.options.

1.13.1 (Jan 11, 2021)

Additions

Added support for Tokyo and Sydney interconnect locations. These edges can be used by interconnect customers by specifying { edge: 'sydney-ix' } or { edge: tokyo-ix' } in Device.setup() or new Device() options.

1.13.0 (Nov 11, 2020)

1.13.0-beta2 has been promoted to 1.13.0 GA. Here’s a summary of what’s new in 1.13.0.

New Features

Voice diagnostics using runPreflight API

The SDK now supports a preflight test API which can help determine Voice calling readiness. The API creates a test call and will provide information to help troubleshoot call related issues. Please see the following for more details.

Connection warning data

Connection.on('warning') now provides data associated with the warning. This data can provide more details about the warning such as thresholds and WebRTC samples collected that caused the warning. The example below is a warning for high jitter. Please see Voice Insights SDK Events Reference for a list of possible warnings.

connection.on('warning', (warningName, warningData) => {
  console.log({ warningName, warningData });
});

Example output:

{
  "warningName": "high-jitter",
  "warningData": {
    "name": "jitter",

    /**
     *  Array of jitter values in the past 5 samples that triggered the warning
     */
    "values": [35, 44, 31, 32, 32],

    /**
     * Array of samples collected that triggered the warning.
     * See sample object format here https://www.twilio.com/docs/voice/client/javascript/connection#sample
     */
    "samples": [...],

    /**
     * The threshold configuration.
     * In this example, high-jitter warning will be raised if the value exceeded more than 30
     */
    "threshold": {
      "name": "max",
      "value": 30
    }
  }
}

Also in this release

Added high-packets-lost-fraction network warning. This new warning is raised when the average of the most recent seven seconds of packet-loss samples is greater than 3%. When the average packet-loss over the most recent seven seconds is less than or equal to 1%, then the warning is cleared.
The behavior for raising the constant-audio-level warning has been updated. Now, the most recent ten seconds of volume values are recorded and then analyzed. If the standard deviation of these samples is less than 1% of the maximum audio value, then the warning is raised. When the standard deviation is greater than 1% and the warning has already been raised, then the warning is cleared.
We now log an outgoing event to Insights when making an outbound call. This event also contains information whether the call is a preflight or not.
Added a boolean field to the signaling payload for calls initiated by Device.runPreflight for debugging purposes.

Device Events	Affected Connection Events
device.on('connect')	connection.on('accept')
device.on('error')	connection.on('error')
device.on('cancel')	connection.on('cancel')
device.on('disconnect')	connection.on('disconnect')