Twilio Changelog

In order to enhance security for all of our users, Twilio SendGrid now requires customers on paid plans to use API Key authentication on all API requests and SMTP configurations. Customers must also enable Two-Factor Authentication (2FA) for all users, subusers, and teammates. Visit our documentation for more information on Upgrading to API Keys and Enabling Two-Factor Authentication.

This release of Flex UI and WebChat UI introduces new syntax options for Chat Markdown and overall improvements in stability of this feature including several bug fixes. To learn more about Markdown, visit our Flex docs. Markdown is currently in Beta and can be enabled for your account using a Pre-release feature flag.

For more details on this release, please visit the release notes for Flex UI and WebChat UI.

Emergency Calling is now generally available in the United Kingdom for Programmable Voice SIP Interfaces. Customers are now able to make Emergency Calls from their Twilio United Kingdom local phone numbers that are capable of emergency calling using Programmable Voice SIP Interfaces with the Twilio platform, which will route emergency calls to the appropriate Public Safety Answering Point (PSAP) and pass along the corresponding emergency address.

Learn more here.

Voice Insights Subaccount Dashboard has been updated to allow for filtering based on the edge location or media region where subaccounts' calls took place.

This allows you to compare the performance of subaccounts across regions. For example, you may find that a subaccount that is performing well in Ashburn (us1) is actually an outlier in terms of call behavior for calls in Dublin (ie1).

Edge locations can be included or excluded from the results, and the underlying data can be exported to CSV.

For more information see our docs.

Voice Insights Subaccount Dashboard has been updated to allow for filtering based on the edge location or media region where subaccounts' calls took place.

This allows you to compare the performance of subaccounts across regions. For example, you may find that a subaccount that is performing well in Ashburn (us1) is actually an outlier in terms of call behavior for calls in Dublin (ie1).

Edge locations can be included or excluded from the results, and the underlying data can be exported to CSV.

For more information see our docs.

Voice Insights has been updated to appropriately identify the codec of calls using a dynamic RTP payload ID. Previously, some calls established using a codec with a dynamic RTP payload ID may not have displayed the correct ID in the Call Summary API response and the codec name may have been missing in Console.

If your application has logic built around the RTP payload ID from Call Summary API responses, you should be aware that codes like Opus will now return a broad range of potential payloads. Calls established with non-dynamic RTP payload IDs are not impacted by this change.

Voice Insights has been updated to appropriately identify the codec of calls using a dynamic RTP payload ID. Previously, some calls established using a codec with a dynamic RTP payload ID may not have displayed the correct ID in the Call Summary API response and the codec name may have been missing in Console.

If your application has logic built around the RTP payload ID from Call Summary API responses, you should be aware that codes like Opus will now return a broad range of potential payloads. Calls established with non-dynamic RTP payload IDs are not impacted by this change.

Twilio has completed validation of the integration between Flex and Glance. The following features have been verified and are available for customers of Flex and Glance:

• Co-browse directly from within Twilio Flex
• Data obfuscation (credit card, SSN, etc.)
• 1-click connect for your website visitors
• Out-of-the-box integration with Twilio Web Chat
• One-way agent video

To learn more about Glance’s capabilities and how to enable it for your application, visit our integration documentation.

Today we are releasing two major version increments of our mobile SDKs for Video, iOS 4.0 and Android 6.0. The Chromium WebRTC engine in these SDKs has been upgraded from m67 to m83. In addition to the security and performance improvements, this WebRTC engine supports Simulcast screensharing and private IP concealment via mDNS.

These iOS and Android SDKs have added support for remote participant reconnecting events. Opus DTX is now included and enabled by default. In addition, the Android capturing and rendering programming models have been updated to provide developers with more flexibility and control. The iOS SDK is now built with Xcode 12.0 and delivered as .xcframework, and the application screen sharing capability has been simplified.

With the WebRTC upgrade developers get the latest enhancements to WebRTC and ensure compatibility with recent browser releases. Opus DTX significantly reduces the bandwidth consumed by silent participants. Remote reconnecting events provide developers a way to provide visual cues to users when automatic reconnections are happening.

For a full description of all the changes, see the Android SDK 6.0 changelog and the iOS SDK 4.0 changelog. The migration guides for moving to these new SDK versions are documented here and here.

The Marketing Campaigns Design Editor now supports four new column layouts. In addition to evenly proportioned columns, you can now create layouts with ratios of 1:2, 2:1, 1:3, and 3:1. As with prior layouts, each column contains multiple drop zones where you can add non-column modules such as buttons, text, and images.