Twilio Changelog

We have enhanced how Programmable Video client SDKs connect to the Video Signaling servers. All SDKs now perform a back-off and retry if they receive a busy signal from the server. Additional error codes have been added to help developers troubleshoot client connection issues. The time for the JavaScript client SDK to connect has been reduced by over 250 milliseconds for connections originating outside of the us1 Twilio Region.

These changes will reduce the connection failure rate and help developers to manage the end user experience if connection failures do occur. The SDK versions are as follows:

• Twilio Video Javascript 2.5.0
• Twilio Video iOS 3.3.0
• Twilio Video Android 5.7.0

To learn more, visit the SDK specific changelogs for the Javascript SDK, iOS SDK, and Android SDK.

Twilio Conference resource now includes two additional fields that describe the reason why the conference has ended. A Voice Conference can end for several reasons. It can end when all participants have left, when the moderator has left, or it may also end programmatically via an API request. It can sometimes be difficult to determine the reason why the Conference ended. The new fields reason_conference_ended and call_sid_ending_conference on the Conference resource will make it easier to troubleshoot why the conference ended either via API or console.

Click here to learn more about the different reasons a conference can end in our Conference Resource documentation.

Twilio Edge Locations

This release includes support for the expansion of Twilio’s Global Infrastructure via Edge Locations which allows connectivity control into and out of Twilio’s platform. The Voice Client JS SDK uses these Edges to connect to Twilio’s infrastructure via the new parameter Twilio.Device.Options.edge. This new parameter supersedes the now deprecated Twilio.Device.Options.region. See Twilio.Device.Options.edge API documentation for more information.

Example

const device = new Device(token, { edge: 'ashburn' });

Support for Edge Fallback (Beta)

Deployments designed to connect to multiple Twilio Edge locations can take advantage of the new fallback mechanism. To enable the edge fallback, specify an array of edge names via Twilio.Device.Options.edge. When enabled and a connection failure is encountered, the SDK will reattempt the connection to the next Edge location in the array. For more details about how the fallback works, see the Edge fallback documentation.

Example

const device = new Device(token, { edge: ['ashburn-ix', 'san-jose-ix', 'roaming' ] });

For download instructions see this page

To get started with Twilio Voice Client JS SDK, see our quickstart

We have updated all Flex projects that use Automatic Updates to Flex UI 1.19.

This Flex UI release brings the following new features to Flex:

• Support for using Yarn as a package manager: Developers can manage their project dependencies using Yarn package manager. Yarn is now supported in the client libraries Flex UI 1.19 and Flex WebChat UI 2.4. Yarn can be used by updating any plugins to use the latest version of the Flex Plugin Builder. Visit our Yarn documentation for more details.
• Data sorting for Real-time Queues View: Developers have more control over the sorting and customization options for columns they add to the Real-time Queues View. You can learn more about this feature within our documentation.
• Handlebars dependency upgrade: We have upgraded Handlebars to 4.7.3 to fix critical security vulnerabilities exposed in previous versions of Handlebars. This may be a breaking change if you use certain undocumented Handlebars features. You can find more information about this change in the Handlebars changelog.
• Flex UI and WebChat API Reference: API references describe all available public interfaces, methods and properties. Refer to the Flex UI API Reference and Webchat API Reference for more details. This is currently available as a Pilot feature.

For a full changelog, visit client libraries release notes:

Flex UI 1.19

Flex WebChat 2.4

Reminder: You can pin to individual versions of the Flex UI or manage your Automatic Updates within the Flex Admin UI.

Twilio SendGrid now provides two security features that allow you to verify that email event data is being posted by Twilio SendGrid: a Signed Event Webhook and OAuth 2.0. These security features are independent of one another and can be used together.

Twilio SendGrid’s Signed Event Webhook uses the Elliptic Curve Digital Signature Algorithm to sign requests. The signature allows customers to verify that event data is being posted by Twilio SendGrid.

OAuth 2.0 for the Twilio SendGrid Event Webhook allows customers to verify that Twilio SendGrid is properly authorized by them to post to their URLs using the Client Credentials grant type.

To learn more about these new features in Beta, visit our documentation.

The email editors within Marketing Campaigns now support more options for formatting your images. You can crop, flip and rotate your images, add filters, or make adjustments like contrast or opacity all from within your email editing workflow. These editing options are also available within the Design Library under Your Images. Learn more.

Starting August 15, 2020 you will be able to view call and conference logs in Console--and retrieve the resources via GET to the /Calls, /Conferences, and /Participants endpoints--for thirteen months after the resource is created. This represents a significant change as these logs are currently stored indefinitely by Twilio and retrievable via Console and API.

Before this change goes into effect, we will provide a Bulk Export utility in Console. Bulk Export will generate S3 files containing one day of data per file and deliver the download link via webhook, email, or Console. Records older than thirteen months will only be able to be retrieved via Bulk Export.

If you view logs in Console there is no follow up action, but just be aware that calls and conferences will now only display logs for the previous 13 months.

If you perform log extraction via API on a rolling basis, it is important to verify that you are pulling the logs at a frequency that will remain unaffected by this change.

Starting October 14, 2020 you will be able to view message logs in Console--and retrieve the resources via GET to the /Messages endpoint--for thirteen months after the resource is created. This represents a significant change as these logs are currently permanently stored by Twilio and retrievable via Console and API.

Before this change goes into effect we will provide a Bulk Export utility in Console and via API. Bulk Export will generate S3 files containing one day of data per file and deliver the download link via webhook, email, or Console. Records older than thirteen months will only be able to be retrieved via Bulk Export.

If you view logs in Console there is no follow up action, but just be aware that messages will now only display logs for 13 months.

If you perform log extraction via API on a rolling basis, it is important to verify that you are pulling the logs at a frequency that will remain unaffected by this change.

Emergency Caller ID is now available for Programmable Voice SIP Interfaces. Customers are now able to set a single phone number on a SIP Domain as the Caller ID to be used as the Emergency callback number on that domain. This is the phone number that will be used by emergency responders as the callback number in case the call gets disconnected.

Click here to learn more.

Studio and Functions can now be used to develop compliant healthcare applications that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Products and Services.

Learn more about how to build on Twilio for HIPAA compliance.